Quick pick
Which pricing model is right for your SaaS?
Answer one question and we'll point you to the right model — then read the full section below for the nuance.
Quick model selector
What scales with your product's core value?
Model 1 of 7
Per-seat pricing
Charge a fixed monthly fee per user (seat). Revenue scales naturally as customers grow their teams. The most familiar model for buyers — they know exactly what they'll pay.
Works best for
- CRM, project management, communication tools
- Products where value = team collaboration
- B2B SaaS with predictable team growth
- Products where individual users have distinct sessions
Watch out when
- Your product is used by one power user for a whole team
- Customers resist adding seats to avoid cost (seat-sharing)
- Value delivered doesn't scale with headcount
Revenue properties
- Predictable, easy to forecast
- Natural expansion revenue as teams grow
- Churn risk per seat vs. per customer
- Enterprise deals inflate per-seat pricing significantly
Real examples
Salesforce ($25–300/user/mo), Notion ($8–16/user/mo), Linear ($8/user/mo)
Typical range
$5–300/seat/month
Model 2 of 7
Usage-based pricing
Charge for what customers actually consume — API calls, data processed, messages sent, events tracked. Lowers the barrier to entry and revenue grows naturally with customer success. The dominant model for infrastructure and AI tools in 2026.
Works best for
- APIs, developer tools, data infrastructure
- AI features with per-token or per-call costs
- Products where usage genuinely varies widely across customers
- PLG motions — free tier with pay-as-you-grow
Watch out when
- Customers can't predict their monthly bill (creates anxiety, not delight)
- Your COGS scale with usage (margin compression at high volume)
- Enterprise buyers need budget certainty (commit + overage model helps)
Revenue properties
- Revenue correlates with customer success
- Harder to forecast — high variance month-to-month
- Negative churn possible when customers grow
- Complex to bill accurately at scale
Real examples
Twilio ($0.0079/SMS), OpenAI ($0.002/1K tokens), Stripe (2.9% + $0.30/transaction)
Model type
Pay-as-you-go or commit + overage
Model 3 of 7
Flat-rate pricing
One price for everyone. No tiers, no seat counting, no usage metering. Simple to communicate, easy to budget for, and zero negotiation friction. The right choice for a narrow set of SaaS products.
Works best for
- Niche compliance or reference tools with uniform value delivery
- Products where seat counting is impractical
- Bootstrapped products targeting a single customer segment
Watch out when
- High-value customers and low-value customers use the same product — you're leaving revenue on the table
- You want a natural expansion revenue path
- Your product could serve multiple segments at different price sensitivities
Revenue properties
- Maximum simplicity — easiest to sell and explain
- No expansion revenue without a price increase
- Revenue ceiling at current customer count × flat price
Real example
Basecamp ($299/mo flat — unlimited users and projects)
Typical range
$49–999/month
Model 4 of 7
Tiered pricing
Multiple plan levels (typically Free/Pro/Enterprise or Starter/Growth/Scale) at different price points with different feature sets. The dominant model for modern SaaS because it serves the widest range of customers while enabling natural upgrade paths.
Works best for
- SaaS with a wide customer range (SMB to enterprise)
- Products with clear feature differentiation across segments
- PLG motions — free tier drives adoption, paid tiers capture value
- Most modern B2B SaaS
Watch out when
- More than 3–4 tiers creates decision paralysis
- Tier differentiation is artificial — customers can't see the value gap
- Free tier costs too much to serve and converts too few
Revenue properties
- Best natural upgrade path of any model
- Enterprise tier drives disproportionate revenue
- Complex to model — need per-tier churn and conversion rates
Real examples
HubSpot (Free/Starter/Pro/Enterprise), Slack (Free/$7.25/$12.50/Enterprise), Figma (Free/$12/$45/Enterprise)
Typical tiers
Free + 2–3 paid tiers
Model 5 of 7
Freemium
A permanently free plan with limited features or usage, alongside paid plans. The free plan is a distribution mechanism and acquisition channel — not a product in itself. Used by the most successful PLG companies to build massive top-of-funnel.
Works best for
- Products where value is immediately obvious in the free tier
- Strong network effects — free users make the product better
- Viral / word-of-mouth distribution potential
- Products with low COGS for free users (software limits, not compute)
Watch out when
- Free users consume expensive resources (compute, storage, support)
- Free-to-paid conversion is below 2% — you're subsidising non-customers
- The free plan cannibalises the paid plan's value proposition
Revenue properties
- Long payback due to large free user base
- Massive top-of-funnel for relatively low marketing spend
- CAC is much lower when it works — organic and viral acquisition
Real examples
Notion, Slack, Figma, Dropbox, Zoom (all with generous free tiers)
Typical free→paid conv.
2–5% for B2B, 1–3% for B2C
Model 6 of 7
Per-feature pricing
Customers pay for a base product and add specific features as paid add-ons. Allows fine-grained monetisation of premium capabilities without forcing all users to the highest tier.
Works best for
- Products with clearly separable premium capabilities
- Existing product with natural upsell opportunities
- Enterprise add-ons (SSO, advanced analytics, custom integrations)
Watch out when
- Feature pricing feels nickle-and-diming to customers
- The feature catalogue becomes too complex to navigate
- Core product value is diluted by the add-on structure
Revenue properties
- Excellent expansion revenue from existing customers
- Higher ARPU ceiling vs. fixed-tier models
- More complex billing and entitlement management
Real examples
Intercom (base + add-ons for each product), HubSpot (base hubs + individual feature modules)
Model 7 of 7
Hybrid pricing
A combination of two or more models. The most common hybrid in 2026: tiered plans (per-seat base) with usage-based overages or add-ons. Captures the best of each model while managing the complexity of billing for both.
Common hybrid combinations
- Seat-based base + usage overages (Datadog, Snowflake)
- Tiered plans + per-feature add-ons (HubSpot, Intercom)
- Freemium + per-seat paid tiers (Slack, Notion)
- Base subscription + success fee (outcome-based)
Watch out when
- Billing complexity becomes a sales friction point
- Customers can't predict their monthly cost
- Engineering cost to support multiple billing streams
Revenue properties
- Highest ceiling for expansion revenue
- Most complex to model and forecast
- Requires robust billing infrastructure (Stripe Billing, Chargebee)
Real examples
Datadog (per-host/month + per-feature add-ons), Snowflake (compute credits + storage), AWS (hundreds of usage-based services)
Side by side
All 7 models compared
| Model | Revenue predictability | Expansion revenue | Implementation complexity | Best customer fit |
|---|---|---|---|---|
| Per-seat | Team-based B2B tools | |||
| Usage-based | APIs, infra, AI tools | |||
| Flat-rate | Niche tools, single segment | |||
| Tiered | Most modern B2B SaaS | |||
| Freemium | PLG, collaboration, viral tools | |||
| Per-feature | Established SaaS with upsell opportunities | |||
| Hybrid | Scale-stage SaaS, enterprise-heavy |
FAQ