Your Shop Only Runs Because You're Always There

The Day the Phone Was Mike's and Nobody Else's

March 2020. I'm at a card table in my garage. Hank's two, climbing up my leg, trying to eat a pen. My dad's in the hospital — knee replacement that went sideways, six weeks of complications. And I'm watching the phone not ring.

Not our shop line. Our shop line was ringing fine. I mean Mike's cell. The number he'd been giving customers since 1997, maybe earlier. The number on his cards, in his head, in the heads of every GC and property manager and repeat customer who'd been calling Whittaker Plumbing since my dad started it in 1984.

Mike wasn't answering. Mike was in a hospital bed. And out there somewhere, people had a number they'd been dialing for 36 years that was going to voicemail.

We almost lost the shop. We had a week in April where the receivables were about $14,000 light of what we needed and I couldn't explain it until I could. The shop had no customer list in any real sense. Just Mike — his memory, his word, the number in his pocket. When he stopped picking up, we found out fast what was actually holding the thing together.

It was him. Only him.

---

You're Not the Owner. You're the System.

When I was at Crestwood Plumbing from 2012 to 2018, I watched how a 30-truck shop works. They had a dispatch board. Written routing for after-hours calls. A contact at every supply house who knew the account by name. An actual three-ring binder that told every new CSR what to do when a job went sideways. Wasn't elaborate. Just written down. It existed outside anybody's skull.

I came back to Whittaker in 2019 and found three trucks, a limping schedule, and my dad's head. That was the whole operation.

Here's what I didn't see until Hank was eating my pen: I'd done the same thing. Taken a shop that lived in one person's brain and moved it into mine.

So ask yourself — actually answer it, don't skim past — what happens to your shop on Tuesday if you're unreachable?

Who else can authorize a purchase over $500 at your supply house? Do you have a contact at the city permit desk — a name, a person who knows your license number? Does anyone else at your shop know that name? What about the GC who always pays slow, the one who needs a signed PO before you'll even schedule him — does your CSR know that, or does it just live in your memory as a thing you handle?

What about the lady on Edgewater whose dog bites — the one where you always call ahead before the truck pulls up? Your tech rings the bell. Dog freaks out. She calls in upset. You know to call first. He doesn't, because you never wrote it down.

That's not a system. That's you. And the system crashes when you do.

---

What Actually Needs to Be Written Down

I'm not talking about an operations manual. Not a 60-page document with an org chart. Nobody's reading that. Becca wouldn't read it. Dom wouldn't read it. You wouldn't.

I'm talking about what lets Becca or Dom run Tuesday without you. Just Tuesday. Start there.

Becca revealed, without meaning to, exactly which things lived only in my head. She'd call me for the same categories of things over and over. That list is your documentation checklist.

Supplier logins. Not just the account number — the website login, the contact name at the branch, whether you're on credit or pay-as-you-go. Somewhere Becca can find it without calling me.

Permit contacts. Who handles residential permits in your area, what paperwork they want in what order, which inspectors want the pressure test documented before they'll walk through. I know all of this. None of it is written anywhere another person could use it.

Slow-pay GCs. Which ones need a signed PO before you schedule. Which ones are on COD because they went 90 days twice. Does your CSR know? Or do they book the job and you find out when the invoice sits?

After-hours routing. Who gets called, in what order, what they can do on their own versus what requires you. I had this in my head as "Dom calls me." That's a dependency, not a process.

Customer quirks. The biters, the cash-only people, the guy on Broadview who has to watch every minute of the work and will talk your tech's ear off for two hours if you let him. Put a note in Jobber. Thirty seconds. Saves everybody the phone call.

---

The Guys Who Say "My Crew Knows What to Do"

I'm in a truck two days a week. I should be in the office. I've known this for about three years. The reason I'm still in a truck isn't loyalty to the trade. It's avoidance. The truck is familiar. The diagnostic problem is satisfying. Writing down how things work is not satisfying and I keep not doing it.

I know guys who've convinced themselves the crew handles it. And I believe the crew is good. What I don't believe is that anything the crew knows is written anywhere — which means it's one resignation away from gone.

Think about how your best tech learned your way of doing things. He rode with you. Watched you. Picked it up over a season or two. That's fine for him. It's a terrible training model because it only works when you're there to ride with, and it produces a slightly different version every time someone new learns it that way.

I've said this before about apprentices and I'll say it again: the guys coming up now aren't worse than the guys coming up in 2005. They're being trained worse. By guys like me, who are too busy to sit down and write out what good looks like. So the apprentice learns from whoever has time for him, which is usually the second-best tech, who learned it from whoever had time for him. Each hand-off, a little more gets lost because there's nothing written to check it against.

That knowledge isn't tough because it's deep. It's fragile because nothing's holding it still.

---

