Framework library · M&A and corporate strategy
Post-merger integration
Post-merger integration turns the deal case into dated work: what must be ready on day one, what is decided in the first 100 days, and what takes a year or more. The integration approach comes first, because a business to be absorbed and one to be preserved need different plans. It is set by how much the two businesses depend on each other and how much autonomy the acquired one needs to keep its value.
Use it when
- A deal has been signed and the two businesses must run as one, or deliberately apart, from the day it closes.
- The deal case depends on synergies that need dated actions and named owners.
- Customers, staff and regulators need to see a coherent sequence of what changes and when.
- A regulator has attached conditions to the deal, such as remedies, divestments or network commitments, with dates the integration must meet.
Avoid it when
- The acquired business will be held at arm's length with only financial reporting. Light governance and an acquisition integration scorecard are enough.
- You need to know what the synergies are worth. Size them in a synergy assessment. The roadmap schedules the work but does not price it.
- You are separating a business rather than combining one. Use a carve-out plan, which has its own day one and transitional services.
How to run it
Choose the integration approach
Decide how far the businesses will be combined: absorbed completely, preserved as they are, combined gradually, or held as an investment. The choice sets how much roadmap there is.
Set up the integration office
A small team with an integration lead, a weekly rhythm and the authority to settle questions between workstreams. Name a leader from each company for every workstream.
Plan day one backwards from closing
List what must work on the first morning: payroll, customer service, billing, network operations, legal entities and the message to staff and customers. Everything else can wait.
Fill the first 100 days with decisions
Leadership appointments, the operating model, the target network and IT architecture, the brand. A decision taken late usually costs more than one taken imperfectly.
Put every synergy on the roadmap
Each synergy in the deal case becomes an item with a start, an end and an owner. A synergy with no item on the roadmap will not be delivered.
Review weekly and re-plan quarterly
Track progress in the integration office every week, and reset the roadmap each quarter as what is found after closing replaces what diligence assumed.
Work through it
Answer the questions below, or load the worked example to see a finished one. The drawing updates as you type. Export the result as a PowerPoint deck, a Word document, an Excel workbook, a PDF or plain text.
What you type stays in this browser, so you can close the page and come back to it. It is not sent to Blue Prysm or anyone else, and the exports are made here, on your device. Privacy policy.
Mistakes to avoid
- Planning the technical integration and leaving customers and staff to hear about changes after they happen. Customer churn and the loss of key people are where merger value leaks first.
- Treating day one as the finish line. Most synergies arrive between months 4 and 12, when management attention has moved on.
- Integrating everything by default, including the parts of the acquired business that made it worth buying. Decide what to preserve before deciding what to combine.
- Running the integration office as a reporting function. It needs the authority to settle a dispute between workstreams within a week.
- Starting network or IT migration before the target architecture is decided, and then migrating twice.
Where it comes from
Philippe Haspeslagh and David Jemison, Managing Acquisitions: Creating Value Through Corporate Renewal (Free Press, 1991), set the choice of integration approach (absorption, preservation, symbiosis or holding) by weighing the need for strategic interdependence against the need for organisational autonomy. The pre-close, day one, 100-day and first-year structure used here is common practice rather than any one author's. Source.
Use it with
Work through it with us
The frameworks here are free to use as they stand. If you would rather work through the question behind this one with us, these are the ways an engagement starts.