The strongest cloud commitment renewals start a full twelve months before the existing AWS Savings Plans, Azure Reservations, GCP Committed Use Discounts, or OCI Universal Credits expire. The reason is structural: discount leverage comes from a credible alternative, and building a credible alternative takes time. Twelve months is enough to refresh the usage forecast, benchmark current discount tiers, test whether workloads could move, and let the seller see that resigning on the same terms is not your only path. Start in the last quarter and you have surrendered all of that before the first call.
A renewal is a negotiation, not an administrative event. Here is how to use each quarter of the runway so you arrive at the table with options rather than a deadline.
Why does timing decide the discount?
Cloud sellers price against your alternatives. If your only realistic option at expiry is to resign because there is no time to do anything else, the seller carries no pressure to improve terms and every reason to let the clock run. The discount you receive tracks the credibility of your walk away option, and credibility is a function of preparation time. A forecast you can defend, a benchmark of what comparable buyers pay, and at least one workload you have genuinely scoped to move elsewhere all take months to assemble. Compress that into the final weeks and the seller, who tracks your renewal date precisely, simply waits you out.
The asymmetry is the point. The provider knows your commitment end date to the day. If you treat it as a surprise, you negotiate against a counterparty who has known the deadline for a year and prepared accordingly.
What does each quarter of the runway do?
Treat the twelve months as four working phases, each producing an artifact you will need at the table.
- Months 12 to 9, forecast. Rebuild the demand forecast from current usage and the product roadmap, not last cycle's number. Commitment coverage should follow a defensible forecast, so this is the foundation everything else rests on.
- Months 9 to 6, benchmark. Establish what discount tier your spend level and growth profile should command. Without a benchmark you cannot tell a good offer from a bad one, and the seller knows it.
- Months 6 to 3, options. Scope at least one credible alternative: a workload that could move to another cloud, a shift from commitment to on demand for volatile capacity, or repatriation of a steady base load. The option does not have to be exercised to have value, but it has to be real.
- Months 3 to 0, negotiate. Open the conversation with the forecast, the benchmark, and the option already in hand. The final quarter is for closing, not for discovery.
How does the runway change AWS, Azure, GCP, and OCI specifically?
The mechanics differ by provider, and the runway lets you act on each.
- AWS. Savings Plans and Reserved Instances expire on fixed dates, and an Enterprise Discount Program layered on top trades a multi year spend commitment for a tier. A year of runway lets you align the commitment layer and the agreement layer so they renew on terms you set rather than defaulting.
- Azure. Reservations can be exchanged, and a Microsoft Azure Consumption Commitment carries a shortfall clause where unspent commitment is still owed. The runway is where you reconcile drawdown against the MACC so you do not commit to a figure you cannot consume.
- GCP. Committed Use Discounts come in spend based and resource based forms with different flexibility, and enterprise agreements carry the same use it or lose it structure. Time lets you choose the CUD shape that matches a forecast you trust.
- OCI. Universal Credits renew as annual flex, and Support Rewards offset Oracle support fees. A runway lets you size the annual flex to real consumption rather than rolling last year's number forward.
These figures and structures are provider current as of 2026; verify the specific tier and clause language against each provider's current agreement before you commit.
A worked example
A European software company faced a renewal on a large committed spend agreement and historically resigned in the final month each cycle. We moved the process to a twelve month runway. In the first quarter we rebuilt the forecast and found roughly a fifth of the prior commitment covered capacity the company no longer used. In the next two quarters we benchmarked the discount tier and scoped a steady analytics workload that could credibly move to a second cloud. By the time the renewal conversation opened, the company committed only to the capacity it could defend, secured a better tier than the expiring agreement, and stopped paying for the retired fifth. The combined effect was a material reduction in committed spend with no loss of capacity the business actually needed. Figures are verified against billing data and anonymised.
Frequently asked questions
When should a cloud commitment renewal start?
Why does starting early improve the discount?
What if our usage forecast is uncertain?
Talk this through with us
We run cloud commitment renewals as a twelve month process across AWS, Azure, GCP, and OCI, building the forecast, the benchmark, and the credible alternative that win better terms. We take zero provider commissions and answer only to you. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on either a Fixed Fee scoped up front or a no risk Gainshare basis. Book a strategy call to scope it for your estate, and follow more analysis in The Cloud Spend Navigator.
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.