A commitment is only worth what it actually saves against the rate you would otherwise have paid. This is how to track commitment ROI properly: the counterfactual, the two health metrics, and the report that lets you defend the next purchase.
To track commitment ROI you measure the realized savings a reservation, savings plan, or committed use discount produced against the on-demand cost you would otherwise have paid, then weigh it against what the commitment cost you, including any capacity you reserved but did not use. It sounds obvious, but most teams never do it, which is why so many commitment programs run for years on faith rather than evidence.
This guide belongs to the complete guide to cloud commitment management, where the buying order and instrument choice are covered. Here the focus is the back half of the loop: proving, in dollars, that the program earns its keep. Without that proof you cannot defend the next renewal to finance, and you cannot tell an over-committed portfolio from a healthy one.
Commitment ROI is meaningless without a baseline. The right baseline is the counterfactual: what the same usage would have cost at on-demand rates if you had bought no commitment at all. Every major provider's cost tooling exposes this, AWS Cost Explorer reports savings plans and RI net savings against on-demand, Azure and GCP report the equivalent for reservations and CUDs. Pull the on-demand-equivalent cost for the usage your commitments covered, and you have the gross number to measure against.
Be careful that the counterfactual reflects rightsized usage. If you committed before rightsizing, the on-demand counterfactual is inflated by the oversized instances, which flatters the ROI. This is one more reason the method puts rightsizing first, covered in why you should rightsize before you commit.
Gross savings overstate ROI because they ignore the capacity you paid for but never used. Realized ROI subtracts the cost of unused commitment from the gross saving. A savings plan with 80 percent utilization is paying for a fifth of its commitment with nothing to show, and that waste, the hidden cost of idle commitments, comes straight off the return.
Realized commitment ROI = (on-demand-equivalent cost of covered usage − actual committed cost − cost of unused commitment) ÷ actual committed cost. The middle term is the rate discount you captured; the third term is the penalty for over-committing.
ROI is the outcome; coverage and utilization are the levers that drive it, and they must be read together. Coverage tells you how much eligible usage is on a committed rate, low coverage means uncaptured savings. Utilization tells you how much of what you committed you actually used, low utilization means over-commitment. The full treatment is in coverage and utilization: the two numbers that matter; for ROI tracking, the discipline is to never report one without the other.
We build the ROI view that nets realized savings against idle commitment, account by account, so you can defend every renewal. On the performance model, if we do not save you money, there is no fee.
Get a commitment audit →In any organization with linked accounts, a commitment bought by one team can cover another team's usage, which makes raw account-level numbers misleading. Blended vs unblended rates explains the trap: a consolidated bill blends the shared discount across accounts, so the account that benefited and the account that paid for the commitment can look identical. For honest ROI you track at the consolidated level for the program total, and use unblended rates to attribute the saving back to the usage that earned it.
The ROI view only changes behavior if it is reported regularly and consistently. Build a monthly commitment ROI report that shows realized savings against the counterfactual, coverage and utilization trends, and a forward view of upcoming expirations so renewals are never a surprise. This is the artifact that turns commitment management from a faith-based purchase into a defensible program, and it feeds directly into forecasting commitment needs for the next cycle. For finance audiences, pair it with the framing in how to report cloud cost to the CFO.
On the SaaS-on-AWS engagement, tracking realized ROI monthly is what let us hold savings-plan utilization above 98%: every month the report flagged any drift early, so coverage was trimmed before idle commitment ate into the return. The discipline of measuring is what protected the 33% reduction over time.
Tracking ROI closes the commitment loop. Read the complete guide to cloud commitment management for the full discipline, and download The Commitment Strategy Playbook: RIs, Savings Plans, CUDs for the worksheets, including the ROI template. When you want the measurement run for you continuously, see our commitment management service.
New commitment instruments, FOCUS changes, hyperscaler pricing shifts, and the plays that actually move a bill. No schedule, no filler.