Eight months after a growth round closed, a CTO walked the board through the remediation plan written into the deal. One slide read: checkout performance, improved. A board member asked what sounded like a friendly question. Improved from what to what? .... Guess what. Nobody had captured the starting numbers in week one. The work had almost certainly helped. There was just no way to prove it.

It got worse. The remediation work had been captured as a flat list of eleven fixes (no owners, no sequence, no baselines) and treated by the team as the investor's homework rather than their own roadmap. Every senior engineer was pulled off feature work for a quarter to grind through it, and the product roadmap the investor had actually paid for slipped two releases. The diligence itself had been excellent: sharp report, right findings, fair price. But the report had become a punch list, not a plan.

Why this matters

The diligence report is not the finish line. More like the opening balance. The findings that surfaced before close (the debt ledger, the security gaps, the migration nobody scoped, the one engineer who owns the data plane) do not automatically vanish post-close. They get written into the deal as a holdback, a remediation condition, or a 100-day plan, which way too often gathers dust.

A real 100-day plan does two jobs at once: it reduces the risks that were priced in, and it starts building the value the investor paid for. Get it right and trust compounds, the first board meeting is calm, and the harder work later gets funded without a fight. Ignore it and the same risks resurface sooner than later, costing longer roadmap time, eroding investors' trust.

What separates a plan from a checklist

It ties to the value thesis, not just the risk list. Investors did not buy a backlog of bugs. They bought a thesis: this platform supports the next phase of growth, wins regulated enterprise deals, or improves margin at scale. Every workstream should connect to one of those levers. A plan that is all remediation and no value creation tells the board the team is playing defense with their money.

It has named owners, not teams. "Engineering will improve observability" is not an owner. "Maya owns the SLO rollout for the three revenue-critical journeys" is. Diffuse ownership is how a plan quietly dies.

It establishes baselines before it promises improvement. You cannot prove you cut checkout latency if nobody wrote down where it started. The first job of the plan is often measurement: capture the starting numbers for the metrics that matter (Edition 3) so value creation is provable. This is the step teams skip most, and the one investors notice first.

It sequences: stabilize, then prove, then build. A team that kicks off a database migration before the system is stable and instrumented is optimizing on quicksand. Stop the bleeding, stand up the baselines, then take on the structural work.

Stage and stake: how the lens sharpens

Stake sets the depth here too (see Edition 2).

Minority growth: the investor does not hold the steering wheel, so the plan is a shared agenda, not a mandate. The output is a short, jointly owned list of priorities and a review cadence.

Majority and control buy-outs: here the investors own the outcome and the plan is binding. Expect an operating partner driving it, board-level tracking, and remediation tied to the deal model. The findings priced in at close become funded workstreams, with budgets and dates.

Carve-outs: here the 100-day plan is typically a standup plan: Day-1 readiness, exit from the Transition Service Agreement, identity and data separation, interim runbooks. Value creation waits until the carved-out entity can stand on its own.

Patterns and practices worth adopting

Convert the diligence report into a ranked backlog. Give every material finding an owner, a cost estimate, a value or risk tag, and a position in the sequence. The Debt Ledger from Edition 4 is the right shape; it turns a static report into a living plan.

Bank a few quick wins early. A visible improvement in the first weeks (a noisy alert silenced, a slow query fixed) buys credibility for the harder, slower asks. Quick wins are not the point, but they fund the trust you will need later.

Run the plan on a cadence, in the open. A short weekly working review and a monthly board summary keep it honest.

Tie each workstream to a metric you will report later: margin, deployment frequency, MTTR, whatever the thesis rests on. If a workstream has no metric, ask why it is in the plan.

Red flags in the first 100 days

  • The diligence report never becomes a plan. It closes with the deal and is never opened again.
  • The plan is a flat list of dozens of items with no sequence, no owners, and no link to the value thesis.
  • No baselines captured, so every later claim of improvement is an argument instead of a number.
  • The plan is the investor's plan, handed down and quietly resented, with no real management buy-in.

Two or more of these and the first board meeting gets tense. Several of these and the plan reappears at the next round, at a higher price.

Mini-Glossary

  • 100-day plan: A focused post-close roadmap that turns diligence findings and the value thesis into sequenced, owned workstreams. This is the opening chapter of an investor's wider value-creation plan.
  • Operating partner: A specialist, often on the investor's side, who helps a portfolio company execute the plan rather than just advise on it.
  • Baseline: The starting measurement of a metric, captured early so later improvement can be proven.
  • Deal model: The financial model that justified the price, projecting growth, margins, and return over the hold period. Remediation costs surfaced in diligence get written into it, so slipping plan becomes slipping returns.
  • TSA (Transition Service Agreement): In a carve-out, the temporary arrangement under which the seller keeps providing services until the new entity can operate alone.

Your turn

What happened to the last 100-day plan you lived through? Did the diligence report become a real roadmap, or did it close with the deal and gathered dust? Share the scar. It helps the next team.

Next in the Playbook

Edition 28 turns to Exit-Readiness and Integration Playbooks: how the diligence discipline runs when you are being bought. Stay tuned!

Originally published on the Tech Due Diligence Playbook newsletter on LinkedIn.