Revenue model
16 agent skills to validate software ideas before you build — Mom Test interviews, JTBD, market research, pretotype tests, unit economics, and go/no-go scorecards. For Cursor, Claude Code & skills.sh.
npx -y skills add eltntawy/idea-discovery-playbook --skill revenue-modelAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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.
What its author says it does
Copied from the file, not written here
Designs pricing hypotheses, revenue scenarios, and unit-economics checks including CAC, ARPU, churn, LTV, and payback for software ideas. Use when the user asks about pricing, willingness to pay, unit economics, ARR, MRR, or revenue projections.
SKILL.md
1.8 KB, as published. Nobody here has run it
Revenue Model
Checklist
- Anchor pricing to competitor bands
- State the target segment and pricing logic
- Build base, upside, and downside scenarios
- Estimate CAC by channel
- Compute ARPU, churn, LTV, payback, and LTV:CAC
- Record whether economics support strong go, conditional go, or kill
Scenario table
| Scenario | Price | Adoption | CAC | Churn | LTV | LTV:CAC | Notes |
|---|---|---|---|---|---|---|---|
| Base | |||||||
| Upside | |||||||
| Downside |
Default monthly churn to 5% unless evidence says otherwise.
LTV:CAC decision bands (canonical)
| LTV:CAC (base case) | Interpretation |
|---|---|
| < 2:1 | Kill cue — economics do not support the stated goal |
| 2:1 to < 3:1 | Conditional go only — name the gap (price, CAC, churn, segment) |
| ≥ 3:1 | Meets bar for Strong go on unit economics (with scorecard and other stages) |
Willingness to pay
Prefer deposits, LOIs, pre-orders, and paid pilots over compliments or email-only signups.
Output
Save to discovery/<topic-slug>/research/YYYY-MM-DD-<topic-slug>-revenue.md.
Gives 0 of the 12 instructions most pricing monetisation skills give
Counted across 366 of the 366 authors here whose files we hold, read 2026-08-06
- verify webhook signaturesin 23 of 366, across 19 files
- differentiate tiers using features, limits, or supportin 15 of 366, across 4 files
- read product marketing context before asking questionsin 14 of 366, across 6 files
- base price on perceived value, not costin 14 of 366, across 3 files
- use Van Westendorp to find acceptable price rangein 14 of 366, across 3 files
- use MaxDiff to identify highly valued featuresin 14 of 366, across 3 files
- choose a value metric that scales with customer valuein 14 of 366, across 9 files
- handle webhook events idempotentlyin 12 of 366, across 6 files
- understand the upgrade context before recommendingin 11 of 366, across 4 files
- align the pricing metric with delivered valuein 10 of 366, across 4 files
- install stripe packagein 10 of 366, across 5 files
- calculate unit economics metricsin 10 of 366, across 5 files
Said here and by no other author read
- anchor pricing to competitor bands
- estimate CAC by channel
- compute ARPU, churn, LTV, payback, and LTV:CAC
- record whether economics support strong go, conditional go, or kill
- default monthly churn to 5% unless evidence says otherwise
- prefer deposits, LOIs, pre-orders, and paid pilots over compliments
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.