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
- Distinctive: line 80
Use top-down and bottom-up.
- Distinctive: line 82
Document every assumption (penetration, ARPU, growth rate).
- Distinctive: line 95
Run sensitivity on churn, CAC, and price.
≈ “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.
Files
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
| Need | Skill |
| Executive business case and roadmap | business-consultant |
| Build requirements from validated model | business-analyst |
| Research writing polish | tech-writer-researcher |
| Product discovery UX | product-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:
| Block | Research focus |
| Customer segments | Who pays vs who uses; ICP |
| Value proposition | Job, pain, gain; differentiation |
| Channels | Acquisition and delivery |
| Relationships | Self-serve vs enterprise vs community |
| Revenue streams | Pricing model and packaging |
| Key resources / activities / partners | What enables the model |
| Cost structure | Fixed 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:
| Dimension | Notes |
| Primary revenue model | Sub, usage, take rate, hybrid |
| Pricing tiers | Entry price, enterprise motion |
| GTM motion | PLG, sales-led, channel |
| Unit economics signals | Public 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
## SourcesHand 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
Other versions1 project uses a version of this.
Word for word · 1
- daemon-blockint-tech/Agentic-Enteprises-Skill★ 8100% same
Edited · 0
None found.
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 repository197 other files it gives its agents.
- ab-testing-engineerSkill
- actuarial-analystSkill
- actuarial-consultingSkill
- actuarySkill
- advanced-long-term-actuarial-mathematicsSkill
- advanced-persistent-threatSkill
- advanced-short-term-actuarial-mathematicsSkill
- agentic-ai-developerSkill
- ai-adversarial-robustness-engineerSkill
- ai-context-engineerSkill
- ai-engineerSkill
- ai-lead-opsSkill
- ai-memory-developerSkill
- ai-redteamSkill
- ai-researcherSkill
- ai-risk-governanceSkill
- ai-skill-managerSkill
- ai-token-improvement-plan-engineerSkill
- aml-cftSkill
- aml-complianceSkill
- analytics-data-engineering-manager-productSkill
- analytics-data-engineerSkill
- anti-false-positive-decision-makingSkill
- applied-ai-architect-commercial-enterpriseSkill
- appointed-chief-actuarySkill
- asset-liability-managementSkill
- associate-actuarySkill
- assumption-settingSkill
- auditorSkill
- bcm-disaster-recovery-specialistSkill
- bi-analystSkill
- build-validatorSkill
- business-analystSkill
- business-consultantSkill
- certified-information-systems-security-professionalSkill
- chief-information-security-officerSkill
- ci-cd-engineerSkill
- cicd-engineerSkill
- cisco-certified-network-professionalSkill
- classified-cyber-security-senior-managerSkill
- classified-software-devsecops-engineerSkill
- cloud-architectSkill
- cloud-compliance-specialistSkill
- cloud-economistSkill
- cloud-engineerSkill
- cloud-security-engineerSkill
- cloud-system-administratorSkill
- cluster-deployment-engineerSkill
- code-securitySkill
- commercial-counselSkill
- communication-leadSkill
- community-executive-escalations-program-managerSkill
- compliance-engineerSkill
- compliance-specialistSkill
- compute-accounting-managerSkill
- control-software-developerSkill
- corporate-counselSkill
- country-managerSkill
- cross-department-translationSkill
- cryptographer-specialistSkill
- The first 60 shown.
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.

