The deal room problem
Acquisition synergies are typically identified by the deal team during due diligence, presented to the board to justify the valuation, and then handed over to an integration team to deliver. The problem is that the deal team and the integration team are rarely the same people, the synergy assumptions are rarely tested operationally before the deal closes, and by the time the integration starts, the synergy targets have become commitments to investors rather than working hypotheses.
The result is predictable. McKinsey research consistently shows that between 50% and 70% of M&A transactions fail to achieve the synergies that justified the deal valuation. This is not primarily a financial modelling problem or a due diligence failure. It is an integration execution problem - and the roots of it are usually visible before Day 1 if anyone is looking.
"The synergies were there. We could see them. The problem was that realising them required decisions that neither business was willing to make post-close - and no one had agreed to make those decisions before signing."
- Integration Director, PE-backed healthcare group
The three types of synergy and why each fails differently
Cost synergies
The most commonly modelled synergy type. Typically involves headcount reduction, property rationalisation, procurement savings, and elimination of duplicated systems. Cost synergies fail most often because the assumptions are made at function level without understanding the operational interdependencies - cutting shared services without understanding what those services actually support, or assuming two finance teams can become one without accounting for the systems and process work needed to make that possible.
Revenue synergies
Cross-selling, new market access, combined customer base. Revenue synergies are the most optimistically modelled and the most commonly unrealised. They typically assume that two sales teams will willingly sell each other's products, that customers will respond to combined propositions, and that the operational infrastructure exists to service a combined offering. None of these things happen automatically, and revenue synergies almost always take longer to materialise than cost synergies - sometimes by years.
Capability synergies
Access to talent, intellectual property, technology, or market knowledge the acquirer lacked. These are often the stated strategic rationale for deals that are hard to justify on financial synergies alone. Capability synergies fail most often because the capabilities being acquired are embedded in the people and culture of the acquired business - and those people leave when the culture changes post-acquisition, taking the capability with them.
Six reasons synergies remain unrealised
1. Synergy targets were set before operational design
The numbers are built into the deal model before anyone has designed how the combined business will actually operate. The assumptions cannot be tested against reality until it is too late to change the deal.
2. No single owner for synergy delivery
Cost synergies span Finance, HR, IT, and Operations. Revenue synergies span Sales, Product, and Marketing. Without a single integration office with authority across all of these, accountability fragments and synergies fall in the gaps.
3. Integration planning starts after close
Detailed integration planning in most mid-market deals starts in the weeks after close, not before. This means the first 30-60 days - when the organisation is most receptive to change and most anxious for direction - are spent planning rather than acting.
4. Business-as-usual is deprioritised
Integration consumes management time that was previously spent running the business. Revenue drops, service quality slips, and key customers become uncertain. The financial model did not include a line for integration distraction.
5. Technology decisions are deferred
Two businesses with different ERP, CRM, and finance systems cannot realise most cost synergies until they operate on common platforms. The technology integration decision - which system wins - is often deferred because it is contentious, and the synergies are deferred with it.
6. Cultural resistance is underestimated
Senior management in the acquired business often cooperates visibly while middle management - which controls day-to-day operations - resists quietly. The integration looks like it is progressing until it stops progressing.
Culture risk in M&A: why it is misunderstood
Culture risk in M&A is frequently described as a soft issue - a concern for HR while the hard integration work happens elsewhere. This framing is wrong in a specific way: culture determines whether decisions that have been made on paper are actually implemented in practice.
The most common form of cultural resistance in acquisitions is not overt. Senior leaders in the acquired business do not hold press conferences announcing they disagree with the new direction. What happens is more damaging: they comply with the letter of integration decisions while making them unworkable in practice. Processes are designed in ways that require the old system. Data definitions remain different. Customer relationships are managed in ways that make standardisation difficult.
The practical implication is that cultural due diligence cannot be separated from operational due diligence. The question is not just "are the cultures compatible" - it is "do the leaders of this business have the operational authority and the motivation to implement the changes the integration requires?"
Where cultural risk is identified, the response is not a culture programme. It is a clear decision about which leaders will be in which roles post-integration, made early and communicated directly - not held back until the deal team has moved on.
Technology integration after a merger
Technology integration is typically one of the two or three largest single-line items in an integration budget and one of the most commonly underestimated risks. The reasons are structural:
- Due diligence technology assessments focus on licensing cost and support contracts, not on data quality, configuration complexity, or the degree of customisation that has accumulated over years of use
- The "which system wins" decision is politically charged and is often resolved based on the acquirer's preference rather than on a rigorous assessment of which system is actually better suited to the combined business
- Data migration between systems - particularly financial, customer, and operational data - is consistently underestimated in both cost and elapsed time
- The period during which two systems are running in parallel is operationally expensive and creates reporting difficulties that directly impair the management information the integration governance process depends on
The organisations that handle technology integration well treat it as a workstream that needs to start planning at due diligence stage, not as a project that can be scoped after close. The decision about whether to migrate, integrate via API, or run parallel systems indefinitely needs to be made with full awareness of the operational and financial implications - not inherited as a default.
The Day 1 plan and why it shapes everything that follows
Day 1 is the first day of combined operations after deal close. What happens on Day 1 - and in the days immediately before and after it - has a disproportionate effect on how the integration proceeds.
A robust Day 1 plan covers:
- Leadership communications: what is said to employees of both businesses, by whom, and how - before any external announcement
- Operational continuity: confirmation that critical operational processes continue uninterrupted - customer service, payroll, supplier payments, regulatory reporting
- Governance and reporting: how the combined business is managed from Day 1 - who attends which meetings, what numbers are reported, who makes which decisions
- Retention of key people: identification of the individuals - not necessarily the most senior - whose departure in the first 90 days would materially damage the business, and confirmation of their retention arrangements
- Quick wins: two or three visible changes that demonstrate the integration is progressing and creating value, planned in advance and ready to announce in the first 30 days
Organisations that treat Day 1 planning as an administrative task - rather than as the first major operational test of the combined business - typically find that the tone it sets is harder to change than they expected.
What good integration looks like
The distinguishing characteristics of acquisitions where synergies are realised are consistent:
- Integration planning starts during due diligence, not after close - the integration team is engaged before the deal completes so that Day 1 is ready, not being designed
- A single integration office has accountability for synergy delivery across all workstreams, with direct access to the CEO and reporting into the board on a defined cadence
- Synergy assumptions are stress-tested operationally before the deal closes, not accepted as financial model outputs
- Leadership decisions in the acquired business are made early and clearly - people know their role in the combined organisation within 30 days of close, not 90
- Technology integration has a defined decision and a sequenced plan, not a deferred working group
- Business-as-usual performance is tracked independently from integration milestones - and drops in trading performance are treated as integration risks, not acceptable collateral
Acquiring or integrating a business?
Assured Velocity provides independent M&A integration support from pre-close planning through Day 1 and the first 100 days. No vendor relationships. Outcome-focused.