Tuesday, October 20th, 2026

Here's a quick test. It takes about ten seconds and most people fail it.

Pretend you're gone from December 21st through New Year's Day. Phone off. Laptop closed. Not "checking in once a day." Gone.

What breaks?

Don't answer with your gut. Answer with a list. Which invoices don't go out. Which leads sit in the inbox until January. Which client gets a confused email from somebody on your team who doesn't know the answer. Which ad keeps running after the offer expired. Which password lives only in your head.

If the list is short, close this email and go enjoy your Tuesday.

If the list is long, you're not alone, and I've got a theory about why.

You're still doing your old job.

Every owner I know got promoted at some point. Maybe it happened the day you hired your first person. Maybe it happened the day revenue crossed a number that meant you couldn't do it all anymore. Somewhere along the way, the business needed you to stop being the person who does the work and start being the person who decides what work gets done.

You took the promotion. You just never cleaned out your old desk.

So now you've got two jobs. The new one, which is leading the thing, and the old one, which is everything you were doing three or five years ago when the business was smaller. Building the proposals. Formatting the reports. Answering the same five questions from every new client. Fixing the website at 11pm. Checking every invoice before it goes out. Writing every follow up by hand.

None of those tasks are bad. Some of them you're great at. A few of them you actually enjoy. And there's the catch. The old job feels like the thing that made you good, so letting go of it feels like letting go of the part of you that works.

The data says this isn't a you problem. It's an owner problem. The vacation gap numbers from OnDeck have been rattling around for a while and they haven't gotten any prettier. Most owners who take a vacation at all are taking about five business days a year, roughly half of what a typical corporate employee gets. And of the ones who do get away, about two thirds check in with work every single day.

So the person who owns the company has less freedom than the people who work for one. That's backwards, and for most of us it's backwards because the business was built around the old job, and the old job can't take a day off.

You've got about nine weeks left in the year. The holidays are coming whether you're ready or not. And there's one week in late December when your clients slow down, your team wants time off, and you'd like to be a human being with your family for a few days.

That week is going to run a stress test on your business. You can let it happen to you, or you can run the test yourself in November and fix what breaks before it matters.

Run it yourself. Here's how.

You can't hand off what you can't see, and you can't see your own week. Nobody can. Your memory of what you do is a highlight reel. The real list is longer and dumber.

For ten working days, write down every task you touch. Every one. Not "worked on client stuff." Write "rebuilt the onboarding doc for the new client," "answered the same pricing question for the third time this week," "fixed the broken link in the confirmation email."

Next to each one, jot how long it took. Rough is fine.

If you hate logging, Rize tracks where your time goes in the background and will show you the uncomfortable truth without asking you to remember anything. Pair it with a quick note at the end of each day for the stuff that happened off the laptop, like the phone calls and the texts you answered in the parking lot.

At the end of ten days you'll have somewhere between sixty and a hundred and fifty line items. Most people are shocked by two things. How many of them are repeats, and how many of them have nothing to do with the job they think they have.

Now go down the list and ask one question about every task.

Which version of me does this belong to?

Some tasks belong to the owner you are now. Setting direction. Making the hard calls. Key relationships. Pricing. Hiring. The two or three things only you can do because of who you are and what you know.

Some tasks belong to the person you were three years ago. Delivery work you've done a hundred times. Admin. Scheduling. Formatting. First drafts of things that follow a pattern.

And some tasks don't belong to anybody. They're leftovers from a version of the business that doesn't exist anymore. The weekly report nobody reads. The meeting that used to matter. The manual check you started doing after one bad week in 2023 and never stopped.

Every task gets one of four labels.

Keep. It belongs to the owner. You do it.

Teach. It belongs to the old you, and somebody else can learn it.

Automate. A system can do it without a person.

Kill. Nobody would notice if it stopped.

