Tiered vs Usage-Based Pricing
When to use tiered pricing vs usage-based for your SaaS, with examples, revenue implications, and the hybrid models that win for many companies.
- How the two models work
- Side-by-side comparison
- Tiered pricing: revenue predictability, expansion friction
- Usage-based pricing: alignment with value, revenue volatility
- Hybrid pricing: the dominant pattern in 2026
- Use tiered pricing when...
- Use usage-based pricing when...
- Use hybrid pricing when...
- Switching from tiered to usage-based
- Common pricing mistakes
- What to do next
Tiered pricing charges customers a fixed fee for a bundle of features and capacity. Usage-based pricing charges based on actual consumption (API calls, data processed, events, seats added). Tiered is predictable but caps natural expansion. Usage-based scales perfectly with customer value but creates revenue volatility. Most successful modern SaaS companies use a hybrid that combines tiered base + usage components.
This article compares the two head-to-head, then explains when each one wins and why hybrid pricing has become the default for new SaaS companies in 2024-2026.
How the two models work
Tiered pricing offers 3-4 named plans (Starter, Pro, Business, Enterprise). Each plan has a fixed monthly or annual price and includes a defined feature set + usage allowance. The customer picks the tier and pays the same amount each month regardless of actual usage, until they outgrow the allowance and move up.
Usage-based pricing charges per unit consumed: per API call, per GB processed, per event tracked, per active user, per minute of compute. The customer pays for what they actually use. Some companies have no base fee; others have a small platform fee plus usage on top.
Use the SaaS Pricing Calculator to model both structures against your customer mix and see which produces more revenue with your unit economics.
Side-by-side comparison
| Dimension | Tiered | Usage-based |
|---|---|---|
| Revenue predictability | High | Variable |
| Customer-side predictability | High | Variable (concerning) |
| Expansion automation | Limited (tier upgrades only) | Strong (every unit of usage) |
| Net dollar retention typical | 100-110% | 120-140% |
| Buying process | Easy ("pick a plan") | Complex (forecast usage) |
| Sales cycle | Shorter | Longer (POC required) |
| Suitable for | Most SaaS | Infrastructure, API platforms, data tools |
| Examples | HubSpot, Asana, Zendesk | Snowflake, Twilio, AWS, Stripe |
Tiered pricing: revenue predictability, expansion friction
Tiered pricing is the default for most B2B SaaS. The reasons it dominates:
- Predictable bills make budget approval easier. Procurement can sign a PO knowing the exact cost.
- Predictable revenue makes financial planning easier for the SaaS company too. MRR is highly forecastable.
- Simple buying decision. The customer picks one of 3 plans; no forecasting required.
- Easy to discount. Annual prepay discounts, multi-year deals, and volume discounts are all simple structures around fixed tier prices.
The downside is that expansion is bounded. A customer on the Pro tier paying $499/month stays there for a long time, even if they get 5x more value from the product over a year. Net dollar retention for pure tiered pricing typically caps at 110-115%.
OpenView's 2024 SaaS pricing survey showed that tiered-only companies had median NDR of 105%, while companies with usage components had median NDR of 117%.
Usage-based pricing: alignment with value, revenue volatility
Usage-based pricing aligns spend perfectly with value. A customer using more of your product pays more, automatically. The category leaders in cloud infrastructure (Snowflake, Datadog, MongoDB Atlas, Twilio) all use heavy usage-based components.
The benefits:
- Land easily, expand naturally. Small initial commitment, usage grows as the customer succeeds.
- No expansion negotiation needed. Bills increase with usage; no sales rep involvement.
- NDR is structurally higher. 120-140% NDR is common for usage-based leaders.
- Aligns vendor incentives with customer outcomes. You make more money only when the customer uses more.
The costs:
- Revenue is volatile. A customer with declining usage produces declining revenue, sometimes sharply.
- Customer pushback on unpredictable bills. Finance teams hate not knowing what next month costs.
- Longer sales cycles. Enterprise prospects need to forecast usage before committing.
- Harder to comp sales. Reps cannot easily quote "ACV" if usage is variable.
Snowflake's stock famously sold off in late 2022 when customers optimized their workloads and reduced consumption, showing that usage-based revenue is genuinely more volatile than tiered subscription revenue.
Hybrid pricing: the dominant pattern in 2026
The model that has emerged as the winner for most modern SaaS combines both:
- Base tier with platform fee. Covers the core feature set and a generous usage allowance.
- Usage above the allowance. Customers pay per unit when they exceed the included quota.
- Optional add-on modules. Premium features unlocked at higher tiers.
Examples from leaders:
| Company | Tiered component | Usage component |
|---|---|---|
| HubSpot | Marketing/Sales/Service Hub tiers | Contact count, marketing email volume |
| Notion | Per-seat tiers | AI add-on per seat |
| Stripe Connect | Platform fee | Per-transaction percentage |
| Datadog | Per-host base | Logs, APM events, custom metrics on top |
| Linear | Per-user tier | (Mostly tiered, minor add-ons) |
| OpenAI API | Tiered access plans | Per-token usage |
The hybrid captures the predictability of tiered (most customers stay close to their committed base) while keeping the expansion of usage-based (heavy users naturally pay more).
If you are starting fresh in 2026, hybrid is the right default unless you have a specific reason to be pure tiered or pure usage-based.
Use tiered pricing when...
Pure tiered pricing is the right choice when:
- Customer value does not scale linearly with usage. Project management software, HR tools, and CRM all have value tied to team size and feature access, not to consumption of a measurable unit.
- Buyers strongly prefer predictable bills. SMB customers and many mid-market customers want to know exactly what they will pay.
- You serve self-serve buyers who need to make a fast decision. Three named plans on a pricing page convert better than a usage-based calculator.
- Your usage signal is weak or hard to measure cleanly. If you do not have a reliable way to meter consumption, do not charge for it.
- Sales cycles are short. Tiered pricing reduces friction in fast-moving deals.
Use usage-based pricing when...
Pure or heavy usage-based pricing is the right choice when:
- You sell infrastructure or developer tools. API platforms, data warehouses, observability tools, and compute services all map cleanly to usage.
- Customer value scales linearly with consumption. More API calls means more transactions processed, which means more revenue for the customer.
- You want to land small and expand automatically. Usage-based pricing creates a frictionless onramp that grows with the customer.
- Your gross margins are high enough to absorb volatility. Usage-based revenue is bumpier; you need 70%+ gross margins to make the smoothing work over a year.
- You serve customers who are sophisticated about cost forecasting. Engineering and data teams are usually fine with usage-based; sales and marketing teams often resist.
Use hybrid pricing when...
In other words, almost always for new SaaS. Hybrid works when:
- Most customers stay close to a predictable base, but heavy users could pay much more. This describes most B2B SaaS.
- You want NDR above 115% without creating budget anxiety for the median customer.
- You sell both to small teams (who need predictability) and large teams (who can absorb variable costs).
- Your product has a clear value metric you can meter (seats, contacts, events, AI tokens, transactions).
Switching from tiered to usage-based
Many SaaS companies that launched with pure tiered pricing add usage-based components 3-5 years in, usually around the time they want to compete in larger accounts and lift NDR.
The transition is non-trivial:
- Existing customers resist new variable charges on top of their predictable bill.
- Sales reps trained on tiered pricing struggle to sell consumption.
- Finance has to forecast revenue under a new model with limited historical data.
The cleanest pattern is to add usage charges only above a generous threshold and grandfather existing customers for 12 months. After grandfathering, migrate customers in waves at renewal.
Common pricing mistakes
- Pricing tiers too close together. If your Pro is $99 and Business is $129, the anchoring math does not work. Aim for 3-5x between tiers.
- Usage prices that are too high. A customer hitting a $50,000 monthly bill for unexpected usage will demand a refund and probably churn. Cap risk with predictable overage rates and notifications.
- No platform fee on usage-based. A pure pay-per-use model creates customers who try the product for $5/month forever. A small platform fee filters out non-buyers and stabilizes revenue.
- Hidden usage charges. If customers learn about usage costs after they have already integrated, you have lost their trust. Disclose everything on the pricing page.
What to do next
Model both pricing structures against your customer mix using the SaaS Pricing Calculator. Compare expected ARR per customer, revenue volatility (standard deviation across months), and NDR under each structure. Then check the unit economics against LTV to make sure your CAC payback works under whichever pricing model you pick.
The pricing model is one of the biggest strategic decisions in a SaaS business. Get it right at launch where you can; iterate where you have to.
Calculators referenced in this guide
Keep reading
Bootstrapping vs VC Funding: When to Choose
A clear-eyed comparison of bootstrapping vs venture funding for SaaS, including the operational, financial, and personal trade-offs.
B2B vs B2C SaaS: Metrics That Matter
A side-by-side look at which SaaS metrics matter for B2B vs B2C, why the benchmarks differ, and when to use which model.
Business & SaaS Disclaimer
This article is for educational purposes. Actual business performance varies based on many factors. SaaSCalcHub is not business or financial advice. Consult business advisors, CPAs, and consultants for your specific situation.
Last updated: Jun 2, 2026