Vol 1 · Issue 88 · Sunday, August 9, 2026

You know the vacation I am talking about.

You are somewhere nice. The family is in the water. You are under an umbrella with a laptop on your knees telling yourself this is just twenty minutes, and it is fine, and you would rather handle it now than come back to a mess.

That is not a vacation. That is your office with worse wifi and better scenery.

I am not going to give you a lecture about work life balance. You are an adult, you built something, and if you want to work on a beach that is your business. But I want to make a different argument, because the vacation question is not really about vacation.

It is the cleanest diagnostic there is for whether you own a business or a job.

A job stops paying when you stop showing up. A business does not. And the two week test is how you find out, honestly and quickly, which one you have got.

Do not book two weeks off to find out. That is how you learn the answer in the most expensive way possible, while your family watches.

Run the dry run instead. Seventy two hours. Pick three consecutive business days in the next month and go dark. Not on vacation. You are at your desk, or at home, or wherever. You are just unreachable to the business.

No Slack. No email. No approvals. No "quick questions." Your team knows you are out. Nobody knows it is a test.

Give one person an emergency line and define emergency narrowly. Client is threatening to leave, somebody got hurt, a payment system is down. Not "we are not sure how to handle this."

Then, and this is the actual assignment, you keep a list of everything that came to you anyway, and everything that broke.

Three days is enough. If three days generates a two page list, you have your answer and you did not need to ruin a trip to get it.

When the list comes back, it sorts into four buckets. Almost everybody has at least two of them running hot.

Decisions. Things stalled because nobody was allowed to call it. This is the permission problem, and it is the fastest one to fix. If your list is mostly this, you already know what to do, because it is a Red list and a conversation.

Knowledge. Things stalled because nobody knew how. Somebody had permission and still could not move, because the how lives in your head. This is the documentation problem, and it is slower but not hard. Ten one pagers on the ten things that stalled.

Access. Things stalled because you are the only one with the login, the signing authority, the vendor relationship, the bank access. This is the sneaky one, and I want to spend a minute on it.

Relationships. Things stalled because a client would only talk to you. This is the slowest to fix and the most valuable one to solve.

Most owners find out during a dry run that half a dozen things route to them purely because of credentials. The Google account. The domain registrar. The payment processor. The insurance portal. The one vendor who will only deal with the owner because that is how it has always been.

That is annoying on a Tuesday when you are unreachable. It is a genuine crisis if something actually happens to you.

And I mean that plainly. If you got hit by a truck tomorrow, could your spouse or your business partner or your operations lead keep the company running long enough to sell it or wind it down properly? For a lot of owners the honest answer is no, and not because the business is not viable, but because nobody can get into anything.

This one takes an afternoon and it is the highest return afternoon in this entire arc.

That is it. One afternoon. And it converts a category of failure that is embarrassing on vacation and catastrophic in an actual emergency.

This is the one owners defend the hardest. "My clients hired me. They want me. That is the whole value."

Sometimes true. Usually not as true as it feels.

Most of the time your clients want their problem handled well and their questions answered fast. You are how that has always happened, so they associate the outcome with you. That association is real, but it is not fixed, and it will not transfer on its own. It transfers on purpose or not at all.

The move is not to disappear. It is to add before you subtract.

Bring the second person into the relationship while you are still fully in it. They sit on the calls. They send some of the updates. Over a couple of months the client stops noticing which one of you replied, because both replies are good.

Then you step back gradually, and you do it while things are going well. Nobody has ever successfully introduced a new point of contact in the middle of a problem. If you wait until you are burned out or a crisis hits, the handoff reads as abandonment, because from the client's side that is precisely what it looks like.

The context is the hard part. Not the tasks, the context. What they care about, what they said in March, who the difficult stakeholder on their side is, why we do not bring up the 2024 project. That lives in your head and it is the actual reason handoffs feel impossible. Getting it out of your head, whether that is clay.earth or CRM notes or a shared doc that somebody actually maintains, is what makes the relationship transferable at all.

One more thing shows up in every failed dry run, and it has nothing to do with the four buckets.

Even when the business runs fine, owners check in constantly because they have no way to know things are fine. So they call. They log in. They ask for updates. Not because anything is wrong, but because the absence of information feels exactly like the presence of a problem.

The fix is a scoreboard you can read on your phone in thirty seconds. Not a dashboard project. Five numbers.

The last two matter as much as the numbers. A person you trust writing two honest sentences on a Friday will do more for your ability to actually disconnect than any amount of automated reporting, because it answers the question you are actually asking, which is not "how are the numbers" but "is anything on fire."

You can wire the numeric part up in Make.com so it lands as a Friday message without anybody assembling it by hand. Do the automated part automatically and the human part by hand. Trying to automate the judgment is what turns useful reporting into noise everybody stops reading.

And if you want to know whether you are actually stepping back or just telling yourself you are, Rize is a fairly brutal mirror. Owners routinely believe they have handed off a whole category of work and then discover they are still in it four hours a week.

Passing is not that nothing came to you. Something always comes to you, and it should.

Passing means: no client relationship got damaged, no revenue got lost, no decision sat blocked for three days waiting on you, and nothing needed you that a person with permission, a document, and a login could not have handled.

You are allowed to come back to a list of things to sort out. That is normal. The bar is that the list is annoying rather than expensive.

If you fail, and most people do the first time, the failure is the deliverable. That list of what broke is a better strategic plan than anything you would come up with staring at a whiteboard, because it is not theoretical. It is the actual set of constraints holding your company at its current size, ranked by how loudly each one screamed when you stopped compensating for it.

Fix the top three. Run it again in ninety days. That is the whole loop.

Three reasons, and only one of them is about time off.

The first is that a business that runs without you is worth money and a business that does not is worth roughly the value of its equipment. Nobody buys a job. If you ever want to sell, or bring in a partner, or step into a different role in your own company, this is the entire thing being valued.

The second is that burnout in owner operated businesses almost never comes from the volume of work. It comes from the fact that it never stops. There is no version of the week where the thing runs without you, and that is a very different weight than being busy.

The third is the one nobody talks about. You cannot think while you are the bottleneck. Every genuinely good decision I have watched an owner make came out of a stretch of quiet. Every mediocre one came out of a reactive week. If your calendar has no room for a thought that takes longer than nine minutes, you are going to keep running the same playbook, which is exactly why revenue goes flat and stays flat.

That is the whole arc this week, and it is really one idea in four parts. Monday: you are approving things that do not need you. Wednesday: the answers live in your head instead of on a page. Friday: you hired for the fun work instead of the work that is eating you. Today: here is how you find out whether any of it worked.

None of it requires more revenue, more staff, or a better market. It requires you to stop being load bearing.

So pick your three days. Put them on the calendar before you close this email, because the version of this you intend to do next month is the version that never happens.

Then go find out what you have actually built.

Reply with VACATION and I will send you the seventy two hour test kit. The prep checklist, the four bucket sorting sheet for whatever breaks, and the emergency access document template so you can knock out the access problem in an afternoon.

Talk Soon,
Dan
Dan Kaufman
Founder, Dead Simple Growth and Pinnacle Masters

P.S. If your first reaction was "there is no way I can go three days," that is not a reason to skip it. That is the finding. Write down the specific reasons you cannot, because that list is the same list you would have gotten from running the test. You just got it for free. The test would only have told you which of those reasons were real.