business-model-teardown
Skill2 starsChanged 5 months agoMITView on GitHub
Reverse-engineer a company's business model from its public website using a Business Model Canvas lens — how it creates value, who it serves, how it makes money, its cost drivers, and how durable the model is. Use when the user asks "how does this business make money", "what's their business model", "reverse engineer this company", or shares a site and wants the economics and revenue model explained rather than just the marketing.
In this repository14 other files it gives its agents.
- ad-creative-analysisSkill
- competitor-teardownSkill
- email-nurture-teardownSkill
- funnel-auditSkill
- icp-segmentationSkill
- landing-ux-reviewSkill
- offer-teardownSkill
- online-school-auditSkill
- positioning-messaging-auditSkill
- pricing-analysisSkill
- review-miningSkill
- seo-content-gapSkill
- social-proof-auditSkill
- webinar-funnel-teardownSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
When the user wants the money mechanics, not the messaging.
- Distinctive: line 41
If the site is purely a landing page with no product/pricing detail, say what can and cannot be inferred.
- Distinctive: line 108
Never fabricate revenue, margins, CAC/LTV, or customer counts.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Business Model Teardown
Explain how a company actually makes money — and how durable that is — from nothing but its public website.
What it does
Reconstructs a company's business model using the Business Model Canvas, then adds a revenue-model and unit-economics read. Output is a one-page model plus a judgment on what makes the model work and what threatens it. This is the "economics" complement to a positioning/marketing teardown.
When to use this skill
- "How does
<company>make money?" - "What's their business model / revenue model?"
- "Reverse-engineer this company's economics from their site."
- When the user wants the money mechanics, not the messaging.
Inputs needed
- Required: the company's website URL.
- Helpful: the industry, whether they're B2B/B2C, any known facts (funding, pricing) the user already has.
- If the site is purely a landing page with no product/pricing detail, say what can and cannot be inferred.
Method
- Read for evidence — homepage, product, pricing, about, customers, careers.
- Fill the Business Model Canvas — nine blocks:
- Customer segments — who they serve.
- Value propositions — the job done for each segment.
- Channels — how they reach and deliver to customers.
- Customer relationships — self-serve, sales-led, community, success.
- Revenue streams — how money comes in (see revenue-model patterns below).
- Key resources — what the model depends on (tech, brand, data, network).
- Key activities — what they must do well.
- Key partnerships — integrations, suppliers, channel partners.
- Cost structure — main cost drivers (people, infra, ads, content).
- Classify the revenue model — subscription/SaaS, transactional/usage, marketplace/take-rate, advertising, one-time/license, services, info-product/ course, freemium, or a hybrid. Note pricing metric (per seat, usage, flat).
- Sketch unit economics qualitatively — value metric, likely ACV band, apparent motion (PLG vs sales-led), and what drives CAC vs LTV. No invented numbers.
- Judge durability — moats (network effects, switching costs, brand, data), and risks (concentration, thin differentiation, platform dependence, churn signals).
Output format
# Business Model Teardown — <Company>
## TL;DR
- What they sell, to whom, and how they charge — in 3 bullets.
- The one thing the model lives or dies on.
## Business Model Canvas
| Block | Finding |
|-------|---------|
| Customer segments | |
| Value propositions | |
| Channels | |
| Customer relationships | |
| Revenue streams | |
| Key resources | |
| Key activities | |
| Key partnerships | |
| Cost structure | |
## Revenue model
- Type:
- Pricing metric / value metric:
- Go-to-market motion (PLG / sales-led / hybrid):
## Unit-economics read (qualitative)
- CAC drivers:
- LTV / retention drivers:
- Apparent ACV band & why:
## Durability
| Moats | Risks |
|-------|-------|
## Bottom line
2–3 sentences: is this a strong model, and what would you watch?Quality bar
- Distinguish stated revenue mechanics (visible pricing) from inferred ones.
- Never fabricate revenue, margins, CAC/LTV, or customer counts. Use bands and reasoning ("likely mid-ACV sales-led, because pricing is gated and there's a demo CTA"), and say when something is unknown.
- The durability section must name specific moats/risks, not generic ones.
Common mistakes to avoid
- Confusing the value proposition (marketing) with the revenue model (economics).
- Asserting precise financials that the site can't support.
- Stopping at "it's a SaaS" without the pricing metric and motion.
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.

