How to Evaluate Cloud Cost Risk in M&A Due Diligence

To evaluate cloud cost risk in M&A due diligence, pull 12 to 24 months of billing actuals, test how much spend rests on commitments and when they expire, measure recoverable waste, compute unit economics and gross margin, check vendor and region concentration, then price both the downside and the remediation upside into the model. The biggest hidden risk is commitments that expire and revert the bill to on-demand rates, which makes the forward run-rate higher than the trailing bill. The biggest hidden upside is waste, which a disciplined program turns into a recoverable double-digit percentage of monthly spend.

Last updated: June 2026. Written by Morten Andersen and reviewed by Fredrik Filipsson, built on our See, Cut, Lock, Run method.

This guide sits in our CFO's guide to cloud cost management, the cluster pillar it links up to, and connects to the broader cloud cost optimization playbook. The unit-cost analysis here builds on our companion guide on how to benchmark cloud spend as a percentage of revenue. Diligence is a See step exercise applied to someone else's estate before you own it.

What is cloud cost risk in M&A due diligence?

Cloud cost risk in M&A due diligence is the chance that a target's cloud spend is understated, about to rise, or structurally inefficient in ways that erode margin after close. Unlike a fixed data-center cost, cloud spend is variable, contract-laden, and sensitive to growth, so the trailing twelve months can mislead. A buyer treats diligence as a test of the forward run-rate and its quality: how much of the bill is locked at a discount, how much is waste, whether unit cost is improving, and how exposed the spend is to a single contract. The output is a number, or a range, that adjusts the valuation and seeds the integration plan.

How do I evaluate it, step by step?

Evaluate it by working from billing actuals through the four risks to a priced remediation plan. Six steps:

1. Pull the full billing dataset. Request 12 to 24 months of cost and usage exports across every account, plus commitment and private pricing contracts. Result: analysis on actuals, not summaries.
2. Test commitment coverage and expiry. Measure the share of spend covered by Reserved Instances, Savings Plans, or CUDs, and when each expires. Result: the true forward run-rate after reversion.
3. Measure waste and right-sizing headroom. Quantify idle and zombie resources, oversized instances, and low utilization. Result: the recoverable portion of the bill.
4. Compute unit economics and gross margin. Tie cloud cost to revenue, customers, or transactions over time. Result: whether the cost curve is improving or worsening.
5. Check vendor and region concentration. Map spend by provider, region, and agreement. Result: the re-pricing and migration exposure.
6. Price remediation into the model. Turn recoverable waste and renegotiation upside into a dated plan. Result: risk and upside both in the valuation.

How does commitment expiry change the forward run-rate?

Commitment expiry raises the forward run-rate because spend covered by discounted Reserved Instances, Savings Plans, or Committed Use Discounts reverts to on-demand pricing when those instruments lapse. AWS, for example, documents that Savings Plans and Reserved Instances apply a discount only for their term, after which usage is billed at standard rates, per the AWS Savings Plans documentation. If a target funds a large share of its bill with commitments expiring within the deal horizon, the trailing bill understates the real cost of running the business forward. Model the reversion month by month, and treat near-term expiry as both a financing item and a day-one renewal task.

How do unit economics and concentration affect the deal?

Unit economics tell you whether the target's cloud cost scales in its favor, and concentration tells you how fragile its current pricing is. If cost per customer or per transaction is falling as volume grows, the business gets healthier with scale; if it is rising, the cloud bill will outpace revenue and compress gross margin, which is a structural mark against the valuation. Concentration compounds this: spend locked into one provider or one enterprise agreement can be efficient today but exposed at renewal, or expensive to move if the post-close architecture changes. Read both alongside our benchmark of cloud spend as a percentage of revenue to place the target against its peers.

Frequently asked questions

What is cloud cost risk in M&A due diligence?

Cloud cost risk in M&A due diligence is the chance that a target's cloud spend is understated, about to rise, or structurally inefficient in ways that hit margin after close. The common forms are commitments that expire and revert the bill to on-demand rates, heavy waste that inflates the run-rate, unit costs that rise with scale, and concentration in one vendor or contract. Diligence prices both the downside risk and the recoverable upside into the deal model.

What cloud documents should I request in diligence?

Request 12 to 24 months of detailed cost and usage exports for every cloud account, all commitment contracts such as Reserved Instances, Savings Plans, and CUDs with their expiry dates, any private pricing or enterprise discount agreements, and the target's own tagging and allocation data. Summaries hide the detail that matters; the line-item exports are what let you test coverage, waste, and unit economics.

How does commitment expiry affect a deal?

Expiring commitments can sharply raise the post-close bill, because spend covered by discounted Reserved Instances, Savings Plans, or CUDs reverts to on-demand rates when those commitments lapse. If a large share of the target's spend is on commitments expiring soon, the real forward run-rate is higher than the trailing bill suggests. Model the reversion explicitly and treat near-term expiry as a financing and integration item.

Can cloud waste be an upside in an acquisition?

Yes. Heavy waste is a risk to the trailing margin but an upside to the buyer, because idle resources, oversized instances, and unbought commitments are recoverable after close. A disciplined optimization program routinely takes a meaningful percentage off the monthly bill, so quantified waste becomes a value-creation lever you can underwrite in the model and execute in the first hundred days.

The short version

Cloud cost diligence works from billing actuals through commitment reversion, waste, unit economics, and concentration to a priced remediation plan. Done well it protects the valuation from a hidden run-rate and hands the buyer a value-creation lever for the first hundred days. When you want that diligence run independently and the upside executed after close, that is what our Managed FinOps service delivers.