This framework helps founders and product leaders choose between five primary digital business models — subscription, transactional, marketplace, platform, and freemium — based on product characteristics, usage patterns, marginal costs, market size, and network effects. The default recommendation for most SaaS products is subscription with usage-based tiers, because it provides predictable recurring revenue and higher customer lifetime value than transactional models. [src1] However, marketplace and platform models can generate significantly higher enterprise value when network effects are strong. [src4]
| Input | Why It Matters | How to Assess |
|---|---|---|
| Product type | Software tools favor subscription; connecting buyers and sellers favors marketplace | Ask what the product does and who it serves |
| Usage frequency | High-frequency use supports subscription; low-frequency favors transactional | Ask how often a typical customer needs the product |
| Marginal cost per customer | Near-zero marginal cost enables freemium; high marginal cost eliminates it | Ask about infrastructure, support, and fulfillment costs per additional user |
| Total addressable market | Freemium requires >1M potential users; niche markets favor subscription | Ask about target market size and segment |
| Network effects potential | Strong network effects favor marketplace/platform; no network effects favor subscription | Ask whether the product becomes more valuable as more users join |
| Revenue predictability need | High need for predictable revenue favors subscription; tolerance for variability enables transactional | Ask about investor expectations, burn rate, and planning needs |
START — Which business model fits best?
├── Does the product connect independent buyers and sellers?
│ ├── YES — Are transactions the core value?
│ │ ├── YES → EVALUATE: Marketplace (commission-based)
│ │ │ ├── Can you solve the chicken-and-egg problem?
│ │ │ │ ├── YES + 18-24 month runway → RECOMMEND: Marketplace
│ │ │ │ │ Reason: Transaction facilitation is the product
│ │ │ │ └── NO → RECOMMEND: Subscription SaaS (tool for one side)
│ │ │ └── Is AOV > $50? Commission model viable if yes
│ │ └── NO (connections only) → RECOMMEND: Subscription or lead-gen
│ └── NO
│ ├── Does the product become more valuable with more users?
│ │ ├── STRONG network effects
│ │ │ ├── Can third parties build on it?
│ │ │ │ ├── YES → RECOMMEND: Platform (rev share + API fees)
│ │ │ │ └── NO → RECOMMEND: Subscription with network tiers
│ │ ├── WEAK / NO network effects
│ │ │ ├── Frequent usage? → RECOMMEND: Subscription
│ │ │ └── Infrequent usage? → RECOMMEND: Transactional
│ │ └── UNCERTAIN → Default to Subscription
│ └── Marginal cost near zero AND TAM > 1M?
│ ├── YES → EVALUATE: Freemium + premium tiers
│ │ ├── Clear free/paid boundary? → RECOMMEND: Freemium
│ │ └── No clear boundary → RECOMMEND: Free trial + subscription
│ └── NO → RECOMMEND: Subscription or transactional
├── OVERRIDE CONDITIONS:
│ ├── Investor expects predictable MRR/ARR → Subscription required
│ ├── Product is infrastructure/API → Usage-based pricing preferred
│ └── TAM < 100K users → Avoid freemium
└── DEFAULT (if inputs are ambiguous):
└── RECOMMEND: Subscription with usage-based tiers
Reason: Most forgiving model — predictable revenue,
adjustable pricing, works across market sizes
| Factor | Subscription | Transactional | Marketplace | Platform | Freemium |
|---|---|---|---|---|---|
| Revenue predictability | High (recurring MRR/ARR) | Low (variable) | Medium (scales with GMV) | Medium-High | Low until conversion matures |
| Time to first revenue | 1-3 months | Immediate | 6-18 months | 12-24 months | 3-6 months |
| CAC (B2B typical) | $200-700 | $50-200/sale | $100-500/side | $500-2,000/dev | $10-50 free, $200-500 convert |
| LTV potential | High (multi-year) | Low (per-txn) | High (if liquid) | Very high | Variable (2-5% convert) |
| Scalability | Linear | Linear | Exponential | Exponential | Exponential if TAM large |
| Best when | Frequent use, ongoing value | Infrequent, high per-use value | Connecting supply & demand | 3rd parties extend product | TAM >1M, marginal cost ~$0 |
| Worst when | Sporadic usage | Ongoing access needed | Cannot solve cold-start | No developer interest | High marginal cost, small TAM |
| Hidden costs | Churn management | Demand generation | Fraud, trust/safety | DevRel, API maintenance | Supporting 95%+ free users |
→ Marketplace (commission-based). Commission rates of 10-30% depending on value delivered and competitive alternatives. 51% of top marketplaces use commission as primary revenue model. [src2]
→ Subscription. Subscription models produce higher long-term customer lifetime value than transactional models through ongoing engagement and upselling. Average B2B SaaS annual churn benchmarks are 3.5-5%. [src1, src7]
→ Platform (API + rev share). Five dynamics to evaluate: network effects, clustering, disintermediation risk, multi-homing vulnerability, and bridging potential. [src3]
→ Freemium + premium tiers. Conversion rates average 2-5%. Below 2% signals the free tier is too generous or premium tier is not compelling. [src5]
→ Transactional (pay-per-use). Customers who need a product 2-3 times per year resist monthly fees. High per-transaction value makes this viable. [src6]
→ Start with subscription, add complexity later. Most forgiving starting model — provides predictable revenue, is easy to price and adjust, and creates a direct customer relationship. [src7]
→ Subscription with usage-based tiers. When inputs are ambiguous, subscription with usage-based pricing components is the lowest-risk choice. Provides revenue predictability while pricing scales with customer value. [src7]
Companies launch a freemium model targeting a niche market of 50-100K potential users. With 2-5% conversion rates, this yields only 1,000-5,000 paying customers — often insufficient to sustain operations while incurring costs for tens of thousands of non-paying users. [src5]
For niche markets, use a 14-30 day free trial with a subscription model instead — this delivers the try-before-you-buy experience without the ongoing cost of free users. [src5]
Founders build a two-sided marketplace and launch to zero supply and zero demand, expecting both sides to arrive simultaneously. Without critical mass, the marketplace delivers no value and users churn before network effects can form. [src2]
Successful marketplaces typically start by providing standalone value to one side (usually supply). Achieving liquidity on one side first significantly increases survival rates. [src2]
Teams choose subscription because it is familiar, even when usage patterns do not support recurring payment. Customers who use a product 2-3 times per year resent monthly charges and churn quickly, destroying the revenue predictability that made subscription attractive. [src6]
Audit expected usage patterns before selecting a model. High-frequency use supports subscription. Low-frequency use supports transactional or pay-per-use. Variable use supports usage-based pricing with a small base subscription. [src1]
| Scenario | Subscription | Transactional | Marketplace | Platform | Freemium |
|---|---|---|---|---|---|
| CAC (B2B) | $200-700 | $50-200/sale | $100-500/side | $500-2,000/dev | $10-50 free, $200-500 convert |
| CAC (B2C) | $50-150 | $5-50/sale | $20-100/side | $100-500/dev | $1-10 free, $50-150 convert |
| Payback period | 6-18 months | Immediate | 12-36 months | 18-36 months | 12-24 months |
| Gross margin | 70-85% | 40-70% | 60-80% (net rev) | 70-90% | 70-85% (paid users) |
| Annual churn (B2B) | 3.5-5% | N/A | 15-25% (supply) | 10-20% (devs) | 5-8% (paid users) |
| LTV:CAC target | 3:1+ | 2:1+ per cohort | 4:1+ | 5:1+ | 3:1+ (paid only) |
Hidden cost multipliers: Add 15-25% for payment processing and billing infrastructure. Marketplace models add 10-20% for trust/safety and dispute resolution. Platform models add 25-40% for developer relations and API maintenance. Freemium models must budget for serving non-paying users — typically 60-80% of infrastructure costs serve free-tier users. [src5, src7]
Fetch when a founder, product leader, or strategy consultant is choosing a business model for a new product, evaluating whether to change an existing business model, or comparing revenue model options. Especially relevant at pre-seed/seed stage, before product-market fit, or when pivoting from one model to another.