Cloud Cost Due Diligence: What PE Firms Miss Before Close

The cloud line item nobody audits

Private equity due diligence is thorough on revenue, margins, headcount, customer concentration, and cap table mechanics. Cloud infrastructure costs — often the second- or third-largest operating expense after payroll — typically get a single line item in the financial model: “hosting and infrastructure.”

That single line item hides a web of commitments, billing structures, and optimization gaps that can materially affect post-acquisition economics. We've seen cloud cost surprises ranging from $300K to $2M annually in the first year after close — not because the costs were hidden, but because nobody asked the right questions before the deal closed.

Orphaned commitments: paying for resources nobody uses

Reserved Instances and Savings Plans are pre-paid commitments. When an acquisition target purchased 3-year RIs eighteen months ago, the acquirer inherits the remaining eighteen months of those commitments — whether or not the underlying workloads still justify them.

Orphaned RIs are common in companies that have gone through infrastructure changes, migration projects, or headcount reductions. The team that purchased the RIs may no longer exist. The workloads they covered may have been containerized, right-sized, or decommissioned. But the commitment remains on the bill, and it transfers with the AWS account.

Due diligence should include a full inventory of active commitments across all cloud providers: instrument type, remaining term, monthly cost, and current utilization rate. Any RI or Savings Plan with utilization below 70% is a red flag that warrants investigation before close.

EDP and EA surprises

AWS Enterprise Discount Programs and Azure Enterprise Agreements are negotiated contracts with minimum spend commitments. If the target company committed to $5M in annual AWS spend to get an 8% EDP discount, the acquirer may inherit that commitment — and the obligation to maintain that spend level to keep the discount.

This matters especially when the acquisition plan includes consolidating cloud accounts or migrating workloads. If you plan to move the target's workloads onto your existing AWS infrastructure, their EDP commitment doesn't come with you. The discount disappears, but the minimum spend obligation may survive the contract period.

Due diligence should capture: all active EDPs and EAs, their terms and minimums, remaining duration, and whether they're tied to specific billing accounts or legal entities. The interaction between the target's cloud contracts and the acquirer's existing agreements needs to be mapped explicitly.

Billing organization structure mismatches

AWS Organizations, Azure Management Groups, and GCP organizational hierarchies don't always map to legal entity structures. A company might run all its AWS accounts under a single payer account that's owned by a subsidiary, not the parent entity being acquired. Or they might share a billing organization with a joint venture partner that isn't part of the deal.

These mismatches create post-close headaches. RI sharing within an AWS Organization means discounts flow across all linked accounts — including accounts that might belong to entities outside the acquisition perimeter. Untangling shared billing relationships after close can take 3–6 months and may result in temporarily higher costs as discount sharing is disrupted.

The DD checklist should include: a complete map of billing organization structure, which legal entities own which payer accounts, which accounts share discounts, and which accounts will need to be separated post-close.

The cost basis nobody verified

Most acquisition models project infrastructure costs forward based on recent spend trends. But “recent spend” often includes temporary discounts, one-time credits, or unsustainable optimization that inflates margins pre-sale.

Common examples: the target received a $500K AWS promotional credit that expires in six months. They negotiated a one-time Azure pricing concession during a contract renewal that won't carry forward. They purchased a burst of 1-year RIs right before the sale process to show lower run-rate costs, knowing those commitments would need renewal (at possibly different terms) post-close.

Normalizing the cloud cost basis means stripping out one-time credits, identifying expiring discounts, and projecting what the actual run rate will be 12 months post-close under the acquirer's billing structure. This is the number that belongs in the financial model — not the trailing twelve months of invoices.

A practical DD checklist for cloud costs

Before close, the cloud cost diligence should answer:

• What is the total cloud spend by provider, and what's the trend over 12–24 months?
• What active commitments exist (RIs, Savings Plans, CUDs), and what are their utilization rates?
• What contractual commitments (EDPs, EAs) exist, and what are their minimum spend obligations?
• How does the billing organization structure map to the legal entities being acquired?
• What credits, promotional pricing, or temporary discounts are inflating current margins?
• What is the normalized run rate after expiring discounts and credits are removed?
• What is the discount coverage gap, and what savings are available through a managed discount service?

Getting these answers typically requires access to 6–12 months of detailed billing data from each provider. A cloud cost assessment during the DD period — ideally in the 30–60 days before close — can surface the issues that a standard financial audit misses. For a deeper look at what happens after the deal closes, see our guide on cloud costs in the first 90 days post-acquisition.