What Usage-Based Pricing Changes for Customer Success
Under a subscription model, a customer who stops using your product is a renewal risk. Under usage-based pricing, a customer who stops using your product is a revenue problem this month. That one difference changes a surprising amount about how Customer Success works.
More SaaS companies are moving to usage-based or hybrid pricing, where some or all of the bill depends on how much the customer actually uses. If your company is heading that way, CS is usually the team that feels it first.
Renewal stops being the big moment
In a classic subscription business, the calendar is built around the renewal date. CS spends months preparing, and the renewal is where revenue is won or lost.
With usage-based pricing, revenue is won or lost every month. A customer can stay under contract and still cut their spend in half by using less. The renewal still matters, but the real question is whether usage is growing, holding or quietly shrinking between renewals.
That shifts the job from protecting a date to managing a trend. It also makes a CS revenue pipeline more important, because expansion and contraction show up continuously instead of once a year.
Usage data finally means something
I've argued for a long time that logins are a weak signal, and that CS should focus on outcomes rather than activity. Usage-based pricing sharpens that point. The usage that matters is the usage the customer pays for, and it's tied directly to revenue.
That's good news for CS. Your health signals and your revenue signals start to line up. A drop in the metered activity is both a churn risk and a revenue dip, and it shows up in the data quickly. Teams that already predict risk from usage patterns have a head start.
Watch out for bill shock
The biggest new risk in a usage model is the surprise invoice. A customer's usage spikes, the bill jumps, and a happy customer becomes an angry one overnight. Even if the usage was valuable, nobody likes being surprised by a bill.
CS should get ahead of this. Know which accounts are trending above their usual spend, reach out before the invoice lands, and help the customer understand what drove the increase and whether it's worth it. Something like: "Your team's usage is up sharply this month because the second region went live. Here's what that means for your bill, and here's what they're getting out of it." That conversation builds trust. The surprise invoice spends it.
Forecasting gets harder
Subscription revenue is easy to forecast: you know the contract values and the renewal dates. Usage revenue moves around. For Finance, that makes CS insight more valuable, because the CSM is often the first to know that a customer is about to launch a new team, cut a program or change how they use the product.
That only works if CS and Finance agree on what they're measuring. Net revenue retention, gross retention and expansion all need clear definitions in a usage model, especially around what counts as contraction versus normal fluctuation. It's worth agreeing on those definitions with Finance before the first quarter where the numbers disagree.
What I'd change on a CS team
If my company were moving to usage-based pricing, these are the first things I'd adjust:
Put metered usage at the center of the health score, and alert on sustained drops, not single bad weeks.
Make adoption the core of onboarding, because in a usage model, adoption is the revenue.
Add proactive spend reviews for accounts trending well above or below their normal range.
Give CSMs visibility into billing data, so they're never surprised by what the customer sees.
Rethink CS targets around net revenue over time, not only renewal dates. That's a good moment to decide whether CSMs should carry a quota.
Usage-based pricing rewards the things good CS teams already care about: real adoption, real value, and early warning when either one slips. The difference is that now the results show up on every invoice.
If your company is moving toward usage-based pricing and you're working out what it means for CS, I'd be glad to help think it through.
