Customer success metrics, usage-based pricing: four of them stop working, because revenue is no longer fixed at signature. Net revenue retention moves with consumption instead of with renewals, a usage-weighted health score double counts revenue, churn has no cancellation event to detect, and the renewal date stops being the date the account is decided.
Customer success metrics, usage-based pricing and a renewal date that no longer means what it did: when your company moves from seats to consumption, credits or tokens, four numbers on the CS dashboard quietly stop describing the business. Nothing announces it. The dashboard keeps rendering, the health scores keep turning green, and the first sign of trouble is a renewal that arrives at half the commitment nobody saw coming.
This page is for the Head of CS or RevOps lead whose accounts run on consumption or hybrid pricing. It names the four metrics that break, gives the replacement for each with the arithmetic, and sets out the churn definition you have to write down before anybody can report a number. Public filings from consumption businesses supply the definitions; the practitioner quotes come from people already living with them.
- Under usage-based pricing the renewal date is not the risk date. The date a customer's committed balance runs out at the current pace is, and it usually lands in a different quarter.
- A usage-weighted health score is a revenue report wearing a colour, because under consumption pricing usage is the revenue. Score the shape of consumption instead: breadth, workloads, and pace against plan.
- Churn needs a definition when there is no cancellation. Pick one, write the threshold down, and report the dormant accounts separately from the cancelled ones.
- Benchmarkit and Pavilion put median gross revenue retention at 92% for usage-based pricing companies against 88% for subscription companies in their May 2025 report, on N = 225.
- Consumption businesses report net retention on trailing revenue, not on ARR at two dates, which is why their published figures sit ten or more points away from an ARR-based number on the same accounts.
Questions this page answers
- Our pricing is consumption based, how do CS metrics change?
- How do you calculate NRR with usage-based pricing?
- What is churn when a customer can go to zero and stay a customer?
- How do I build a health score for a credits or tokens product?
- When should a CSM intervene on a commit drawdown?
- Does usage-based pricing have better or worse retention than subscriptions?
- What should a CSM be measured on at a consumption company?
- Customer success metrics, usage-based pricing: which four break first?
- Why does NRR move with consumption instead of with renewals?
- What replaces the renewal date under usage-based pricing?
- How should a health score change when usage is the revenue?
- What counts as churn under usage-based pricing when nobody cancels?
- Which numbers should a consumption customer success team report?
- How does GainTrace handle usage-based pricing signals?
Customer success metrics, usage-based pricing: which four break first?
The commitment clock is the date a customer's committed balance runs out at their current consumption pace. Under usage-based pricing it replaces the renewal date as the date the account is decided: a clock that lands before the term ends means an early expansion conversation, and a clock that lands long after it means a smaller renewal that nobody has booked a meeting about.
Four customer success metrics break when pricing moves to consumption, and they break for one shared reason: revenue is no longer fixed at signature. A subscription tells you what a customer is worth for twelve months on the day they sign. A consumption contract tells you what they have committed to spend, which is a ceiling, a floor, or neither, depending on the contract.
| Metric | What it meant on subscriptions | What usage-based pricing does to it | Use instead |
|---|---|---|---|
| Net and gross revenue retention | A cohort's ARR now against its ARR a year ago, moved by renewals and upgrades | ARR becomes an estimate of variable spend, so the number moves every month with consumption and with holidays | Retention on revenue recognised across two twelve-month windows, on a named cohort |
| Health score | Usage as a proxy for value, weighted alongside support and sentiment | Usage is the revenue, so a usage-weighted score reports the invoice back to you and calls it health | Consumption shape: breadth of workloads, new use cases started, pace against plan, committed against on-demand mix |
| Churn | A cancellation event with a date, a reason code and an owner | No event exists. A customer can drop to near zero, stay contracted, and appear in the active count for a year | A written threshold: zero or near-zero consumption for a set number of days, reported beside contract non-renewal |
| The renewal date | The date the account is decided, and the anchor for every play | The decision happens when the commitment is consumed or abandoned, which is rarely the renewal date | The commitment clock, refreshed weekly, with plays hung off the clock instead of the calendar |
“A lot of the job is no longer just "relationship + product value"... jumping between product analytics, billing, CRM, and support tools... trying to make sense of weird usage patterns... figuring out whether an account is actually healthy or quietly drifting away...”
That description of the job is the honest version of what changes. The data a CSM needs moves from the CRM into billing and product analytics, and the question moves from whether the customer is happy to whether the customer is consuming what they bought at the pace they planned.
Why does NRR move with consumption instead of with renewals?
Net revenue retention under usage-based pricing is computed on revenue recognised, not on ARR at two dates, because there is no contracted run rate to compare against. Consumption businesses say so in their own filings.
“Product revenue is a key metric for us because we recognize revenue based on platform consumption, which is inherently variable at our customers' discretion, and not based on the amount and duration of contract terms.”
NRR = Cohort revenue recognised in the second year ÷ Cohort revenue recognised in the first year × 100
- Cohort
- every customer that consumed anything in the first month of the first year, kept in the calculation at zero if they stop
- Revenue recognised
- money consumed across twelve months, which is why a seasonal dip or a holiday quarter shows up in the number
- Why not ARR
- a commitment is a budget, not a run rate. Two customers on the same commitment can consume 60% and 140% of it
- What good looks like
- one basis, named in the metric, used every quarter. NRR vs NDR covers why the ARR version of the same accounts can read ten points apart
Published figures show the effect. For fiscal 2025, Twilio reported a dollar-based net expansion rate of 108% on a quarterly revenue cohort, Datadog about 120% on a trailing twelve-month ARR cohort, and Snowflake a net revenue retention rate of 125% on two years of product revenue. Each number is honest, and none is comparable with the others.
The retention picture for usage-based businesses is also better than most teams expect. In the Benchmarkit and Pavilion 2025 report, covering CY2024 and based on N = 225 for the retention charts, median gross revenue retention was 92% for companies on usage-based pricing against 88% for subscription pricing and 88% for hybrid, with the usage-based quartiles running from 88% to 96%. Median NRR for hybrid pricing companies was 110% on N = 228. The survey is self-selected, so read the direction and not the decimal.
“Usage-based pricing seems more logical, but it can also make costs unpredictable. Outcome-based pricing sounds attractive, although defining and measuring a successful outcome is not always simple.”
What replaces the renewal date under usage-based pricing?
The commitment clock replaces the renewal date as the anchor for customer success work under usage-based pricing. Two numbers build it: how much of the commitment is left, and how fast it is being consumed. Both live in billing, both refresh daily, and neither appears on a renewal calendar.
Days of commitment left = Remaining committed balance ÷ Average daily consumption over the last 30 days
- Remaining committed balance
- the contracted commitment minus what has been drawn down, in money or in credits, whichever the contract is written in
- Average daily consumption
- the last 30 days, not the contract average, because the recent pace is what the next quarter will look like
- What good looks like
- the clock lands shortly before the term ends. Landing early is an expansion conversation; landing months late is a renewal that will shrink
Pace = (Consumed to date ÷ Committed amount) ÷ (Days elapsed ÷ Days in term) × 100
- Consumed to date
- drawdown since the term started, from billing and not from product analytics, so it matches the invoice
- Days in term
- the contracted term, which for capacity contracts often runs one to four years and not twelve months
- What good looks like
- 100 means on plan. Under 80 for two consecutive months is the trigger for a conversation; over 120 is an expansion trigger, not a compliment
Worked example
A customer commits $120,000 for a twelve-month term starting 1 January 2026. By 31 May they have consumed $36,000: 30% of the commitment against 41% of the term elapsed, a pace of 73%. Average daily consumption over the last 30 days is $260, so the remaining $84,000 would take about 323 days to draw down, roughly 110 days past the end of the term. On a subscription this account is green until November. On consumption, the renewal is already smaller and the conversation belongs in June, when there are still six months to change the pace. These figures are illustrative; run them on your own contracts.
Two contract details change how the clock is read, and both are worth checking before you build anything. Unused capacity often rolls over at renewal on the purchase of more capacity, which turns an underconsuming customer into a renewal that looks flat and a business that is not growing. And consumption typically dips during holidays, which Snowflake names in its own filing as difficult to predict, so a December pace figure is not a trend.
“Help CSMs identify consumption rate and opportunities for early renewals and upsells.”
How should a health score change when usage is the revenue?
A usage-weighted health score double counts under usage-based pricing, because usage and revenue are the same event. The score tells you an account consumed a lot last month, which the invoice already said, and it says nothing about whether that consumption will continue. Score the shape of the consumption instead of its volume.
| Input carried over from subscriptions | Why it misleads on consumption | Score this instead |
|---|---|---|
| Total usage volume | It is the invoice. High volume this month says nothing about next month's budget owner | Pace against plan, and the direction of the last four weeks against the account's own baseline |
| Logins and active users | Automated pipelines and agents consume without anyone logging in, so an account can be busy and silent | Breadth: how many workloads, projects or use cases are live, and how many started this quarter |
| Feature adoption breadth | Useful, but it misses the money. Two features can be 90% of spend | Concentration: the share of consumption coming from the single largest workload |
| Contract value | The commitment is a budget, not what the customer is worth this year | Committed against on-demand mix, and the drawdown rate against the commitment |
| Support ticket volume | It still works, and it is more predictive here than on subscriptions | Keep it, paired with cost-to-serve, because a heavy consumer with a heavy ticket load can be unprofitable |
Concentration is the input teams most often miss. An account consuming $40,000 a month from one pipeline is one engineering decision away from zero, while an account consuming the same amount across nine workloads is embedded. The customer health score mechanics are otherwise unchanged, and the failure modes in why is my customer health score accuracy so poor apply here too, with the level-versus-change rule mattering more because consumption is noisy by the week.
“Every AI action has a real, variable cost attached, so the more a customer actually uses the feature, the more it costs the company, which is the opposite of how SaaS margins are supposed to behave as usage scales.”
That is why cost-to-serve belongs beside health on consumption accounts. A customer whose spend is growing on a workload you serve at negative margin is a revenue success and a gross-margin problem, and the CS team is usually the first to know.
What counts as churn under usage-based pricing when nobody cancels?
Churn under usage-based pricing needs a written definition, because the cancellation event that subscription businesses count does not exist. A customer can consume nothing for eight months, keep a live contract, appear in the active customer count, and never be counted as lost. Pick a definition, write the threshold into the metric name, and report the dormant accounts separately.
| Definition | Catches | Misses | Use when |
|---|---|---|---|
| Contract not renewed at term end | The formal loss, with a date finance recognises | Everything that happened in the eighteen months before it | You need a number that reconciles to the financial statements |
| Commitment lapses to on-demand only | Customers who stopped committing but still buy occasionally | Customers who quietly cut the commitment at renewal | Committed contracts are the business model and on-demand is the tail |
| Renewed at a lower commitment | Contraction, which on consumption is the main form of loss | Accounts that renew flat while consuming a fraction of the commitment | You want the number that matches gross revenue retention |
| Zero consumption for 60 consecutive days | Dormancy while the contract is still live | Seasonal customers, unless you exclude their known off-season | Usage is continuous for healthy accounts, for example infrastructure or messaging |
| Consumption below 25% of plan for two months | The slow fade, early enough to act on | Nothing much, which is why it produces false positives and needs a human | You want a working queue and not a reporting number |
Report two of these, never one. A financial churn number that only counts non-renewal will always look better than the business feels, and a dormancy number on its own will never reconcile with finance. Retention rate vs churn rate covers why the retention number and the churn number have to share a definition before they can be read together.
“Also curious if failed payments/expired cards get treated as a churn signal on your end, or if that lives in a totally separate process from the usage-based stuff”
Which numbers should a consumption customer success team report?
Report five numbers on consumption accounts, and put the commitment clock at the top of the list. The dashboard a subscription team runs on, health colour and renewal date, answers the wrong question here, so re-cut it in this order and give each number an owner.
Pull the drawdown from billing, not from product analytics
Consumed to date, remaining commitment, and the contracted term for every account. It has to match the invoice, because the customer's procurement team is reading the invoice.
Compute pace and the commitment clock weekly
Two columns beside every account. Sort by clock date and read the accounts whose clock has moved most since last week, rather than the ones with the lowest pace.
Write the churn definition down and publish both versions
One financial definition that reconciles to the accounts, one operational definition with a threshold in days or percent. Both appear in the same report, labelled.
Rebuild the health score on shape, not volume
Breadth of workloads, concentration of spend, pace against plan, committed against on-demand mix, support load. Drop total usage volume from the score entirely.
Move the CSM calendar off the renewal date
Plays trigger on pace crossing a threshold or the clock moving by more than 30 days, at whatever point in the term that happens. The renewal meeting becomes a confirmation, not a negotiation.
Fix the comp plan last, once the numbers are stable
A consumption quota on accounts that churn in and out is a measurement problem before it is a motivation problem. Get the pace and clock numbers trusted for a quarter first.
“Our pay structure is 80% fixed and 20% sales incentive. 20% is split between 60% GRR and 40% Consumption... GRR Measure = (ARR 12 months ago - CQ ARR) / ARR 12 months ago... Consumption Measure = Current month consumption / Consumption quota for the month”
Read that GRR formula closely: it computes the share of ARR lost, which is a churn rate, under the name GRR. The same post says the accounts keep churning in and out, so no CSM has held the same account for 24 months, which makes any cohort-based retention number for an individual CSM meaningless. Both problems are ordinary in consumption pricing and both are fixable on paper before anybody argues about the payout.
Before the consumption dashboard goes live
- Drawdown comes from billing and matches the invoice the customer receives.
- Every account has a commitment clock date and a pace figure, refreshed weekly.
- The churn definition is written down, with its threshold, and a financial version sits beside it.
- Dormant accounts are listed separately from cancelled ones and counted in neither by accident.
- Total usage volume has been removed from the health score.
- Rollover terms are recorded per contract, because they change what a flat renewal means.
- Seasonal and holiday dips are excluded from pace triggers by rule, not by judgement.
- Net revenue retention states its basis: revenue recognised or ARR, and the cohort it uses.
Our NRR calculator will run the retention side from a cohort export once the basis is settled. The clock and the pace columns are the two you will have to build, and they are worth more than anything else on the list.
How does GainTrace handle usage-based pricing signals?
GainTrace reads billing and product usage together, so drawdown against commitment sits on the account record next to the support and relationship signals. Customer health scores change against each account's own baseline instead of total volume, which is what keeps a consumption score from repeating the invoice, and triage surfaces the accounts whose pace moved this week while there is still term left to act on.
Frequently asked questions
Our pricing is consumption based, how do CS metrics change?
How do you calculate NRR with usage-based pricing?
What counts as churn when a customer can go to zero and stay a customer?
Is retention better or worse under usage-based pricing?
Should a CSM at a consumption company carry a consumption quota?
What does a health score look like for a credits or tokens product?
How this was researched
Definitions and disclosures for consumption revenue and net retention come from annual reports on Form 10-K filed with the SEC in 2026 for fiscal 2025 by Snowflake, Twilio and Datadog, read directly. Retention benchmarks by pricing model come from Benchmarkit and Pavilion's 2025 B2B SaaS Performance Metrics Benchmarks, covering CY2024, with N = 225 on the retention charts and N = 228 on the NRR chart; the survey is self-selected. Practitioner quotes come from 33,600 Reddit posts published between May 2024 and September 2026, of which 19 mention usage-based pricing and 12 mention consumption, and from 4,978 public G2 reviews of five customer success platforms, of which 7 mention consumption and one mentions usage-based pricing, which is itself a finding about how little the tooling addresses this model. The commitment clock, the pace formula, the four-metric taxonomy and the churn definition table are our own analysis, and the worked example uses illustrative figures.
- Snowflake Inc., Form 10-K for the fiscal year ended 31 January 2026 (SEC EDGAR)
- Twilio Inc., Form 10-K for the year ended 31 December 2025 (SEC EDGAR)
- Benchmarkit and Pavilion: 2025 B2B SaaS Performance Metrics Benchmarks
- r/CustomerSuccess: Are CS roles at AI/Infra/devtools companies becoming more like Customer Success Engineers?
- r/CustomerSuccess: Compensation Structure / Sales Incentive for Customer Success
- r/SaaS: Are AI agents making per-seat SaaS pricing obsolete?
Build the commitment clock this week, sort your accounts by it, and move the plays off the renewal calendar. Start free or book a demo.
See GainTrace first in your Google results
Add as a preferredsource on Google