The questions buyers ask most about software licensing exposure and the price they pay, answered in one place, with links to the detail behind each valuation lever.
Software in deal valuation FAQ answers the questions buyers ask most often about how software licensing exposure affects the price they pay and the protections they negotiate. Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and it lands as a publisher audit after close, so it belongs in the valuation rather than as an afterthought. This page brings the core questions together in one place and links to the detailed treatment of each, so a deal team can find the right answer quickly and then go deeper where it matters. It is a map of the cluster as much as a set of answers.
The first questions are almost always about scale and timing. How large can software exposure be, when does it surface, and why does standard diligence miss it. The short answer is that the exposure can run into eight or nine figures for a large estate, it surfaces as a publisher audit in the months and years after close, and standard diligence misses it because it reviews contracts and spend without reconciling actual deployment against entitlement. The detailed treatment of how the exposure feeds the price sits in how software risk affects deal valuation.
The next set of questions is about mechanics: where the number goes once it is quantified. A single cost to cure feeds several levers. It can be priced into the consideration, treated as an EBITDA adjustment where it changes normalised earnings, backed by an indemnity and reps, and secured through an escrow. The diagram below shows how one quantified figure drives all four, which is the central idea of valuing software risk properly rather than leaving it in a footnote.
Each lever does a different job. Pricing the exposure into the consideration handles a one off cure that the buyer will fund, and the method is set out in pricing software exposure into the purchase price. An EBITDA adjustment handles a recurring change in run rate cost, because a recurring cost reduces the earnings base the multiple is applied to, and the detail is in software licensing and EBITDA adjustments. The reps, warranties, and indemnity handle exposure that is hard to quantify at close or that may surface later, covered in reps and warranties for software licensing and software licensing indemnities explained.
The reason the levers must be coordinated is that the same exposure can otherwise be counted more than once or missed entirely. A disciplined approach maps each pound of exposure to exactly one mechanism, drawing on a single quantified cost to cure. The completion mechanism then reflects what is known at close, as explained in software exposure and working capital adjustments, while the indemnity catches what surfaces afterwards.
| Exposure | Best lever | Why |
|---|---|---|
| One off cure cost | Purchase price | A single known outflow |
| Recurring run rate cost | EBITDA adjustment | Lowers the earnings base |
| Hard to quantify risk | Reps and warranties | Allocates without a fixed number |
| Post close audit | Indemnity and escrow | Recovery after completion |
| Accrued maintenance | Working capital | Value already consumed |
The publishers that drive most of this exposure are Oracle, SAP, Microsoft, IBM, and increasingly Broadcom for VMware, Salesforce, and ServiceNow, as of June 2026. Their agreements carry the metrics, audit rights, and change of control terms that turn a quiet estate into a settlement. Any valuation that ignores their position is incomplete.
A frequent question is whether software exposure can simply be handled after close as part of integration. The answer is that it can be handled there, but at a far higher cost. Before signing, the buyer controls the price and the agreement and can allocate the risk to the seller. After close, the same exposure is a cost to cure with no counterparty to share it, because the seller has been paid and the publisher sets the terms. The change of control event itself can trigger consent, termination, or repricing, and the deal structure decides which clauses bite, so the worst time to discover the exposure is after the structure is fixed.
This is why the cluster treats software as a valuation question first and an integration question second. The reconciliation that quantifies the exposure produces the number that drives price, EBITDA, indemnity, and escrow, and then doubles as the day one plan for the combined estate. The scale at stake is real: in publicly reported disputes, SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, as of June 2026. Numbers of that order belong in the valuation, underwritten before the price is agreed.
For deals where the usual protections are weak, such as distressed sales and carve outs, the exposure concentrates further and recourse falls away, which is covered in software risk in distressed and carve out deals. In every case the principle is the same: quantify the exposure, map it to the right lever, and protect the value before close.
This FAQ sits at the centre of software in deal valuation, and the reconciliation behind every answer comes from software spend diligence. Engage your own counsel for legal interpretation of any agreement or claim.
Tell us where the deal stands. We respond within one business day with a scoped, buyer side engagement that protects the value you underwrote.
Book a confidential call