Full narration of the briefing. Click a section heading to jump the player to that moment.
Buyers spend months on the discount percentage and minutes on the clauses around it. That is backwards. A deep discount on a commitment you cannot safely carry is a loan you took against your own forecast. So this episode runs the commitment in the order that actually protects you, and most of it comes from real agreements filed publicly as contract exhibits, not from anybody's opinion.
Fix the measurement basis before the number. By default the commitment retires on what you actually pay after your discount, which means the discount makes the commitment harder to hit. Ten million at twenty percent needs twelve and a half million of list consumption to satisfy. Ask for gross measurement in writing.
It is a definitional argument rather than a price argument, which makes it more winnable than a rate concession, and for most mid sized buyers it is worth more than two or three points. Then ask the second question nobody asks: what exactly retires it? Support, professional services, marketplace, Savings Plan prepayments, each one is a separate line in the definition and each one is negotiable.
Back weight the ramp. Commitments cannot fall year over year, so the shape you sign in year one governs the whole term. AWS's default is front loaded, which creates shortfall risk while you are still migrating. Set year one at or below what you can prove today and put the growth in years two and three where the migration actually lands.
A ramp you beat is leverage at every review. And if AWS wants a bigger year one, let them buy it: onboarding credits, funded migration sprints, or a discount step that triggers when you reach the higher tier.
Then negotiate the relief you hope never to use. The default shortfall clause is a plain gap true up, invoiced at your discounted rate. What is negotiable is everything around it: a cure period after measurement, quarterly true ups instead of one annual surprise, and a step down right of twenty five to forty percent on defined triggers like a divestiture, a business unit closing, or sustained service failure. And ask for two things by their contract names, because AWS has signed both.
An Available Balance, which turns shortfall money into prepaid credit you can still consume rather than money simply burned. And a Rollover Amount, which carries an unused balance from an expiring agreement into its successor. Ask for them by name and the conversation changes, because you are no longer requesting an invention.
Know what the signature actually costs you. This is the clause almost nobody prices. The filed agreements say that during the term of the addendum neither AWS nor you may terminate for convenience. So the thirty day exit right you had under the standard agreement is suspended for the whole term.
Anyone in your business who believes AWS is always month to month is wrong the moment you sign. Read it both ways though: it also stops AWS terminating you at thirty days notice, which is a genuine protection worth naming to your risk function. Two more that ride along in the standard template. A logo and name licence that survives termination.
And a preferred cloud provider clause that binds your public and private statements about your cloud choice. That second one is a real concession and it is usually given away free. Trade it.
And protect the base the discount applies to. A percentage discount floats on a list price AWS controls and may change with thirty days notice, or none at all for new services. AWS proved the point in twenty twenty six by raising capacity block prices twice inside six months. So ask for fixed unit rates on your concentrated spend, keep the cross service percentage for everything else, and add a greater of clause so you take whichever is better if AWS cuts list.
That is not exotic: AWS drafted exactly that protection into its own agreement back in twenty seventeen. And get the sentence that stops the eligible services list becoming a unilateral amendment right, the one that says AWS may only add a service to the excluded list within thirty days of it becoming generally available. If it is missing from your draft, it is the cheapest ask in the document.
One last point. At Redress Compliance we structure these agreements on pure contingency: twenty five percent of what we save you. Nothing saved, nothing paid. Next episode: credits, marketplace and support, the three lines where most of the remaining money sits.
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