agentleFS
NikitaDmitrieffNikitaDmitrieff/auto-co-meta/.claude/skills/startup-business-models/SKILL.md

startup-business-models

Skill43 starsChanged 9 months agoMITView on GitHub

Use when choosing or evaluating a startup revenue model, pricing/value metric, packaging/tier design, or calculating unit economics (LTV, CAC, payback, gross margin, NRR), including usage-based/credit/AI pricing and variable compute/COGS constraints.

4 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask for the smallest set of inputs that makes the decision meaningful:

    line 12
  2. Distinctive:

    If numbers are missing, proceed with ranges + explicit assumptions and highlight what to measure next.

    line 20
  3. Very specific:

    Use references/unit-economics-calculator.md for formulas, benchmarks, and common pitfalls.

    line 28
  4. Distinctive:

    Prefer cohort/segment views over blended averages.

    line 29
  5. Very specific:

    Use references/pricing-research-guide.md for WTP methods and pricing interview scripts.

    line 36
  6. Very specific:

    Use assets/pricing-tier-design.md to draft tiers, limits, upgrade triggers, and enforcement rules.

    line 37
  7. Distinctive:

    Use this when you are changing pricing, packaging, value metric, limits, discounts, or billing cadence.

    line 59
  8. Very specific:

    Use references/saas-metrics-playbook.md for definitions and templates (MRR/ARR, churn, NRR, Quick Ratio, Magic Number, burn multiple, stage …

    line 87
  9. Distinctive:

    Use discount guardrails and renewal logic (avoid ad-hoc deals).

    line 119
  10. Distinctive:

    Use only when explicitly requested and policy-compliant.

    line 137

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Startup Business Models

Systematic workflow for choosing revenue models, pricing, and unit economics.

Quick Start (Inputs)

Ask for the smallest set of inputs that makes the decision meaningful:

  • Business type: SaaS, usage-based/API, marketplace, services, hardware + service
  • ICP/segment(s): SMB / mid-market / enterprise (and ACV/ARPA bands)
  • Current pricing and packaging: value metric, tiers, limits, discount policy, billing cadence
  • Unit economics drivers: fully-loaded CAC, gross margin/COGS (include LLM/infra/third-party), churn/retention, expansion (NRR)
  • Constraints: sales motion (PLG vs sales-led), implementation constraints (billing metering, proration), gross margin floor, payback target

If numbers are missing, proceed with ranges + explicit assumptions and highlight what to measure next.

Workflow

  1. Classify the model
  • Subscription, usage-based, freemium, marketplace take-rate, transaction fee, ads, outcome-based, credit-based, hybrid.
  1. Build a segment-level unit economics snapshot
  • Use references/unit-economics-calculator.md for formulas, benchmarks, and common pitfalls.
  • Prefer cohort/segment views over blended averages.
  1. Evaluate model fit and risks
  • Align price metric with value delivered and cost incurred (especially usage + AI compute).
  • Identify failure modes: margin compression, adverse selection, channel conflict, support cost explosions, metering/overage friction.
  1. Propose pricing + packaging changes
  • Use references/pricing-research-guide.md for WTP methods and pricing interview scripts.
  • Use assets/pricing-tier-design.md to draft tiers, limits, upgrade triggers, and enforcement rules.
  1. Define measurement and roll-out
  • Define success metric + guardrails, evaluation design, and explicit lag windows (conversion now, retention later).
  1. Deliver a decision-ready output
  • Recommendation, rationale, assumptions, scenarios (base/best/worst), and next experiments.

2026 Heuristics (Context-Dependent)

  • Prioritize payback and gross margin over a single ratio; LTV:CAC is easiest to game.
  • Typical SaaS targets (directional, by segment/stage): LTV:CAC 3-5x, payback 6-12 months (PLG) or 12-18 months (sales-led early), NRR >100% (mid-market/enterprise) and gross margin >70% (software-only).
  • For usage-based / AI products: model contribution margin per unit (token/job/workflow) and set pricing guardrails (rate limits, minimums, commit tiers, credit expiries).

Related Skills (Routing)

  • startup-idea-validation
  • startup-competitive-analysis
  • startup-fundraising
  • startup-go-to-market

Pricing Change Measurement & Experiment Design

Use this when you are changing pricing, packaging, value metric, limits, discounts, or billing cadence.

1) Define success and guardrails (before launch)

