Turnaround plan
The sequence for a business in trouble: stabilise cash, then cost, then revenue, with stakeholder confidence run alongside because the bank and the board move faster than the plan.
The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.
What it is
A staged response to a business in distress, run in a strict order because doing them together burns the time distress does not allow. Cash first, because insolvency is the actual clock. Cost second, because it is inside management's control and moves fastest. Revenue third, because it is slowest and least certain, and betting on it before cash is stable is how turnarounds fail.
- Cash stabilisation
- The thirteen-week cash flow, covenant headroom, and the specific actions — payment terms, discretionary spend, asset sales — that extend the runway. This is the only workstream with a genuine deadline.
- Cost reduction
- Structural cost out, sequenced from fastest and least damaging to slowest and most disruptive. The bank and the board want to see this moving before revenue plans are even discussed.
- Revenue recovery
- Only credible once cost and cash are stabilising. A revenue plan presented as the whole answer, before the cost line has moved, reads as denial rather than a plan.
- Stakeholder confidence
- The bank, the board, key customers and the workforce move on a different clock from the plan itself, and faster. Someone owns this communication explicitly, separate from whoever is running delivery.
- The weekly cadence
- Distress is managed weekly, not monthly. A monthly board pack is the wrong instrument for a business whose cash position can move materially in a fortnight.
How you run it
- Build the thirteen-week cash flow firstWeekly, not monthly. This is the instrument that tells you how much time the rest of the plan actually has.
- Name every action that extends the runwayPayment terms, discretionary spend, asset sales, standstill discussions. Date each one and assign an owner.
- Sequence cost reduction from fastest to most disruptiveStructural cost the business controls directly, moved first. This is the credibility the rest of the plan is built on.
- Hold the revenue plan until cost is movingA revenue recovery story presented before cost credibility is established reads as denial. Sequence it deliberately behind cost, not in parallel.
- Put stakeholder confidence on its own weekly rhythmBank, board, key customers and the workforce, each briefed on a cadence that matches how fast their confidence can move, not how fast the plan updates.
The prompt
Run this tool in your own Claude
The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.
Your playbook
It lands in the earliest stage this tool suits. Move it on the Playbook page.
You’ll need
- A short-term cash flow forecast, weekly rather than monthly
- The covenant or facility position and its actual dates
- A named owner for stakeholder confidence, separate from delivery
You’ll end up with
- A cash runway with the actions that extend it, dated
- A cost and revenue plan sequenced in that order, not run in parallel
- A stakeholder communication rhythm that keeps pace with the numbers