SaaS Pricing Models: Tiered vs Usage-Based vs Hybrid

Pricing is the single most underworked part of most SaaS products. Founders will spend six months on a UI refresh and six minutes on their pricing page. Then, a year in, they'll wonder why their ACV has stalled, why expansion revenue is flat, or why a new competitor is winning deals at 40% of their price.

The three dominant pricing models in modern SaaS — tiered subscription, usage-based, and hybrid — each create different incentives for buyers, different revenue dynamics, and different operational complexity. Picking the right one matters. Picking the wrong one is survivable but expensive. This post is a practical walk through how each model behaves in production, with guidance on which tends to fit which kind of product.

Model 1: Tiered subscription (the classic)

A tiered subscription model offers 2–4 fixed plans (Basic, Pro, Enterprise), each at a flat monthly or annual price, each including a bundle of features or usage limits. You pay $99/month for Pro whether you use it once or 1,000 times.

Where it works well:

• Products with predictable usage patterns where the value per user is stable
• B2B tools where buyers want predictable budgeting
• Products where feature differentiation is clear enough to map to tiers
• Early-stage products still figuring out their value metric

Where it breaks down:

• Power users extract enormous value from the cheap tier and underpay relative to value delivered
• Light users feel overcharged because they're paying for capacity they don't use
• Expansion revenue is lumpy — it only happens on tier upgrades, not continuous usage growth
• Pricing discussions during enterprise sales get stuck because the tier bundles don't match what the customer actually wants

Key metrics impact: ARR is clean and predictable. Net revenue retention comes almost entirely from logo expansion and plan upgrades, not usage creep. Churn risk is binary — customers stay or leave, with little middle ground.

Model 2: Usage-based (the scaler)

In a usage-based model, customers pay for what they actually consume — API calls, storage, compute, transactions, messages, active users, whatever your "value metric" is. Snowflake, Twilio, and Stripe are canonical examples.

Where it works well:

• Products where customer value scales directly with usage
• Infrastructure tools and APIs with clear consumption units
• Products targeting a wide range of company sizes (usage-based lets a tiny customer and a huge customer both feel the price is fair)
• Products where the customer's growth is a tailwind for your revenue

Where it breaks down:

• Buyers hate unpredictable bills. Unbounded usage-based pricing makes procurement teams nervous.
• Cash flow and forecasting become harder (your MRR chart has more variance)
• Low-usage periods (holidays, customer dips) mean revenue dips that a fixed subscription wouldn't
• If your value metric doesn't cleanly map to the customer's success, you create bad incentives

Key metrics impact: Net revenue retention can be much higher (well above 120% for healthy usage-based companies) because existing customers organically consume more. But your revenue has higher variance, and "ARR" becomes a fuzzy concept — some teams track run-rate revenue based on the last month instead.

The critical choice in usage-based pricing is the value metric. It has to be:

1. Something the customer feels like they get more value from as they consume more
2. Something the customer can understand and predict roughly
3. Something that tracks your actual cost to serve

Pick wrong and you'll fight about it with customers for years.

Model 3: Hybrid (the modern default)

Hybrid pricing combines a base subscription fee with usage-based components on top. You pay $500/month for the platform, plus $0.002 per API call above 100K, plus $50 per additional seat.

Most successful SaaS companies shipped post-2022 are using some variant of hybrid pricing. It's become the default for good reasons.

Why it works:

• Base fee gives customers predictability and gives you ARR you can bank on
• Usage component captures expansion value as customers grow
• Price discrimination across customer sizes is natural — small customers mostly pay the base, large customers mostly pay on usage
• Enterprise deals can be structured around committed usage with overage pricing, which finance teams understand

Where it gets tricky:

• Pricing page complexity can hurt conversion (how many variables does a prospect have to model?)
• Explaining the pricing in sales conversations takes more time
• Billing infrastructure is more complex (proration, usage aggregation, invoicing)
• Deciding the split between base and usage requires real analysis

Key metrics impact: Best of both worlds. Predictable base ARR, usage-driven expansion, net revenue retention typically lands in the 110–130% range for healthy hybrid companies.

How to pick

A rough decision flow we've used with clients:

1. Can you identify a clean value metric that scales with customer success? If yes, hybrid or pure usage is on the table. If no, stick with tiered.
2. Does your ideal customer include a wide range of company sizes? If yes, hybrid. A single tiered plan will either price out small customers or underprice large ones.
3. Do your customers value budget predictability? Most enterprise buyers do. Pure usage-based is harder to sell into large procurement without at least commit-and-overage structure.
4. How complex is your billing infrastructure tolerance? Usage-based and hybrid models require real investment in metering, aggregation, and billing. Tiered is much simpler to run.
5. Are you early-stage and still figuring out your value metric? Start tiered. You can migrate to hybrid once you've learned what customers actually value.

Common mistakes we see

After watching dozens of SaaS products work through pricing, these are the mistakes that come up most:

• Pricing based on features instead of value. "Pro has 10 more features than Basic" isn't pricing — it's feature gating. The question is "how much more value does a Pro customer get," not "how many features can we stuff into this tier."
• Not raising prices, ever. Companies afraid to raise prices as their product matures and the market accepts higher pricing leave enormous money on the table. Price is a product decision, not a commitment.
• Value metric that punishes success. If your pricing metric is "database rows stored," your customer's incentive is to purge their own data. That's bad for you and bad for them. Pick metrics that align incentives.
• Too many plans. Three tiers is plenty. Five is a sign you couldn't decide. Seven is a sign you've given up.
• Hidden annual-vs-monthly penalties. If you charge 12x the monthly price for annual, nobody will go annual. 20% off annual is a much better deal for both sides.

A note on pricing page UX

The pricing page isn't just a price. It's a sales tool. The best pricing pages we've shipped have:

• Clear "who this is for" under each tier (by company size or use case)
• Default to annual toggle (with a "or monthly" option visible)
• One tier visually emphasized as "most popular" or "recommended"
• A calculator or estimator for usage-based components
• Social proof near the pricing (logos, testimonials) to reduce "is this worth it" friction
• An "Enterprise: talk to sales" tier even if you mostly self-serve — it anchors the other prices and lets bigger deals not be capped

This is as much a design and product problem as a business problem. Our UX/UI design and SaaS development teams regularly work on pricing architecture alongside the core product.

The takeaway

There's no universal right answer. Tiered is simpler. Usage-based scales with customer growth. Hybrid balances the two and is increasingly the modern default for a reason. What matters is picking a model that matches your value delivery, your customer's buying behavior, and your operational capacity.

If you're working through pricing strategy for a new product or a model change on an existing one, we're happy to think through it with you — get in touch.