Reference

What is integration readiness?

Integration readiness is whether the buyer can run the integration. That is a different question from whether the synergies exist.

A buyer is ready when it has decided what it is integrating for, and how far. Someone runs it full-time, and that person is not the chief executive. The buyer can take control on the first day and fill the leadership quickly, through a selection process run in the open. It has a plan to keep customers and to keep both businesses hitting their numbers. It can track the whole thing against a baseline.

In our experience most acquisitions fail on execution, not on the deal. The failures are the same ones every time. Under-communication, no master plan, lost momentum, and a Day 1 that arrives as a date on the lawyers' timetable.

The deal case answers whether the synergies are real, how big they are and who is being paid for them. Readiness answers whether the buyer will get them. The two are scored separately because they fail separately. A good deal can be integrated badly, and often is.

What integration readiness is not

Readiness is not a synergy number. The number belongs to the deal case. Readiness asks whether a baseline, an owner and a rhythm exist to turn it into savings in next year's budget.

It is not a hundred-day plan on its own. A hundred-day plan is one output.

Readiness asks three things. Have the decisions the plan depends on been made? Does someone have the authority to run it? Can the business absorb it while still trading?

And it is not a bank-scale programme office. Below a certain size, the machinery is one good person, one weekly meeting, one tracker and a checklist of a few dozen items. The test is whether those exist, at any headcount.

1. The end state: what are we integrating for, and how far?

The first area is intent. Full integration is assumed because it is the default, and the deal rationale is the only document.

A ready buyer has written down which functions integrate fully, selectively or not at all, and why. It has written down what must not change for customers. The big decisions are each marked as closed, current thinking or open, with a date: leadership, brand, systems, sites, which practices survive. The target's sources of advantage are named and marked "do not touch". That way the acquirer's way does not win by default.

As a buyer, you should settle these before the deal closes:

Write one page on what the deal is for, and let it decide how far to integrate.
Go function by function. Mark each one as integrate fully, integrate in part, or leave alone, with the reason.
List the big decisions: leadership, brand, systems, sites. Mark each as closed, current thinking or open, with a date.
Name what the target does better than you, and mark it "do not touch". Otherwise your own way wins by default, and you remove what you paid for.
Write down what must not change for customers.

2. Governance: who runs it, and who decides?

The second area is the machinery. The failure is the chief executive, the finance director or the deal adviser "keeping an eye on it" on top of their day job. Nobody can say who decides a cross-functional issue. Every argument goes to the owner, one at a time.

A ready buyer has a named integration lead with stature on both sides. That person is freed from most of their day job, with written decision rights. A steering group meets weekly through the first hundred days, with the authority to remove roadblocks. A handful of guiding principles settle arguments before they start: customer first, best of both, speed over perfection. Each workstream belongs to the line manager who will live with the result, with their best people backfilled.

To get the machinery right, a buyer needs to:

Name one integration lead, with standing on both sides. Free them from most of their day job.
Write down who decides what. Test it: ask three executives who settles a cross-company issue, and check you get one answer.
Run a weekly steering group for the first hundred days, with the authority to clear roadblocks.
Agree a handful of principles that settle arguments before they start. Customer first. Best of both. Speed over perfection.
Give each workstream to the line manager who will live with the result, and backfill their day job.
Keep one plan, in one place.

3. Day 1: can we take control on the first morning?

The third area is the hinge. Day 1 is either "nothing changes" or "everything changes". The same people are asked to do both control and optimisation in week one.

A ready buyer has a checklist of a few dozen actions by function. Each has an owner and a date, and the list is reviewed daily in the last fortnight. Bank signatories, approval limits, payroll, insurance, contracts with change-of-control clauses and reporting lines are all settled before close, within what can legally be shared. Every manager in the target knows who they report to and what they can approve on the first morning. For the first weeks, a daily forum of people who can decide handles what has gone wrong.

Whether the buyer takes control on Day 1 is a practice in the readiness area of an integration check. What the two ends look like:

Lagging: Bank signatories, approval limits, payroll, insurance cover and reporting lines are discovered after close; the target's managers do not know who they report to.
Leading: Delegations, banking, payroll, insurance, contracts with change-of-control clauses and interim reporting lines are all settled before close. Every manager in the target knows their line and their limits on the morning of Day 1.

Before the first morning, make sure you have done the following:

Build a Day 1 checklist of a few dozen actions by function, each with an owner and a date. The lawyers' completion checklist is a different document.
Settle the basics before close: bank signatories, approval limits, payroll, insurance, and contracts with change-of-control clauses.
Tell every manager in the target who they report to, and what they can approve, before the first morning.
Review the checklist daily in the last fortnight.
Hold a daily forum for the first weeks, attended by people who can decide.

