Executive Summary
A multinational logistics business needed to negotiate its AWS Master Contract, the Enterprise Discount Program, without a clear internal view of its own financial exposure or the discount value realistically available at its scale, a position that risked either overpaying or over-committing to spend the business didn't need. The client engaged Epitechnic to advise on and deliver the negotiation directly, rather than negotiate from that position of incomplete information.
Epitechnic engaged senior leaders and finance teams across the global firm to build alignment before negotiating, then produced a playbook covering the client's financial exposure and the likely discount value available, and built the business case for the deal. Epitechnic then negotiated the agreement directly on the client's behalf.
The result was a valuable deal, aligned to a business case the client had defined in advance, rather than an outcome shaped primarily by the provider's opening position.
Business Challenge
A Master Contract negotiation with a hyperscale cloud provider is not a routine procurement exercise. It sets the cost base for a significant part of a client's global technology spend for years, against a counterparty that runs negotiations like this constantly, while any individual client runs one perhaps once every few years.
Without an independently-produced view of financial exposure and realistic discount value, a client risks two different failures: accepting a weaker deal than its actual scale warrants, or over-committing to spend levels the business doesn't need to hit a headline discount. Left unaddressed, either failure sets the wrong cost base for the life of the contract, and is expensive to unwind once signed.
Success Criteria
- A clear, independent understanding of the client's financial exposure under the proposed contract
- A realistic view of the discount value available given the client's actual scale
- A negotiating playbook, aligned across senior leadership and finance, before entering the room
- A defined business case for the deal
- A negotiated agreement aligned to that business case
Epitechnic Approach
Epitechnic positioned itself as the client's negotiating counterpart to AWS, not an adviser reviewing a deal after the fact. That meant building genuine alignment across senior leaders and finance before negotiating began, so the playbook and business case reflected the whole organisation's position, not just the technology function's view of it.
Solution
Cross-functional alignment
A Master Contract decision affects the whole global firm's cost base, but the negotiation risked being run by technology alone, without full alignment from finance and senior leadership. Epitechnic decided to engage senior leaders and finance teams across the global firm before negotiating, not after a deal had already been shaped.
A negotiating position that finance and senior leadership haven't aligned on is a weak position, both with AWS and internally once the deal needs sign-off. The result was a negotiating position aligned across the organisation before it was ever presented to AWS.
The negotiating playbook
The client did not have a clear internal view of its own financial exposure or the discount value realistically available given its scale. Epitechnic decided to produce a negotiating playbook covering both, rather than enter negotiations without a defined, evidence-based position.
A hyperscale provider negotiates agreements like this constantly. A client entering without a defined position is negotiating from a structural disadvantage regardless of its actual commercial leverage. The result was a playbook that gave the client a defined, evidence-based negotiating position for the first time.
The business case and negotiation
The client needed an agreement aligned to a clear target, not a deal reached without one. Epitechnic decided to build the business case first, then negotiate directly on the client's behalf against that target.
Negotiating against a defined business case, rather than an open-ended goal, is what allows a negotiator to know when a deal is good enough to accept and when to hold out for more. The result was a valuable deal, secured on the client's behalf, aligned to the business case.
Outcomes
Financial impact: A valuable AWS Master Contract secured, aligned to a defined business case.
Risk reduction: Financial exposure understood and negotiated from a position of evidence, rather than accepted on the provider's terms.
Executive benefits: Senior leadership and finance had visibility and alignment on a significant, multi-year cost commitment before it was signed, not after.
Governance improvements: A negotiating playbook and business case the client retains as a reference for future cloud commercial negotiations.
Why It Worked
The engagement succeeded because Epitechnic built the client's negotiating position before entering the room, not during. Cross-functional alignment, a defined playbook grounded in the client's actual exposure and scale, and a business case with a clear target, are what allowed this negotiation to be run on the client's terms, against a counterparty that negotiates deals like this far more often than the client does.
Key Takeaways
Challenge: A global logistics business needed to negotiate a significant, multi-year AWS Master Contract without a clear internal view of its own financial exposure or realistic negotiating leverage.
Approach: Epitechnic built cross-functional alignment, produced an evidence-based negotiating playbook, defined the business case, then negotiated the agreement directly on the client's behalf.
Outcomes: A valuable deal secured, aligned to a defined business case, and a playbook the client retains for future negotiations.
Lessons: Negotiating with a hyperscale provider without an independently-built position is a structural disadvantage regardless of a client's actual commercial leverage; the position has to be built before the negotiation starts.