Two good things already exist at every capital table.
Action plans get written, and often well — the 100-day plan, the value-creation roadmap, the post-investment programme. And capital gets gated: milestones sit in half the term sheets in this sector. Both halves of a disciplined deployment are already on the table.
Now look at what connects them. Nothing — and not because anyone is failing at their job. The plan and the tranches were built by different parties for different purposes, and coupling them was never anyone's mandate.
So the plan stays advisory, and the tranches gate on negotiated numbers — revenue thresholds, bookings — that come from no diagnosis of what is actually broken. A company can clear its revenue milestone dead-on while the design flaw underneath compounds, and the tranche releases into the same unread break.
Gated capital, ungated causes.
What is missing is a structure, not a service: a deployment programme in which the diagnosed blockers are the release conditions. Each becomes a gate, with its closing condition named in advance and verifiable by anyone. Money moves when evidence clears a gate, not when a narrative survives a board meeting.
Four requirements make that work, and each closes a specific failure mode.
The blockers are named and filed. A finite list, not a risk register — each tension with an address that determines when it must clear. Design blockers clear before operational ones; operational before scale preparation. The filing is the schedule.
The gates are typed and ordered. External conditions stand watch — capital staged behind evidence that the gate has opened, not behind hope that it will. Design fixes come before operational fixes, and operations before scale preparation, because scale preparation on top of an unfixed design is preparation for scaling the flaw.
Evidence closes gates, people don't. Every gate's closing condition is defined before work starts and can be checked by any party: hours per install measured at six, not a taskforce reporting progress. The tension is resolved when it no longer measures. And the gate defines what must be true — never how. Nothing cascades; no imposed methodology, no OKR programme. I say that from experience, not theory: cascade objectives down through an organisation and a company that needed to fix five things ends up administering five hundred. Full freedom of method stays with the executives who own the work.
The re-read decides. On a quarterly clock, the same instrument runs again — same questions, same standard. The gates answer with evidence, not narrative. A gate clears, the position lifts, a tranche releases. And when gates don't clear — same tensions, same places, quarters of runway spent — that too is an answer, early enough to act on. The verdict was a position on a path, not a stamp.
Pass can be terminal. Some blockers sit outside everyone's reach — a category price floor, a regulatory gate, a competitive window that closed — and the honest end of that read is an orderly exit, taken early enough to preserve value.
But Pass does not have to be terminal, and the difference is knowable. Pass means the company as constituted cannot clear its blockers. It says nothing yet about whether the holder can.
Some blockers sit outside the executive team's control entirely and squarely inside the investor's. The leadership seat that fails under load: the team cannot replace its own chief executive; the board can. The pivot the executives can see but cannot sanction, because it reads as proposing the end of what the company is: the shareholders can propose it. The market that closed and the switch that has to be authorised: the capital behind the company can authorise it.
Company-controllable. Investor-controllable. Controllable by no one. That three-way distinction separates a Pass worth working from a Pass worth taking — and it is the reason a Pass report is worth reading to the end. A Pass whose blockers the holder controls isn't a lost position; it's a turnaround with a named lever.
The difference between funding a conviction and funding a programme is not enthusiasm. It is whether the money is attached to the diagnosis.
For a fund mid-raise, a gated programme converts a stalled position from a story that has to be managed into a documented turnaround with named conditions and a clock. For a family office or an industrial holder, the same structure turns patience into an asset rather than an exposure: duration finances a repair instead of underwriting a drift.
Fix first. Then protect the next check.
The full essay on Under Load goes further: all four requirements in full, the three investor-controllable blockers, the OKR-cascade warning from operator experience, and what the gate plan does for a fund mid-raise and for a family office's patience.