
Business Model Design
- 29 installs
- 122 repo stars
- Updated January 22, 2026
- omer-metin/skills-for-antigravity
Helps with ai & agent building tasks during AI-assisted development.
About
business-model-design is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.
- business-model-design
- AI & Agent Building
- AI-coding skill
Business Model Design by the numbers
- 29 all-time installs (skills.sh)
- Ranked #9,417 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/omer-metin/skills-for-antigravity --skill business-model-designAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 29 |
|---|---|
| repo stars | ★ 122 |
| Last updated | January 22, 2026 |
| Repository | omer-metin/skills-for-antigravity ↗ |
What it does
Helps with ai & agent building tasks during AI-assisted development.
Files
Business Model Design
Identity
Role: Business Model Architect
Personality: You think in value flows - where value is created, how it moves, who captures it. You understand that the best business model is one that aligns incentives across all stakeholders. You're pragmatic about copying proven models and creative about adapting them. You always tie business model to unit economics.
Expertise:
- Business model patterns
- Revenue model design
- Unit economics analysis
- Value proposition mapping
- Cost structure design
- Business model innovation
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult `references/patterns.md`. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
- For Diagnosis: Always consult `references/sharp_edges.md`. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
- For Review: Always consult `references/validations.md`. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Business Model Design
Patterns
---
Name
Business Model Canvas
Description
Mapping the complete business model
When To Use
Designing or analyzing business models
Implementation
Business Model Canvas
1. The Nine Building Blocks
┌──────────────────────────────────────────────────────────────────┐
│ Key │ Key │ Value │ Customer │ Customer │
│ Partners │ Activities │ Propositions │ Relationships│ Segments │
│ │ │ │ │ │
│ Who helps │ What we │ What value │ How we │ Who we │
│ us do this? │ must do? │ we deliver? │ interact? │ serve? │
├───────────────┼───────────────┼───────────────┤ │ │
│ │ Key │ │ Channels │ │
│ │ Resources │ │ │ │
│ │ │ │ How we │ │
│ │ What we need? │ │ reach them? │ │
├───────────────┴───────────────┴───────────────┴──────────────┴───────────┤
│ Cost Structure │ Revenue Streams │
│ │ │
│ What are the major costs? │ How do we make money? │
└───────────────────────────────────┴──────────────────────────────────────┘2. Value Proposition
The Value Proposition Canvas
Customer Profile:
- Jobs to be done
- Pains
- Gains
Value Map:
- Products/Services
- Pain relievers
- Gain creators
Fit = Value Map addresses Customer Profile3. Customer Segments
| Type | Description | Example |
|---|---|---|
| Mass Market | Broad, undifferentiated | Consumer goods |
| Niche | Specialized, specific | Enterprise security |
| Segmented | Different needs in same market | SMB vs Enterprise |
| Multi-sided | Distinct interdependent groups | Marketplace |
4. Revenue Streams
| Type | Description | When |
|---|---|---|
| Subscription | Recurring access | Ongoing value delivery |
| Transaction | Per-use or per-sale | Clear value per transaction |
| Licensing | Rights to use | IP-based value |
| Advertising | Attention monetization | Free user base |
| Commission | % of transaction | Facilitating transactions |
| Freemium | Free + Paid tiers | Network effects matter |
5. Cost Structure
Fixed Costs: Don't change with volume
- Salaries
- Rent
- Software licenses
Variable Costs: Scale with volume
- COGS
- Transaction costs
- Customer support
Business Model Impact:
- High fixed, low variable = scale economics
- Low fixed, high variable = flexibility---
Name
Revenue Model Selection
Description
Choosing how to monetize
When To Use
Designing monetization approach
Implementation
Revenue Model Guide
1. Revenue Model Types
| Model | Mechanism | Best For |
|---|---|---|
| SaaS/Subscription | Recurring fee | Ongoing value, predictable |
| Transactional | Per transaction | Variable usage |
| Marketplace/Commission | % of GMV | Connecting buyers/sellers |
| Usage-Based | Pay-per-use | Metered value |
| Licensing | One-time fee + maintenance | Software, IP |
| Advertising | CPM/CPC | Attention/audience |
| Freemium | Free + Premium | Network effects |
| Hardware + Subscription | Device + Recurring | IoT, hardware products |
2. Selection Criteria
| Factor | Consideration |
|---|---|
| Value timing | When is value delivered? |
| Customer preference | How do they want to buy? |
| Competition | What's the market norm? |
| Cash flow | What do you need? |
| Scalability | Does it scale? |
| Stickiness | Does it create retention? |
3. Hybrid Models
Examples:
- SaaS + Usage-based: Base fee + overages
- Freemium + Premium: Free tier + paid
- Product + Services: Core + implementation
- Hardware + Subscription: Razor/razorblade4. Revenue Model Fit
| Product Type | Typical Model |
|---|---|
| Business software | SaaS subscription |
| Developer tools | Free tier + paid |
| Marketplaces | Commission |
| Consumer apps | Freemium or Ads |
| Enterprise | License or SaaS |
| Infrastructure | Usage-based |
5. Model Evolution
Early stage: Simple model
Growth stage: Add upsell paths
Scale stage: Multiple revenue streams
Example:
v1: Single subscription tier
v2: Multiple tiers (starter, pro, enterprise)
v3: Platform/marketplace (services, apps)---
Name
Unit Economics Design
Description
Understanding the economics of one customer
When To Use
Validating business model viability
Implementation
Unit Economics Framework
1. Core Metrics
LTV (Lifetime Value)
= ARPU × Gross Margin × Customer Lifespan
= ARPU × Gross Margin / Churn Rate
CAC (Customer Acquisition Cost)
= Total Sales & Marketing / New Customers
LTV:CAC Ratio
= LTV / CAC
Target: > 3:1
Payback Period
= CAC / (ARPU × Gross Margin)
Target: < 12 months2. Metric Benchmarks
| Metric | Healthy | Concerning |
|---|---|---|
| LTV:CAC | > 3:1 | < 2:1 |
| Payback | < 12 mo | > 18 mo |
| Gross Margin | > 70% | < 50% |
| Net Revenue Retention | > 100% | < 90% |
| Churn (Monthly) | < 2% | > 5% |
3. Unit Economics by Model
SaaS
ARPU = Monthly subscription
Gross Margin = ~80-90%
Churn = Monthly logo churn
CAC = Sales + Marketing / New logosMarketplace
ARPU = Take rate × GMV per user
Gross Margin = ~60-80%
Churn = Seller and buyer churn
CAC = Cost to acquire both sidesE-commerce
ARPU = AOV × Purchase frequency
Gross Margin = ~30-50%
Churn = Time between purchases
CAC = Marketing / New customers4. Improving Unit Economics
| Lever | Actions |
|---|---|
| Increase LTV | Reduce churn, increase ARPU |
| Reduce CAC | Better targeting, lower cost channels |
| Improve Margins | Reduce COGS, increase prices |
| Reduce Payback | Faster activation, upfront payment |
5. Cohort Analysis
Track unit economics by cohort:
- Acquisition cohort
- Channel cohort
- Segment cohort
- Pricing cohort
Find best-performing cohorts, focus there.---
Name
Business Model Innovation
Description
Creating new business model approaches
When To Use
Differentiating or disrupting
Implementation
Business Model Innovation
1. Innovation Types
| Type | Description | Example |
|---|---|---|
| Revenue model | New way to monetize | Subscription instead of purchase |
| Value chain | New way to deliver | Direct-to-consumer |
| Target segment | New customer | Prosumer instead of enterprise |
| Value proposition | New benefit | Convenience instead of price |
| Cost structure | New economics | Asset-light vs ownership |
2. Innovation Patterns
Unbundling
- Break apart integrated offering
- Let customers buy pieces
- Example: ESPN+ from cable bundle
Bundling
- Combine separate offerings
- Create integrated solution
- Example: Microsoft 365
Platform Shift
- From product to platform
- Others build on you
- Example: Salesforce AppExchange
Subscription Shift
- From purchase to subscription
- Recurring relationship
- Example: Adobe Creative Cloud
Asset Light
- Don't own the assets
- Orchestrate others' assets
- Example: Airbnb, Uber
3. When to Innovate
| Situation | Consider |
|---|---|
| Market expects model | Copy proven model |
| Model is competitive advantage | Innovate |
| Existing models failing | Must innovate |
| Technology enables new model | Innovate early |
4. Innovation Risk
Business model innovation carries risk:
- Customers don't understand
- Hard to compare
- Requires education
Mitigate:
- Test with early adopters
- Offer transition paths
- Build proof pointsAnti-Patterns
---
Name
Revenue Before Value
Description
Monetizing before delivering value
Why Bad
No one pays for unrealized value. Damages trust. Limits growth potential.
What To Do Instead
Prove value first. Monetization follows value. Free can be strategic.
---
Name
Model-Market Mismatch
Description
Choosing model that doesn't fit market
Why Bad
Customers won't buy. Sales cycles lengthen. Friction everywhere.
What To Do Instead
Understand how customers want to buy. Match model to expectations. Consider market norms.
---
Name
Ignoring Unit Economics
Description
Building without understanding economics
Why Bad
Can't scale unprofitable. VC subsidy hides problems. Business isn't viable.
What To Do Instead
Model unit economics early. Validate before scaling. Fix economics at small scale.
---
Name
Premature Complexity
Description
Multiple revenue streams too early
Why Bad
Complexity without scale. Dilutes focus. Hard to optimize.
What To Do Instead
Master one model first. Add complexity with scale. Simple scales better.
Business Model Design - Sharp Edges
Unit Economics Denial
Id
unit-economics-denial
Summary
Ignoring or rationalizing bad unit economics
Severity
high
Situation
Business losing money on every customer
Why
Hope that scale will fix it. VC money masks problems. Focus on growth, not profitability.
Solution
Facing Unit Economics Reality
Healthy vs Unhealthy Rationalization
| Unhealthy | Reality Check |
|---|---|
| "We'll make it up on volume" | Losing more at scale |
| "CAC will drop with brand" | When? How much? |
| "Expansion will fix LTV" | Prove it at small scale |
| "Competitors lose money too" | Not a strategy |
Unit Economics Audit
Calculate honestly:
- True CAC (include all costs)
- True COGS (all delivery costs)
- True churn (annualized)
- True LTV (conservative assumptions)
LTV:CAC < 2? You have a problem.Fix Paths
| Problem | Solutions |
|---|---|
| CAC too high | Better targeting, lower cost channels, PLG |
| COGS too high | Automation, renegotiate, simplify |
| Churn too high | Product improvement, success investment |
| ARPU too low | Pricing, upsell, better customers |
When Unit Economics Can Be Fixed Later
Defensible only when:
- Network effects require scale first
- Winner-take-all dynamics
- Clear path to profitable cohorts
- Investors understand and fund path
Even then: Monitor closely.Symptoms
- Burn rate increasing faster than revenue
- "We'll figure out monetization later"
- Avoiding detailed unit economics analysis
Detection Pattern
unit economics|LTV|CAC|profitability
Revenue Model Mismatch
Id
revenue-model-mismatch
Summary
Choosing revenue model that doesn't fit
Severity
high
Situation
Customers don't want to buy this way
Why
Copied model without context. Didn't research how customers buy. Optimized for you, not customer.
Solution
Revenue Model Fit
Customer Buying Signals
| Signal | Model Implication |
|---|---|
| "We have annual budgets" | Annual contracts |
| "We don't know usage yet" | Subscription vs usage |
| "We want to try first" | Free tier needed |
| "We buy from procurement" | Enterprise model |
Model-Market Fit Check
Research:
1. How do customers buy similar products?
2. What are they currently paying?
3. Who approves the purchase?
4. What's their payment preference?
Match model to answers.Warning Signs
| Sign | Likely Issue |
|---|---|
| Long sales cycles | Model too complex |
| Price objections | Wrong pricing model |
| Low conversion | Friction in model |
| High churn | Value not perceived |
Model Adjustment
If model isn't working:
1. Interview churned/lost customers
2. Ask why they didn't buy
3. Test alternative models
4. Don't assume you know bestSymptoms
- Customers asking for different buying options
- Lost deals due to pricing model
- Low conversion despite interest
Detection Pattern
revenue model|pricing model|how to charge
Multi Sided Imbalance
Id
multi-sided-imbalance
Summary
Platform/marketplace with unbalanced sides
Severity
high
Situation
Can't grow both sides together
Why
Chicken-and-egg problem. One side subsidizes other poorly. Wrong side monetized.
Solution
Multi-Sided Platform Balance
The Chicken-Egg Problem
Marketplaces need both sides:
- Sellers won't come without buyers
- Buyers won't come without sellers
Solving this:
1. Seed one side first
2. Single-player mode value
3. Subsidize harder sideWhich Side to Subsidize
| Subsidize | When |
|---|---|
| Supply (sellers) | Supply is scarce, unique |
| Demand (buyers) | Demand is scarce, valuable |
| Neither | Organic network effects |
Monetization Side Selection
Charge the side that:
- Gets more value
- Has more alternatives
- Is less price sensitive
- Isn't the growth constraint
Example:
- Airbnb: Hosts pay (supply constrained)
- Uber: Riders pay (demand side)
- LinkedIn: Recruiters pay (value received)Balance Metrics
| Metric | Healthy |
|---|---|
| Supply/Demand ratio | Stable |
| Time to match | Decreasing |
| Transaction success | >80% |
| Both-side retention | Healthy |
Symptoms
- One side of marketplace dying
- Can't attract one side
- Transactions not happening
Detection Pattern
marketplace|platform|two-sided
Free Forever
Id
free-forever
Summary
No path from free to revenue
Severity
medium
Situation
Users love free, won't pay
Why
Free tier too generous. Paid value unclear. No upgrade triggers.
Solution
Freemium Path Design
Free Tier Principles
Free tier should:
- Deliver core value
- Create habit
- NOT satisfy all needs
Free tier should NOT:
- Give everything away
- Have no limits
- Feel completeUpgrade Trigger Design
| Trigger | Mechanism |
|---|---|
| Usage limits | Hit the wall naturally |
| Team needs | Collaboration requires upgrade |
| Feature locks | Advanced features gated |
| Support levels | Better support for paid |
Conversion Funnel
Free user →
Experiences value →
Hits limit or needs more →
Sees clear upgrade path →
Converts
Each step needs design and measurement.Free Tier Audit
Questions:
- What % of free users could be satisfied forever?
- What triggers exist for upgrade?
- How clear is the value of paid?
- Are free users becoming paid over time?
Symptoms
- High free usage, low conversion
- Free users never upgrade
- "Why would I pay?"
Detection Pattern
freemium|free tier|conversion
Complexity Creep
Id
complexity-creep
Summary
Business model becoming too complex
Severity
medium
Situation
Too many pricing tiers, add-ons, options
Why
Added complexity over time. Trying to please everyone. No model simplification discipline.
Solution
Model Simplification
Complexity Signals
| Signal | Meaning |
|---|---|
| Sales needs config sheets | Too complex |
| Customers ask "which one?" | Unclear tiers |
| Multiple discount types | Price integrity lost |
| Revenue spread thin | Too many options |
Simplification Principles
Good rule: 3 tiers maximum
- Starter: Entry point
- Pro/Growth: Main revenue
- Enterprise: High-touch
Add-ons should be rare, high-value.Complexity Audit
List all:
- Pricing tiers
- Add-on options
- Discount types
- Contract variations
If > 20 combinations: Simplify.Migration Path
When simplifying: 1. Grandfather existing customers 2. Migrate new customers to simple 3. Gradually transition existing 4. Communicate value
Symptoms
- Sales cycles lengthening
- Customers confused
- Finance struggling to track
Detection Pattern
pricing complexity|too many options|simplify
Business Model Design - Validations
Missing Revenue Model
Id
no-revenue-model
Severity
high
Type
conceptual
Check
Business must have defined revenue model
Message
No clear revenue model defined.
Fix Action
Define how the business will make money
Negative Unit Economics
Id
bad-unit-economics
Severity
high
Type
conceptual
Check
Unit economics should be positive or have clear path
Indicators
- LTV:CAC < 2:1
- No path to profitability
Message
Unit economics are not viable.
Fix Action
Fix CAC, churn, or ARPU before scaling
Unclear Value Proposition
Id
no-value-proposition
Severity
high
Type
conceptual
Check
Value proposition must be clearly articulated
Indicators
- Can't explain value in one sentence
- No differentiation
Message
Value proposition not clear.
Fix Action
Define clear value proposition and differentiation
Revenue Model Doesn't Fit Market
Id
model-market-mismatch
Severity
medium
Type
conceptual
Check
Revenue model should match how customers want to buy
Message
Revenue model may not fit customer expectations.
Fix Action
Research how customers buy and align model
Too Complex Business Model
Id
overcomplicated-model
Severity
medium
Type
conceptual
Check
Business model should be simple and understandable
Indicators
- More than 5 pricing tiers
- Many add-on options
Message
Business model too complex.
Fix Action
Simplify to 3 tiers maximum
Cost Structure Not Understood
Id
no-cost-structure
Severity
medium
Type
conceptual
Check
Cost structure should be clearly mapped
Message
Cost structure not well understood.
Fix Action
Map fixed and variable costs clearly