How to step out of daily operations without the business slowing down
Every decision routes through you. Every exception waits for you. This is the guide to unpicking that, in the order that works, using what is already written across the playbook and the diagnosis.
Free to read. No account, no email.
What founder dependency actually is
Long hours are the wrong test. Plenty of founders work long weeks and the business runs fine without them for a fortnight. Dependency is narrower than that. It is when the business cannot complete normal work without a decision, a piece of knowledge, or an approval that exists only in you.
The test is simple. Take one ordinary week. Not a quiet one. Ask what would stall if you were unreachable from Monday to Friday. If the answer is quotes, exceptions, client escalations, and anything that needs judgment, the business is running on you.
That is a design problem. It is fixable in a defined order, and the order matters more than the effort you put into it.
Why the usual advice does not work
The common advice is to delegate more. Founders try it, and within a month the work is back on their desk. Three reasons account for most of that.
The first is that the task moved and the authority did not. Someone was asked to handle client onboarding but still has to check with you before agreeing to anything unusual. Every exception returns. The queue moved, it did not shorten.
The second is that the process was never written down. You hand over something you have done four hundred times and know by feel. The person receiving it has your five-minute summary. When it goes wrong, the fastest repair is you doing it, and the handover quietly reverses.
The third is hiring as the fix. A new person joins a structure where roles already overlap and nobody is clearly accountable. Cost goes up. Load stays. This is the most expensive version of the mistake, and it is the one founders reach for first because it feels like progress.
Where the time goes when you measure it
Founder weeks tend to break into four kinds of work.
| Kind of work | Where it should sit |
|---|---|
| Only you. Pricing the unusual deal, the relationship that closes the year, the call about direction. | Stays with you. This is the job. |
| Reached you by habit. Approving routine spend, checking work you already trust, joining calls out of interest. | Decision rights. Draw the line once and it stops. |
| Reached you by gap. Chasing an invoice, rewriting a proposal, fixing a handoff between two people. | A role or a process is missing. Naming which one is the work. |
| Reached you by fear. Redoing a team member's output because the standard was never written. | An SOP and a feedback conversation, in that order. |
Do the sort honestly and watch how small the first row turns out to be. That is the useful part of the exercise. A week that looks unmovable is usually a week full of work that never got a home.
The order to fix it in
Measure, then decide, then structure, then document.
Measure first because you cannot delegate a week you have not looked at. Decide second because handing over a task without the authority to finish it creates a queue rather than a handover. Structure third because a role has to exist before a person can be hired into it. Document fourth because a written process is what lets someone else hold your standard when you are not in the room.
AI comes after all four. A model applied to an undocumented process will produce a faster version of the confusion you already have. Once the process is written and running, the same model has something real to work with. That sequence is the whole thesis behind how we build.
Where this fits with the diagnosis
The diagnosis runs seven audits and maps the answers onto the five leaks above. It takes about five minutes and produces a report that names which level is under most stress, whether it is a symptom or the cause, and what to fix first. It is free and it does not need an account.
If you would rather read than answer questions, start with the Self chapters and work forward. The material is the same either way. The diagnosis just gets you to the right chapter faster.
Founder dependency shows as five different leaks.
The diagnosis engine sorts what you are feeling into five leaks, then tells you which ones are the symptom and which one is the cause. The first three are usually what you notice. The last two are usually why.
Level 1
Revenue leakage
Quotes go out late because you write them. Follow-up stops when your week gets heavy. Good clients are never asked for the second piece of work.
Level 2
Cost leakage
Work gets redone because the brief lived in your head. Your hours go to things a coordinator could hold. Utilisation is guessed rather than measured.
Level 3
Risk leakage
One person knows how the important account really works, and it is you. A week away is a week the business holds its breath.
Level 4
People leakage
Roles overlap, so nobody is clearly accountable. The team asks rather than decides, because the line between the two was never drawn.
Level 5
Systems leakage
The process exists, but only as habit. Handoffs vary by who is on shift. There is no number that tells you a part of the business is working.
The order
Symptom before cause
Fixing revenue and cost while people and systems stay broken buys a quarter. The engine names which level is acting as cause so the repair holds.
Four moves, in this order.
Each one is a chapter you can read now. Doing them out of order is the most common reason a founder tries to step back twice and ends up further in.
Move 1
Find out where your week actually goes
Not where you think it goes. A real audit of the last two weeks, sorted into work only you can do and work that reached you by accident.
Move 2
Draw the line on who decides what
Delegation fails when authority stays behind with the task. If the team still has to ask, you have not delegated, you have queued.
Move 3
Design the role before you hire into it
Hiring around a broken structure adds cost without removing load. Shape the role against the work that needs an owner.
Move 4
Write down the process that only you know
A documented process is what lets someone else hold the standard. It is also what AI needs before it can help with any of it.
Three tools that produce something you can hand to a person.
Free, no account. Each one ends with a written artifact instead of a score.
10 minutes
Delegation Map
Sort your current load into what to delegate to a person, what to outsource, and what to automate.
15 minutes
First Handoff Planner
Take one thing off your desk properly, with the brief, the checks, and the first review date written down.
20 minutes
SOP Starter
Turn one process you carry in your head into a document someone else can follow.
Where the rest of it lives.
This page routes. The thinking sits in the playbook, free to read, no email.
Part 2, Self
Your time, your energy, decision rights, and the delegation ladder. Eight chapters on the founder as the constraint.
Part 3, Team
Role design, when not to hire, feedback that holds a standard, and building a team that decides without you.
Part 4, Systems
Process mapping, the seven wastes, SOPs, and the metrics that tell you a part of the business is working.
The Business Machine
The first chapter of Volume II. Map how work moves through the business before you try to remove yourself from it.