Cloud Cost Optimization — Beyond FinOps
FinOps tools handle the operational layer. The commercial layer — EDPs, MCAs, CUDs, private pricing agreements — is where the real savings live. Here's what the FinOps platforms can't touch.
- The split every cloud cost strategy misses: operational vs commercial
- AWS EDP: the structure most buyers sign without understanding
- Microsoft MCA-E: the post-EA structure that's quietly becoming dominant
- Google Cloud CUDs and committed-use discounts: the underrated lever
- The cross-cloud arbitrage play
- Reserved instances, savings plans, and the 'stranded commitment' risk
- Software-as-a-Service layered on top of cloud (the double-negotiation problem)
- Why cloud cost optimization is a 25% gainshare engagement
The split every cloud cost strategy misses: operational vs commercial
FinOps platforms (Apptio, Cloudability, Flexera, CloudCheckr, Ternary) are excellent at the operational layer — right-sizing instances, identifying idle resources, tagging workloads. But the biggest savings are at the commercial layer: the vendor contract itself.
A well-optimised AWS environment on an unfavourable EDP is still overspending by 15-25%. Our AWS EDP negotiation service addresses the commercial layer.
AWS EDP: the structure most buyers sign without understanding
AWS EDPs lock in multi-year commits in exchange for tiered discounts. Typical starting tier: $1M/year. The structure looks simple but contains traps: over-commit penalties, inflexible service-category allocation, and an EDP-only pricing shelf that's worse than on-demand once you exceed the commitment.
See our AWS EDP tactics and cross-cloud cost service.
Microsoft MCA-E: the post-EA structure that's quietly becoming dominant
The Microsoft Customer Agreement for Enterprise (MCA-E) is replacing traditional EAs for Azure-centric customers. It offers operational flexibility but zero price hold for non-committed consumption.
Read Microsoft EA vs MCA-E for the trade-off analysis.
Google Cloud CUDs and committed-use discounts: the underrated lever
Google Cloud's CUD structure is actually more flexible than AWS EDPs at most commitment tiers — but few buyers know how to combine region-flexibility CUDs with sustained-use discounts.
Our Google Cloud negotiation service runs this analysis as step one of every engagement.
The cross-cloud arbitrage play
Running 2-3 cloud providers is 15-25% more expensive operationally than a single provider. But having a credible second cloud gives you 10-20% better pricing from your primary cloud. The math almost always works out to favour multi-cloud if you negotiate it correctly.
Detail in our multi-cloud economics white paper.
Reserved instances, savings plans, and the 'stranded commitment' risk
Buying 1-year RIs with cash reserves sounds smart. Buying 3-year RIs in an environment where cloud architecture is changing every 6 months is how you end up with $400k of stranded commitment.
Our operating rule: never commit more than 60% of stable-baseline consumption. Read reserved vs savings plans for the decision framework.
Software-as-a-Service layered on top of cloud (the double-negotiation problem)
Your Snowflake sits on AWS. Your Databricks sits on Azure. Your Datadog prices off your cloud-data volume. The SaaS contract and the cloud contract are entangled — and both need negotiation. Most buyers only negotiate one of the two.
Our SaaS negotiation service handles the cross-contract linkage.
Why cloud cost optimization is a 25% gainshare engagement
Unlike FinOps platforms that charge monthly regardless of outcome, our cloud cost negotiation service is 25% of verified savings. If we can't reduce your AWS or Azure contract, you pay nothing.
Book a free estimate if you have a cloud contract renewal inside the next 120 days, or see pricing.
Frequently asked questions
Do we need FinOps tools AND negotiation, or is one enough?
Both. FinOps tools handle operational efficiency (right-sizing, tagging, visibility). Negotiation handles commercial efficiency (discount tiers, commitment flexibility, price holds). The layers don't overlap.
How much can AWS EDP negotiation save on a $5M annual spend?
Typical engagement reduces EDP commit pricing by 15-22%, plus recovers 5-10% through structural renegotiation. On $5M spend, that's $1-1.6M over a 3-year term.
What's the best time to renegotiate cloud contracts?
90-120 days before the vendor's fiscal-quarter end. For AWS, Azure, and Google Cloud, the most aggressive quarter-end concessions happen in Q4 (Oct-Dec for AWS/Google, Apr-Jun for Microsoft).
Related reading
- Cloud Cost Negotiation service
- AWS EDP Negotiation
- Google Cloud Negotiation
- Microsoft / Azure Negotiation
- Cloud vendor fiscal calendars
Ready to apply this to a real contract?
30-minute free estimate. We review your specific renewal or audit and tell you whether we think the savings are worth pursuing — no commitment either way.
Get Free Estimate How It Works