Most 100 day plans are a wish list with a calendar stapled to it. They list forty initiatives, assign them to the same four people, and then those four people also have to run the business. By week three the plan is fiction and everyone knows it, but nobody says so out loud.
A real post-merger integration 100 day plan is a capacity plan. It starts with how much change the acquired business can absorb and how many hours your team actually has, and only then does it decide what happens when. I have run roughly sixteen integrations, and the plans that held up were never the longest ones. They were the ones that said no to most of the list until the business was stable.
Get the 100 day integration tracker (XLS)
The plan below as a spreadsheet you can assign and update every week: tasks, owners, due dates, status, and checkpoint gates. Free.
What this page does, and what it leaves to others
Three tools do three jobs. The full post-merger integration checklist identifies every task. This page puts those tasks in order against your team's capacity. The post-merger integration playbook explains how to make and defend the hard decisions behind them. Use all three, in that spirit: what, when, why.
Before you build the plan: three decisions
You cannot sequence work you have not scoped. Settle these first, ideally before close, because they change every row in the table below.
1. The operating model
Decide, on purpose, whether you will preserve and strengthen the business, selectively integrate parts of it, or substantially consolidate it into yours. A preserve plan is mostly protection and a light reporting layer. A consolidate plan carries real system, branch, and org changes, and it needs a much longer runway than 100 days. One size does not fit all, and the plan that fits a consolidation will smother a business you meant to preserve.
2. The capacity budget
List the people who will carry the work and be honest about what share of their week integration gets. A finance lead who is also closing the month does not have twenty hours free. Count the hours, then count the tasks. If the tasks need more than the hours, cut tasks. Do not hope.
3. The change ceiling
Employees and customers can absorb only so much change at once. Decide in advance what must not change in the first 30 days: pay plans, service levels, pricing, who answers the phone. Owning the business does not mean you understand it yet. The ceiling protects you from your own enthusiasm.
The plan: checkpoint by checkpoint
Each block ends at a checkpoint. A checkpoint is a gate, not a date to celebrate. If the exit test is not met, you do not move on. You fix it first. Owners below are roles; swap in names. Each row has one accountable owner, and anyone in parentheses supports. In a smaller company one person may hold two roles, which is exactly why the capacity budget matters.
| When | What gets done | Owner |
|---|---|---|
| Pre-close (the 2 to 4 weeks before you sign or fund) | ||
| Pre-close | Write the integration thesis and choose the operating model. Name the critical people and the top accounts that must stay. | Integration lead (deal sponsor signs off) |
| Pre-close | Agree with the seller what changes, what does not, their role, and what they have told employees and customers. | Deal sponsor |
| Pre-close | Freeze the opening baseline: headcount, customers, margin, cash, receivables. Confirm change-of-control and assignment terms. | Finance lead |
| Day 1 to Day 30: stabilize | ||
| Day 1 | Payroll, banking, cash access, and signing authority live. Systems access set, with a list of what nobody touches yet. | Finance lead (IT lead sets systems access) |
| Day 1 | First all-hands meeting. Employees hear it first, then customers, then vendors. | Executive sponsor (seller stands alongside) |
| Week 1 | Open the risk and issue log. Personally contact the top accounts. Confirm every critical employee knows their role is secure. | Integration lead (sales lead makes the account calls) |
| Weeks 2 to 3 | Stay conversations with the critical few. Targeted retention in place where it matters. No compensation plan changes. | HR lead (executive sponsor holds the conversations) |
| Weeks 2 to 4 | Listen. Ride along on service calls, sit in the branch, read the customer files. Map how the business really runs, including the handshake deals. | Operations lead |
| Week 4 | First review of actuals against the opening baseline: people, customers, profits, cash. | Finance lead |
| Checkpoint, Day 30. Exit test: no critical resignations, no lost top account, payroll and cash clean, and an issue log with an owner on every line. | ||
| Day 31 to Day 60: align | ||
| Weeks 5 to 6 | Settle org clarity: keep their management layer or fold it into yours. Announce roles, not intentions. | Executive sponsor (HR lead drafts the structure) |
| Weeks 5 to 7 | Start the first easy integrations, in sequence: reporting calendar, benefits enrollment, insurance, and basic financial close alignment. | Finance lead (HR lead runs benefits) |
| Weeks 6 to 8 | Build the synergy ledger. Separate bankable savings and revenue from the aspirational, and give each line one owner. | Finance lead |
| Weeks 6 to 8 | Decide vendor consolidation case by case. Find out why they got their rate before you move them to yours. | Operations lead |
| Week 8 | Second baseline review. Compare the opening customer cohort separately from new sales. | Finance lead (sales lead explains the customer trend) |
| Checkpoint, Day 60. Exit test: operating model confirmed or deliberately revised, org settled, synergy ledger owned, and the baseline trend explained. | ||
| Day 61 to Day 100: set up growth | ||
| Weeks 9 to 10 | Decide cross-sell timing and territory rules. Start with the accounts where trust is highest. | Sales lead |
| Weeks 9 to 11 | Begin the operating improvements the thesis promised, one at a time, sized to capacity. | Operations lead |
| Weeks 11 to 12 | Transfer knowledge held by any single person. Document the processes that live only in someone's head. | Operations lead (HR lead tracks who holds what) |
| Weeks 12 to 13 | Stand up the scorecard and the governance rhythm that warn you before the P&L does. | Integration lead (finance lead builds the numbers) |
| Day 90 to 100 | Write the day 100 review: what held, what dipped, what is next. Set exit criteria for integration, and a growth number with an owner. | Executive sponsor |
| Checkpoint, Day 100. Exit test: people and customers retained against the baseline, the dip understood, the next 100 days written, and every growth target owned by a named person. | ||
Why the order matters
The sequence follows one rule: protect before you improve, then drive growth. Days 1 to 30 are about not breaking anything. Days 31 to 60 are about aligning the structure once you understand it. Only after that do you push cross-sell and operating improvements.
Reverse that order and you pay for it. Push cross-sell in week three and you risk the relationship you just bought. Change the pay plan in week two and your best producers start taking calls from recruiters. Consolidate the vendors in week one and you lose the rate that made the business profitable. One issue is never just one issue, and the plan has to leave room to find the real one.
Capacity checks that keep the plan honest
- Count the tasks due this week against the hours each owner said they had. If the hours do not cover the tasks, move a task, do not stretch a person.
- Check that every task has exactly one owner. Two owners means no owner.
- Ask the acquired team what changed this week from their side. If they cannot name it, you are not communicating enough.
- Review the top accounts and the critical people by name. Any surprise goes straight to the issue log.
- Compare actuals to the opening baseline, not the budget you inherited.
- Stop one thing. Every plan needs something removed as often as something added.
Expect the dip
Performance and morale usually fall before they climb. That is the valley of despair, and it tends to show up around days 30 to 60, right when the first visible changes land. It does not mean the plan is failing. It means people are learning something new while still doing their jobs. Plan for it, tell your sponsors it is coming, and keep the retention and communication work running through it. How you lead people through that stretch is covered in leading the change after an acquisition.
Where to go deeper
Two tasks deserve their own pages because they decide the outcome more than any other. The first is the opening day itself: see the day 1 readiness checklist. The second is keeping the few people who hold the business together: see employee retention after acquisition. Keeping the key employees is what lets you keep the key customers.
Run the plan with your team
The tracker puts every task, owner, and checkpoint gate in one editable file, so the weekly review takes minutes, not an hour.
Questions
What is a post-merger integration 100 day plan?
It is a dated, owned sequence of work for the first 100 days after an acquisition closes. It covers stabilizing the business, aligning people and structure, and setting up growth, with checkpoints at day 1, 30, 60 and 100 so you know whether to move forward or fix something first.
Why 100 days?
It is long enough to stabilize the business and short enough to keep urgency. It is a planning window, not a deadline for finishing. Value creation usually runs well past day 100, and a consolidation takes longer than a preserve and strengthen approach.
Who should own the 100 day plan?
One named integration lead, backed by an executive sponsor with authority to settle disputes. Each task then has one owner of its own. Shared ownership is how tasks quietly disappear, and a plan owned by a committee is owned by nobody.
What if we fall behind the plan?
Cut scope before you stretch people. Move lower priority tasks past the next checkpoint, keep the people, customer, and cash work on schedule, and tell the team what moved and why. A smaller plan that is delivered beats a complete plan that is ignored.