Merger integration playbook

A merger integration playbook is the written routine a combined company follows after the deal closes. It names who runs the integration, what gets decided in the first hundred days, how systems, contracts and people are merged, and what is left alone.

It is not the deal itself. A merger is the legal union of two firms and the share swap that makes one entity out of two. That page covers the transaction; this one covers the operation afterwards.

Most of a playbook is written before the deal is announced, using only public information, then filled in once the data room opens. Teams that start it after close spend the first month arguing about who decides.

The work is unglamorous and it is where value leaks. Two payroll systems, two helpdesks and two sets of vendor contracts all have to become one — on a date, without dropping a customer.

Key takeaways

• The playbook starts at close, not at signing, when the deal team hands over to an integration lead.
• A named integration office with its own budget beats a steering committee, because somebody has to be able to decide.
• Some steps wait for competition clearance, so the legal calendar sets the operational one.
• Deciding what not to integrate is half the work; two brands can share a back office and keep separate front ends.

How it works

A playbook sets out phases, owners and decision rights. The usual shape is a hundred day plan, a twelve month plan and a steady state, each with a named owner, a short list of decisions and a weekly meeting that clears blockers.

Before anything moves, the playbook asks what each change will actually hit. A change impact analysis lists the processes, systems and roles a decision touches, which is how you learn that one supplier code sits inside four board reports.

People readiness is the other half. A change readiness assessment tells you whether a team can absorb a new system this quarter or will quietly keep the old one running beside it.

Decision rights matter more than the plan. Write down who can approve a system choice, who can approve a redundancy and who can approve a contract exit, with a named person against each, before week one.

Customers notice integration before employees do. Invoices change format, support numbers move and account managers get reassigned, and each of those is a reason to call a competitor — so customer facing changes go last.

Timing is not entirely yours. The Federal Trade Commission’s antitrust guide notes that premerger notification under the Hart-Scott-Rodino Act lets agencies examine the likely effects of proposed mergers before they take place.

The duty sits in statute. Section 18a of Title 15 of the United States Code requires both sides to file and sets a waiting period that ends on the thirtieth day after the filings are received, or the fifteenth for a cash tender offer.

So integration steps that assume a combined market position wait for clearance, and a good playbook says plainly which ones those are.

Examples

Integration looks different by size and sector, but four questions always recur: which system survives, which brand survives, who reports to whom, and which contracts get renegotiated. Here is how that plays out in practice.

Deals that need clearance first. Two competitors cannot merge their pricing teams or share customer lists while the review runs, so the playbook keeps those workstreams sealed and dates them from clearance rather than from close.

Running two sets of operations separately for a few months is a cost the plan has to carry openly.

Back office consolidation. Mid sized firms often move payroll and accounts payable to a provider during year one — which is an outsourcing transition plan with a merger wrapped around it.

Unwinding a decision. If the combined company later brings that work back in house, the same discipline runs in reverse under a reverse transition plan, facing the same question about which system survives.

Overlapping vendor contracts. The combined firm usually holds two contracts for the same service with different end dates. The cheaper rate is rarely available until the later one expires, so the saving lands in year two.

A playbook also records what will not be measured. Chasing cost-saving claims nobody can verify produces a spreadsheet nobody believes, and the integration office loses the authority it needs. Measure three things well instead of thirty badly.

Related terms

• Transition costs outsourcing: the one off cost of moving work; the playbook budgets it, this term defines it.
• Change control notice: the formal record of an agreed scope change, which a live integration generates weekly.
• Merger: the legal union and the deal itself; the playbook covers everything after it closes.
• Change impact analysis: maps what a single change touches before anyone approves it.
• Reverse transition plan: moves work back from a provider, the mirror image of a transition in.

FAQ

When does a merger integration playbook start?

It is written before close and used from day one. The deal team hands over to an integration lead the morning the transaction completes.

Who should own merger integration?

A dedicated integration office with its own budget and a direct line to the chief executive. A part time steering committee cannot clear blockers fast enough.

What belongs in the first hundred days?

Day one essentials come first: payroll, building access, customer notices and a single point of contact. Organisation design, contract rationalisation and the decision on which systems survive follow.

Should every system be merged?

No — and saying so early saves a year of argument. Two brands can share finance, payroll and procurement while keeping separate products, pricing and sales teams.

How long does merger integration take?

Systems and organisation work usually fills the first year, with the remainder settling over the following one or two. The playbook’s job is to make that span predictable rather than short.

Start your provider shortlist on Outsource Accelerator before the integration timetable is fixed.