agentsclimarketplace

Business model

Skill vmobifystudio/app-dev-team/skills/business-model

Use when deciding or revisiting how the product makes money — pricing, tiers, trial shape, ad load, unit economics — by ceo when setting the model, by cpo when a scope decision turns on revenue, and by product-researcher when investigating willingness to pay. A pricing analysis is a document, not a standing role.From its SKILL.md

Install
npx -y skills add vmobifystudio/app-dev-team --skill business-model

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, as published. Nobody here has run it

Business model

The output of this skill is a decision with its arithmetic written down, not a strategy essay. The arithmetic is what makes it possible to be wrong on purpose and notice later.

Pick the model before the price

ModelFits whenThe thing that kills it
Paid up frontthe value is obvious before useno trial means no conversion signal at all
Freemium → subscriptionvalue compounds with usethe free tier is either useless or sufficient
Consumable / creditsusage is bursty and costs you per unitusers cannot predict their spend and stop
Adsreach is large and session length is realad load destroys the experience that earned the reach
Ads + removal IAPboth of the abovethe paid tier competes with your own ad revenue

The studio's defaults and hard rules live in knowledge/monetization.md (house-conventions) — NO-AD zones, consent, frequency caps. Those are not negotiable by a pricing decision.

The arithmetic, written out

State each number, and say where it came from — measured, comparable, or assumed:

Price point               <value> in <currency/tier>
Cost to serve one user    <infra + per-unit + store commission>
Conversion assumption     <%>  (source: measured | comparable | ASSUMED)
Retention assumption      <month-1 / month-12>  (source: ...)
Revenue per install       price × conversion × expected periods
Break-even installs       fixed cost ÷ revenue per install

Every ASSUMED is a hypothesis with a falsifying test, handed to data-analyst to instrument (growth-analysis). An assumption that is never instrumented is a number that will be quoted for years as if it were measured — the most expensive artifact this skill can produce.

The trial and the paywall

Decide and record: what is free forever, what the trial includes, its length, whether a card is required, what happens at expiry to data created during the trial (it must not disappear), and where the paywall appears in docs/12-flows.md. A paywall not in the flow doc is a paywall QA never tests.

Output

A ## Business model section in docs/00-vision.md with the model, the arithmetic, and every assumption labelled — plus the instrumentation request in docs/52-analytics.md for each one.

Keep looking

Skills are one crate of 610,220. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.