SaaS Pricing Models: Per-Seat, Usage, Tiered or Hybrid?

The best SaaS pricing model is the one your buyer already understands and your sales motion can actually sell. That sounds obvious, but I have watched founders agonise over per-seat vs usage vs tiered vs hybrid like it is a moral decision, when really it is a fit question. In 5+ years selling B2B SaaS and closing everything from €500 monthly deals to a single €120K contract, the pattern I keep seeing is simple: pricing goes wrong not because someone picked the wrong model, but because they picked a model that fought their motion instead of feeding it.

So let me walk you through the four saas pricing models the way I would over a coffee, with the actual trade-offs nobody puts on the pricing page. No frameworks for the sake of frameworks. Just what each one does to your revenue, your forecast, and the poor human who has to close the deal.

The four saas pricing models, and what each one actually costs you

Every pricing structure is really a bet on what your value scales with. Get that mapping right and pricing sells itself. Get it wrong and your best rep spends every call explaining why the price makes sense, which is the worst possible use of a sales conversation.

Here is how I think about the four, stripped of the consultant fog.

• Per-seat. You charge per user. Slack, most CRMs, basically every collaboration tool. Value scales with how many people touch the product.
• Usage-based. You charge for consumption. API calls, messages, GB stored, rows processed. Twilio, Stripe, most infra. Value scales with activity.
• Tiered. You bundle features and limits into named packages at fixed prices. Starter, Pro, Enterprise. Value is packaged, not metered.
• Hybrid. A base platform fee plus a usage or seat component on top. Where most serious B2B SaaS ends up eventually.

Per-seat: predictable, sellable, and quietly leaking value

Per-seat is the easiest model to sell and the easiest to forecast, which is exactly why so many founders default to it. Your buyer knows how many people they have. You know your ACV the moment you know the headcount. Renewals are clean. Finance loves it.

The problem shows up later. Per-seat disconnects price from value the moment usage and headcount stop moving together. A customer who gets enormous value from your product but only needs three logins pays you almost nothing. Worse, per-seat quietly punishes adoption: every new person your champion wants to add costs them budget, so they ration access, and rationed access kills expansion and stickiness. You end up incentivising your customers to use you less.

Per-seat works when the product genuinely is per-person, a tool each user opens daily to do their own job, and when seats naturally grow as the account grows. If that describes you, don’t overthink it. If it doesn’t, you are leaving expansion revenue on the table and you probably feel it at renewal.

Usage-based: aligns with value, wrecks your forecast

Usage-based pricing is the darling of the last few years and for good reason. When your value maps to consumption, it is the fairest model there is. The customer pays in proportion to what they get. Small users start cheap and grow into big bills without a single upsell call. Product-led growth loves it because someone can swipe a card and self-expand with zero human involved.

The catch nobody mentions on stage: usage-based pricing turns your revenue into a weather forecast. You no longer know what next quarter looks like, because your customers don’t either. A seasonal dip in their business is now a dip in your MRR, and you didn’t churn a single logo. It also makes some buyers deeply nervous. A CFO staring at an uncapped, variable invoice is a CFO who wants a spending cap, an alert, and a long conversation before signing. That friction is real and it slows deals.

The other trap is picking the wrong usage metric. If you meter something the customer can’t predict or doesn’t connect to value, you have built a pricing model out of anxiety. The metric has to be something they understand, can roughly forecast, and feel good about paying more for as it climbs.

Tiered: the workhorse, if you package it honestly

Tiered pricing is the most common model in B2B SaaS for a boring, good reason: it works, and it is easy to buy. Three named packages, clear jumps between them, a fixed number to put in a budget. The buyer self-selects into the tier that matches their size and ambition, and the good-better-best structure does a lot of quiet psychological work, that middle tier is where you want most people to land, and everyone knows it.

Where tiered goes wrong is packaging by accident instead of on purpose. Founders throw features into tiers based on gut feel, then wonder why nobody upgrades. The whole point of tiers is the upgrade trigger, the specific limit or feature a growing customer hits that makes the next tier a no-brainer. If your tiers don’t have obvious upgrade triggers, you have three price points and no expansion engine.