Five Days at Disney World Almost Broke Us

We did Disney this past fall. Five days, all four of us, because Maeve had been asking since second grade and you can't say no forever. Getting our family on a plane is like getting a variance from the city — lots of paperwork, multiple sign-offs, something always falls through. But we went.

I handed off to Dom, gave Becca extra hours, told myself it was fine.

Here's what happened.

Day two. Dom scoped a line on a call off West 130th — classic Cleveland, older clay, partial collapse, spot repair, real money on the table. He knew exactly what it was. He couldn't authorize the repair quote. He called me. I was in a line at Epcot. We got it worked out, but I was on the phone for 45 minutes in a theme park while Hank was losing his mind next to a fountain and Becca was on another phone calling the customer back.

Same week. Our supply house — Consolidated on Brookpark — put a credit hold on the account because an invoice from 60 days out had kicked back. Wrong billing address. My fault, I'd never updated it. Nobody else could clear the hold. Required my voice confirmation. Dom paid out of pocket on a $1,100 job and got reimbursed later. He was not thrilled. I don't blame him.

Then a Google review came in — not a bad one, just a confused one, guy misread his invoice on a water heater swap and thought he'd been overcharged. Normally I'm on those within a day. This one sat for six days. By the time I got to it, he'd already posted on Nextdoor. One problem became two.

Every one of those had a fix that didn't require me. Authorization thresholds for Dom, agreed to ahead of time and written somewhere. Updated billing address on the Consolidated account — five-minute task I'd skipped for eight months. A response protocol for Becca to handle reviews when I'm out, so she knows what she can say on her own and when to wait for me.

None of that is complicated. None of it was done.

---

What You're Doing Monday Morning

Three things. Not ten. Three.

First. Think about the one call you most dread someone else taking. The one where you think, I just need to handle this myself. Write down how you'd handle it — step by step, plain language, like you're leaving a note for someone who's sharp but doesn't know your shop. Don't call it a process. Call it notes. Call it whatever. Just get it out of your head and into a document somebody can find.

Second. Open Jobber — or whatever you're running — and spend an hour on customer records. Add notes. Dog biter, call ahead, cash only, slow pay, the guy on Broadview who watches everything. Becca built out our whole follow-up sequence in Jobber without being asked because she was in there every day and saw what was missing. The notes field exists. Put things in it.

Third. List every account or vendor relationship where only you can authorize something. Supply house credit. Permit desk contacts. The verbal PO agreement with a GC. Pick one and add a second name to it this week. One phone call to Consolidated to add Becca as an authorized contact. One conversation. Do one.

That's it. If those three things happen Monday, you're closer to a Tuesday that doesn't require you standing in the middle of it.

---

Questions I Get About This

I'm a two-truck shop — isn't this overkill?

At two trucks you're probably the tech and the dispatcher and the guy who knows where the spare torch tip is. When you're out, everything stops — not some things, all of it. The smaller the shop, the more concentrated everything is in one person. You don't need a binder. You need one hour and a Google Doc your wife or your one other guy can actually find.

How do I do this without it becoming a project that never starts?

Don't sit down to build a system. Do it the same day something happens. You handled a call Thursday that only you could handle — write down how before you close the ticket Friday. Do that for a month, you've got four things documented. Do it for a year, you've got something real. Attach the writing to the event while it's still fresh. The "documentation day" you schedule for next month won't happen.

My best guy's been here 12 years and he'd push back if I tried to write his job down.

I've watched this one play out. He's not wrong to feel it — his knowledge is genuinely valuable and he knows it. Don't start by asking him what he knows. Start with what the office fails to give him — what information he always has to ask for twice, what slows him down, what he'd fix if he could. Document those gaps. That's easier to get to yes on, and it gets you in the habit of writing things down without making him feel like he's training his replacement.

Should I hire an ops manager?

At three to five trucks, probably not full-time — the salary doesn't pencil unless you're really billing. But a CSR who owns the office side changes things earlier than most guys expect. Becca's two days a week did more for us than my fifth truck did. The real question is whether there's a person — even part-time — who owns the back-office work and isn't you.

What's the minimum someone needs to know to run this place for a week?

Supplier contacts and account credentials. How the schedule gets built. Who can authorize what dollar amount on what job type. Where the licenses and insurance certificates live. How you want a customer complaint handled on the phone. That's five documents, none longer than a page. With those five things, someone can keep the shop moving without you. Not thriving. Moving. Get there first.

What software actually helps with this?

A notebook works if someone can find it. The problem isn't usually the tool — it's that nothing ever makes it out of your head into any tool. Whatever your CSR already lives in is the right answer, because that's where the work happens. The customer notes and job history in Jobber are there if you put things in them. You're not shopping for new software. You're building the habit of writing it down before you close the ticket.