Synergy Tracking in M&A: From Deal Thesis to Realized Value

The synergy case is the foundation of every acquisition. The deal team builds it during due diligence. The board approves it. The integration team is measured against it.

The problem: the synergy case is usually a static document — a set of assumed savings with a timeline and a probability weight. And the people tracking whether those synergies actually materialized are working from a spreadsheet that hasn’t been updated since week 8 of the integration.

By the time anyone notices the synergy is underperforming, the integration is far enough along that it’s too late to course-correct. The $30M in IT cost synergies that was supposed to materialize is now looking more like $12M — but nobody found out until close-out reporting, not when the gap first appeared.

Why Synergy Tracking Usually Fails

It’s built as a reporting function, not a governance function

The typical synergy tracking setup: a spreadsheet with line items. Each line item has an assumption, a timeline, and an owner. Every quarter, the owner updates the status. This is reporting, not governance.

Governance means: when a synergy is at risk, something happens automatically — an alert, a review, a escalation. Reporting means: someone notices six months later and updates the spreadsheet.

The difference matters most in IT synergies, which are where most M&A integrations underperform.

IT synergies are the hardest to track

The synergy case usually has three categories: cost synergies, revenue synergies, and operational synergies. IT contributes primarily to cost synergies — and cost synergies from IT integration are the hardest to quantify accurately and the easiest to underperform on.

Why: IT synergy assumptions tend to be optimistic. “We’ll eliminate the duplicate Salesforce licenses” ignores that the licenses are on different contract cycles and can’t be cancelled without penalties. “We’ll consolidate the two Azure tenants” underestimates the complexity of migrating workloads that were built to operate independently. “We’ll decommission the legacy data centre” assumes the applications running there can be migrated — but discovery found three of them have undocumented dependencies on a system in the other entity’s network.

Discovery would have surfaced all three of those issues before the deal closed. But most acquisitions don’t do enough discovery before signing, and the synergy case is built on the incomplete picture.

The tracking cadences are misaligned

Integration programs track progress weekly. Finance tracks synergies quarterly. The integration team’s weekly burn-down chart shows tasks completed. The synergy tracker gets updated when finance asks for the quarterly report.

By the time a synergy gap appears in the quarterly report, the integration team has been working for 11 weeks without knowing the assumption was wrong. Course correction in week 11 is much harder than in week 2.

Building Synergy Tracking as a Governance Function

Map synergies to discovery data

Every IT synergy in the deal thesis can be traced back to a specific discovery finding. “Eliminate duplicate Salesforce licenses” traces to the license inventory from discovery. “Consolidate Azure tenants” traces to the cloud resource inventory. “Decommission legacy data centre” traces to the application dependency map.

When discovery data feeds the synergy tracker, the tracker becomes a live reflection of what the integration is actually accomplishing. If the license inventory shows 40 Salesforce licenses being used by 30 users, the synergy tracker shows the baseline. If the migration dashboard shows 25 of those 30 users migrated to a single instance, the synergy tracker shows the progress.

Set milestone targets tied to integration phases

Synergies don’t materialize all at once. They materialize in stages tied to integration milestones:

Day 1: Baseline established. What are we paying today, before any integration work? This comes from the discovery data — license inventory, infrastructure costs, vendor contracts.

Week 8 (Discovery Complete): What synergies are now available to pursue, given what we found? Discovery may have surfaced additional waste that wasn’t in the original synergy case, or may have invalidated some of the original assumptions.

Week 18 (Migration Wave 1 Complete): First wave of migrations done. License cancellation opportunities can be executed. First infrastructure decommission opportunities appear.

Week 36 (Migration Complete): Integration infrastructure is consolidated. The full synergy realization opportunity is available.

Year 2: Synergies fully realized. Contract cycles have turned, legacy infrastructure is decommissioned, organizational duplication is eliminated.

Each phase has specific synergy targets with specific owners. The governance layer tracks phase-gate achievement against those targets.

Build automated alerts for variance

When a synergy is tracking to miss its target by more than X%, an alert fires. Not at the quarterly review — immediately, at the point where the variance first appears.

For IT synergies, this means: when a migration wave completes but license cancellation hasn’t happened because the contract is on a 3-year cycle with a 6-month cancellation notice, the synergy tracker knows the timeline and flags the variance at the point where the delay first appears.

Track synergies by type, not just total

Not all synergies are equal. IT cost synergies fall into categories with different realization timelines and different certainty levels:

• License consolidation (high certainty, medium timeline): Can be executed when contracts come up for renewal or when cancellation penalties are acceptable. Realizable within 12-18 months.
• Infrastructure decommission (medium certainty, long timeline): Requires migrations to complete before the source infrastructure can be turned off. Realizable at 18-36 months.
• Headcount redundancy (low certainty, long timeline): The hardest IT synergy to realize. Organizational changes take time, HR processes have legal constraints, and the assumption that two IT teams become one often underestimates the complexity of the combined function.

Track each category separately so that the synergy tracker shows which bucket is performing and which is at risk.

The Governance Dashboard

ACQI Governance includes synergy tracking as a first-class function:

• Synergy register: Every synergy from the deal thesis, with baseline, target, timeline, and owner
• Realization tracker: Progress against each synergy, updated from integration milestone data
• Variance alerts: Automated alerts when a synergy is tracking to miss its target
• Scenario modelling: If this synergy doesn’t materialize, what is the revised deal value?
• Integration health score: Combined view of integration progress and synergy realization

The dashboard shows the board-level view (are we on track to realize the synergies that justified the deal?) and the operational view (what specific integration activities are driving or threatening each synergy target?).

The ACQI Governance module tracks synergies from deal thesis to realized value. See how it works. Request a demo →