Consumption-based licensing: pay-as-you-go, commit and credits compared.
Consumption pricing moves 20–40% of a typical enterprise contract out of predictable subscription fees and into variable usage charges. This note explains how the metering models work, where the cost risk actually sits, and how to negotiate a commitment that protects the budget rather than the vendor.
Consumption pricing is sold as fairness — you pay only for what you use — but the mechanics favour the vendor, because the meter runs in their system, the commit is set against your forecast, and the overage rate is the one number buyers most often fail to negotiate. The structurally safe position is to commit conservatively to a floor you are certain to exceed and negotiate the overage rate down, because undercommitting is cheap to correct and overcommitting is not.
01 Key findings
Consumption spend is an output, not an approval. Your bill is no longer a fixed line you signed off; it is the result of a meter you do not fully control, reconciled after the fact through ordinary operational drift — idle resources, retrying integrations, log verbosity left high.
The risk is asymmetric by design. Undershoot the commit and the prepaid shortfall is pure waste; overshoot it and the excess bills at an overage rate typically 20–50% above your committed rate. The buyer loses on both sides of an inaccurate forecast; the vendor is protected on both.
The headline discount is quoted against the commit. That gives the vendor every incentive to inflate the committed volume. Convert every offer into effective price per unit at your realistic usage, not the committed usage, before comparing tiers.
Match the model to the usage shape. Variable, spiky or seasonal demand genuinely favours consumption; steady, predictable demand favours a committed subscription. Most large estates are a blend and should be priced as one.
Consumption contracts erode at renewal. The vendor resets your commit off a peak month rather than your steady-state run rate. Walk in with your own usage baseline, separated from temporary spikes, and commit to the baseline.
02 Metering models
Vendors meter consumption in four broad ways, and each shifts cost risk differently. The unit is always cheap to generate and expensive to govern, so spend climbs through operational drift rather than deliberate buying decisions.
| Model | Metered unit | Typical vendors | Main buyer risk |
|---|---|---|---|
| Compute / resource | vCPU-hours, GB-hours, nodes | AWS, Google Cloud, Azure | Idle and orphaned resources still meter |
| Transaction / event | API calls, documents, messages | Twilio, Stripe, integration platforms | Spikes from one bad integration |
| Data volume | GB ingested, stored, or egressed | Datadog, Snowflake, Splunk | Ingest grows faster than value |
| Active record / object | Monthly active users, rows, tables | ServiceNow, Salesforce add-ons | Cleanup lag inflates the count |
Most enterprise consumption deals are not pure pay-as-you-go. They pair a committed minimum — paid whether or not you use it — with an overage rate for anything above the commit, so a buyer carries both the risk of overcommitting and the risk of a punitive rate for going over.
03 Where the cost risk sits
The asymmetry is the point. Commit to 100 units and use 70, and you still pay for 100 — the prepaid shortfall is pure waste. Commit to 100 and use 140, and the extra 40 bills at the overage rate. The buyer loses on both sides of an inaccurate forecast while the vendor is protected on both. The instinct to commit high in exchange for a deeper headline discount is usually a mistake, because the discount applies to a number you may never reach.
Vendors set the committed minimum against an optimistic forecast, then price overage at the undiscounted list rate. Undershooting wastes the prepaid amount; overshooting costs full price. Negotiate the commit down to the floor you are certain to hit, push the discounted rate to apply to all consumption rather than only the committed tier, and cap the overage rate so a single usage spike cannot bill at three times your effective price.
04 Pricing the commitment
The headline discount is quoted against committed volume, which gives the vendor an incentive to inflate the commit. A 30% discount on a $2M commit sounds better than a 22% discount on a $1.4M commit — but if real usage is $1.3M, the smaller commit is cheaper in absolute dollars and carries far less prepaid waste.
Always convert the offer into effective price per unit at your realistic usage, not at the committed usage, before comparing tiers. This is the same discipline covered in our guide to contract benchmarking methodology: the comparison that matters is effective unit price, not headline discount percentage. The vendor's spreadsheet is built to make the largest commit look like the best value; yours has to expose what each tier actually costs at the volume you will really hit.
05 Cost curves vs subscription
The cost of getting the commit wrong is easiest to see in effective price per unit. Take a platform metered at a committed rate of $0.80/unit with a $1.20 overage rate. The chart shows what the same 760,000 units of real usage actually cost under two commitment strategies:
The conservative buyer pays the committed rate on 700,000 units and the overage rate on only 60,000 — an effective $0.83, a fraction above the committed rate. The buyer who chased the deeper discount on the larger commit pays for the full million and lands at $1.05, well above the rate they signed for. The same real usage costs the conservative buyer roughly 21% less. Consumption is genuinely better for spiky, seasonal or early-life workloads where a fixed subscription forces you to pay for a peak you rarely hit; it is worse for steady demand, where a subscription or reserved commitment locks in a lower unit price and removes the variance.
06 Negotiation levers
Five levers move a consumption contract in the buyer's favour. They sit inside the broader renewal discipline in our software contract negotiation guide, and they matter most at renewal, when the vendor will try to reset the commit upward off a peak month.
Set the commit at your confident floor, not your hoped-for ceiling, so prepaid waste is structurally impossible.
Secure the committed discount rate on all consumption including overage, removing the penalty for growth.
Win rollover so unused committed volume carries to the next period rather than expiring, softening the cost of a conservative commit.
Cap year-over-year increases on the per-unit rate, because a consumption contract with an uncapped rate is an open-ended liability.
Secure usage visibility and alerting in writing, with the vendor obligated to provide real-time consumption data — you cannot govern a meter you cannot see.
Beyond the committed and overage rates, a consumption contract carries a second layer of charges buried in the metering definitions: data egress that can exceed the cost of the compute that produced it, premium support metered as a percentage of consumption, minimum charges per transaction, and rounding rules that bill partial units as whole ones. Demand the full metering specification in writing and model a realistic month against it — the effective price is the rate plus every one of these charges.
07 Model-selection framework
Four considerations decide whether a workload belongs on a consumption meter, a committed subscription, or a blend. Weight them to your situation before signing.
Usage shape
Spiky, seasonal or early-life demand favours consumption; steady, predictable demand favours a committed subscription that locks a lower unit price. Match the model to the shape rather than forcing one model on the whole estate.
Forecast confidence
The narrower your confidence interval on next year's usage, the safer a larger commit becomes. Wide uncertainty argues for a low commit and negotiated overage protection rather than a deep discount on a number you may miss.
Governability
Meters you can tag, alert on and shut down are safe to run hot; meters with no showback discipline drift upward unchecked. Weight governability before committing to any usage-metered unit.
Blend and staging
Most large estates carry a durable baseline plus a variable layer. Price the baseline as a committed subscription and the variable layer as consumption, rather than paying subscription rates for spikes or consumption rates for steady load.
08 Our recommendation
Your workload is spiky, seasonal or early in its life and a fixed subscription would force you to pay for a peak you rarely hit. Commit to the confident floor, negotiate overage down, and put alerting and tagging around the meter before the first bill.
Your usage is stable and predictable. A committed subscription or reserved commitment locks a lower unit price and removes the variance — a vendor pushing pure consumption on a steady workload is selling you variance you do not need.
You carry a durable baseline plus a variable layer. Price the baseline as a subscription and the spikes as consumption, and hold the vendor to effective unit price across both rather than a single headline discount.
09 Renewal and guardrails
Consumption contracts erode at renewal in a way subscriptions do not, because the vendor resets your committed minimum off your peak usage during the term rather than your steady-state run rate. A quarter where one project drove usage high becomes the anchor for the next commit. The defence is to walk into the renewal with your own usage analysis showing the durable baseline, separated from temporary spikes, and to commit to the baseline — the same erosion mechanism covered in our discount erosion at renewal guide.
Because consumption spend is operational, the controls that protect it are operational too: tagging and showback so every metered unit has an owner, automated alerts at 50, 75 and 90% of the committed volume, scheduled shutdown of non-production resources, and a monthly review of the top consuming workloads. These turn a runaway meter into a managed one.
Pressure-test a consumption deal before you sign
Our vendor negotiation practice models your usage curve, sets the commit, and negotiates the overage protections that keep variable spend predictable.
The Licensing Edge
Weekly cloud and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.