You Don't Own a Business If Only You Can Run It

My dad ran Whittaker Plumbing & Drain for 36 years on a Rolodex and a personality. Knew every customer by first name. Knew their dogs' names. Knew which lady on Broadview needed you to come in through the side door because the front steps were icy and she'd never remember to tell you. Three trucks, steady work, a reputation in Parma that took three decades to build.

And in March of 2020, when Mike Whittaker stopped answering his phone because he was in a hospital bed with a knee replacement that turned into a six-week complication, the calls stopped coming back.

Not all of them. But enough.

I was sitting at a card table in my garage running dispatch with two-year-old Hank climbing up my leg, realizing in real time that what I'd inherited wasn't a plumbing company. It was a 65-year-old man's relationship network. And that man was currently unavailable.

The shop didn't belong to Whittaker Plumbing. The shop belonged to Mike. Everything that made it run was in his head, and his head was somewhere in the ICU at Parma Community.

---

If Only You Can Run It, You Don't Own It

You can own 100% of the equity and still be completely dependent on one person to keep the whole thing from falling apart. If that person is you, you don't own a business. You own a job with your name on the truck.

Mike wasn't careless. He worked hard every day for 36 years. Trained me on the tools, on the trade, on how to talk to customers. What he never trained anyone on was the business, because the business was him. His brain was the CRM. His personal cell was the dispatch line. His handshake deals with vendors were the accounts payable system. Nothing written down. Nothing anyone else could find.

The moment he was out, I was doing triage on accounts I barely recognized. We had a supply house relationship I didn't know the terms on. We had longtime customers who called Mike's personal cell when they had problems and bypassed the main line entirely. Several of them, when they got voicemail for three weeks straight, just called somebody else. One of them had been a customer since 1991.

---

What "Documented" Actually Means

When I was at Crestwood Plumbing of Cleveland from 2012 to 2018, their dispatch ran on paper checklists and a CSR who'd been doing the job for nine years. She could train someone. The process was written down well enough that a new hire on day one didn't have to call her every twenty minutes to figure out what to do next.

That's the bar. Not a binder. Not a policy manual.

The bar is: could someone do this job their first week without calling you?

When I took over Mike's shop in January 2020, the answer to that question was no. For everything. There were no call scripts. No pricing logic written anywhere. No path for when something went sideways on a job. When Dom hits something weird on a call, he calls me. Always. Because there's no other option.

If your answer to "what happens when something weird comes up" is "they call me," you haven't documented a process. You've documented your own indispensability.

Working documentation gets used without the author in the room. That's the whole test.

---

Spring 2020

Mike went in for the knee replacement in late February. Post-op infection, readmission, a complication that turned two weeks into six weeks in the hospital and another four in rehab. Gone from February through May.

The calls from longtime customers came in the first week. They wanted Mike. Some of them said it directly. "Is Mike available? I'd like to talk to Mike." I told them Mike was recovering, that I was his son, that I'd been running the shop. Some of them were fine. Some said they'd call back. A few of them I never heard from again.

I'm not bitter. Those were people who'd trusted a specific human being for fifteen or twenty years. They weren't rejecting Whittaker Plumbing. They were loyal to Mike, and Mike had never built anything to catch that loyalty when he wasn't there to receive it himself. The loyalty had nowhere to land.

Then there were the accounts. I found a supplier we'd been buying water heaters from at a price that didn't make sense. Turned out Mike had a handshake deal that went back maybe fifteen years, something he'd worked out after buying a lot of units during a slow stretch when the supplier needed the volume. Nobody wrote it down. The supplier didn't volunteer it when I started calling in orders. I overpaid for water heaters for three months before I figured out something was wrong and asked directly.

That's what "it's all in his head" costs. In actual dollars.

---

Succession Planning Isn't for When You're Ready to Retire

Most small shop owners think about succession when they're 60, or when their knees go, or when a kid shows some interest. That's backwards.

The time to train your replacement is right now, while you're still there to catch their mistakes. You can't build this under pressure. Mike couldn't have transferred 36 years of relationships and pricing logic and vendor deals in six weeks even if he'd been healthy enough to try.

I love my dad. I mean that first because I mean it. And I'd tell any of my own kids, Trent, Maeve, Hank, that if they ever want to take over this shop, we're doing it with a written buyout agreement and a real operating document, and we're starting that process years before I plan to hand anything over. Not because I don't trust them. Because the handshake I inherited from Mike almost sank us both, and the handshake wasn't what broke things. The undocumented business did.

I write about apprentice training sometimes. Here's what I say: the problem isn't the apprentices. The problem is guys like me don't have time to train them right, then act surprised when they don't know things. We're the failure point. If you wait until you're under pressure to transfer knowledge, the transfer's already screwed. There's no version of "I'll document it when I have time" that actually happens. You're never going to have time. That's the job.

