Enterprise discount negotiation is undergoing a structural shift: the discount that used to come from volume is increasingly coming from commitment. For decades, buying more meant paying less per unit — the more seats or licences you held, the deeper your tier. That model is being dismantled. From 1 November 2025, Microsoft prices cloud services under its Enterprise Agreement at a flat list rate regardless of whether you have 500 users or 50,000; discounts now depend on committed spend and multi-year adoption, not seat count. Understanding the difference between volume and commitment discounting — and which lever applies to which vendor — is now central to any negotiation, and it builds directly on our contract negotiation strategy master guide.
Volume vs Commitment: Two Different Discounts
A volume discount rewards how much you buy; a commitment discount rewards how much you promise to spend, and for how long. The two behave very differently in negotiation. Volume discounts are largely automatic and transparent — cross a threshold, earn the rate — which means there is little to negotiate beyond confirming the tier. Commitment discounts are the opposite: they are bespoke, opaque, and highly negotiable, because the vendor is pricing the certainty your commitment gives them. That is precisely where the leverage sits, as we explain in our guide to vendor negotiation leverage — the more certainty you offer, the more discount you can extract, provided you protect your flexibility in return.
| Mechanism | What it rewards | Typical discount | Negotiability |
|---|---|---|---|
| Volume tier | Quantity purchased | Set by published tier | Low — threshold-based |
| Commitment (AWS EDP) | Multi-year spend commitment | 30–50% off on-demand | High — bespoke |
| Commitment (Azure MACC) | Committed Azure consumption | Tiered by commitment size | High — bespoke |
| Service volume (e.g. CloudFront) | Usage of a specific service | +5–20% on that service, stacks | Medium |
The Commitment Trap
Commitment discounts are powerful, but they transfer risk from the vendor to you. An AWS Enterprise Discount Program commitment, sized correctly, captures a 30–50% effective discount against on-demand pricing — but a commitment sized to optimistic growth forecasts becomes a liability the moment actual consumption falls short, leaving you paying for capacity you never used. The discipline is to commit to the floor of your demand, not the forecast: size the commitment to consumption you are certain of, and let the rest stay flexible. The trade-off between commitment depth and flexibility is the same one we analyse in our guide to contract term length, where a longer commitment buys a deeper discount only if the exit and flexibility terms are negotiated alongside it.
A commitment discount is the vendor paying you for certainty. The mistake is paying for that discount with certainty you do not actually have — committing to forecast growth rather than to the demand floor you can stand behind even in a bad year.
Stack the Discounts You Are Entitled To
The largest discounts come from layering mechanisms that the vendor presents as alternatives. On AWS, an EDP commitment discount applies on top of Reserved Instances, Savings Plans, service-specific volume discounts and private pricing addenda — and a buyer with heavy use of a specific service such as CloudFront can capture an extra 5–20% on that portion, stacked on the EDP rate. Vendors rarely volunteer the full stack, so the buyer has to assemble it deliberately. One enterprise that bundled its EDP, support and Marketplace negotiations into a single conversation reached a 42% effective discount — well above what any single lever would have produced. Benchmarking each layer against market data, the discipline in our guide to enterprise software price benchmarking, is what tells you whether the stack is complete.
The same stacking logic applies beyond cloud. On a software agreement, the negotiable layers are the licence discount, the support rate, multi-year pre-payment terms, and any bundled-product concessions — and vendors habitually concede on the visible licence line while holding firm on the support and overage layers the buyer never thought to negotiate. Treat every layer as separately negotiable, and require the vendor to show the discount on each rather than a single blended headline number. A blended figure is designed to obscure which layers were genuinely discounted and which were left at list, and unpicking it is often where the last several percentage points of saving are found.
The Scale of the Prize
The numbers justify executive attention. For an enterprise spending $5 million or more a year on AWS, the difference between negotiated and non-negotiated pricing is typically $2–8 million per year — a recurring sum larger than most discrete IT projects. Yet because commitment discounts are bespoke and opaque, they are routinely left on the table by buyers who assume the vendor's first proposal reflects their best rate. It does not. The first proposal reflects the discount the vendor would prefer to give, and the gap to the achievable rate is exactly what a structured negotiation closes — the core of our IT procurement best practices. For the AWS-specific mechanics, our AWS EDP negotiation guide and the AWS vendor hub go deeper; for the Microsoft commitment shift, the Microsoft vendor hub tracks the post-November pricing model.
How to Approach the Negotiation
Treat volume and commitment as separate negotiations even when the vendor bundles them. Confirm the volume tier as a baseline, then negotiate the commitment discount as the real prize — offering the certainty of a multi-year commitment sized to your demand floor, in exchange for the deepest rate and explicit flexibility protections: the right to adjust the commitment for divestiture or material business change, and a cap on any shortfall penalty. Model the whole arrangement on a total-cost basis, as set out in our guide to total cost of ownership, so the discount is measured against the real long-term spend rather than the headline rate. To structure a volume-and-commitment negotiation for a specific renewal, request a confidential briefing, and ground the approach in our CIO Contract Governance framework.