Portfolio timing is the discipline of choosing when your cloud commitments expire so renewal works in your favour. Co termination aligns the end dates of large commitments and the enterprise agreement onto one date, concentrating the spend the provider stands to lose if you walk, which is what unlocks a better discount. Staggering does the opposite, spreading smaller commitments across the calendar so no single forecast miss strands a large block of capacity. AWS Savings Plans and Reserved Instances, Azure Reservations and the Azure Savings Plan, GCP Committed Use Discounts, and OCI Universal Credits each carry their own term and renewal clock, and the enterprise agreement sits above all of them with its own. Managing those clocks as one portfolio, rather than reacting to each as it arrives, is where timing turns into money.
Most estates never decide their renewal calendar; it accretes. A Savings Plan bought in March, Reservations renewed in July, an enterprise agreement signed in November, and suddenly there is no month without an expiry and no moment of real leverage. Here is how to take the calendar back.
Why does renewal timing create leverage?
A provider negotiates hardest when the most spend is genuinely in play. If a small Savings Plan lapses on its own, the provider risks almost nothing and concedes almost nothing. If a large enterprise agreement, the Reservations underneath it, and the next compute commitment all come up for renewal in the same window, the provider is suddenly defending a material share of your account on one date. That concentration is the difference between a polite renewal and a real negotiation.
The other half of leverage is the credible option to move. Timing only matters if you could actually act on it. A renewal date with a forecast you can defend, benchmark pricing in hand, and at least one workload you genuinely could place elsewhere is a date the provider takes seriously. The same date with no preparation is just an administrative deadline you will meet on their terms.
When should you align, and when should you stagger?
The answer is both, applied to different parts of the portfolio. Align the strategic layer: the enterprise agreement and the large, durable commitments that cover your stable baseline. Bringing those to a common renewal window creates the single high leverage moment worth preparing for. Stagger the tactical layer: shorter commitments on workloads that are still finding their shape, so a forecast miss expires gradually rather than all at once. A staircase of small expiries also lets you true up coverage continuously as confidence grows, instead of betting the whole portfolio on one annual guess.
Provider mechanics shape what is even possible. AWS Savings Plans and Reserved Instances carry one or three year terms you can ladder. Azure Reservations can often be exchanged, which gives you more freedom to reshape end dates mid term, and the MACC term sets the outer clock everything draws down against. GCP Committed Use Discounts run their own terms on top of automatic sustained use discounts. OCI Universal Credits draw down an annual pool whose renewal date you can anchor your other commitments around. Read each instrument before you assume the calendar is fixed.
How do you build a renewal calendar?
Start by listing every commitment and agreement with its start date, end date, term length, monthly value, and whether it can be exchanged or laddered. That single view usually reveals the problem immediately: expiries scattered across the year, large and small commitments treated identically, and an enterprise agreement renewal that nobody is preparing for until the quarter it lands. From there, decide a target renewal window for the strategic layer and ladder the new tactical commitments so they expire into that window or just before it, never randomly.
A scaling fintech had three Savings Plan tranches, two Reservation blocks, and an enterprise agreement, all expiring in different months. No single renewal ever carried enough weight to negotiate. Mapping the portfolio and laddering the next commitments so the enterprise agreement, the largest Savings Plan, and the core Reservations all renewed within one quarter created a concentrated moment, prepared three months ahead with a defensible forecast and benchmark pricing. The provider improved the discount tier materially against a credible threat to move a workload. The smaller tactical commitments stayed staggered so the firm kept the flexibility to true up coverage as it grew. Figures are verified against billing data and anonymised.
What are the timing traps to avoid?
The first trap is over alignment. If every commitment expires on the same day, a single bad forecast strands the entire estate and you renew everything under maximum pressure. Concentrate the strategic layer, not the whole portfolio. The second trap is auto renewal you did not schedule, which quietly resets a commitment at the old terms and erases the leverage moment you were building toward. The third is starting too late: the data, the benchmark, and the credible alternative take months to assemble, and a renewal you begin in its final weeks is a renewal you have already lost. The fourth is letting a long enterprise agreement term lock in workloads you already plan to rearchitect or repatriate, because a discount on capacity you are trying to leave is negative value.
Frequently asked questions
What is co termination in cloud contracts?
Should I align or stagger my cloud commitments?
How early should I start a renewal?
Take control of your renewal calendar
We map every commitment and agreement across AWS, Azure, GCP, and OCI, design the renewal timing that gives you leverage, and prepare each negotiation from the buyer side with zero provider commissions. Our guarantee: we reduce your cloud spend or we reimburse our service fee. Pricing is either a Fixed Fee scoped up front or Gainshare, a share of verified savings with no retainer and no risk.
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.