Post-merger integration plan
Where the synergy case is either delivered or quietly written off. Day one, the first hundred days, and which of two organisations' processes actually survives.
The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.
What it is
The plan for turning two organisations into one, run from the point a deal is agreed rather than from the point it closes. Its whole purpose is to stop the synergy thesis from being quietly abandoned the moment the deal team moves on to the next one, which is where the majority of acquired value is actually lost.
- Day one
- What visibly changes on the first day for customers, employees and suppliers, and — as important — what deliberately does not change yet. Ambiguity on day one is where trust and key people are lost fastest.
- The first hundred days
- The sequence of what integrates first, chosen for what unlocks the rest rather than for what is easiest. Systems, reporting lines, and customer-facing processes are rarely integrated in the same order twice.
- Which process wins
- Where the two organisations' ways of working conflict, a decision is made and stated rather than left to whichever team shouts loudest. Undecided conflicts resolve themselves badly, in public, over months.
- Synergy tracking
- Every synergy from the original thesis, tracked against its owner and its date, not re-derived after close. A synergy case that changes after the deal is done is evidence something was missed or oversold.
- Retention of the people the deal depends on
- Named individuals whose departure would materially damage the case, with a specific reason for each to stay through the period that matters most.
- Stranded cost
- What cost remains after integration that the synergy case assumed would disappear — often IT, property or management layers that turn out harder to unwind than modelled.
How you run it
- Bring the synergy thesis in from the acquisition screenEvery synergy, its owner and its date. This plan exists to deliver that thesis, not to write a new one.
- Decide what changes on day one and what deliberately does notAmbiguity here is where trust and key people are lost fastest. State both explicitly, even the things staying the same.
- Sequence the first hundred days by what unlocks the restNot by what is easiest. Systems, reporting lines and customer processes rarely integrate in the same order twice — choose deliberately.
- Resolve every process conflict and state the decisionWhere the two organisations' ways of working differ, decide which wins and say so. An undecided conflict resolves itself badly, in public.
- Track synergies against the original thesis and name a retention listEvery synergy against its owner and date; every person the case depends on, with a specific reason to stay through the period that matters.
The prompt
Run this tool in your own Claude
The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.
Your playbook
It lands in the earliest stage this tool suits. Move it on the Playbook page.
You’ll need
- The synergy thesis from the acquisition screen, with owners named
- Which of the two organisations' systems, processes and people decisions win where they conflict
- The retention risk for people the deal depends on
You’ll end up with
- A day-one plan covering what visibly changes and what does not
- A hundred-day plan sequenced by what has to happen first
- Synergy tracking tied to the original thesis, not a new number invented after close