Full narration of the briefing. Click a section heading to jump the player to that moment.
Most buyers negotiate with the person in front of them. On an AWS deal that person almost certainly cannot give you what you are asking for, and knowing that changes how you run the whole campaign. So before the plan, the machine. Who prices an AWS deal, what clock they run on, and how your ask reaches somebody with authority.
Your account manager cannot price your deal. AWS's own job postings describe a global organisation that owns private pricing, split into two teams. One handles standard agreements drafted from approved frameworks. The other, Strategic Customer Engagements, is chartered for deals that are large, complex, or highly competitive, and it owns deal structure and negotiation through to closure.
Read that list of three triggers again, because two of them are things you control. You cannot change how large your deal is this year. You can make it structurally complex, by bundling renewals and expansions together, and you can make it competitive, by running a real alternative. Those are the levers that move your file to the people who set prices.
And know how AWS describes the programme internally. Private pricing, in its own words, is positioned to grow both revenue and margin. A discount programme is a margin instrument. That is not cynicism, it is the frame the other side is working from.
The calendar has two clocks, and one is monthly. The strategic clock is the calendar year, because Amazon's fiscal year ends on the thirty first of December, and quarters close in March, June, September and December. But the operational clock is the one that catches people. Practitioners who transact these agreements report that paperwork must be submitted by the twentieth of a month to go live on the first of the next, with at least ninety days end to end through the approval process and typically two to four rounds of negotiation.
Which means a deal you agree on the twenty second of December does not start in January. You have lost a month of discount and handed AWS your deadline. And unlike a classic software vendor whose quota retires on signature, an AWS account team is measured on consumption that is already running, so year end pressure buys you term concessions and credits far more reliably than it buys headline rate.
Start nine months out, not ninety days. At nine months you build the baseline from episode four. At six months the competitive alternative goes out as a genuine request, because a credible bid takes months to mature and a last minute one fools nobody. At four months your term sheet goes to AWS, so the negotiation happens on your paper rather than theirs.
And from two months you manage the endgame against their calendar and the submission cutoff, not against your expiry date. If you are inside sixty days when you start, you have already given away most of what you were going to negotiate for.
The channel decision is a structural one. Buying through a reseller can genuinely beat direct, mostly on support economics and for estates below the private pricing threshold, where a reseller is realistically the only route to a discount at all. But understand what you are handing over. Under the classic reseller model your accounts sit inside their organisation, which means the Reserved Instances and Savings Plans are purchased in their organisation and are their asset, not yours.
They cannot move with you. A departing account loses access to its own historic cost data while the reseller keeps it. And AWS publishes tooling that lets a partner show you a marked up version of your bill and block your visibility of the real rates. So if you go through the channel, insist on the structure where you keep your own AWS organisation and your own payer account, demand written confirmation of whose organisation holds the commitments, and get a covenant that they will never apply a policy preventing your accounts from leaving.
That last clause is invisible to buyers who do not know the mechanic exists.
One voice, and one written mandate. Behind it the usual four roles: the executive sponsor who owns the walk away, the negotiator who runs every conversation, the engineer who validates the technical claims, and the FinOps analyst who keeps the numbers current. And a signed one page mandate, because AWS sells above you as comfortably as it sells to you. When the account team briefs your executives on an AI vision, the memo your CFO signed is what your executives quote back.
One last point. At Redress Compliance we run this campaign end to end on pure contingency: twenty five percent of what we save you, and nothing saved, nothing paid. Next episode: AWS's playbook at the table, and the counters that work.
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