Cloud spend governance after a merger starts with one consolidated view of both estates, then moves through commitment consolidation, tagging reconciliation, and a unified chargeback model, in that order. You cannot govern spend you cannot see, so a single normalised cost model across every account and provider comes first, ideally on the FOCUS billing standard so the two billing exports speak the same language. Combined spend can then qualify for a better AWS Enterprise Discount Program tier or Azure MACC terms, but the shortfall and use it or lose it clauses still apply, so size the combined floor to real consumption. The biggest avoidable loss is two estates carrying duplicate commitments and idle capacity neither side reconciles.
Here is the sequence, the commitment math, and where the money usually leaks during integration.
What is the first move?
See everything before you change anything. Two companies arrive with different account structures, different tags, different providers, and often different FinOps maturity. Build one normalised cost model that maps every account across both estates to a single taxonomy. The FOCUS billing standard helps here because it gives both providers and both organisations a common schema, so you are comparing like with like rather than reconciling two formats by hand.
This view surfaces the immediate duplicates: two monitoring stacks, two log pipelines, overlapping environments, and commitments on both sides that no longer match combined usage. None of that is fixable until it is visible.
How do you consolidate commitments?
Each side likely holds its own commitments: AWS Savings Plans and Reserved Instances, Azure Reservations and the Azure Savings Plan, GCP Committed Use Discounts, or OCI Universal Credits, plus enterprise agreements layered on top. After a merger the combined footprint changes the right coverage, and combined spend can unlock a higher discount tier.
- Re forecast on the combined estate. Coverage that was right for each company alone is rarely right for the merged whole. Rebuild the forecast before renewing anything.
- Align renewal timing. A combined enterprise agreement only delivers a better tier if you time the two renewals together and present one forecast. Mismatched dates forfeit the leverage.
- Respect the clauses. The Azure MACC shortfall and the use it or lose it structure on GCP and Oracle agreements do not soften because you merged. Size the combined floor to consumption you are confident in.
How do you unify chargeback?
Reconcile the foundations before you allocate cost. Two tagging schemes and two account hierarchies cannot feed one chargeback model without producing disputes that stall the integration. Map both estates to a single tag taxonomy and account structure, run showback first so teams can see and trust their numbers, then move to chargeback once the data is clean. Chargeback forced onto inconsistent tags creates arguments, not accountability.
A Fortune 500 retailer acquiring a smaller competitor inherited a second AWS estate with its own Savings Plans, a separate monitoring stack, and tags that did not match. We built one FOCUS based view across both, retired the duplicate monitoring and log pipelines, re forecast coverage on the combined footprint, and timed the two enterprise agreement renewals together to reach a higher discount tier. Tagging was reconciled to one taxonomy, showback went live across both organisations, and chargeback followed once the data was trusted. Figures are verified against billing data and anonymised.
Where does the money leak during integration?
Three places, consistently. Duplicate tooling and observability stacks that both teams keep running because no one owns the decision to cut one. Idle environments from the acquired company that nobody decommissions because ownership is unclear. And commitments on both sides that overlap with combined usage, so you are covered twice in some places and exposed in others. A clear owner for the integration and a decommissioning policy close all three.
Frequently asked questions
What is the first governance move after a merger?
Can you combine two enterprise agreements for a better rate?
How do you unify chargeback across two companies?
Bring two estates under one model
We consolidate merged cloud estates into one governance model, from the combined view through commitments to chargeback, with zero provider commissions. Our guarantee: we reduce your cloud spend or we reimburse our service fee. Pricing is either a Fixed Fee scoped up front or Gainshare, a share of verified savings with no retainer and no risk.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.