The cloud commitment negotiation guide.

This guide covers the two layers of commitment, the instruments per cloud, where leverage comes from, and how much to cover.

What are the two layers of cloud commitment?

Enterprise cloud discounts come in two layers that stack. The first layer is resource commitments: AWS Savings Plans and Reserved Instances, Azure Reservations and the Azure Savings Plan, GCP Committed Use Discounts, and OCI Universal Credits. These discount specific usage in exchange for an hourly, capacity, or spend commitment over one or three years. The second layer is enterprise agreements: the AWS Enterprise Discount Program, the Azure MACC, GCP enterprise agreements, and Oracle Universal Credits at the portfolio level. These trade a larger, multi year spend commitment for an additional discount tier across the account. You negotiate the agreement, then place resource commitments underneath it. The Azure MACC carries a shortfall clause that makes the structure explicit: unspent commitment is still owed at the end of the term.

Which instruments does each cloud use?

The instruments differ in flexibility. AWS Savings Plans trade a lower headline discount for the freedom to move across instance families and regions, while Reserved Instances lock specificity for a deeper rate. GCP offers spend based and resource based CUDs with different scope, and sustained use discounts apply automatically without any commitment. OCI Universal Credits are fungible across services but the annual flex balance must be drawn down or it is lost. Knowing which instrument suits which workload is half the negotiation.

Where does negotiation leverage come from?

Leverage is not rhetoric, it is four concrete things. A credible forecast, because the provider discounts certainty and a forecast you can defend with billing history is worth more at the table than an aspirational number. Benchmark data, because knowing what comparable buyers pay sets a floor you can hold. Timing, because a renewal negotiated with twelve months of runway is a negotiation, and one started thirty days before expiry is a capitulation. And the real option of placing workloads elsewhere, because a provider that knows a workload can move to another cloud discounts differently than one that knows it cannot. None of these require bluffing. They require preparation, and they are why the same spend can earn very different discounts.

How much should you commit?

Coverage follows a defensible forecast, not the discount table. Picture your usage as a stable baseload with a variable layer on top. The baseload, the capacity you are confident will run for the whole term, is what you commit; the variable layer stays on demand so that a dip does not leave you paying for idle commitment. Chasing a higher discount tier by committing above the baseload is the most common and most expensive mistake, because the stranded commitment costs more than the extra discount saves. The right answer for most mature estates is well short of full coverage, with the exact line set by how confident the forecast is.

Where to go next

Build the forecast that the whole negotiation rests on in aligning commitments to a risk adjusted forecast, and learn the traps to avoid in the cloud negotiation mistakes that cost millions. The full negotiation framework is the cloud commitment negotiation guide, and the way commitments fit the wider program sits in the cross cloud cost optimization guide.

Take the next step on your cloud spend

We are an independent buyer side advisory that cuts public cloud spend across AWS, Azure, GCP, and OCI. We hold over $2.4B in annual cloud spend under management, take zero provider commissions, and deliver a 31 percent median reduction in the first 90 days. Our guarantee is simple: 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 to you.