---

What Your Replacement Actually Needs to Know

Not an org chart. Not a mission statement. The actual stuff that runs a day.

Pricing logic for jobs that go sideways. Slow tub drain, Dom scopes the line, sixty feet out the clay's collapsed, there's a mature oak nobody's touching, hand-dig, permit, inspection. Started as an $89 drain snake. I'm at $6,800 best case, $9,500 if the tree becomes a problem. How does Dom price that call when I'm not standing in the driveway? Right now, he calls me. That's not a system. I need to write down the decision tree: what triggers a scope, what findings trigger which repair categories, when I bring in a sub. All of it lives in my head. None of it is written anywhere.

Customer relationship knowledge. The neighborhood reputation stuff. Who we are on Nextdoor in Parma. Which longtime customers have been with us since Mike's era and what that relationship actually requires. There's a lady who's been calling us since 1997. She needs a ten-minute conversation before she'll accept a quote. That's not a complaint, it's just how she is, and knowing it means the call goes smooth instead of sideways. Becca carries most of this right now. She's in the office two days a week. If Becca's not there, that knowledge doesn't exist anywhere.

The vendor relationships. Which rep at the supply house actually calls back. Which accounts have net-30 terms we've earned by paying early. Handshake stuff, mostly. Needs to be written down before it disappears the way Mike's water heater deal disappeared.

The escalation path. When a tech finds something unexpected, who do they call? Right now the answer is Joe. Joe needs to stop being the answer.

---

What You Do This Week

You're not going to be ready. Do it anyway.

Pick one job type you run constantly. Water heater swap. Drain snake. Sewer scope and quote. Then record yourself talking through every decision you make from the first call to the closed invoice. Voice memo on the way home from the job. Talk through it out loud. Get someone to clean up the transcript. It doesn't have to be pretty to work.

Then figure out who in your shop could run things for two weeks if you got hit by a truck. Be honest about whether that person actually exists. If they do, sit down with them this week and tell them three things they don't know yet. Not a meeting with an agenda. A conversation in the truck. "Here's how I think about pricing a scope job. Here's what I do when a customer wants a number before I've seen the work. Here's who to call at the supply house if something's weird on an order." Three things. That's enough to start.

Then write down one vendor relationship, one pricing rule, and one customer who's been with the shop long enough that the relationship predates you. Just those three things, enough context that someone else could pick up that account without you in the room.

The shop almost died in 2020 because everything was in one man's head. I watched it happen. I'm still fixing the gaps. Don't wait until the pressure's on to find out where yours are.

---

FAQ

If I'm the best plumber in the shop, isn't it more efficient to stay on the tools and keep billing?

For this week, maybe. For this year, no.

Every hour you spend as the best tool on your own bench is an hour you're not building the thing that makes the shop run without you. I still go out on jobs two days a week. I know it's a problem. But there's a difference between going out because you love it and going out because nobody else can do what you do. If nobody else can do what you do, that's not efficiency. That's a dependency you built on purpose and kept building every day you didn't fix it.

How do I document processes when every job is different?

You're not documenting outcomes. You're documenting how you think. A job that goes sideways doesn't need a script, it needs a framework. "When a scope shows collapse past forty feet under a structure, here's how I think through the options" is useful. A price list isn't. Voice memo it on the way home and have someone clean it up later.

My shop is just me and one other guy. Isn't this overkill?

It's more urgent at two people than at ten. At ten, there's some redundancy whether you planned it or not. At two, you are the redundancy, and when you go down, there is none. A two-truck shop that loses the owner for six weeks doesn't slow down. It stops. Start small, one voice memo, one conversation, but don't tell yourself you're too small for this to matter. You're not.

What's the difference between training someone to do my job and handing over the business?

Training someone means the shop runs when you're in the hospital, or at Trent's hockey game, or stuck at a job that ran long. A sale or a handoff is a legal and financial transaction. You can do the second without ever doing the first. Most owners should be doing the second right now regardless of what they ever plan to do with the first.

How do I handle longtime customers who want me specifically?

Some of them won't fully transfer. I've made peace with that. But most of them will accept someone else if you're the one who makes the introduction. "I'm sending Dom, he's been with me six years, he'll take care of you" lands completely different than a stranger showing up at the door. You introduce them. You vouch. You follow up after the first job. Do it in person when you can.

When does building your replacement actually cost more than it saves?

In my experience, it doesn't. But the cost is up front and the savings come later, which makes it feel that way for a long time. The hour you spend recording your pricing logic doesn't pay off this week. It pays off in eighteen months when your lead tech quotes a sewer job correctly while you're somewhere else. Most owners never do this. That's also why most owners are still taking 9 p.m. calls when they're 60.