Here’s the uncomfortable truth about most deals: the negotiation gets the attention, and the integration gets the leftovers.
The financial model is stress-tested to three decimal places. The legal work runs for months. Then the deal closes, everyone exhales — and the actual work of turning two organisations into one begins with no owner, no sequence, and no plan. That gap is where deal value goes to die.
A post-merger integration plan is the thing that closes that gap. Not the checklist of tasks — I’ve written a separate post-merger integration checklist for that — but the framework that decides what happens when, who owns it, and how you’ll know it’s working. This piece is about the framework. Specifically, the first 100 days, because that’s the window where an integration either builds momentum or quietly stalls.
I’ve led these programmes. What follows is the structure I use.
Why most integrations drift without a plan
Integrations rarely fail at the technical layer. Data gets migrated. Contracts get novated. Systems get connected eventually. What fails is the coordination — a pattern Harvard Business Review and McKinsey have documented extensively: the hundred decisions that each need someone to own them, in the right order, before the next one can happen.
Without a plan, three things go wrong, every time.
Everything becomes urgent at once. Finance wants the general ledgers consolidated. IT wants identity and access sorted. Sales wants a unified pipeline. HR wants the org design signed off. All of it is real, all of it is competing for the same small group of people, and with nothing sequencing the work, the loudest voice wins rather than the most important one.
Nobody owns the seams. Each function will run its own slice competently. The failures happen between functions — the customer data that HR needs but IT controls, the payroll cutover that depends on a finance decision that depends on a legal entity that hasn’t been confirmed. Those dependencies live in the gaps, and gaps have no natural owner.
The clock runs out before anyone notices. Integration energy is highest in the first few weeks and decays fast. Miss the early window and you’re trying to force change through an organisation that has already gone back to business as usual. Momentum is a resource, and it’s non-renewable.
A plan fixes all three by doing one unglamorous thing: it makes the sequence explicit and gives every piece of work an owner and a date.
What a post-merger integration plan actually is
Let me be precise about terms, because “plan” gets used loosely.
A post-merger integration plan is not a Gantt chart with a thousand rows, and it’s not the task checklist. It’s a decision framework with four parts:
- The workstreams — the discrete bodies of work (finance, technology, people, customer, brand, legal, operations) that each need a lead and a remit.
- The sequence — what has to happen before what, expressed as phases rather than dates, so the plan survives contact with reality.
- The governance — how decisions get made, escalated, and communicated, so the programme doesn’t stall every time two workstreams disagree.
- The measures — the small set of indicators that tell you whether the integration is actually delivering the value the deal was built on.
Everything below hangs off those four parts. The checklist is the tactical layer underneath — use both together. This is the map; the checklist is the turn-by-turn.
Pre-close: the groundwork that decides everything
The best integrations are half-run before the deal closes. You usually can’t act on much pre-close — competition law and confidentiality see to that — but you can prepare, and preparation is where the first 100 days are won or lost.
Three things matter before Day 1.
Appoint the integration lead now, not later. This is the single highest-leverage decision in the whole programme. One person needs to own the integration end to end — not the CFO doing it in the margins, not a committee, one accountable lead with the authority to make cross-functional calls. If that person isn’t named before close, the first two weeks after close are spent working out who’s in charge instead of integrating.
Agree the integration thesis. Why did this deal happen? Cost synergies? Market access? Capability? Talent? The answer dictates everything about sequencing. A cost-driven deal front-loads consolidation; a growth-driven deal protects the acquired team’s momentum and integrates slowly. If the leadership can’t state the thesis in one sentence, the integration will pull in three directions at once.
Build the Day 1 plan. Day 1 is theatre as much as logistics — it’s the first signal every employee, customer and supplier receives about how this is going to go. Decide in advance what changes on Day 1 (usually very little) and what is explicitly staying the same for now. Certainty is the gift you give people on Day 1. Ambiguity is the thing that starts the rumour mill.
The first 100 days, phase by phase
The 100-day integration plan isn’t arbitrary. A hundred days is long enough to make real structural progress and short enough to hold urgency. I run it in three phases.
Day 1 to Day 30 — Stabilise and signal
The first month is not about transformation. It’s about stability and trust.
The goal is simple: nothing breaks, everyone gets paid, customers keep getting served, and every person in both organisations hears — clearly and early — what’s happening and what it means for them. You’re not restructuring in month one. You’re proving the combined organisation can operate, and you’re buying the goodwill you’ll spend later.
Practically, this phase locks down the essentials: payroll continuity, access to systems, a single source of truth for customer and financial data, and a communication cadence that people can rely on. Set up the programme governance in week one and run it from day one — the workstream leads, the weekly rhythm, the escalation path.
Resist the urge to make big changes now. The organisation is watching to see whether you’re a safe pair of hands. Earn that first.
Day 30 to Day 60 — Integrate the core
With the organisation stable, the middle phase is where real consolidation starts — carefully.
This is where the systems and process work gets going: consolidating the financial close, unifying the core toolset, aligning policies, and starting the harder people work of org design where the deal thesis calls for it. It’s also where the dependency management earns its keep, because this is the phase with the most cross-workstream collisions.
The discipline here is sequencing over speed. Data migration errors compound — a rushed general-ledger consolidation or a botched customer-data merge creates cleanup work that outlasts the whole programme. Move deliberately, validate as you go, and let each consolidation prove itself stable before you stack the next one on top.
Day 60 to Day 100 — Realise and hand off
The final phase is about locking in the value and making the change durable.
By now the structural work should be landing: the synergies the deal was built on start to show up as actual numbers, the new operating model is running rather than being designed, and the workstreams begin winding down into business as usual. The integration lead’s job in this phase shifts from driving to handing off — transferring ownership of each integrated function to the permanent leadership that will run it.
The 100-day mark is a milestone, not a finish line. Some work — deep systems consolidation, full cultural integration — runs well beyond it. But by day 100 you should be able to say, honestly, whether the integration is delivering, and hand a clear picture to the people who’ll carry it forward.
Governance and workstream leads: who owns what
An integration lives or dies on its governance, and governance is mostly about answering one question quickly: when two parts of the business disagree, who decides, and how fast?
The model I use is deliberately lightweight.
One integration lead, accountable for the whole programme, with the authority to make cross-workstream calls and the access to escalate the ones above their pay grade without delay.
A lead per workstream — finance, technology, people, customer, brand, legal, operations — each owning their slice end to end and, crucially, owning the dependencies they hand to and take from other streams. The seams are somebody’s explicit job, not an orphan.
A steering group that meets often early (weekly in the first month) and exists to unblock, not to admire progress. Its entire purpose is to clear the decisions that are stuck between workstreams before they cost a week.
One communication cadence, run centrally. Internal first, then customers, then market — in that order, every time. The fastest way to lose the people you just acquired is to let them learn about their own future from a customer or a press release.
If you get the governance right, the rest of the post-merger integration programme becomes manageable. Get it wrong and no amount of planning detail will save you.
Measuring integration success
Most integrations measure activity — tasks closed, systems migrated, milestones hit. Activity is easy to count and tells you almost nothing about whether the deal is working.
Measure against the thesis instead. A small set of indicators, tied directly to why the deal happened:
- Value capture — are the synergies (cost or revenue) the deal was underwritten on actually materialising, on the timeline that was promised?
- Retention — are you keeping the people and the customers that carry the value? Regretted attrition in the first hundred days is the clearest early warning that an integration is in trouble.
- Operational continuity — is the combined business serving customers at least as well as the two separate businesses did? Any dip here is value leaking out the side.
- Momentum — are workstreams hitting their phase transitions, or is the programme slipping? Slippage in the first month predicts slippage in the third.
Four measures, reviewed every week, tied to the thesis. That’s enough to know whether the plan is working — and to fix it while there’s still time to fix it.
The point of a plan
A post-merger integration plan doesn’t make the work easy. It makes the work sequenced, owned, and visible — which is the difference between an integration that compounds value and one that quietly erodes it.
The deal team hands you two companies and a thesis. The plan is how you turn that into one company that actually delivers on it. The first 100 days are where that’s decided.
Ready to plan your integration?
If you’re heading into a merger or acquisition — or you’re already in one and it’s starting to drift — this is exactly the work I do. Need an experienced PMI lead to own the plan and drive the first 100 days? Talk to Aaron →
Aaron Darke is a Senior Project & Programme Manager with 25+ years’ experience running complex programmes across post-merger integration, brand consolidation, and digital transformation — including corporate rebrand and consolidation work for LexisNexis and multi-brand portfolio programmes for Century Yuasa. He works on contract across the USA, Mexico, Australia and New Zealand. Available for post-merger integration engagements.
Preguntas frecuentes
What is a post-merger integration plan?
It's the framework that governs how two organisations combine after a deal closes — the workstreams, the sequence they run in, the governance that makes decisions, and the measures that track whether the integration is delivering the value the deal was built on. It sits above the task-level checklist and directs it.
Why 100 days?
A hundred days is long enough to make real structural progress and short enough to hold urgency. Integration energy is highest immediately after close and decays quickly, so the framework concentrates the highest-value work into the window where the organisation is still ready to change.
How is the plan different from a post-merger integration checklist?
The checklist is the task list — the specific, tickable actions in each area. The plan is the framework around it: what happens in which phase, who owns each workstream, how decisions get made, and how success is measured. You use both together, but the plan is what stops the checklist becoming a thousand disconnected to-dos.
Who should own the integration plan?
A single, named integration lead with the authority to make cross-functional decisions — appointed before the deal closes, not after. Committees and part-time owners are the most common reason integrations stall in the first month.
When should we start planning the integration?
Before close. You usually can't execute much pre-close for legal and confidentiality reasons, but the highest-leverage decisions — naming the integration lead, agreeing the deal thesis, and building the Day 1 plan — all happen in the pre-close window. Integrations that start planning after close spend their first weeks working out who's in charge.