Modeling software synergies for the deal thesis

Modeling software synergies for the deal thesis is where many acquisitions overstate the value of consolidation. The thesis promises savings from merging licences, retiring duplicate tools, and buying at greater scale, yet those savings sit on top of a software estate whose true licensing position is rarely tested. Inherited software licensing exposure is usually latent and unquantified in standard due diligence, which means the synergy model often counts savings while ignoring the repricing, lost discounts, and cure costs that offset them. This page sets out how buyers model software synergies honestly, why the gross number almost always overstates the net, and how the thesis survives contact with the licensing reality.

Why modeling software synergies for the deal thesis goes wrong

The standard synergy case takes the two software stacks, identifies overlap, and assumes the combined entity keeps the cheaper option and retires the rest. That logic ignores the contracts underneath. Software licences are not freely portable. Change of control and anti assignment clauses can trigger consent, termination, or repricing, and the publisher is under no obligation to honour the cheaper of two deals once the entities combine. The act of consolidating can itself trigger a renegotiation in which the publisher resets pricing to its advantage, wiping out the saving the model assumed.

Three forces commonly erode a gross software synergy. Repricing on change of control resets discounts that were negotiated by one party and do not transfer. Volume discounts can be lost rather than gained where combining estates pushes the buyer into a metric or edition that costs more per unit. And the cost to cure any inherited shortfall has to be funded before the saving can be realised. A model that books the gross saving without these offsets produces a synergy number the deal cannot deliver.

Building a defensible net synergy

A credible synergy model starts from the contracts, not the spend. For each major publisher, the buyer needs to know the metric, the term, the renewal date, and the change of control treatment before assuming any saving. Only then can it judge whether consolidation produces a real reduction or simply moves the cost. The publishers that most affect this analysis are the ones that carry the most audit and repricing risk: Oracle, SAP, Microsoft, IBM, and increasingly Broadcom for VMware, Salesforce, and ServiceNow. Their agreements tend to be the least portable and the most likely to reprice on a combination.

The output should be a net synergy with the offsets shown explicitly, so the investment committee sees what it is relying on. Booking a gross saving and hoping the offsets stay small is how synergy targets are missed in the first year. The same reconciliation that quantifies the cost to cure also reveals where consolidation is genuinely accretive and where it is not, which is why the synergy model and the cost to cure model should be built from one dataset rather than two.

Where consolidation raises the recurring cost of the estate, that belongs in the software licensing and EBITDA adjustments rather than as a positive synergy. Keeping the synergy model and the EBITDA bridge consistent stops the buyer claiming a saving in one place that it has already given back in another.

Timing and the realisation curve

Even a real synergy rarely lands on day one. Licences run to renewal dates, duplicate tools need migration before they can be retired, and committed terms carry exit costs. A synergy that is real in year three can be negative in year one once dual running and migration are funded. The honest model phases the saving along a realisation curve that respects contract terms, rather than assuming the full run rate from completion. Investment committees that approve a deal on a day one number are often disappointed by the first integration review.

The realisation curve also interacts with the integration plan. Consent driven renewals, data migration, and the retirement of duplicate systems all take management time and carry execution risk. A synergy that depends on renegotiating an Oracle or SAP agreement is not guaranteed simply because the model assumed it. Building the curve with the contract calendar in view, and stress testing the assumption that the publisher will cooperate, produces a number the deal team can defend through the hold period rather than only at approval.

None of this means software synergies are illusory. Consolidation genuinely reduces cost where estates overlap and where contracts allow it. The point is to model the net, not the gross, and to show the offsets so the thesis rests on a number the deal can actually deliver. A disciplined net synergy is more persuasive to an investment committee than an optimistic gross one, because it survives the scrutiny of the people who will be held to it.

What the deal team should produce

The synergy section of the deal thesis should carry three things: a gross saving from consolidation, a clearly itemised set of offsets, and a net synergy phased over a realisation curve. Each offset should trace to the contract that causes it, so the assumption can be tested rather than taken on faith. This turns the synergy case from a headline into a defensible model, and gives the integration team a plan it can execute against rather than a target it inherits without a path to reach it.

Done well, the exercise also protects the wider valuation. A synergy model built from the contracts feeds the same reconciliation that drives pricing, EBITDA adjustments, and indemnity, so the buyer underwrites one consistent view of the software estate. That consistency is what separates a thesis that holds through the hold period from one that unravels at the first renewal. The work sits squarely within software in deal valuation, and the contract level analysis behind it comes from software spend diligence.

Engage your own counsel for legal interpretation of any agreement or change of control clause.