Transactions

Synergies

The cost savings and revenue benefits expected from combining two businesses — a primary component of acquisition rationale and a consistent source of post-acquisition disappointment when operational delivery does not match pre-deal modelling.

Standard Definition

Synergies are the expected benefits from combining two businesses: cost synergies (overhead elimination, procurement consolidation, facility rationalisation) and revenue synergies (cross-selling, market access, combined pricing power). In acquisition modelling, synergies justify the premium paid above standalone value. In practice, they are consistently overestimated — particularly revenue synergies, which depend on customer behaviour that is difficult to predict.

How each stakeholder reads it

Synergies looks different depending on your role.

Synergies are why a strategic buyer may pay more than a financial buyer. Their ability to eliminate your overhead, consolidate procurement or access your customer base justifies a higher price. The risk is that acquisition models overstate synergies — and the premium paid for synergies that are not subsequently delivered destroys value.

Our experience is that cost synergies are more reliable than revenue synergies. We model synergies conservatively and build detailed integration plans before close, because synergy delivery is an execution problem — not a modelling exercise. The businesses where synergies were not delivered were almost always ones without integration plans before the transaction closed.

Synergy realisation requires disciplined sequencing. Cost synergies require headcount decisions, system integrations and facility rationalisation — each creating disruption. Revenue synergies require commercial team alignment, product training and customer communication — each taking longer than assumed. Treating synergies as a natural consequence of combination rather than a managed program will not deliver them.

Synergy governance requires defined owners, milestones and timelines for each identified synergy. Synergies in the model but not in the operating plan will not be delivered. The board should receive regular integration progress reporting against synergy realisation milestones.

Why it matters

Synergies are delivered in operations, not in models.

Cost synergies are more reliable than revenue synergies. The businesses that deliver synergies most consistently begin integration planning before close — not after. A detailed week-by-week integration roadmap before day one is the difference between delivered and assumed synergies.

Revenue synergies that require system integration cannot be delivered until integration completes — typically 12–24 months. Revenue synergies that require cross-selling cannot be delivered until commercial teams are aligned and trained — typically 6–18 months. The synergy timeline is almost always longer than the model assumes.

Operational context

What shapes synergies inside a business.

Integration Planning

Synergies with defined owners and milestones before day one are significantly more likely to be delivered.

Cultural Compatibility

Incompatible operating cultures destroy value through attrition and conflict during integration.

System Complexity

System integration almost always takes longer and costs more than projected, delaying dependent synergies.

Common failure patterns

Revenue synergies built on customer cross-buy assumptions that do not materialise
Procurement savings delayed by system integration complexity and timeline extension
Headcount synergies creating capability gaps that must be re-hired at cost
Integration consuming management attention and leaving core businesses under-managed

Semantic relationships

Buyer Interpretation

How buyers and M&A advisers read this.

See the Buyer and Board perspectives in the stakeholder tab panel above. This is how acquirers, M&A advisers and lenders interpret this term during a transaction — and how it directly affects deal structure, pricing and terms.

Common Founder Mistakes

Synergy assumptions that distort deal structure and value.

The failure patterns listed above describe how this term most commonly creates value problems for founders — through misunderstanding, mismanagement or mispresentation during a process. Each pattern has a correctable upstream cause.

Related Doctrine