What Belongs in a 100-Day Integration Plan
A 100-day integration plan is the operating document that turns a deal thesis into assigned work. It holds four things: a synergy register, a decision-rights matrix, a retention list, and a governance cadence. Every line carries a named owner, a date, and a measure.
Most plans fail an easier test than that. They list activities instead of commitments. “Integrate finance systems” is a heading. “The platform controller closes the first consolidated month by March 31” is a commitment. Only one of those can be missed visibly.
This article covers what belongs in the plan and how to sequence it. It also covers what to leave out, who owns it, and how to read it at week six.
What is a 100-day integration plan?
A 100-day integration plan converts the value in the deal model into owned, dated commitments. It covers the first three months after close. It is narrower than an integration strategy and wider than a project tracker.
It is also not a Day 1 checklist. Day 1 is a continuity test: people get paid, customers get served, the entity can produce a financial statement. The 100-day plan starts once continuity is proven and asks a different question. What do we change first, and who owns changing it?
The 100-day boundary is a forcing device, not a deadline. Very little finishes inside 100 days. The window forces the platform to decide what matters first. It does that while the acquired business is still paying attention, before old habits reassert themselves.
A useful plan is short. If it runs past a few pages, it has become a status report.
Why do the first 100 days decide the outcome?
Because the market gives a deal credit at announcement and takes it back afterward. KPMG analyzed more than 3,000 public-to-public deals over $100 million between 2012 and 2022. It found that 57.2% of acquirers destroyed shareholder value. Total shareholder return dropped an average of 7.4% in the two years following.
Two years is the measurement window. The first 100 days is where the trajectory inside that window is set.
What separates the acquirers who keep the value is capability rather than strategy. McKinsey’s Global M&A Capabilities Survey drew 1,841 responses. In it, 76% of high performers said they staff integration with people who have the right skills. At low performers, 46% said the same.
The plan is rarely the problem. Who is free to run it usually is. On a roll-up this compounds. Each add-on lands on a platform whose capacity was already spoken for by the last one.
What are the four components of a 100-day integration plan?
Four documents do the work. Everything else is commentary on them.
The synergy register
The synergy register is the line-by-line translation of the deal model into initiatives. Each line carries an owner, a baseline, a KPI, and a date.
The baseline matters more than people expect. Without one, a synergy cannot be shown to have landed. Disputes about whether it landed then consume more management time than the synergy was worth.
Sequence cost synergies ahead of revenue synergies. Cost lines are usually inside the platform’s control and land within the window. Revenue lines depend on customers, and customers do not move to your timetable.
One test separates a real register from a decorative one. If a missed line changes what happens the following week, the register is live. If it does not, you have a spreadsheet.
The decision-rights matrix
The decision-rights matrix says who decides what, at the acquired business, from Day 1. It needs to cover four areas at minimum: pricing, hiring, capital expenditure, and systems.
Most early integration friction is not disagreement about the answer. It is ambiguity about who gets to give it. A sales leader does not know whether a discount needs their sign-off or the platform’s. The deal stalls, and the customer notices.
Write the matrix before close. It costs an afternoon and prevents a quarter of small escalations.
The retention list
The retention list names the specific people who carry economic value, not a headcount band or a department.
Value usually sits with fewer people than the organization chart suggests. The engineer who is the only one who understands the pricing logic. The operations manager the largest customer calls directly. These names belong on a list with a retention action and an owner against each.
A list of roles is not a retention list. Roles do not resign.
The governance cadence
The governance cadence is the meeting rhythm that keeps the other three documents alive. Weekly at workstream level, biweekly at steering level, monthly with the sponsor is a common shape.
The cadence has one job. It makes the plan’s status visible often enough that a slip is caught while still cheap. It should also be a cadence the platform can keep running after any outside help leaves. If it depends on someone who is billing hourly, it is not governance.
How should a 100-day integration plan be sequenced?
Sequence by dependency, not by function.
The instinct is to organize the plan by workstream, because that is how the team is organized. It produces a plan where five functions each run their own track and collide in week seven. Finance cannot close a consolidated month until IT has mapped the chart of accounts. HR cannot communicate the new structure until the decision-rights matrix exists.
Build the dependency map first, then assign dates backward from the things that block the most. The workstream view can be a filter on that plan. It should not be its structure.
For a fuller picture of how the pre-close and post-close phases fit together, see our approach to post-merger integration services.
What does not belong in a 100-day plan?
Three things, and they account for most bloated plans.
Anything with no owner. A line without a name is a wish. Delete it or assign it.
System migrations that are not continuity-critical. ERP consolidation is real work with a real payback. It is almost never first-100-days work. Attempting it in the window usually costs the early synergies that were achievable.
Culture initiatives without a decision behind them. Culture work matters, and it fails when it arrives as workshops rather than as resolved operating questions. Where culture and operating-model differences are the real obstacle, the fix is deciding whose process wins. Not running a values session.
Who owns the 100-day integration plan?
One person, named, whose other responsibilities have been reduced to make room.
The common failure is appointing the CFO or the platform COO and changing nothing else about their workload. Both jobs then get done at roughly 60%, and neither shortfall is visible until a quarter closes badly.
Where the integration crosses more than two functions, that owner usually needs an Integration Management Office behind them. The IMO arbitrates between workstreams and escalates what is stuck. Below that threshold, a named owner and a weekly cadence is often enough.
How do you know by week six whether the plan is working?
Four signals, all visible well before day 100.
- The synergy register has movement. Lines have moved from planned to in progress with dates that have not silently slipped.
- Escalations are arriving. Silence in week six is not calm. It means issues are being absorbed locally instead of surfaced.
- Nobody on the retention list has resigned. Departures in the first six weeks are the most expensive kind, because they take undocumented knowledge with them.
- The steering meeting is shorter than it was in week two. A shortening meeting means decisions are being made at the right level.
If three of the four are missing at week six, the plan does not need more detail. It needs a different owner or less scope.
What changes for an add-on versus a platform acquisition?
The components stay the same. The weighting changes.
For an add-on into an established platform, the decision-rights matrix does most of the work. The operating model already exists. The only question is which parts the acquired business adopts, and the synergy register is usually shorter and more certain.
For a platform acquisition, or a merger where neither side is obviously the model, the sequencing question is harder. There is no default operating model to fall back on. The plan has to carry an explicit decision about which company’s processes survive. That decision belongs in week one, not week ten.
Platforms that absorb acquisitions well keep all four documents standing between deals. The capability compounds. Rebuilding it per deal does not.
If you are staring at a close date and no plan, start with two things. Name the owner, then write the decision-rights matrix. Those two decisions unblock most of the rest.
