Usage-based pricing charges customers for what they consume rather than how many people have a login. It produces the highest net retention figures in software, and it introduces forecasting problems that per-seat businesses never face.
The decision is not about which model is modern. It is about whether value in your product scales with consumption or with headcount.
The core test
Ask what a customer getting twice as much value from your product looks like. If it means twice as many people using it, per-seat is the honest model. If it means the same three people processing twice the volume, per-seat punishes success and usage-based fits.
Infrastructure, messaging, payments, data processing and most API products fall clearly on the usage side. Project management, CRM, design tools and internal collaboration fall clearly on the seat side. The interesting cases are in between, and they usually end up hybrid.
Picking the billing metric
This choice matters more than the price itself. A good usage metric has four properties.
- It tracks value. The customer should feel that a bigger bill means they got more. Billing on API calls when the customer cares about successful outcomes breaks this — they pay for retries.
- It is predictable to the customer. If a buyer cannot estimate next month’s bill within a reasonable range, procurement will refuse the contract regardless of price.
- It is hard to game. Metrics customers can trivially batch or compress will be, and your revenue will fall without usage falling.
- It is cheap to measure. You will have to meter it accurately, show it in real time, and defend it in a billing dispute.
When no single metric satisfies all four, most companies land on a platform fee plus a consumption component — which is also the structure procurement teams find easiest to approve.
What usage-based pricing does well
Three effects, all real.
It lowers the barrier to starting. A customer can begin at $50 a month and grow, without a procurement cycle for seats they are not yet sure they need. This is why usage pricing and product-led growth pair so naturally.
It produces strong net retention. Expansion happens without a sales conversation. Companies on consumption models routinely report net revenue retention well above 120%, because every customer who grows pays more automatically.
It aligns incentives. You make more when the customer does more, which makes adoption work genuinely mutual rather than a vendor-side obsession.
What it does badly
Revenue becomes hard to forecast. A seasonal customer base means revenue that swings 20% between quarters with no change in the business. Boards dislike this, and so do lenders.
Downside is unbounded. When customers cut spending, your revenue falls immediately and without a cancellation. Per-seat contracts at least hold until renewal; consumption revenue can halve in a month.
Bill shock creates churn. A customer who gets an unexpected invoice four times larger than last month will not celebrate their growth. Spend alerts, soft caps and an in-product usage meter are not optional extras — they are the difference between expansion and an angry cancellation.
Sales compensation gets complicated. What exactly did the rep sell? Most companies end up compensating on committed spend rather than realised consumption, which reintroduces a negotiation that the pricing model was supposed to remove.
The hybrid that most companies arrive at
In practice, a large share of successful consumption businesses are not purely consumption. The common structure has three parts: a platform fee that covers the baseline and makes revenue forecastable, an included allowance sized to typical usage, and a clearly priced overage rate above it.
This keeps the expansion mechanics of usage pricing while giving finance a floor and giving the customer a predictable base. It also gives you something to discount in an enterprise negotiation that is not the unit rate.
Migrating an existing customer base
Changing pricing on customers you already have is the hardest part, and the most common cause of self-inflicted churn.
- Model the winners and losers first. Run every existing account through the new pricing. If more than a fifth would see a significant increase, the structure needs work before the communication does.
- Grandfather with a deadline, not forever. Twelve to eighteen months on the old plan is generous; permanent grandfathering creates a tier you will maintain for a decade.
- Lead with the customers who win. Move accounts that will pay less first. They become references, and the change arrives in the market as a reduction rather than an increase.
- Give everyone a calculator. Not a pricing page — an actual tool fed by their real usage history showing what they would have paid last quarter. Nothing defuses anxiety faster.
The pricing page itself needs rethinking too, since consumption pricing is harder to present than three columns of features. Our notes on pricing page best practices cover the patterns that work.
What finance needs before you ship it
Usage pricing moves work from the sales team to the finance and engineering teams, and the work is not optional.
Metering has to be accurate and auditable. You will have billing disputes, and the only acceptable answer is a per-event log the customer can inspect. Build the usage export before the billing logic, not after.
Revenue recognition gets more complex. Committed spend drawn down over a year, overage billed in arrears and credits carried forward all have accounting treatments. Involve whoever signs off the accounts before the model is final, not when the auditor asks.
Forecasting needs a new method. Per-seat businesses forecast from contracts; consumption businesses forecast from cohort usage curves. Expect the first two quarters of forecasting to be poor, and say so in advance rather than being surprised by it.
Collections change shape. Variable invoices fail more often than fixed ones, because they exceed pre-approved purchase order amounts. Budget for a higher rate of billing exceptions.
Communicating the bill
The difference between a consumption product customers trust and one they resent is almost entirely about communication, and it comes down to four surfaces.
- A live usage meter in the product. Current period consumption, projected bill at current rate, and how that compares to last period. Visible without hunting for it.
- Threshold alerts. At 50%, 80% and 100% of whatever the customer considers normal, to whoever owns the budget rather than only the admin who signed up.
- An itemised invoice. Not a single line saying “usage”. Volume by category, rate applied, and the total, so a finance team can reconcile it without emailing support.
- A spending cap the customer controls. Even a soft one. The ability to set a ceiling is what makes procurement comfortable approving a variable contract at all.
Companies that get these four right see consumption pricing drive expansion. Companies that skip them see it drive support tickets and, eventually, churn.
Frequently asked questions
Does usage-based pricing increase churn?
Logo churn often falls, because customers can scale down instead of leaving. Revenue volatility rises, which can feel like churn in the numbers even when no one has cancelled.
Can a per-seat product add usage pricing later?
Yes, and adding a usage component alongside seats is usually easier than replacing them. The common path is to meter one high-value action and charge for it above an included allowance.
How do enterprises buy consumption products?
Almost always as a committed spend contract: an agreed annual amount drawn down by usage, often with a discount for committing. This gives procurement a fixed number and gives you forecastable revenue.
What happens to the sales team?
The motion shifts from closing seats to landing an initial commitment and then driving adoption. Compensation usually moves to committed spend plus a component on net expansion.
