The pattern
The deal closes. The announcement goes out. The leadership teams shake hands. And then, almost immediately, the operating reality of two businesses trying to become one starts to surface — in ways the deal model did not fully anticipate.
Reporting lines are ambiguous. Systems do not talk to each other. Two finance teams are producing two versions of the same numbers. A key person in the acquired business has handed in their notice. The synergies in the investment case are real — but the path to realising them requires making a hundred operating decisions simultaneously, in a business where the ownership of those decisions has never been defined.
Six months later, the board is asking why integration is taking longer than planned. The answer is almost always the same: the integration was treated as a project when it needed to be treated as an operating system problem.
Why the first 100 days are decisive
The first 100 days of an integration set patterns that are extraordinarily difficult to change later.
The acquired business is watching. Every decision made — or deferred — in the first weeks sends a signal about how the combined organisation will work. Ambiguity about decision rights is interpreted as incompetence or indifference. Speed and clarity are interpreted as control and intent. The cultural integration does not happen in a series of away days — it happens in the operating decisions made under pressure in the first quarter.
The financial exposure is also concentrated in this period. Most value destruction in acquisitions happens early — through talent loss, customer disruption, and operating inefficiency created by ambiguity. Synergies take time to realise. Costs of poor integration are immediate.
The first 100 days do not determine the long-term success of the acquisition. They determine whether long-term success is still possible.
The three things integrations get wrong
1. No single operating plan.
The most common integration failure is structural: two organisations running in parallel, each under its own operating model, with a co-ordination layer sitting above them that has no real authority.
The acquirer has its systems, its metrics, its cadence, its reporting. The acquired business has its own. The integration plan describes how they will eventually be harmonised. But in the meantime, both continue operating independently — which means the combined entity has no single view of its performance, no agreed metrics, and no unified accountability structure.
Decisions that should be made in the combined business get deferred because nobody knows whose model applies. Reporting takes twice as long because two sets of data need to be reconciled. Synergies that depend on operational alignment cannot be tracked because the operating model has not been unified.
The integration needs a single operating plan from day one — not a harmonisation roadmap, but an actual operating structure that defines how the combined business runs immediately, not eventually.
2. Decision rights are left undefined.
Integrations create an enormous volume of ambiguous decisions. Who approves a hire in the acquired business — the legacy leadership team or the new parent? Who owns the customer relationship when accounts span both entities? Which finance system is the source of truth? Who makes the call when the two cultures disagree?
Every one of these decisions, left undefined, consumes leadership time, creates anxiety in the acquired team, and slows execution. And unlike the normal operating state — where decision rights can develop organically over time — integrations require explicit decisions to be made immediately, under time pressure, while both organisations are watching.
The integration office must define decision rights for the combined entity before the first week ends. Not a comprehensive governance framework — a practical, specific set of rules covering the decisions that will arise most frequently and have the highest operational impact.
3. Synergies are tracked on a spreadsheet, not in the operating model.
Every deal model has a synergy case. Cost synergies from consolidating duplicate functions. Revenue synergies from cross-selling. Working capital improvements from combined purchasing power. The model is credible. The numbers are real.
But synergies do not realise themselves. They require operating decisions — specific actions, made by specific people, on specific timelines — to convert from a line in a model to cash in the business. And when those decisions are tracked in a spreadsheet rather than embedded in the operating cadence, they do not get made.
The synergy tracker becomes a reporting exercise rather than an execution mechanism. Progress is described rather than owned. By the time the board asks why the synergy case is underdelivering, the answer is that the decisions required to realise the synergies were never formally assigned to anyone.
What a well-run integration looks like
Integration execution is not complicated. But it requires a level of operating discipline that most businesses apply to steady-state operations but not to the inherently chaotic environment of a deal.
An integration management office with real authority.
Not a co-ordination function — an operating structure with a named leader, a defined mandate, and the decision authority to make calls across both entities without escalating everything to the board. The IMO is the temporary operating system of the combined business. It exists to make decisions that cannot wait for the permanent operating model to be designed.
The IMO leader needs three things: direct access to the CEO or PE partner, the mandate to resolve cross-functional conflicts without deferring them, and a clear sunset — an end date at which the IMO hands over to the permanent operating structure.
Integrating three acquisitions simultaneously — two core, one adjacent — required exactly this operating structure: a single plan, unified metrics, and synergies owned by people rather than tracked in a model. The multi-acquisition integration case study covers what that looked like in practice.
A single operating plan, not two parallel ones.
Within the first two weeks, the combined business needs one operating plan. Not the acquirer’s plan plus the acquired company’s plan, co-ordinated by a steering committee. One plan, with unified metrics, a single reporting structure, and a weekly operating cadence that covers the combined entity.
This does not mean the acquired business loses its identity or its operating model immediately. It means there is a single agreed view of performance and a single mechanism for making decisions — which is the minimum required to run a combined business rather than two adjacent ones.
Synergies owned by people, not by a model.
Every synergy in the investment case should have a named owner, a specific delivery date, and a defined set of actions required to realise it. The synergy tracking mechanism should be part of the weekly operating review — not a separate reporting process run by the finance team.
When a synergy is at risk of missing its timeline, the owner presents the obstacle and the proposed resolution in the weekly review. The IMO makes the call. The synergy stays on track or is formally revised. The model reflects reality rather than hope.
Leadership and culture decisions made early.
The single most costly integration mistake is deferring leadership decisions in the acquired business. Which roles survive in the combined entity? Where do reporting lines land? Who owns the customer relationship?
These decisions are uncomfortable. They are usually deferred because the acquirer does not want to create anxiety in the acquired team before integration is underway. But the anxiety already exists — and ambiguity makes it worse, not better. The people most likely to leave are the ones with the most options, and they make their decision in the first sixty days based on what they observe about how the integration is being run.
Leadership decisions should be made and communicated within the first thirty days. Not the complete organisational design — that takes longer. But the decisions that affect the senior team’s confidence in the integration’s direction.
The 100-day operating checklist
A practical integration starts with five things in the first two weeks:
- IMO established — named leader, defined mandate, direct board access, clear sunset date
- Single operating plan — one set of metrics, one reporting structure, one weekly cadence covering the combined entity
- Decision rights defined — practical rules for the high-frequency, high-impact decisions that will arise immediately
- Synergies assigned — every synergy line has a named owner, a delivery date, and a defined action plan
- Leadership decisions made — senior structure confirmed and communicated within thirty days
Everything else — systems harmonisation, brand integration, culture alignment — follows from this foundation. Without it, every subsequent integration workstream operates in ambiguity.
The diagnostic
Four questions identify integration risk quickly:
- Is there a single operating plan for the combined entity — one set of metrics, one cadence, one view of performance — or are two parallel operating models still running?
- Does every synergy line in the deal model have a named owner and a specific delivery date?
- Have the senior leadership decisions in the acquired business been communicated — or are people still waiting to find out what their role is in the combined entity?
- When a cross-entity conflict arises — a decision that spans the acquirer and the acquired business — is there a defined mechanism for resolving it, or does it escalate to the CEO?
Why this matters beyond the deal
Post-acquisition integration is the most concentrated test of an organisation’s operating discipline. The conditions — ambiguity, speed, high stakes, cultural friction, competing operating models — amplify every weakness in the operating system and every strength.
Companies that integrate well do not do so because they have a better integration playbook. They do so because they have a functioning operating system — clear decision rights, owned metrics, a weekly cadence that produces decisions rather than updates — that they can extend to cover the acquired entity immediately, rather than building it from scratch under deal pressure.
The acquisition is the strategy. The integration is the execution. And as with every other form of execution, the gap between intent and outcome is determined by the operating discipline that converts one into the other.