How do you make your business run without you?

Can a business really run without its founder?

Yes, though not all at once and not by accident. A business runs without you when the things that only you do today have been handed over, written down or given a clear owner. Most founders get there one area at a time.

It helps to admit that the dependence is normal. In the early days you were the sales team, the support desk and the finance function, and the company grew around that. Gallup’s research on founders and delegation puts the shift neatly: as a company grows, the founder must “work on the business, rather than intensely in it.” It also found that only one in four employer entrepreneurs it studied had high levels of what it calls Delegator talent. So if handing over feels unnatural, you’re in the majority.

There’s a useful idea from software here. Engineers talk about a team’s truck factor, or bus factor: the number of people who would have to disappear before a project stalls. A 2016 study of 133 popular GitHub projects by Avelino and colleagues describes it as a way to measure “how prepared is a project to deal with developer turnover.” It found that 65% of those projects had a truck factor of two or less. In plain words, most of them depended on one or two people. Young companies often look the same, and the one person is usually the founder.

What actually stops when you’re away?

Usually four kinds of thing. Decisions wait for your sign-off. Customers wait for you personally. Know-how sits in your head or your password manager. And the team waits to check with you, even on things they already know how to do.

These are different problems with different fixes, which is why “delegate more” rarely helps on its own:

• Decisions. Price changes, refunds, hires and spending above a small amount all queue for you.
• Customers. Your biggest accounts have your mobile number, not the company’s.
• Knowledge. How the invoicing works, which supplier to call, where the contract lives.
• Team. People ask first, not because they can’t decide, but because asking has always been safer.

Most founders lean hardest on one or two of these. Finding out which ones is the first job, because fixing the wrong area first is how a hand-over plan stalls.

How do you stop decisions waiting for you?

Write down the decisions you make most often, who can make each one without you, and up to what amount. A limit with a number in it gets used. “Use your judgement” doesn’t, because nobody wants to guess wrong with the founder’s money.

Start with frequency, not importance. The decision you make twenty times a month costs your team more waiting than the one you make twice a year. For each one, write a single line:

• “Anyone in sales can offer up to 10% off an annual plan. Tell me after.”
• “The ops lead can approve supplier spend under £2,000 without asking.”
• “The support lead can refund any order under £200 the same day.”

Then share the list and leave it alone. The first time someone uses a limit and picks differently from you, let it stand. If you overrule it, everyone learns the list was decoration. We call the slow build-up of waiting decisions Decision Debt, and the Decision Debt calculator will show you roughly what yours is costing.

How do you hand customers over to the team?

Introduce a named second contact to your biggest customers, and then let that person handle the next real request from start to finish. An introduction on its own changes nothing. The customer has to see the other person solve something.

Customers come to the founder because the founder has always answered. Early on, that was good service. But it also means your best accounts are tied to your phone. If you’re away, they wait, or they feel let down.

The hand-over works best in three steps. First, a short message or call where you introduce the second contact and say plainly that they can make decisions. Second, the next time the customer asks for something, you pass it straight to that person and stay out of the reply. Third, after it’s resolved, you check with the customer that it went well.

How do you get what’s in your head written down?

Record how one process works while you do it, then ask someone else to run it next time while you watch. A ten-minute screen recording beats a forty-page manual nobody reads, because it captures the steps you no longer notice you’re taking.

Don’t document everything. Pick the processes that would hurt most if they stopped for two weeks: payroll, invoicing, the monthly numbers, the supplier you always phone yourself. Then look for the things only you can reach. Shared accounts, admin logins and supplier relationships that run through your personal email are the quiet ones. Move them into a shared password manager or a company account before you go, not from the airport.

The second half matters more than the recording. When someone else runs the process for the first time and gets stuck, that’s the gap in your notes. Fix the note, not the task.

How do you stop the team checking with you first?

Step back from the places where checking happens. Let someone else run next week’s leadership meeting, and stay quiet for the first twenty minutes. When people bring you a question they could answer themselves, ask what they would do and then tell them to do it.

