AWS EDP Negotiation, Part 1: Talking Points on the Bet Against Your Own Forecast

Transcript

Full narration of the briefing. Click a section heading to jump the player to that moment.

A bet against your own forecast 0:00

An EDP is a bet you make against your own forecast, and AWS holds the model. The private pricing deal trades a committed spend for a cross service discount, and every mechanic in it favors the side with better data: the commitment is invoiced if you fall short, the growth model behind the proposed commit is theirs, and AWS reads your usage telemetry in more detail than your own finance team does. Meanwhile the headline percentage that anchors the whole conversation is the least interesting number in the deal. I am Tom, Claire is with me, and this is part one of the VendorBenchmark AWS EDP prep.

Your position is stronger than it looks 0:47

Your position is stronger than the anchoring suggests. The do nothing fallback is genuinely fine: on demand with Savings Plans keeps running with no deadline at all. The real money sits in service specific private rates on your top spend lines, in credits that stack quietly beside the discount, and in shortfall flexibility that turns the commitment from a cliff into a corridor. The rule that governs everything: optimize first, commit second, and commit below your own forecast, never at their model.

Overcommitting buys a discount on money you then have to find ways to spend, which is not a discount at all.

The four shifts 1:23

Four shifts. Commit below the forecast: shortfall is invoiced, so the commit is sized at your conservative baseline, ramped in annual tranches, never at the growth curve on their slide. Optimize before you commit: a commitment signed on unoptimized spend locks the waste in for the term; rightsizing and Savings Plans coverage come first. The headline percentage is not the deal: the real rate is the blend, the cross service discount stacked on Savings Plans plus private rates on your heaviest lines, data transfer above all.

And credits and capacity are the second currency, with Marketplace purchases retiring commitment at a negotiable counting percentage.

What you assemble 2:10

What you assemble. Their calendar: the fiscal year is the calendar year, quarters end March, June, September, and December, but your on demand fallback means no date is ever yours. The optimized baseline: twelve months of spend after the rightsizing you are actually going to do, built by you. The service mix map: your top five lines by service, with data transfer on its own line regardless of rank.

The Marketplace map: every ISV subscription you could route, priced. The portable tier: workloads that could genuinely run elsewhere, with at least one competing cloud quote; a priced slice is enough to be logged. And one voice.

How the other side is paid 2:53

Know how the other side is paid. The account team is paid on revenue growth and on adoption of strategic services. A signed commitment is forecastable revenue, which is why a commit is easier for them to get approved than a discount, and why the shape of the deal, term, ramp, and counting rules, moves more freely than the headline rate. Trade shape they can book for economics you need.

Private pricing approvals run in bands by commit size, and service specific rates travel a different approval path. Never bluff consumption; they can see it hour by hour.

Five sentences that reprice the deal 3:31

Five sentences reprice the deal against you. We are all in on AWS: you deleted the portable tier and every competing quote. Our own forecast says we will double: you signed their growth model for them. We need the discount live by our date: the fallback runs on demand forever, and the moment you invent a deadline, the deal acquires one, and it is yours.

We will find ways to spend up to the commit: you pre approved the failure mode of every oversized EDP. And engineering already settled the architecture with your solutions team: architecture is pricing. More briefings at redresscompliance dot com slash research videos.