The 100-day plan is the first promise you make after close. It is in the IC memo. It is in the board deck. It sets the tone for the whole hold.
And then it slips.
The deliverables that were supposed to land by day 30 land by day 60. The reporting package that was supposed to be live by day 45 is still being argued about at day 90. The pricing analysis the deal thesis depends on cannot start because nobody can produce clean revenue by segment. By day 100 you are presenting progress on the plan to build the plan.
The reflex is to blame execution. The team is too slow. The CEO is not pushing hard enough. The operating partner is stretched across too many deals. So you add pressure, add people, or quietly extend the timeline.
In my experience, that diagnosis is almost always wrong. The plan did not slip because the team was slow. It slipped because the data the team needed to act did not exist on day one.
You cannot prioritize what you cannot measure
A 100-day plan is a sequence of decisions. Which customer segment to defend. Which product line to push. Which cost to cut. Which contract to renegotiate. Every one of those decisions needs a number behind it before anyone will commit to it.
Here is what happens in practice. The plan says “improve gross margin in the underperforming segment.” Good instruction. Then someone asks which segment is underperforming, and by how much, and why. And the answer takes three weeks to assemble because margin by segment lives in four systems and two spreadsheets, and finance and operations do not agree on how to define a segment in the first place.
So the first month of the plan is not spent executing the plan. It is spent building the picture the plan assumed already existed.
This is the pattern I see most often, and it is consistent. Most 100-day plans slip, and the reason is rarely a people problem. The company spends the early weeks assembling a view of itself that the deal team thought it had bought.
You evaluated this data during diligence. You did not operate it. Those are different things. Diligence answers “is this business roughly what they claim.” Operating the plan asks “which specific lever do I pull this week, and how will I know it moved.” The second question needs a level of data resolution that diligence never required.
The plan assumes a baseline that does not exist
Every 100-day plan is written as if the portfolio company can see itself clearly. Revenue decomposed by the dimensions that matter. Costs at the unit level. Customer behavior by cohort. One agreed number per metric that finance, sales, and operations all stand behind.
Most mid-market companies cannot do this on day one. Not because they are badly run, but because they were run for a different purpose. The previous owner needed numbers good enough to manage the business and tell a clean story at sale. You need numbers good enough to run a value creation plan against a five-year clock. Higher bar, different shape.
The gap between those two shows up the moment you try to act. The plan calls for a decision. The decision needs a number. The number does not exist, or three versions of it exist, and now you are reconciling instead of deciding.
This is why I argue the fix is not a faster team or a longer plan. A faster team still cannot prioritize what it cannot measure. A longer plan just spreads the same problem over more weeks. The fix is to establish the baseline before the plan starts running against it.
The fix is a Day-0 data baseline
A Day-0 baseline is the set of numbers the 100-day plan will be steered by, established and agreed during close or in the first week after, not assembled reactively as each initiative stalls.
The point is sequence. You do the measurement work once, up front, so the plan runs on evidence from day one instead of pausing every two weeks to manufacture the evidence it needs. The work itself is not large. What makes it valuable is doing it before the clock starts, not during it.
I covered the broader sequence of the first 100 days in the post-acquisition data playbook. The Day-0 baseline is the piece that has to come first, because every other workstream in that playbook depends on it.
What a Day-0 baseline contains
This is not a data warehouse and it is not a transformation program. It is a focused artifact you can build in the first week or two. Here is what goes in it.
The metric shortlist. The five to seven numbers the value creation plan actually depends on. Not the forty on a dashboard. The handful that, if they move, mean the thesis is working. For most companies that is revenue by segment, gross margin by product or service line, customer retention or net revenue retention, sales pipeline conversion, and one or two operational drivers specific to the business. If the deal thesis rests on a metric, it is on this list.
One definition per metric, signed. For each number, a single definition that finance, sales, and operations all agree to. What counts as a segment. What counts as churn. How margin is allocated. The goal here is to kill the second and third versions of the truth before they generate a single argument in a board meeting. Most of the value in a baseline comes from this step, not from any new tooling.
The current value and how it was produced. For each metric, the actual number today, the source it came from, and the path it traveled to get there. This is your starting line. Without it you cannot tell at day 60 whether anything moved, because you never recorded where you began.
The data supply chain behind the shortlist. A short map of where each number originates, which systems it passes through, and where it lands in the reporting. You are not mapping every system in the company. You are mapping only the path behind the seven numbers that matter, so when one of them looks wrong you know where to look.
The key person dependencies. For each metric, who can actually produce it. Often it is one person and one spreadsheet. Those are your single points of failure, and you want them named on day one rather than discovered on day 40 when that person is on holiday and the board pack is due.
The known gaps, stated plainly. Where the data does not exist yet, or cannot be trusted, say so up front. A metric you cannot yet measure is a constraint on the plan, and the plan should be written knowing that, not ambushed by it in week six.
That is the whole artifact. A shortlist, agreed definitions, current values, the supply chain behind them, the people who own them, and an honest list of gaps. It is the picture the 100-day plan assumed it already had.
Why this has to happen at close, not after
Three reasons the timing is the entire point.
Attention is highest right after close. The management team expects change and questions in the first weeks. Ask for agreed metric definitions in week one and you get them. Ask in month three and you are interrupting routines that have already hardened.
The diligence context is still fresh. The data issues you found in diligence are still in living memory right after close. Wait a few months and those findings are in a binder nobody opens. The baseline captures that knowledge while people still remember it.
Every downstream workstream waits on it. Add-on integration, management reporting, the customer analytics behind the thesis, all of it assumes the baseline exists. Build the baseline first and the rest of the plan accelerates. This is the same compounding logic behind fixing data integration after an add-on acquisition early rather than late, and behind the case for fixing data before diligence rather than under deadline. Done early, the work guides the plan. Done late, it is a fire drill.
If you want a quick read on whether a portfolio company can support the analytical side of the plan at all, the AI Readiness assessment is a useful starting point before you commit to targets that depend on data the company cannot yet produce.
The 100-day plan you can actually keep
A 100-day plan that slips is rarely a sign of a weak team. It is a sign that the plan was written for a company that could see itself clearly, handed to a company that could not.
The version that holds starts a week earlier than the one that slips. Before the first initiative kicks off, you build the baseline. Seven numbers, agreed definitions, current values, the path behind them, the people who own them, the gaps named out loud.
Then the plan runs on evidence from day one. Every initiative connects to a number with a baseline and a target. The day-60 review becomes a read instead of an argument. And the progress report at day 100 is about the business, not about the plan to build the plan.
You closed the deal to create value, not to spend the first 100 days discovering what you bought. Build the baseline at close and you get the 100 days back.