You've booked the week off. By day two you're answering a supplier query from a sun lounger. By day four you're on a call "just for ten minutes." You come home and tell yourself next time you'll switch your phone off properly. Next time goes the same way.

The instinct is to treat this as a discipline problem — buy a better out-of-office habit, get stricter about notifications. It isn't a discipline problem. It's a structural one: your business doesn't have an operating system that runs without you in the loop.

What "Founder OS" actually means

Every business runs on an operating system, whether anyone designed it or not — the rules for who decides what, how information moves, and what happens by default when no one intervenes. In an owner-run business, that operating system is usually: everything routes through the founder. It works, right up until the founder is on a beach with no signal.

"What happens to this business if the owner leaves?" is the question every buyer asks within the first ten minutes. It's also the question your own week is quietly answering, every time you can't switch off.

Four questions that diagnose it

If a customer complaint landed today, would it reach you directly, or would someone else already have the authority to resolve it? If a five-figure decision needed making this week, is there anyone else who could make it and be right 80% of the time? Does anyone besides you know where the important passwords, contracts and supplier contacts actually live? Has revenue ever grown in a month you were fully offline?

If most of those answers are "no," the holiday isn't the problem. It's the symptom.

Get a clear read on your own dependency.

The Founder Assessment maps exactly where decisions, information and relationships are still routing through you.

Start the Founder Assessment

Why this compounds

Founder-routed decision-making doesn't just cost you rest. It caps how fast the business can grow — every decision waits in a queue of one — and it caps what the business is worth, because a buyer is really asking to purchase a set of assets and systems, not a subscription to your attention. Owner dependency and Founder OS are the same problem seen from two angles: one is about whether the business runs without you; the other is about whether your week does.

Rebuilding the operating system

1. Assign Decision Rights, Not Just Tasks

Name, in writing, who can approve what — spend limits, refunds, hiring — without asking you first.

2. Set an Information Rhythm

A short weekly number-check (revenue, pipeline, cash) that runs whether or not you're in the room, reported to you, not run by you.

3. Write the "If This Happens, Do That" List

The ten situations that currently land on your desk by default — document the answer once so it stops being a question.

4. Test It on Purpose

Take a real day fully offline before you take a real week. Treat what breaks as the punch list, not the verdict.

Most founders can rebuild the core of this in a quarter. What changes isn't how hard you work — it's whether the business has a way of functioning that doesn't have your name as the only variable.

Ready to see where you actually stand?

The Founder Assessment gives you a clear picture of how founder-dependent your business really is — and what to fix first.

Start the Founder Assessment →