20 August 2026 · 3 min read

What the business looks like without you in it

Most founders can describe their product in detail and their absence not at all. That gap is worth closing before it gets tested for you.

Ask most founders to describe their product and they will talk for twenty minutes without pausing. Ask them to describe what happens to the business if they are unreachable for a month, and the answer is usually much shorter, and much less considered.

That is not negligence. It is that the product is the interesting problem, the one you get to solve on purpose, and your own absence is not a problem you ever chose to work on. It only becomes visible when something forces it: illness, a holiday that turns out to matter, a second business that needs the same attention.

It is worth working on before that, because the version you design in advance is much better than the version you improvise under pressure.

The difference between busy and load bearing

Not every dependency on the founder is a problem. A founder who is simply busy, doing a lot of the work personally, is expensive but not fragile. Replace some of their time with someone else's and the business runs the same, just slower to start with.

The dangerous dependency is different. It is the decision nobody else is trusted to make, the relationship nobody else has, the piece of judgement that exists in one person's head and nowhere else. That is load bearing. Remove it without warning and something does not slow down, it stops.

The test is simple: does removing you change what the business can do, or only how quickly it does it? The first is a real risk. The second is just a cost.

Where the load bearing pieces actually hide

They are rarely where founders expect. Not usually the big strategic calls, which tend to get made rarely enough that a delay is survivable.

More often it is the small, frequent judgement: which client gets the benefit of the doubt, which corner is safe to cut this week and which is not, who on the team is actually struggling versus who is just quiet. That knowledge accumulates over years and is almost never written down, because it never felt like a decision worth documenting at the time.

• Client relationships where the trust is personal rather than institutional, and would need rebuilding from nothing if you disappeared.
• Judgement calls made so often they feel automatic, which is exactly why nobody has been taught to make them.
• Information that lives in your head because writing it down never felt urgent, until it suddenly is.

None of these show up on an org chart. All of them show up the day you are not there.

What actually closes the gap

The honest version of this work is slow, and it is mostly about making decisions visible rather than hidden.

Narrate the judgement calls out loud, in front of the people who will one day need to make them, rather than just making them. Let a deputy make the call wrong sometimes, while you can still catch it, rather than only ever seeing it made correctly because you did it yourself. Write down the things that feel too obvious to write down, because obvious to you is not the same as obvious to anyone else.

None of that is glamorous. It looks, from the outside, like doing your job slightly less efficiently for a while. It is the only way the efficiency ever transfers to someone else.

A question worth asking honestly

If I were unreachable for a month starting today, what would the business be unable to do?

Most founders can name at least one true answer immediately. That answer is not a reason to feel exposed. It is simply the next thing worth working on, in the same deliberate way you worked on everything else that used to depend entirely on you.