Hybrid pricing models: combining seats, usage, and tiers without confusing buyers

Every SaaS pricing model eventually runs into a wall. Flat pricing stops matching the range of customers a product serves. Seat-based pricing starts penalizing exactly the behavior a company wants to encourage: more users logging in and getting value. Usage-based pricing turns into a budgeting headache for buyers who need to forecast costs. None of these models is wrong on its own; they are just built for a narrower set of circumstances than most growth-stage SaaS companies eventually operate in.

That is why so many pricing pages that started as a simple three-tier ladder quietly evolve into something more layered: a base platform fee, a per-seat component, and a usage-based overage on top. This is what's usually meant by a hybrid pricing model, and it is becoming the default for products that serve a wide range of customer sizes and usage patterns.[1]

Why flat pricing breaks down first

Flat, single-price plans are the easiest to launch and the first to become a liability. A single price forces a company to guess at an "average" customer, and as the customer base diversifies, that average stops describing anyone. Small teams feel overcharged for a fraction of the value; larger teams find ways around usage limits because the price was never tied to how much value they were extracting. Founders often respond by adding one or two more flat tiers, which delays the problem without solving it, since the underlying issue is that a single, usage-independent number cannot track value across a growing range of customers.

Why pure seat-based pricing breaks down next

Seat-based pricing solves the "one size fits all" problem by tying price to headcount, and it works well for collaboration tools where more seats genuinely means more value delivered. But for products where value comes from data processed, transactions completed, or automation run rather than from how many people are logged in, seat pricing creates a strange incentive: customers restrict access to control cost, which suppresses adoption and makes the product look less "sticky" than it actually is. It also caps revenue growth from a company's best customers, the ones running more volume through the product without necessarily adding headcount.

Why pure usage-based pricing breaks down after that

Usage-based pricing fixes the adoption problem, since customers pay for what they consume rather than for who has access. But it introduces a different one: unpredictability. Finance teams that need to forecast a software budget for the next fiscal year do not want a number that could double if usage spikes. Bessemer Venture Partners' research on cloud software economics has noted that usage-based pricing tends to correlate with strong net revenue retention, but also with more revenue volatility quarter to quarter, which is a harder story for a buyer's CFO to sign off on.[2] Pure usage pricing also punishes customers in the early weeks of onboarding, before they have built habits that generate steady usage, which can hurt activation.

What a hybrid structure looks like in practice

A hybrid model combines these mechanisms deliberately rather than defaulting to one. A common structure looks like this: a base platform fee that covers a set number of seats and a baseline amount of usage, then a per-seat charge once headcount crosses that baseline, then metered usage charges for consumption above the included allotment. Some companies add a tiering layer on top, where the base fee and included usage both scale with plan tier, so an "essentials" customer and a "scale" customer have different starting allowances even before seats or usage overage kick in.

The goal of a hybrid structure is not complexity for its own sake. It is aligning each pricing dimension with the part of the product experience it actually reflects: seats for collaboration, usage for consumption, and a base or bundle for the platform value that exists regardless of how the product gets used. Done well, a hybrid model gives buyers a predictable floor (the base fee) and a fair ceiling (usage tracks actual consumption), which tends to be easier for both procurement and finance to approve than a model with only one lever.

Why this normally requires custom engineering

The reason more companies don't move to hybrid pricing sooner is not that they don't see the logic. It's that most billing systems are built around a single pricing dimension, and combining seats, tiers, and usage into one invoice typically means custom metering pipelines, proration logic for mid-cycle seat changes, and reconciliation between a usage database and a billing system that was never designed to talk to it. Engineering teams that could be building product features end up maintaining a home-grown billing layer instead, and every new pricing experiment becomes a multi-sprint project rather than a configuration change.

How a modular pricing engine avoids the rebuild

This is the specific problem a modular pricing engine is meant to solve. Revvly's modular pricing tools let a team configure usage-based, tiered, bundled, and regional pricing components without writing new billing code for each combination, so a hybrid structure like the one described above can be set up, tested, and adjusted as the business changes. Because pricing changes touch retention as directly as they touch revenue, it helps to make those changes with visibility into how they land: MRR, ARR, and NRR dashboards show the revenue effect of a new pricing structure as it rolls out, and AI-powered churn prediction flags accounts that show early signs of friction after a pricing change, before they become cancellations. Pairing pricing flexibility with that kind of visibility is what makes it possible to iterate on a hybrid model instead of treating the initial launch as final.

Communicating a pricing change well matters just as much as the structure itself. Customers who are moved into a new hybrid plan need context on why their bill will look different, and automated retention workflows can handle that outreach at the account level, rather than a single blanket email to the entire customer base.

Getting the sequencing right

Companies that move to hybrid pricing successfully tend to sequence it in a specific order: they identify which single dimension is closest to failing first (usually seats, since it's the most common starting model), they add the second dimension as a genuinely optional layer rather than a forced migration, and they give existing customers a grandfathering path rather than switching everyone over on the same day. Hybrid pricing is a structural change to how revenue is recognized and forecast, not just a page redesign, so treating the rollout with the same care as a product launch, complete with a phased plan and a way to measure the impact, tends to separate the pricing changes that stick from the ones that get reversed within two quarters.

Frequently asked questions

What is a hybrid pricing model? A hybrid pricing model combines two or more pricing mechanisms, typically a base fee or tier, a per-seat charge, and usage-based metering, into a single pricing structure, rather than relying on just one dimension.

When should a SaaS company move from a single pricing model to a hybrid one? Usually when the current model starts producing the wrong incentives: customers restricting seats to control cost, usage bills becoming too unpredictable for procurement, or a flat price failing to capture the real range of value different customers get from the product.

Does hybrid pricing require rebuilding a billing system? It often does with legacy or single-dimension billing tools, since most weren't built to combine seats, tiers, and usage in one invoice. A modular pricing engine is designed to support these combinations through configuration rather than custom development.

How do you avoid confusing buyers with a hybrid pricing page? Keep the base fee and included allowances visible upfront, and treat usage or seat overages as a clearly labeled add-on rather than burying them in fine print. The pricing page should let a buyer estimate their likely bill without needing a sales call.

Should existing customers be moved to a new hybrid pricing model immediately? Most companies grandfather existing customers for a defined period and communicate the change directly, rather than switching billing structures for the entire base on the same day.

Sources

1. OpenView Partners, 2023 SaaS Benchmarks Report.
2. Bessemer Venture Partners, State of the Cloud report.

Frequently asked questions