Practice · IX.

AWS. EDP and commitment design.

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

Where the practice intervenes

Six points on the AWS commercial cycle.

Pre-renewal

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

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.

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.

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.

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.

Questions

Asked before engagement.

What is an AWS EDP and when does it make sense?

A multi-year cumulative-spend commitment traded for a discount across the AWS bill. It makes sense when trailing consumption plus a documented migration plan support the commitment curve; an EDP sized on aspiration converts a discount into a liability.

How do Savings Plans relate to an EDP?

They layer. The EDP discounts the whole bill against the commitment; Savings Plans and Reserved Instances discount specific usage underneath it. The design question is coverage mix — how much stable usage to lock at the resource layer versus keeping flexibility.

What happens if we miss the committed spend?

The shortfall is typically payable. That is why ramp design — year-one anchor, realistic mid-term, defensible landing zone — matters more than the headline discount percentage.

How are engagements priced?

Three frameworks: fixed fee for scoped deliverables, contingency tied to verified savings, and an annual retainer for continuous coverage across every vendor. The model is agreed on the first call, which is always complimentary, and independence is warranted in writing on every engagement letter.