TypeExamples
Primary success metricNet revenue retention (NRR), ARPA/ARPU, gross margin %, payback period, upgrade rate, expansion MRR
GuardrailsNew logo conversion, activation rate, refund rate, support load, churn (logo + revenue), sales cycle length

2) Pick an evaluation design

DesignBest whenHow to read results
A/B (randomized)Self-serve / PLG flowsCompare conversion, ARPA, refunds, and downstream retention by assignment
Holdout/control cohortPricing is hard to randomizeCompare treated vs. holdout cohorts matched on segment, channel, and start month
Step rollout (time-based)Enterprise contracts, invoicing cyclesCompare pre/post with a parallel cohort (not exposed yet) to reduce seasonality bias
Geo/account rolloutRegions/segments are separableCompare regions/segments; watch for channel mix shifts

3) Use explicit lag windows (avoid premature conclusions)

  • Short lag (days to 2 weeks): checkout conversion, activation, sales cycle friction, refund/support spikes.
  • Medium lag (4 to 8 weeks): upgrades, expansion MRR, usage growth, discounting behavior, proration effects.
  • Long lag (90 to 180+ days, B2B): churn, net revenue retention, renewal outcomes, contraction risk.

4) Report an "all-in" view (not just conversion)

  • Revenue quality: net revenue after refunds, discounts, and credits; gross margin impact (including variable compute/COGS).
  • Segments: break down by plan, seat band, channel, ACV/ARR band, and customer age (new vs. renewal).
  • Decision rule: write a go/no-go threshold (example: "NRR +2pts with no >0.5pt drop in activation and no >10% increase in support load").

SaaS Metrics (Read When Needed)

Use references/saas-metrics-playbook.md for definitions and templates (MRR/ARR, churn, NRR, Quick Ratio, Magic Number, burn multiple, stage focus).

Resources

ResourcePurpose
unit-economics-calculator.mdLTV, CAC, payback calculations
pricing-research-guide.mdWTP research methodology
saas-metrics-playbook.mdSaaS-specific metrics deep dive

Templates

TemplatePurpose
business-model-canvas.mdFull model design
unit-economics-worksheet.mdCalculate and track metrics
pricing-tier-design.mdPricing & packaging worksheet

Data

FilePurpose
sources.jsonBusiness model resources

Do / Avoid (Jan 2026)

Do

  • Define your value metric (seat/usage/outcome) and validate willingness-to-pay early.
  • Include COGS drivers in pricing decisions (especially usage-based).
  • Use discount guardrails and renewal logic (avoid ad-hoc deals).

Avoid

  • Pricing as an afterthought (“we’ll figure it out later”).
  • Margin blindness (shipping usage growth that destroys gross margin).
  • Misleading LTV calculations from immature cohorts.

What Good Looks Like

  • Packaging: a clear value metric, tier logic, and discount policy (with enforcement rules).
  • Unit economics: CAC, gross margin, churn, payback, and retention defined and tied to cohorts.
  • Assumptions: one inputs sheet, ranges/sensitivities, and scenarios (base/best/worst).
  • Experiments: pricing changes tested with decision rules (not “gut feel” rollouts).
  • Risks: margin compression, adverse selection, channel conflict, and support cost modeled.

Optional: AI / Automation

Use only when explicitly requested and policy-compliant.

  • Summarize pricing research and competitor snapshots; verify manually before acting.
  • Draft pricing page copy; humans verify claims and consistency with contracts.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.