The second failure is gating the wrong things. Gate the features that correlate with company size or success, not the features people need to get value on day one. If you paywall the thing that makes your product work, you kill activation, and a customer who never activates never upgrades. I go deeper on this packaging logic in my guide to pricing B2B SaaS to maximise revenue, because tier design is where most of the money hides.

Hybrid: where grown-up SaaS ends up

Here is the thing nobody tells you early: most successful B2B SaaS companies don’t pick one model, they graduate into a hybrid. A base platform fee that guarantees you predictable revenue, plus a usage or seat component that captures upside as the customer grows. You get the forecastability of a fixed fee and the value-alignment of consumption, in one invoice.

Hybrid solves the specific pain that shows up around €1M to €5M ARR, when a single pricing axis stops being fair across your whole base. Your smallest customers feel overcharged by a flat fee. Your biggest ones feel like they are stealing from you. That gap between what you charge and the value delivered is pure lost revenue, and one dimension can’t close it. A base-plus-usage structure lets a tiny startup and a 500-person enterprise both feel like the price is reasonable, without you running two separate price lists.

The risk with hybrid is complexity. Two pricing dimensions is roughly the limit before your buyer needs a spreadsheet to understand their bill, and a pricing model that requires homework is a pricing model that loses deals. Keep the base simple, keep the usage metric singular and legible, and never make a prospect do algebra on a sales call. If they can’t repeat your pricing back to you in one sentence, it is too complicated.

How to actually choose, matched to your motion

Forget what is trendy. Your pricing model has to fit your sales motion, because the motion is what has to sell it every single day. A model that looks elegant on a whiteboard but fights your go-to-market is worse than a boring model that fits.

Here is the honest mapping I use with founders.

• Product-led, self-serve, credit card: usage-based or a simple tiered free-to-paid ladder. Anything that needs a human to explain will strangle self-serve conversion.
• Sales-led, mid-market, one champion: tiered or per-seat. Your buyer wants a fixed number for their budget and a clean upgrade story.
• Enterprise, multi-stakeholder, procurement: hybrid with a negotiated base. Predictability for their finance team, upside for you as they expand.
• Infra or API where value literally is consumption: usage-based, full stop, with a hybrid floor once you have enough scale to want revenue predictability.

When I ran pricing and packaging for the Venture Challenge program, the model followed the motion, 25 teams at a clean €5K each, a fixed price that matched exactly how those buyers thought about the spend, and it produced 170 qualified leads in 90 days. It wasn’t clever pricing. It was fitted pricing. That is the whole game.

One last thing, and I say this to nearly everyone: your pricing is not a decision you make once and carve into stone. It is a hypothesis you test, measure against win rates and net revenue retention, and revise. The founders who win aren’t the ones who guessed right on day one. They are the ones who kept adjusting the model to fit the motion as both evolved. If you want a second pair of eyes on that, this is exactly the work I do as a SaaS pricing consultant, mapping the model to the motion instead of copying whatever competitor happens to rank first on Google.

The mistake underneath all the others

Almost every pricing problem I get called in to fix traces back to one root cause: someone copied a pricing page they admired instead of pricing the value they actually deliver. Notion’s model works for Notion. Twilio’s works for Twilio. Neither will work for you unless your value happens to scale the exact same way theirs does, and it almost never does.

So start from your value, not from a screenshot. What does a customer gladly pay more for as they succeed with you? Answer that honestly and the model picks itself, per-seat if it is people, usage if it is activity, tiered if it is capability, hybrid when one axis stops being fair. Everything else is packaging, testing, and the discipline to keep adjusting.

If your pricing feels like it is fighting your sales team instead of helping them, that is a fixable problem and usually a fast one. Book a sales audit with me and we will pull your model apart, find the revenue leaking out of the wrong dimension, and rebuild it to fit the motion you actually run. Bring your current pricing page. I will bring the uncomfortable questions.