agentleFS
rade-nugrohorade-nugroho/Agentic-Enteprises-Skill/business-model-researcher/SKILL.md

business-model-researcher

Skill9 starsChanged 6 months agoMITView on GitHub

Guides business model research—Business Model Canvas and Lean Canvas, value proposition and customer segments, revenue and pricing models, unit economics (CAC, LTV, payback), market sizing (TAM/SAM/SOM), competitive business-model benchmarking, and evidence-backed synthesis for startups and product strategy. Use when researching how a company or idea makes money, comparing competitor monetization, sizing a market, stress-testing unit economics, drafting a canvas for a pitch, or documenting monetization hypotheses—for shipping pricing/packaging PRDs and paywalls use product-management-monetization—not for delivery BRDs (business-analyst), steerCo consulting engagements (business-consultant), GAAP revenue recognition (senior-revenue-accountant), internal BI SQL (bi-analyst), or technical architecture (senior-system-architecture).

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
  1. Distinctive:

    Use top-down and bottom-up.

    line 80
  2. Distinctive:

    Document every assumption (penetration, ARPU, growth rate).

    line 82
  3. Distinctive:

    Run sensitivity on churn, CAC, and price.

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Business Model Researcher

When to Use

  • Map or critique a business model (canvas, lean canvas, value proposition)
  • Research competitor revenue models, pricing, and packaging
  • Estimate TAM/SAM/SOM with stated assumptions
  • Model unit economics and sensitivity (CAC, LTV, margins, payback)
  • Compare monetization options (subscription, usage, marketplace, ads)
  • Synthesize public sources into a cited business-model brief

When NOT to Use

  • BRDs, user stories, process maps → business-analyst
  • Issue trees, operating model, steerCo recommendation → business-consultant
  • ASC 606, close, contract accounting → senior-revenue-accountant
  • Warehouse metrics and dashboards → bi-analyst
  • Long-form API docs or runbooks → tech-writer-researcher
  • UX journeys and wireframes → product-designer
  • Deal desk CPQ and order forms → deal-operations-administrator
  • Monetization PRDs, paywalls, billing product requirements → product-management-monetization

Related skills

NeedSkill
Executive business case and roadmapbusiness-consultant
Build requirements from validated modelbusiness-analyst
Research writing polishtech-writer-researcher
Product discovery UXproduct-designer
Pitch narrative (if deck-focused)business-consultant references

Core Workflows

1. Define the research question

State explicitly:

  • Subject — company, product line, or greenfield idea
  • Decision — invest, pivot pricing, enter segment, fundraise narrative
  • Audience — founder, product, investors, board
  • Depth — snapshot (2–4h) vs diligence (multi-day)
  • Sources allowed — public only vs internal data

List unknowns as hypotheses to validate or kill.

2. Map the current or proposed model

Fill canvas blocks with evidence tags [source] per claim:

BlockResearch focus
Customer segmentsWho pays vs who uses; ICP
Value propositionJob, pain, gain; differentiation
ChannelsAcquisition and delivery
RelationshipsSelf-serve vs enterprise vs community
Revenue streamsPricing model and packaging
Key resources / activities / partnersWhat enables the model
Cost structureFixed vs variable; COGS vs OpEx

See references/canvas_frameworks.md.

3. Size the market (when needed)

Use top-down and bottom-up; reconcile or explain gap.

Document every assumption (penetration, ARPU, growth rate).

See references/market_sizing.md.

4. Unit economics

Build a simple model:

  • Revenue per customer or unit
  • Variable cost per unit (COGS, infra, support allocation)
  • CAC and payback period
  • LTV (state churn and gross margin assumptions)

Run sensitivity on churn, CAC, and price.

See references/unit_economics.md.

5. Competitive benchmarking

Compare 3–7 peers on:

DimensionNotes
Primary revenue modelSub, usage, take rate, hybrid
Pricing tiersEntry price, enterprise motion
GTM motionPLG, sales-led, channel
Unit economics signalsPublic filings, interviews, estimates

Label fact vs estimate vs unknown.

See references/competitive_benchmarking.md.

6. Revenue model options (greenfield or pivot)

Shortlist 2–3 monetization patterns; score fit to segment and delivery cost.

See references/revenue_models.md.

7. Deliverable

Standard output structure:

## Executive summary (≤ 10 bullets)
## Business model map (canvas table)
## Market size (if applicable) — assumptions table
## Unit economics — base case + sensitivity
## Competitive comparison table
## Risks and open questions
## Sources

Hand strategic recommendation and investment case to business-consultant when exec decision is next.

When to load references

  • Canvas / VPC / lean → references/canvas_frameworks.md
  • TAM SAM SOM → references/market_sizing.md
  • CAC, LTV, payback → references/unit_economics.md
  • Sub, marketplace, usage → references/revenue_models.md
  • Peer comparison → references/competitive_benchmarking.md

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.