4. People: how fast, and how fairly?

The fourth area is leadership and culture. Roles become "co-heads" to avoid a decision. The second level waits months to hear, and the good ones do not wait.

Retention is a bonus offered a month before close, to a list nobody agreed. By then the two people who mattered have already accepted offers. The competitors called them on announcement day.

A ready buyer names the top team at close and the next two levels within weeks. No role has co-heads, and the selection process runs in the open. The few people the value depends on are listed by function, with their flight risk. Each gets a conversation within days of announcement, and levers beyond money.

The specific cultural differences are written down: how decisions are made, what gets rewarded, attitude to risk. The buyer chooses what to harmonise and how fast.

On people, the steps that matter most are these:

Name the top team at close, and the next two levels within weeks. No co-heads.
Run the selection process in the open, so people can see how it works.
List the few people the value depends on, with their flight risk. Speak to each within days of the announcement. Competitors will call them the same morning.
Offer more than money: a role, a project, a say.
Compare the cultures. How are decisions made? What gets rewarded? What is the attitude to risk?
Say which way it is going to be, and how fast.

5. Momentum: do customers stay and do the numbers hold?

The fifth area is the one that dies first. Customers hear about the deal from the press, or from a competitor who calls them the same morning. Nobody owns the accounts both companies share. Two account managers turn up at the same customer with different price lists.

Sales incentives are suspended "until things settle", and the pipeline settles with them. Management attention goes entirely inward. Results slip, and the slip is called a merger cost.

A ready buyer lists its main customers by value and by how much changes for them. Each gets an owner and a call in the first week, and the buyer tracks attrition weekly. The front line is kept out of integration work. Incentives are kept or sharpened. A handful of visible wins land in the first ninety days, so people see the merger working.

To keep customers and the numbers steady, a buyer should:

List the main customers by value, and by how much changes for them. Give each an owner.
Call each one in the first week, before a competitor does.
Decide who owns the accounts both companies share, and agree one price list before anyone visits.
Track customer losses weekly.
Keep sales incentives running, or sharpen them. Never suspend them "until things settle".
Keep the front line out of integration work.
Land a handful of visible wins in the first ninety days.

6. Tracking: is there a baseline, a scorecard and a rhythm?

The sixth area is whether anyone will know how it is going. The synergy number is the only measure. Nobody agreed a starting point, so every saving is disputed. Nobody measures customers or staff.

Risks sit in a register nobody has opened since week two. Reviews look backwards and celebrate. The big failures, a systems cutover or a lost customer, are discovered from the market.

A ready buyer has a baseline both sides accept. Its scorecard covers money, project and risk, customers and employees. A declared steady state says when the integration is over. Each accepted synergy is an owned initiative with a stage gate and a plan-versus-actual.

Reviews are weekly and look forward, at what is late, big or broken. Communication is a workstream with a plan by audience. It keeps going after the launch email.

So that you know how it is going, put these in place:

Agree a baseline both sides accept, before close. Without one, every saving is disputed.
Build a scorecard that covers money, projects and risks, customers, and employees.
Make each synergy an owned initiative, with plan against actual.
Hold weekly reviews that look forward: what is late, what is big, what is broken.
Run communication as a workstream, with a plan for each audience. Give managers an answer to "will I have a job?" before they are asked.
Say in advance what "finished" looks like, so the integration has an end.

When to start

Before close, within what can legally be shared. A clean-team arrangement where needed, a joint planning workshop, an interim operating model, and a hundred-day plan the target's leaders have already seen. A buyer that starts on completion day starts a month late. The customers and the competitors have used the month.

Readiness can be checked before the deal signs, when it is cheapest to fix. The integration check asks the six areas in ten minutes and says which ones are not ready.

Frequently asked questions

How much should we integrate? As much as the deal rationale needs, and no more. A bolt-on bought for its customers may need shared finance and nothing else. A merger of similar size needs the big decisions made early. "Full integration by default" is the most expensive answer. Buyers also pick that one most often without deciding.

Who should lead it? Someone with stature on both sides, freed from most of their day job. They need written decision rights and a direct line to the owner. It should be neither the chief executive, who has a company to run, nor the deal adviser, who leaves.

How long does an integration take? The first hundred days decide it. Control on Day 1, leadership named within weeks, quick wins by the end of the quarter. The rest runs to a declared steady state. For a business of ordinary size, that is usually inside a year.

What if we have never done this before? Then the check will say so, and that is useful. Make the first acquisition small and run it as a practice. The capability is one good person and a weekly rhythm. The first deal builds it, and the rest reuse it.

Updated 2026-09-26.