Practice · IX.

AWS.

The Enterprise Discount Programme commitment ramp, the Savings Plans and Reserved Instances mix, the Marketplace channel pivot, the Migration Acceleration Programme credit treatment, the data egress charge, and the multi-year discount design. AWS contracts close on documented commitment risk, not on the headline discount percentage. Independent buyer-side advisory across compute, storage, data, analytics and the AI/ML stack. Commitment risk modelled, marketplace spend reconciled, AI workloads scoped against documented business cases.

Speak with a Senior Advisor Engagement models
Aws licensing advisory

EDP discounts shift commitment risk. The risk is modelled.

The Enterprise Discount Programme moves the headline discount up and the commitment risk down to the buyer. Without documented overrun protection and a tested ramp, the EDP becomes a forced run-rate at the closing year.

Where the practice intervenes
Six points on the AWS commercial cycle.
Pre-renewal
i.
Estate reconstruction
Nine months before the EDP anchor, the AWS estate is reconstructed across compute, storage, networking, data, analytics, the AI/ML stack and the Marketplace channel. Linked-account hierarchy, savings instrument mix, commitment burn-down and forecast workload growth are mapped. The position paper governs the EDP commercial conversation.
Commitment
ii.
EDP ramp design
EDP commitment is sized against documented workload growth at business-unit level. Multi-year ramp, overrun discount protection, underrun forgiveness, partial year credit treatment and the closing-year cliff are negotiated. Marketplace commitment counting against the EDP is documented.
Savings mix
iii.
Compute Savings Plans / RIs
Compute Savings Plans, EC2 Instance Savings Plans, Reserved Instance laddering and on-demand burst are mixed against forecast workload. The savings-instrument mix is tuned monthly through the term. Convertible-RI exchange and Savings Plan family treatment are documented.
Marketplace
iv.
Channel pivot scope
Software publisher pivots into the AWS Marketplace channel are negotiated against EDP commitment counting, publisher discount loss, and exit-to-direct mechanics. Private offers, public offers and channel partner private offers are negotiated separately.
AI / ML
v.
Bedrock and SageMaker scope
Bedrock model commitment, SageMaker training credit, Trainium and Inferentia commitment, and the AWS-side AI services consumption are sized against documented use cases at business-unit level. Pilot scope, expansion criteria, dollarised business case and exit-to-on-demand terms are documented.
Egress
vi.
Data transfer and exit
Data transfer-out, inter-region transfer, inter-AZ transfer and direct-connect costs are reconciled. Egress charge waivers on documented exit are negotiated. The exit-to-alternative-cloud architecture is documented at signature, not at exit.
Where the work concentrates
Active mandate areas across the AWS book.
All case studies →
EDP renewal and ramp
Commitment, overrun, underrun, cliff
EDP commitment ramp design, overrun protection, underrun forgiveness, closing-year cliff treatment, multi-year discount tier modelling against documented workload growth.
Read →
Savings Plans and RIs
Compute SP, EC2 SP, RI ladder, on-demand
Compute Savings Plans, EC2 Instance Savings Plans, Reserved Instance laddering, on-demand burst. Convertible-RI exchange treatment, Savings Plan family scope, monthly tuning protocol.
Read →
Marketplace commitment
Private offers, channel partner, publisher pivot
AWS Marketplace channel pivot for software publishers, EDP commitment counting, private offer negotiation, channel partner private offer separation.
Read →
Bedrock and AI/ML scope
Model, training, Trainium, Inferentia
Bedrock model commitment, SageMaker training credit, Trainium and Inferentia commitment, AWS AI services consumption against documented use cases.
Read →
MAP credit treatment
Migration, modernisation, optimisation
Migration Acceleration Programme credit eligibility, modernisation funding, optimisation co-investment, credit expiry protection, audit risk on the funded scope.
Read →
Egress and exit architecture
Data transfer, exit waivers, multi-cloud
Data transfer-out, inter-region and inter-AZ transfer, direct-connect cost reconciliation. Egress waivers on documented exit. Multi-cloud and exit architecture documented at signature.
Read →
I.
Named senior advisor
The senior advisor named on the engagement letter leads every AWS conversation. No leverage model, no rotation of junior consultants, no anonymous correspondence with the publisher. The advisor signs every position document.
II.
Counter-signed positions
Every written counter-position to AWS is signed by the senior advisor and counter-signed by a second partner before transmission. Two named signatures on every position document for the full five-year retention period.
III.
Independent on every clause
Admodum holds no commercial relationship with AWS. No reseller margin, no APN partner status, no Marketplace seller relationship, no MAP delivery subcontract. We do not work both sides.
IV.
Commitment is a risk, not a discount
Every EDP commitment is modelled against documented workload growth, overrun protection and underrun forgiveness. The commitment risk is documented at signature and reviewed quarterly through the term.
V.
Five-year retention
Every position paper, counter-position, and closing memorandum is retained inside the firm for five years from engagement close. The buyer can request source workings at any point.
VI.
Reset the baseline every cycle
Every AWS commitment renewal closes with a written baseline reset. The closing position, the contractual amendments accepted, and the live obligations carried forward are tied into the next renewal preparation cycle through the Renewal Programme.
$420M
AWS Spend Advised
31
EDP Cycles Closed
22%
Median Effective Reduction
9
Marketplace Pivots Negotiated
100%
Named Advisor
"
The opening EDP proposal would have committed us to a sixty percent uplift on prior-term run-rate, with the AI services line modelled against an internal forecast we had not validated. After the workload reconstruction and a contested ramp redesign, the closing commitment landed below run-rate with overrun protection and underrun forgiveness in the contract.
Vice President of Cloud Engineering
Financial Services Group · EDP Renewal Q3 2025
Operating principles
How the practice is run.
Commitment is risk.
EDP and Reserved Instance commitments shift run-rate risk from the publisher to the buyer. The commitment is modelled against documented workload growth at business-unit level, with overrun protection and underrun forgiveness in the closing contract.
Marketplace is a separate negotiation.
Software publisher pivots into the Marketplace channel are negotiated against EDP commitment counting and publisher discount loss. Private offers, public offers and channel partner private offers carry distinct commercial mechanics.
AI with a documented exit.
Bedrock, SageMaker, Trainium and Inferentia commitments are approved against a documented business case at business-unit level, with documented expansion criteria and exit-to-on-demand terms. The pilot population is named, the expansion criteria are dollarised, the exit terms are in the contract.
Exit at signature, not at exit.
The exit-to-alternative-cloud architecture, egress waiver mechanics and data residency obligations are documented at signature. Exit cost cannot be negotiated at exit because the buyer has lost the leverage.
Independence
Admodum is not a partner, reseller, or affiliate of any software vendor. No reseller margin, no referral commission, no audit subcontract from any publisher.
Aws licensing advisory

Open an AWS conversation.

Practice across compute, storage, data, AI/ML, and the Marketplace channel. Independent. Buyer-side only. Engagement structured as fixed fee · contingency · annual retainer.

Speak with a Senior Advisor Case Studies