business-model-thinking
Skill4 starsChanged 3 months agoMITView on GitHub
Evaluate monetization and unit economics. Use when how will this make money, business model, monetization, unit economics, or pricing.
In this repository46 other files it gives its agents.
- accessibility-reviewSkill
- accessibility-runtime-auditSkill
- adaptive-component-behaviorSkill
- ai-feature-ux-patternsSkill
- behavioral-pricing-psychologySkill
- business-model-readingSkill
- cognitive-load-heatmap-predictionSkill
- component-style-guideSkill
- cross-functional-reviewSkill
- dark-mode-theming-systemSkill
- dashboard-layout-patternsSkill
- dashboard-scaffolding-contractSkill
- design-drift-detectorSkill
- design-system-builderSkill
- design-to-code-handoffSkill
- design-tokensSkill
- error-boundary-resilience-designSkill
- flow-based-functional-testingSkill
- growth-impact-reviewSkill
- i18n-localization-strategySkill
- information-architectureSkill
- interactive-element-auditSkill
- kinematic-motion-choreographySkill
- micro-interaction-motion-designSkill
- module-registry-syncSkill
- mvp-scopingSkill
- perceived-performance-loadingSkill
- prd-traceability-matrixSkill
- product-discoverySkill
- product-strategySkill
- project-health-diagnosticsSkill
- qa-feedback-loop-orchestratorSkill
- responsive-breakpoint-strategySkill
- responsive-qa-auditSkill
- route-integrity-checkerSkill
- security-privacy-reviewSkill
- stakeholder-requirement-mappingSkill
- touch-gesture-interactionSkill
- typography-systemSkill
- usability-heuristics-checkSkill
- user-flow-mappingSkill
- user-research-synthesisSkill
- ux-chaos-monkeySkill
- visual-hierarchy-reviewSkill
- visual-responsive-regression-testingSkill
- visual-style-extractorSkill
The file
Files
Business Model Thinking
A product without a business model is a hobby. Every design decision has a cost structure; make it visible before it becomes technical debt.
1. Identify the revenue model
How does money flow? SaaS subscription, usage-based, marketplace commission, freemium, one-time purchase, advertising, data licensing. Name the model explicitly.
2. Map the cost structure
Outline infrastructure, personnel, third-party services, and customer acquisition. Order of magnitude is enough; precision comes later.
3. Sketch unit economics
Calculate what one customer costs to acquire (CAC) and what they generate (LTV). Even rough estimates surface unviable models early.
4. Evaluate pricing strategy
Determine who pays: per-seat, per-usage, tiered? Establish the anchor price in the market.
5. Assess scalability
Does the model scale linearly (more customers = proportional cost) or with leverage (more customers ≈ same cost)? Flag models that don't scale.
Completion Criteria
Done when the business model brief completely articulates the revenue flow, cost assumptions, and unit economic realities.
Output Format
Business Model Brief covering revenue model, cost structure, unit economics sketch, pricing rationale, and scalability assessment.
Anti-patterns
- Building features that increase cost without a corresponding revenue path.
- Deferring "how we make money" until after launch.
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.

