startup-business-models
Skill0 starsChanged 5 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
- MaxMiksa/Autonomous-Companyedited, first seen Oct 15, 2026
- MaxMiksa/Auto-Companyedited, first seen Oct 2, 2026
- NikitaDmitrieff/auto-co-metaword for word, first seen Mar 6, 2026
- nicepkg/auto-companyword for word, first seen Feb 11, 2026
Other versions4 projects use a version of this.
Word for word · 2
- nicepkg/auto-company★ 188100% same
- NikitaDmitrieff/auto-co-meta★ 43100% same
Edited · 2
- MaxMiksa/Auto-Company★ 3.2k76% same
- MaxMiksa/Autonomous-Company★ 3.2k76% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- code-review-securitySkill
- cold-email-sequence-generatorSkill
- community-led-growthSkill
- competitive-intelligence-analystSkill
- content-strategySkill
- deep-analysisSkill
- deep-reading-analystSkill
- deep-researchSkill
- devopsSkill
- email-sequenceSkill
- financial-unit-economicsSkill
- find-skillsSkill
- github-explorerSkill
- market-sizing-analysisSkill
- micro-saas-launcherSkill
- ph-community-outreachSkill
- premortemSkill
- pricing-strategySkill
- product-strategistSkill
- scientific-critical-thinkingSkill
- security-auditSkill
- senior-qaSkill
- seo-auditSkill
- seo-content-strategistSkill
- skill-creatorSkill
- startup-financial-modelingSkill
- tailwind-v4-shadcnSkill
- teamSkill
- user-persona-creationSkill
- user-research-synthesisSkill
- ux-audit-rethinkSkill
- web-scrapingSkill
- webshSkill
- agent-browserSkill
- code-review-securitySkill
- cold-email-sequence-generatorSkill
- community-led-growthSkill
- competitive-intelligence-analystSkill
- content-strategySkill
- deep-analysisSkill
- deep-reading-analystSkill
- deep-researchSkill
- devopsSkill
- email-sequenceSkill
- financial-unit-economicsSkill
- find-skillsSkill
- github-explorerSkill
- market-sizing-analysisSkill
- micro-saas-launcherSkill
- ph-community-outreachSkill
- premortemSkill
- pricing-strategySkill
- product-strategistSkill
- scientific-critical-thinkingSkill
- security-auditSkill
- senior-qaSkill
- seo-auditSkill
- seo-content-strategistSkill
- The first 60 shown.
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
- Distinctive: line 12
Ask for the smallest set of inputs that makes the decision meaningful:
- Distinctive: line 20
If numbers are missing, proceed with ranges + explicit assumptions and highlight what to measure next.
- Very specific: line 28
Use references/unit-economics-calculator.md for formulas, benchmarks, and common pitfalls.
- Distinctive: line 29
Prefer cohort/segment views over blended averages.
- Very specific: line 36
Use references/pricing-research-guide.md for WTP methods and pricing interview scripts.
- Very specific: line 37
Use assets/pricing-tier-design.md to draft tiers, limits, upgrade triggers, and enforcement rules.
- Distinctive: line 59
Use this when you are changing pricing, packaging, value metric, limits, discounts, or billing cadence.
- Very specific: line 87
Use references/saas-metrics-playbook.md for definitions and templates (MRR/ARR, churn, NRR, Quick Ratio, Magic Number, burn multiple, stage …
- Distinctive: line 119
Use discount guardrails and renewal logic (avoid ad-hoc deals).
- Distinctive: line 137
Use only when explicitly requested and policy-compliant.
≈ “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.
Files
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
- Classify the model
- Subscription, usage-based, freemium, marketplace take-rate, transaction fee, ads, outcome-based, credit-based, hybrid.
- Build a segment-level unit economics snapshot
- Use
references/unit-economics-calculator.mdfor formulas, benchmarks, and common pitfalls. - Prefer cohort/segment views over blended averages.
- 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.
- Propose pricing + packaging changes
- Use
references/pricing-research-guide.mdfor WTP methods and pricing interview scripts. - Use
assets/pricing-tier-design.mdto draft tiers, limits, upgrade triggers, and enforcement rules.
- Define measurement and roll-out
- Define success metric + guardrails, evaluation design, and explicit lag windows (conversion now, retention later).
- 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)
| Type | Examples |
| Primary success metric | Net revenue retention (NRR), ARPA/ARPU, gross margin %, payback period, upgrade rate, expansion MRR |
| Guardrails | New logo conversion, activation rate, refund rate, support load, churn (logo + revenue), sales cycle length |
2) Pick an evaluation design
| Design | Best when | How to read results |
| A/B (randomized) | Self-serve / PLG flows | Compare conversion, ARPA, refunds, and downstream retention by assignment |
| Holdout/control cohort | Pricing is hard to randomize | Compare treated vs. holdout cohorts matched on segment, channel, and start month |
| Step rollout (time-based) | Enterprise contracts, invoicing cycles | Compare pre/post with a parallel cohort (not exposed yet) to reduce seasonality bias |
| Geo/account rollout | Regions/segments are separable | Compare 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
| Resource | Purpose |
| unit-economics-calculator.md | LTV, CAC, payback calculations |
| pricing-research-guide.md | WTP research methodology |
| saas-metrics-playbook.md | SaaS-specific metrics deep dive |
Templates
| Template | Purpose |
| business-model-canvas.md | Full model design |
| unit-economics-worksheet.md | Calculate and track metrics |
| pricing-tier-design.md | Pricing & packaging worksheet |
Data
| File | Purpose |
| sources.json | Business 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.
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
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.