Then run the money test on everything in Keep. Take what you'd realistically pay someone to do that task, hourly. If it's a fraction of what your time is worth when you're doing owner work, it doesn't belong in Keep. Move it. You're not too good for the task. You're too expensive for it.

Be honest here. The temptation is to put a lot of things in Keep because "nobody does it like I do." That might be true. It's also true that nobody does it at all when you're in the hospital, on a plane, or at your kid's recital, so "like I do" isn't the bar. "Good enough that the client is happy" is the bar.

Start with the Kill pile, because it's free and it's fast.

Stop doing one thing from that pile tomorrow. Don't announce it. Just stop. Wait two weeks. If nobody asks, it's dead. If somebody asks, you just learned it mattered to them, and you can decide whether it goes in Teach or Automate.

You'd be amazed how much of your week is a ritual you're performing for an audience that left.

Here's where most handoffs die. The owner decides to document a process, opens a blank doc, writes "Step 1:", and closes it forty minutes later with nothing.

Writing a process from memory is miserable because you do most of it without thinking. That's the whole reason it's a habit. Your brain skips the steps that matter most.

So don't write it. Record it.

Next time you do a task from the Teach pile, hit record and talk through it out loud like you're training somebody sitting next to you. Why you click this before that. What you check. What usually goes wrong. Where the weird exception lives. If it's a call based process, like a discovery call or an onboarding kickoff, record the call itself. I use Fathom for that, because the transcript is the raw material for the documentation and I never have to reconstruct what I said.

Then take that transcript and turn it into a first draft of a process doc. This is a place where AI genuinely earns its keep, because it's organizing your knowledge, not inventing it. I run it through Galaxy.ai with a prompt like this:

"Here's a transcript of me doing a task out loud. Turn it into a step by step process doc for someone who has never done it. Keep my exact wording for anything that sounds like a judgment call. Flag every place where I said 'it depends' and list the questions they'd need answered."

That last line is the gold. Every "it depends" is a decision you've been making in your head for years. Write the rule down and you've just handed off a piece of your judgment, not just a set of clicks.

Then you read it, fix what's wrong, and you're done. Twenty minutes instead of two hours, and it actually sounds like you.

The second place handoffs die is the jump. The owner goes from doing it themselves to dropping it on somebody's desk with a "you got this." Two weeks later it's a mess, the owner takes it back, and now they've got proof that "nobody can do this but me."

That proof is fake. You skipped the rungs.

Every handoff climbs five rungs, in order.

Rung one, they watch you do it. Live or recorded.

Rung two, they do it with you watching.

Rung three, they do it alone and you check before it goes out.

Rung four, they do it and tell you after.

Rung five, they just do it, and you see the results in a weekly review.

Some tasks climb all five in a week. Some take a month. The mistake is staying on rung three forever because you like checking, or jumping from one to five because you're in a hurry.

And here's a rule I wish somebody had given me fifteen years ago. When they get it wrong on rung three, don't fix it yourself. Send it back with the reason. If you fix it, you just kept the job. If you send it back with the reason, you just taught the job.

If you don't have a team, this still applies. Your "somebody else" might be a part time assistant, a contractor, a virtual assistant for five hours a week, or a system. Same ladder applies to software. Watch the automation run, check its work, then let go.

A lot of the old job isn't tasks. It's glue. The little moves that connect one thing to another. Copying a lead from the form into the CRM. Sending the welcome email. Reminding the client about the appointment. Creating the folder. Pinging the team when a deal closes.

None of that should involve you, and most of it shouldn't involve a person at all.

If your sales and client communication live in Go High Level, you can build most of the follow up and reminder glue inside the platform without touching anything else. If your tools are spread out across a few apps, Make.com is how I connect them, so a closed deal can create the client folder, send the welcome sequence, and drop the kickoff task on someone's list without me lifting a finger.

The rule for this step is simple. If you've done the same connecting move more than ten times this year, it's a build ticket, not a task.

Now the part that makes this real.

