The discount is real. So is the trap.
Every major cloud provider sells the same deal: commit to spend a fixed amount over one to three years and get a percentage off. AWS calls it an EDP or a Private Pricing Agreement, Azure calls it a MACC, Google calls it a Commit Agreement. The mechanics are close enough to treat as one negotiation.
The pitch is simple. You are already spending the money, so why not get 10 to 20 percent off? The catch is in the word "commit". If you spend less than the number you signed, you still pay the number you signed.
Here is how to get the discount without buying your own forecast error.
1. Size the commit on what you will spend, not what you hope to
The rep will ask for your forecast and then propose a commit slightly above it. That is backwards. Your commit should sit below your confident floor, not at your target.
What to look for:
- Your trailing 12 months of actual spend, month by month, not the annual total
- Which workloads are planned to move off the platform, be re-architected, or be shut down
- Whether any large one-off project inflated last year's number
What to ask: "We will commit to $1.1M per year. Show us the discount at that level, and separately at $1.3M, so we can see what the extra commitment is actually buying."
2. Get the growth ramp, not a flat number
A flat three-year commit assumes year one and year three look the same. They never do. Providers can structure commits as a ramp, with a lower number in year one and a higher number in year three. Most reps will not offer it unless you ask.
What to ask: "Structure the commit as a ramp: $900k in year one, $1.1M in year two, $1.3M in year three. Same total, same discount tier."
If the rep says the discount tier is based on the annual number, ask for the tier to be set on the average across the term instead.
3. Check what counts toward the commit
Not every dollar you spend counts. Marketplace purchases, support fees, some third-party services, and certain regions are excluded by default in many agreements. If 20 percent of your bill does not count, your effective commit just went up by 25 percent.
What to look for:
- Whether marketplace spend counts, and up to what percentage
- Whether support plans count
- Whether spend from subsidiaries or separate accounts rolls up
4. Negotiate the shortfall clause before you need it
Every commit agreement has a clause for what happens if you underspend. The default is that you pay the difference. The good versions let you roll a shortfall into an extended term, or apply it against the next agreement.
What to ask: "Add a shortfall provision: if we are under by less than 15 percent at the end of the term, the balance rolls into a 12-month extension at the same rate rather than being invoiced."
This is the single clause that makes a commit safe to sign. A rep who refuses it is telling you what they expect to happen.
5. The discount is not the only lever
The percentage off is the number everyone negotiates, so it is the number with the least room. The other levers usually have more.
Things that cost the provider less than a discount point and are worth more to you:
- Credits for migration or proof-of-concept work, often $25k to $100k
- Support tier upgrade included, or at a fixed price instead of a percentage of spend
- Training credits and architecture reviews
- Price protection on specific services you depend on
- A named technical account manager
6. Time the signature
Cloud reps have quarters, and their quarters end in a predictable pattern. A commit that closes in the last two weeks of a quarter is worth more to the rep than one that closes in the first two weeks of the next.
You do not need to play games. You need to know when the pressure is on their side of the table, and make sure your internal approvals are ready to move in that window.
The bottom line
A cloud commit is you lending the provider certainty in exchange for a discount. Price the certainty correctly: commit below your floor, ramp it, make everything count, and get a shortfall clause. Then spend the negotiation on credits and support, where the provider has more room to give.
TermLift reads a commit proposal the way a procurement lead would: it flags the exclusions, the shortfall terms and the ramp you were not offered, and drafts the email that asks for them.