Pricing Model

A pricing model is the structural mechanism by which a company charges customers, distinct from pricing strategy and revenue model. It encompasses the unit of pricing (per-seat, per-API-call, per-transaction, per-product, flat-platform), the structure of tiers and packages, and the relationship between value delivered and value captured. The main modern options are per-seat (classic SaaS), usage-based (infrastructure SaaS), tiered (good/better/best), flat (single price), per-outcome (rare but value-aligned), and hybrid combinations. Pricing model choice has significant implications for unit economics, sales motion, and customer behavior.

The main pricing models:

Per-seat / per-user:

• Charge per active user or seat license.
• Predictable per-customer revenue; scales with team adoption.
• Common: Salesforce, Slack (historical), most enterprise SaaS.
• Pros: predictable, easy to communicate, aligns with adoption.
• Cons: can incentivize customers to share seats; doesn't capture usage value.

Usage-based:

• Charge for consumption (API calls, storage, processed events, compute hours).
• Aligns cost with customer value; scales with usage.
• Common: Snowflake, AWS, Stripe, Twilio.
• Pros: customer pays for value received; expansion automatic with growth.
• Cons: less predictable revenue; harder for customer to budget.

Tiered / packaged:

• Multiple plans (Starter, Pro, Enterprise) with different features and limits.
• Common at most modern SaaS.
• Pros: enables expansion via plan upgrades; covers different customer sizes.
• Cons: can lock features inappropriately; complex pricing pages.

Flat / single-price:

• One price for the product.
• Simple but doesn't capture variable value.
• Common at consumer subscription (Netflix, Spotify), early-stage SaaS.
• Pros: simple to communicate; no negotiation.
• Cons: doesn't capture value differences across customers.

Per-outcome:

• Charge based on results achieved.
• Aligns most closely with customer value.
• Rare because hard to operationalize.
• Common in some industries (legal contingency, performance marketing).

Freemium:

• Free tier with paid upgrades.
• Acquisition vehicle for paid conversion.
• Common at SMB SaaS, developer tools.
• Pros: low-friction acquisition; product-led growth.
• Cons: many free users never convert; support costs for non-payers.

Hybrid:

• Combinations: per-seat + usage overage, flat platform fee + per-transaction.
• Common at modern companies that found pure models too rigid.
• Captures different value dimensions.

How to choose the right model:

Match to how customers derive value:

• Value scales with team size → per-seat.
• Value scales with consumption → usage-based.
• Value varies by features needed → tiered.
• Value is binary or uniform → flat.

Consider sales motion:

• Sales-led typically works with per-seat or tiered enterprise contracts.
• Product-led works with freemium or usage-based.

Consider customer budgeting:

• Customers prefer predictable costs.
• Pure usage-based can create budget anxiety.
• Caps or commit-and-overage hybrid models address this.

What founders get wrong: Choosing pricing model based on what competitors do rather than how customers derive value. The right discipline: match to value structure, consider sales motion, allow for evolution as business matures.

Related: Pricing Strategy · Revenue Model · Go to Market Strategy · Business Model Canvas · Financial Model

FAQ

What is a pricing model?
The structural mechanism by which a company charges customers, including the unit of pricing (per-seat, per-API-call, etc.), structure of tiers, and relationship between value delivered and captured. Distinct from pricing strategy (positioning and price points).

What are the main pricing models?
Per-seat (classic SaaS, Salesforce), usage-based (Snowflake, AWS), tiered (good/better/best, common modern SaaS), flat (Netflix, Spotify), per-outcome (rare), freemium (SMB SaaS), and hybrid (combinations like per-seat + usage overage).

How do I choose the right pricing model?
Match to how customers derive value (team size = per-seat, consumption = usage-based, feature needs = tiered). Consider sales motion fit (sales-led typically tiered; product-led typically freemium or usage). Provide some predictability for customer budgeting.