A booked synergy is not a banked synergy. Here is how buyers baseline, track and defend software consolidation savings so the number holds when audited.
Measuring synergies from software consolidation is what separates a synergy that was claimed from a synergy that was captured. Software consolidation generates real savings: retired platforms, rightsized contracts, removed duplicate support, and better unit pricing from combined volume. But those savings are easy to overstate and easy to lose. Without a disciplined baseline and ongoing measurement, the number reported to the deal sponsors is a snapshot that decays, and the gap between the claimed synergy and the realised one becomes a credibility problem when someone checks.
Software synergy is harder to measure than most integration savings for three reasons. First, the baseline is moving: both companies were already buying, renewing, and changing software when the deal closed, so the starting point is not a fixed number. Second, the savings interact: retiring a platform changes the volume on another, and rightsizing one contract can affect the terms of another. Third, the savings can reverse: a true up, a renewal at a worse rate, or a department re buying a retired tool can quietly claw back a synergy that was already booked.
Because of these dynamics, a synergy that looks captured in month six can be partly gone by month eighteen. Measurement that does not account for the moving baseline and the reversal risk overstates the result. The discipline is to measure against a defensible baseline, track the savings as they land, and watch for the reversals that erode them.
The method is to build a defensible baseline, attribute each saving to a specific action, and track realisation over time. The baseline is the combined run rate software cost of the two companies as they were, normalised for renewals and changes already in train. Each consolidation action then carries an expected saving: this platform retired saves this much from this date, this contract rightsized saves this much from the next true up. As each action lands, the realised saving is recorded against the expected one, and the variance is explained.
This turns synergy from a single headline into a tracked portfolio of actions, each with an owner, a date, and a number. It also makes the synergy defensible, because every pound claimed traces to a specific action and a specific contract change rather than to an estimate. That traceability is what survives scrutiny from deal sponsors, lenders, and the next round of diligence, and it rests on the reconciled position from post close license reconciliation.
| Element | What to capture | Why it matters |
|---|---|---|
| Baseline run rate | Combined cost before consolidation | Synergy is measured against a defensible starting point |
| Action attribution | Saving tied to each specific move | Every pound traces to a contract change |
| Realisation date | When the saving actually lands | Booked is not banked until it lands |
| Reversal watch | True ups, renewals, re buying | Catches savings that erode after booking |
| Variance explanation | Expected versus realised | Keeps the number credible under scrutiny |
Measuring and defending the synergy is part of integration and consolidation advisory, and the discipline that protects it is building a combined software governance model.
The most overlooked part of synergy measurement is the reversal. A saving booked at the point of action is not the same as a saving that persists. Three reversals are common. A true up reclaims headroom when combined provisioning exceeds a contracted level, turning a rightsizing into an unbudgeted charge. A renewal lands at a worse rate when the buyer lost timing leverage, so a contract saving partly unwinds at the next term. And a department re buys a retired tool, restoring the duplicate spend the consolidation removed.
Measuring synergy honestly means watching for these reversals and reporting net of them. A synergy programme that reports gross savings and ignores the claw backs will overstate its result and lose credibility when the run rate is checked. The defence against reversals is governance: a single purchasing policy stops the re buying, continuous tracking catches the provisioning before it becomes a true up, and controlled timing protects the renewal rate. Measurement reveals the reversal risk, and governance contains it. Engage your own counsel for legal interpretation of any true up or renewal clause.
A synergy figure that reports only the savings is half a number. Software consolidation costs money to achieve: migration effort to move off a retired platform, early termination charges on contracts ended before term, data migration, retraining, and the integration team time the work consumes. An honest synergy measurement nets these one time costs against the recurring savings, so the deal sponsors see both the run rate benefit and the investment required to capture it.
Ignoring the one time costs overstates the synergy and distorts the sequencing decisions. A consolidation that saves a modest amount each year but costs heavily to achieve may be worth doing later, or not at all, while one with a quick payback should be prioritised. Capturing both sides lets the buyer rank consolidation actions by payback period rather than by headline saving, which is how a synergy programme is actually run well. The recurring saving is the prize, but the cost to capture it is what decides the order in which the prizes are taken.
A software synergy figure rarely stays inside the integration team. It is reported up to the deal sponsors who underwrote the case, scrutinised by the finance function that has to see it in the run rate, and eventually examined by the next buyer or lender who diligences the business. Each of these audiences applies a different test, and a number built to satisfy only the integration team will not survive the others. Finance wants to see the saving in the actual cost base, not in a model.
This is why the measurement discipline has to tie every claimed saving to a contract change that shows up in spend. A synergy that exists only in a slide, with no corresponding reduction in what the company actually pays, is the kind of number that erodes trust when the finance team cannot find it. Anchoring each saving to a specific renegotiated contract, retired subscription, or eliminated support line is what lets the synergy claim move from the integration team into the audited accounts without being marked down.
The same traceability protects the business at its next transaction. A buyer diligencing the combined company will test whether the reported software synergies are real and durable, and a programme that can show baseline, action, realisation date, and the contract behind each pound passes that test. One that offers only a headline invites the discount, and the value the integration worked to create is quietly written down in the next deal.
Software synergy is rarely measured for its own sake. It is reported to deal sponsors who underwrote it, to lenders who priced it, and to the next buyer who will diligence it. Each of those audiences will discount a number they cannot trace. A synergy claim supported by a baseline, action level attribution, realisation dates, and a clear account of reversals is credible. A headline number with no traceability is treated as optimistic and marked down.
This is why measurement and the integration roadmap belong together. The roadmap sequences the actions that produce the synergy, and the measurement proves each one landed and held. Together they let the buyer report a software synergy that withstands scrutiny rather than one that has to be defended with assertions. For how the actions are sequenced, see the integration roadmap for the software estate, and for how the gains are protected, see avoiding compliance gaps during integration.
Measurement is one track of post merger software integration, alongside the integration roadmap for the software estate and building a combined software governance model. Engage your own counsel for legal interpretation of any contract or clause.
Tell us where the integration stands. We respond within one business day with a scoped, buyer side engagement that protects the synergy case you underwrote.
Book a confidential call