Full narration of the briefing. Click a section heading to jump the player to that moment.
Two customers sign the same ten million dollar commitment at the same twenty percent discount. One of them is comfortable. The other is a million and a half dollars short before anything goes wrong. The difference is one sentence about how the commitment is measured.
It is the least discussed term in the whole agreement, and it moves more money than the discount rate people spend months arguing about.
The commitment retires on net spend. That means what you actually pay AWS after your discount, not what you would have paid at list. So your discount does not help you retire your commitment. It makes it harder.
Do the arithmetic. A ten million dollar commit at ten percent needs about eleven point one million of list consumption to satisfy. At twenty percent it needs twelve and a half million. The deeper your discount, the more gross usage you must generate to stand still.
Which is why buyers who model it backwards get caught. They look at eleven million of current spend, sign a ten million commit, feel safe, and are short by year two. Ask for gross measurement in writing. It is negotiable, it is rarely requested, and for most mid sized buyers it is worth more than two or three points of discount.
Now hold that next to the support bill. AWS support is charged as a percentage of your monthly charges, and AWS publishes the basis in its own words: gross AWS charges, before any discounts or credits are applied. So there it is. Your commitment retires on net, which is the base that hurts you.
Your support bills on gross, which is also the base that hurts you. AWS uses whichever measure is worse for the customer in each place, and both are entirely legitimate readings of the same contract. The practical effect is that your effective support rate rises as your discount improves. Win a bigger discount and support becomes a larger share of what you actually pay.
Nobody models that, and it is the reason a small customer can win an EDP whose discount is quietly consumed by mandatory support.
The ramp only goes one way. Commitments can stay flat or rise year over year, never fall. And AWS's opening ask typically runs fifteen to thirty percent above the customer's own modeled spend, with year one often built on roughly twenty percent growth over your trailing six months. The counter is a back weighted ramp: year one at or below what you can prove today, with the growth in years two and three where your migration actually lands.
A ramp you beat is leverage at every review. A front loaded ramp is a shortfall you scheduled for yourself while you were still migrating.
Shortfall is a bill, not a conversation. Miss the number and the difference is invoiced. Overspend and you bank nothing toward the next term. And early termination is worse than most buyers imagine: exit part way through a ramping multi year deal and the unused remainder can be owed in full.
So negotiate the relief before you negotiate the number. A cure period after measurement. A step down right of twenty five to forty percent on defined triggers like a divestiture, a business unit closing, or a serious AWS service failure. A mid term review.
Quarterly true ups instead of one annual surprise. None of it is standard. All of it exists in signed agreements.
Every one of these is a drafting question. AWS publishes no rulebook for this program: no discount table, no minimum, no eligible service list, no public cap. Everything is a contract term. Which cuts your way if you use it.
When the account team says something is just how the program works, ask them to point at the policy. There is no policy to point at. There is only your term sheet, and the four sentences you should insist on: how the commitment is measured, what retires it, what happens if you fall short, and what happens if the business changes.
One last point. At Redress Compliance we negotiate these agreements on pure contingency: twenty five percent of what we save you, and nothing saved, nothing paid. Next episode: the discount stack, and why fifteen plus forty five does not equal sixty.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a AWS negotiator