Pick one weekday in November. Put it on the calendar today. On that day, you're unavailable. Not on vacation. Just unavailable, from 8am to 6pm. Your team, your assistant, or your systems run the business without you.

Tell people ahead of time. Leave a one page coverage sheet that says who handles what, where the logins live, what to do if a client is upset, and what can wait until tomorrow.

Then go do something that isn't work. Take a long walk. Go to a movie in the middle of the day. Sit somewhere without your phone.

The next morning, ask one question. What broke, and why did it need me?

Every answer is a fix. A missing process doc. A decision rule nobody wrote down. A login that only lived in your head. An approval that didn't need to be an approval. Fix those, and run a second dry run in early December if you've got the stomach for it.

By the time the real week comes, you won't be hoping the business survives without you. You'll already know.

None of this is complicated. People still don't do it, and I don't think laziness is the reason.

I think it's identity.

The old job is who you were when things were working. It's the version of you that got the business off the ground, landed the first clients, figured out the craft. When you hand that work off, it can feel like you're handing off the proof that you're good at something.

I know that feeling from the inside. When I was rebuilding this year, I caught myself holding onto tasks I had no business doing because they made me feel competent on days when the bigger stuff felt shaky. Formatting something perfectly is a nice little hit of control when the big picture isn't cooperating.

But the business doesn't need you to be who you were. It needs you to be who it needs now. That person's job is smaller in hours and bigger in weight. Fewer tasks. Harder decisions. More thinking. Less doing.

Letting the old job go isn't losing yourself. It's finally showing up for the promotion you already accepted.

Handing off chaos. If the process is a mess when you do it, it'll be a mess when they do it, plus they'll get blamed. Clean it up during the recording step, not after.

Hovering. You climbed to rung five and then started checking everything again because one thing went sideways. One mistake isn't a trend. Fix the process, not the person, and step back.

Picking the wrong first handoff. Don't start with your most complex, highest stakes task. Start with something frequent, low risk, and annoying. Early wins build trust on both sides.

Keeping the fun one as a hobby. Sometimes you'll want to hang onto a task because you enjoy it. That's fine, honestly. Just know you're choosing it, and make sure it's not eating the hours your owner work needs.

I built the whole thing out so you don't have to piece it together from an email.

It's called The Old Job Exit Kit. Inside you'll find the ten day task inventory tracker, the Keep, Teach, Automate, Kill sorting grid with the money test built in, the record first process template, the exact AI prompt for turning a transcript into a process doc, the five rung handoff ladder with a checklist for each rung, the November dry run plan, a one page coverage sheet you can fill in and leave behind, client and team notice templates for the holidays, and a thirty day handoff calendar to keep the whole thing moving.

It's free. No sequence waiting behind it. Duplicate it into your own workspace and go.

Get The Old Job Exit Kit here

And if you run the inventory and realize the problem isn't the tasks, it's that the whole business was built around you and there's no structure underneath it, that's a bigger conversation. It's exactly the kind of thing we work through at Pinnacle Masters. Hit reply and tell me what your list looked like.

Don't build the whole kit this week. Do two things.

Open your calendar and block one full weekday in November. Label it "Dry Run." Don't move it.

Then pick one task from your week that you've done more than twenty times this year. Next time you do it, hit record and talk it through out loud.

That's it. One date on the calendar and one recording.

Nine weeks from now, I hope you're somewhere with your phone in a drawer, and I hope nothing breaks. And if something does, I hope it's something you already knew about.

One step, one day. Grace over guilt. — Dan Kaufman

———————————————————————————

Tools I use and trust. If you sign up through these links I may earn a small commission at no extra cost to you. I only recommend things I actually use.

Rize.io, time tracking that makes you honest about your hours

Fathom.video, AI meeting notes that actually capture what matters

Galaxy.ai, all your AI tools in one place

Go High Level, forms, CRM and follow up in one place

Make.com, automate your workflows without writing code

Beehiiv, where serious newsletter operators publish