In this article
The first 100 days after an acquisition set the conditions for everything that follows. A plan that exists only as a slide deck, or that covers every workstream without prioritising any of them, will not guide a team under pressure. This article explains how to structure a 100-day integration plan that leaders actually use and that captures value rather than just tracking activity.
Why most 100-day plans fail in practice
The most common failure is not a lack of planning. It is a plan that is too broad, too generic, or too focused on process rather than outcomes. Teams spend the first month completing the plan rather than executing it. By day 30, it is already out of date and nobody is treating it as authoritative.
A second common failure is ownership. A plan with 50 workstreams and no clear lead for each one will not be delivered. Integration is inherently cross-functional and politically complex. Without clear ownership, competing priorities fill the vacuum and the plan becomes a background document rather than an active tool.
What the plan should prioritise
Not everything in a 100-day integration is equally important. A useful plan distinguishes between three categories of work.
Day 1 essentials. These are the things that must be in place before the business opens for the first trading day post-completion. Systems access, payroll continuity, customer communications, key supplier notifications, and decision rights clarity cannot wait. If these fail, confidence in the integration collapses immediately.
First 30-day stabilisation actions. These are the activities needed to prevent value erosion in the near term. Retaining key people, securing critical contracts, establishing a reporting baseline, and standing up integration governance all belong here. The goal is to stop things getting worse while the longer-term work is designed.
Days 30 to 100 value capture workstreams. These are the structured workstreams aimed at realising the synergies and strategic rationale that justified the deal. They require proper design, clear ownership, defined milestones, and a governance rhythm that keeps them on track.
The core structure of a workable plan
A 100-day integration plan that gets used typically has six components.
1. Integration objectives
A short statement of what the integration is trying to achieve commercially, not just operationally. These should be the objectives that the deal was premised on, expressed in terms that every workstream lead can refer back to when making decisions.
2. Workstreams with named owners
Every workstream needs a single named owner who is accountable for delivery, not just a team. The workstreams should cover the critical areas: commercial and customer, operations, finance and reporting, technology and data, people and culture, and legal and compliance. Each owner should have a defined scope, a set of milestones, and a clear escalation path.
3. Milestones and decision points
The plan should include explicit milestones at day 30, day 60, and day 100, with a clear statement of what should be true at each point. It should also identify the key decisions that need to be made in the first 100 days, who makes them, and what information is needed to make them well.
4. Dependencies
Integration workstreams are rarely independent. Technology decisions affect operations. People decisions affect commercial continuity. Financial reporting depends on data access. The plan should make the critical dependencies visible so that delays in one area are understood in terms of their knock-on effects.
5. Value capture tracking
If the deal was premised on specific synergies, the plan should include a mechanism for tracking progress against them. This does not need to be elaborate. It needs to be honest. Early visibility of where value capture is on track and where it is at risk allows the integration team to act before the problem compounds.
6. Governance rhythm
The integration needs a weekly operating rhythm. A short integration leadership meeting, a workstream status update process, and a monthly executive or board checkpoint should all be established in the first week. Without a governance rhythm, the plan becomes static and issues accumulate without resolution.
What the first week should achieve
Before the 100-day plan can be executed, the first week has a specific job. The integration leadership team should be named. The workstream owners should be briefed. The Day 1 essentials should be confirmed as complete. The reporting baseline should be established. And the first integration governance meeting should take place.
A first week that achieves these five things puts the integration on a footing from which the 100-day plan can actually be used. A first week that does not will cost far more than one week to recover.
The plans that fail are comprehensive, detailed, and unused. The plans that work are simple enough to hold in the head of every workstream owner.
The difference between a plan that works and one that does not
The plans that work are simple enough to hold in the head of every workstream owner. They have clear ownership, visible milestones, and a governance rhythm that people actually keep. They distinguish between essential stabilisation and longer-term value capture. And they are reviewed and updated, not filed.
The plans that fail are comprehensive, detailed, and unused.
Planning or completing an acquisition?
Our M&A integration advisory covers integration planning, governance design, and workstream delivery support. Fixed scope, senior-led.
