Most hundred-day technology plans are written by people who will not have to execute them, which is why they contain ten priorities. A hundred days supports three.
The window is short for reasons that have nothing to do with ambition. New management is settling, the organisation is anxious, the data is worse than anyone expected, and the first four weeks disappear into access requests and getting a picture of reality. Plan for the seventy days you actually have.
What belongs in the first hundred days
One: close the blocking findings from diligence. Not all of the findings. The subset where doing nothing costs money immediately or prevents the year-one plan from starting. If the diligence was done properly this list already exists and has numbers against it; if it was not, the first three weeks are spent recreating it, which is an argument for the same person doing both.
Two: establish the facts the board will be governed by. By day hundred there should be an agreed number for what technology costs, an agreed view of what the team can deliver in a quarter, and a delivery date that has been set once and not moved. This sounds administrative. It is the single highest-leverage thing in the window, because every subsequent conversation between the fund and the company depends on whether those numbers are trusted.
Three: start the structural change with the longest lead time. If an ERP replacement, a cloud migration or a platform consolidation is happening at all during the hold, it starts now, because the clock is the binding constraint and month eighteen is where these become impossible to finish before exit.
That is the plan. Three things.
What does not belong
A full technology strategy. It will be written from incomplete information and rewritten in month six, and producing it consumes the leadership attention the three items above need.
A reorganisation, unless the diligence identified the leadership as a blocking problem. Reorganising in month two, before anyone has demonstrated anything, removes the information you need to reorganise well in month eight.
A tooling refresh. Changing the ticketing system, the cloud provider or the development pipeline in the first hundred days produces visible activity and no enterprise value, and it is a reliable sign that nobody has decided what actually matters.
New AI initiatives, in almost every case. There are exceptions where an obvious, contained application exists and the data is already there. More often, AI in the first hundred days is a way of avoiding the boring finding in the diligence report.
Why these plans fail
They fail in four recognisable ways.
The plan is not costed, so it competes for budget it was never allocated and loses to something that was. Every item needs a number and a funding source before day one, not after the first board meeting.
Ownership sits with the fund rather than the company. An operating partner can sponsor a plan; they cannot execute one. If there is no named person inside the business whose next twelve months are defined by this plan, it will not happen.
The baseline is wrong. The plan assumes a delivery capacity that the team has never demonstrated, usually because the seller’s roadmap was used as evidence of throughput. Measure two sprints before committing to a date.
And the plan is not visible. The board sees a status colour rather than the two or three numbers that indicate whether anything is moving. Choose the numbers on day one — cost run rate, one delivery metric, one outcome metric — and report the same three every month, including the months they look bad.
A workable shape
| Weeks | Focus |
|---|---|
| 1–3 | Access, verify the diligence findings against reality, name the internal owner |
| 4–6 | Agree the cost baseline and the delivery baseline with the CFO and the board |
| 4–12 | Execute the blocking fixes |
| 6–14 | Mobilise the long-lead structural change: business case, vendor, team |
| 12–14 | First board report on the three agreed numbers, and the year-one plan |
The year-one plan is the output of the hundred days, not its input. That inversion is the part most funds get wrong: the window is for establishing what is true and clearing what is blocking, so that the twelve-month plan written at the end of it is worth the paper it is on.
The uncomfortable part
Sometimes the honest output of the first hundred days is that the technology cannot support the investment case at the price paid, and the plan has to change rather than the technology. That finding is far more valuable in month three than in month twenty, and the adviser who will say it out loud is worth more than the one who produces a green dashboard for eighteen months.