How do I get out of the day-to-day without it falling apart?

You've tried leaving before.

You took the week. You told everyone you were unreachable. Then on day two somebody texted about something genuinely urgent, and you answered, because it was genuinely urgent. By Thursday you were doing an hour a day and telling yourself that was still a win.

It sort of was. It also told your team exactly what to do next time.

The three things everybody tries

You hire someone senior. An ops person, a GM, a number two. Six months later they're running the parts you already had handled, and the decisions still come to you. You've added payroll without removing yourself.

You document everything. SOPs, a wiki, Loom videos on a Sunday. People read them once during onboarding and then ask you anyway, because asking you takes nine seconds and finding the doc takes four minutes.

You go cold turkey. Stop answering. Let it break so they learn. It does break, the break costs a client, and you come back in harder than before.

None of those are stupid. They're the obvious moves and they're the right moves eventually. They fail in that order because they're treating the symptom.

What's actually holding you in

You're not in the day-to-day because you're disorganized. You're in it because you're the only place certain information lives, and nobody can act without it.

Three kinds usually:

The judgment calls. What we do when a client asks for something we don't normally do. Nobody wrote that down because it's different every time, and you've never had to explain the pattern because you just handle it.

The permissions. What someone can spend, approve, promise or refuse without checking. Most owners think these are clear. Ask three people on your team for the number they can spend without asking you, and see if you get the same answer three times.

The history. Why we stopped using that vendor. Why that client gets different terms. Why we do it the slow way on that one job. All of it lives in your head and none of it is written anywhere, so every situation that touches it routes back to you.

Hire a great GM into that, and the GM becomes a very expensive router.

What the numbers say about when this bites

We measured owner-led companies with the same twenty questions.

Under $250K, 56 percent name people as the constraint, and in that band the person is nearly always the owner. There's nobody to delegate to yet, so it isn't really a delegation problem.

By $5M to $20M it looks different. People drops to 24 percent. Operations climbs from 1 percent to 15 percent. That's the band where the machine finally exists and the machine is now the thing that's broken.

The dangerous stretch is between. Somewhere around one to five million you have enough people to delegate to and not enough structure for delegation to land. That's where owners burn out, and it's the band where most of them are still diagnosing the company they had three years ago.

The sequence that works

Not documentation first. Documentation is step three and everybody starts there.

First, find out where you actually are. Not where you feel like you are. Every person answers the same questions separately with no names attached, and you find out which decisions genuinely stop at you versus which ones you just think do. Those two lists are never the same list, and most owners are shocked by which items are on which.

Then set permissions, in numbers. Not "use your judgment." A dollar figure, a discount percentage, a list of things that never need asking. Write them down and then hold to them the first time someone uses one and you disagree. That first time is the whole thing. If you override it, you've taught everyone the number is decorative.

Then document, but only the routed items. You don't need a wiki. You need the eleven things that actually come back to you written down properly. The measurement tells you which eleven.

Then leave, on purpose, short. Two days, not two weeks. Let something small break while the stakes are small and you're still close enough to see what broke and why.

What it costs to stay where you are

Do the math on your own time.

Take the hours a week you spend on decisions somebody else could make if they had the information. Be honest, not generous. Multiply by fifty.

That's the number. Not the money, the hours. Then ask what you'd have built with them, because that's the actual cost, and it's been running every year you've been doing this.

Who this doesn't apply to

If you like being in it, stay in it. Plenty of owners genuinely enjoy the work and don't want a company that runs without them, and there's nothing wrong with that. It's a real business model, and it's just not a sellable one.

The problem is only a problem if you want out and can't get out.

Start with the measurement

Twenty questions, about ten minutes, free.

You'll see which of the five areas your answers point at, and how owners your size answered the same questions. It's the first step of the sequence, and it's the one everybody skips.