The least important part of a 100-day plan is the list of a thousand tasks. It is also the only part most people collect.
Templates get passed around with a note attached: make sure you take our logo off. Then they get filled in like a color-by-number.
The tasks are real. Somebody does have to migrate the email domain. But that list is the part of the plan requiring the least judgment, and it reliably gets the most attention.
The parts that matter are which processes the work touches, who owns each one, and whether that ownership survives the plan. Almost nobody gets those right.
What should be in a 100-day plan?
Open yours and look at how the workstreams are named. If they read Finance, HR, IT, Commercial, you have an org chart with dates attached.
That is the first thing that goes wrong, and it goes wrong for an understandable reason: the org chart is the map everyone already has. But functions are groups of people. Processes are how work actually moves through the company, and they run straight across the functions, which is exactly why they break at the seams where one department stops and the next begins.
Six processes run every software company. Lead to Cash, Procure to Pay, Application Lifecycle, Employee Lifecycle, Customer Lifecycle, Corporate Governance.
Organize the plan around those and the map changes. The handoffs become visible. So do the places where two people each assumed the other one had it.
Under each process, three lines. Who owns it. What it looks like when it runs clean. What has to be true by day 100.
That is the plan. It fits on two pages. If yours runs forty slides, most of what you are carrying is evidence that work is happening, which is not the same thing as work happening.
Fun fact. Ask anyone who has watched me work how many written plans they have seen me produce. If their answer isn’t zero, they haven’t seen me work. Then ask whether anyone could have moved faster, with better outcomes.
When does the 100 days start, at close or at LOI?
At LOI if you’re serious. At close if you’re like everyone else.
The gap between those is roughly sixty days of knowing things.
Set your expectations, though. The questions in diligence are heavily managed. You are being shown a version. That is not a reason to skip the window, it is the reason to use it: what gets managed, and how carefully, tells you where the soft ground is. You are not there for candor. You are there to learn the shape of what somebody decided to show you, which is its own kind of answer.
Teams that start at close spend their first three weeks discovering things that were sitting in a data room in March. Congrats, you made it to day 21 without starting your plan.
Who owns the 100-day plan?
The useful version of that question is: who gets fired if it does not work.
If the answer is a steering committee, nobody does. Steercos review. Reviewing is not owning. A group that convenes every other Thursday to receive an update is a governance mechanism, and governance photographs well without accomplishing much.
Steerco is also code for decision by committee. If you need one to get a decision made, the problem is that you might not know how to make a decision on a regular day, and the acquisition just put a spotlight on it.
This is the second thing nobody gets right, and it costs more than the first. The plan needs an owner who still has a job here after the plan ends. That is the entire test. Not a temporary structure. Not an integration office assembled for the occasion and dissolved at the finish line. Not a firm whose engagement letter expires two weeks after go-live.
There are two different jobs hiding inside the word owner, and plans almost never separate them.
Somebody owns a workstream. That is a slice of the plan, and it ends when the plan does. Somebody else owns a process. That is how the business runs, and it has no end date. When those are the same person, the plan hands off to itself and you never feel the seam. When they are not the same person, day 101 has a gap in it that nobody put on a schedule.
What should you fix first after the deal closes?
All six. In parallel, each one with a different person driving it.
That only sounds reckless if the processes do not have owners, which is the condition most plans are quietly built around. Sequencing is what you do when one team has to carry six things and can only carry two. It is a capacity workaround wearing strategy’s clothes.
Give each process a real owner and the constraint goes away. Six streams move at the same time because six different people are moving them, and nobody is waiting on the CEO to decide which one gets attention this month. The overlap stops being a scheduling problem and becomes the useful part: Lead to Cash and Customer Lifecycle share a handoff, so those two owners work it together instead of queueing behind each other for a slot.
Phasing is not discipline. It is a shortage of ownership, and calling it focus makes it sound like a choice.
How do you know if the 100-day plan is working?
Not from the tracker. The tracker will be green.
Find whoever owns the combined Customer Lifecycle. Ask them what happens when a customer in the newly acquired company goes quiet for thirty days. Time the answer.
Fast and specific means that process has an owner. “That would be a conversation between CS and the account team” means it has a committee, and committees do not own outcomes either. A pause, followed by a question about which side of the house the customer sits on, means you do not have one Customer Lifecycle. You have two, and a meeting.
Do it for all six. It takes an afternoon and tells you more than the status deck does, because it measures the thing the deck is standing in for.
What happens after the 100-day plan ends?
The steerco stops meeting. The tracker sits frozen at 100 percent green forever. Someone sends a note thanking everyone for a tremendous effort.
Then, in a lot of companies, the work quietly stops being anybody’s.
This is the third thing, and it is the one almost nobody survives, because it does not look like failure. Nothing was missed. It executed exactly as designed. The design just ended, and ownership was never written down anywhere except next to workstreams that no longer exist.
The danger comes in two shapes. The first is that whoever ran the workstream was never the process owner, so the work gets handed at the finish line to someone who was not in the room while it was being built. The second is worse, and more common. There was no process owner to begin with. The workstream owner was standing in a vacuum nobody had noticed, doing the job by default, and when the plan ends the vacuum comes back exactly as it was.
Either way you are not on day 101. You are back at day zero, holding a binder, except now everyone believes it was handled.
The good version is boring. On day 101 nothing much happens, because the processes have owners who had them on day 1 and will have them on day 200, and the plan was never the thing holding it together.
The question worth asking before you close it out
Go through the six processes. Name the person who owns each one on day 101.
Not who ran the workstream. Who owns it after.
If you have to check, or if the name changes the moment an engagement ends, the plan was never going to survive its own completion. That is an unpleasant thing to learn on day 101 and a cheap one to learn on day 40.