The discount rate on a cloud commitment is largely set by the provider's published tiers, but the commitment size is the one variable you fully control, and it determines your real outcome. Commit below your steady floor and you leave reliable demand paying full on demand rates. Commit above it and the unused portion is still owed, whether through an idle Savings Plan, a lapsed Committed Use Discount, an unused Azure Reservation, or a Universal Credits shortfall. A deep discount on a commitment you cannot fill is worse than a smaller discount you use fully. The right size is the floor of demand you are confident will run for the whole term, set against a forecast you would defend to your CFO, not the average and not the optimistic peak.
Here is why size beats rate, how to find your defensible floor, and why it holds on every cloud.
Why does commitment size beat discount rate?
Consider the arithmetic. A 60 percent discount on a commitment you use only 70 percent of delivers a worse effective rate than a 40 percent discount you use fully, once the stranded portion is counted. Providers know buyers anchor on the headline rate, which is why a deeper tier often comes bundled with a larger commitment that quietly raises your utilization risk. The number that matters is the effective savings rate, the discount you actually realise after waste, and it is dominated by utilization, which is in turn dominated by sizing.
How do you find the size your forecast can defend?
Pull hourly or daily usage over a representative period and identify the floor, the level that runs through weekends, troughs, and quiet seasons. Right size workloads first so you are not committing against waste. Then set the commitment at or slightly below that floor, layering shorter terms where the forecast is less certain and longer terms only on demand you are confident persists. Aim for utilization in the high nineties rather than the highest coverage percentage, because the last few points of coverage carry the most stranding risk.
Does the same logic hold across every cloud?
Yes. The instrument changes but the arithmetic does not.
| Cloud | Instrument | What an oversize commitment costs you |
|---|---|---|
| AWS | Savings Plans, Reserved Instances | Idle hourly commitment still billed |
| Azure | Reservations, Azure Savings Plan, MACC | Unused reservation and MACC shortfall owed |
| GCP | Committed Use Discounts | CUD charged whether or not you use it |
| OCI | Universal Credits | Unconsumed credits expire at term end |
In every case the defence is the same: size to a defensible floor, keep utilization high, and treat coverage as a risk decision rather than a discount maximising one.
A worked example
A European SaaS company was about to renew its commitments at a deeper tier that required raising the commitment by a third, drawn by the higher headline discount. Modelled against a conservative forecast, utilization would have dropped into the low eighties, and the stranded portion erased most of the deeper discount. Holding the commitment at the defensible floor, accepting a slightly lower headline rate, produced a higher effective savings rate and removed the shortfall risk entirely. The realised saving beat the deeper tier by a clear margin. Figures are verified against billing data and anonymised.
Frequently asked questions
Is the discount rate or the commitment size more important?
How do you size a cloud commitment correctly?
Does commitment sizing work the same on AWS, Azure, GCP, and OCI?
Size your commitments to what you will actually use
We model the floor, size the commitment, and manage utilization so your effective savings rate is high and your shortfall risk is low, as an independent advisory that takes zero provider commissions. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on a Fixed Fee or a no risk Gainshare basis. Download the commitment negotiation playbook, read the cloud commitment negotiation guide, and see commitment coverage targets that make sense.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.