Checking in is a habit that both sides keep alive. The team asks because the founder has a view on everything. The founder answers because answering is quick and feels helpful. Together they teach everyone that nothing is settled until you’ve seen it. If that pattern sounds familiar, our post on why managers struggle to delegate goes into the habits that keep work flowing back to the person in charge.

It also helps to be honest about why you like being asked. Being the one every decision passes through brings control, and control is comfortable. Keeping it can be a fair choice, but it should be a choice, not something that happened while you weren’t looking.

What does preparing for a two-week break look like?

Here’s a hypothetical example. A founder runs a twelve-person software company that sells to small accountancy firms. She hasn’t taken more than three days off in two years. She decides to take two weeks off in August and starts planning six weeks before.

• Six weeks out: she books the dates and tells the team. She keeps a list for one week of every time someone waits for her. It has 31 items. Most are discount approvals, customer escalations and questions about the billing system.
• Five weeks out: she writes decision limits for the five most common items on the list and shares them. The head of sales can approve discounts up to 15%. The support lead can issue refunds and credits up to a set amount.
• Four weeks out: she introduces her account manager to the company’s five largest customers by video call, and passes the next request from each one straight to him.
• Three weeks out: she records two short walkthroughs: running the monthly billing and handling a failed payment. Her operations lead runs billing that month while she watches and says nothing.
• Two weeks out: she moves three supplier logins from her personal email into the shared password manager. She asks the head of product to run the Monday leadership meeting from now on.
• One week out: she takes a trial day off. Two things wait for her: a contract renewal with unusual terms and a question about a hire. She adds both to the decision list with clear owners.
• While she’s away: one person can reach her by phone for a written list of three emergencies. Nobody calls.

When she gets back, a few things were done differently from how she’d have done them. One discount was more generous than she would have offered. Nothing broke. The waiting list in her first week back has nine items, not 31.

The point isn’t that she found a perfect system. She treated the break as a test of the hand-overs, and accepted that “different” isn’t the same as “wrong.”

How far ahead should you plan the time off?

At least a month, and longer if you’ve never done it. The planning is the part that makes the business work without you. A break booked at the last minute just means the work waits, or follows you.

The research on holidays points the same way. Writing in Harvard Business Review, Shawn Achor and Michelle Gielan report that “Poorly planned and stressful vacations eliminate the benefits of time away.” They suggest planning the trip “at least a month in advance,” because one of the key predictors of a good return is the stress caused by not planning ahead. Their work looked at employees in general rather than founders, but the logic carries. For a founder, much of the stress before a break is the hand-over itself, and a month gives you time to do it calmly.

What should still come to you while you’re away?

Very little, and you should decide what in advance. Write a short list of genuine emergencies, such as a serious security incident, a legal deadline or a threat to payroll, and agree who can reach you and how. Everything else waits or gets decided without you.

The list does two jobs. It protects your break, and it tells the team that everything not on it is theirs. Without a list, people will message you about anything they’re unsure of, because they don’t know where the line is. With one, they know.

If being away feels heavy for reasons beyond the to-do list, that’s worth taking seriously too. The weight a founder carries isn’t only tasks, and we’ve written about it in our entry on Founder Load. There’s also a Founder Load self-test if you want to look at that side.

Where does your company lean on you most?

Most founders have a sense that the company depends on them, but not where it depends on them most. Knowing that tells you which hand-over to do first, so you don’t try to fix decisions, customers, knowledge and the team all at once.

Two Weeks Away is a free self-test built for this. It takes about three minutes, needs no sign-up, and your answers stay in your browser. You answer 12 questions about an ordinary month, and you get a score out of 100 with one of three bands: “The company is you”, “Leaning on you” or “Ready for two weeks”. You also see the four areas ranked by how much they lean on you, with one hand-over to try on Monday for each. A low score isn’t a verdict. Holding things close can be the right trade-off in the very early days, or in a crunch. The score shows you where that trade is starting to cost the company.

For a wider read on how you lead, including how often you let someone make a decision you’d have made differently, try The 42 Test. You’ll find the other tests and posts for this stage on the founders page.

A company that runs without you isn’t one where you stop mattering. It’s one where your time goes on the things only a founder can do, because everything else has an owner. Start with one hand-over this week. Then book the break, and let it tell you what to hand over next.