Every growing service shop has a “Mike.”

Mike is the guy who’s been with you since the beginning. He knows the gate codes for the gated communities, he knows which commercial boilers are temperamental, and he’s the only one who remembers that the Smith job from three years ago had a weird wiring work-around.

On the surface, Mike is your MVP. But if you look closer at your call logs, Mike is actually a Shadow Dispatcher. If your junior techs are stopping mid-job to call Mike four times a day, or if your office manager has to “check with Mike” before quoting a simple change order, you don’t have a scalable business. You have a Mike-dependent bottleneck.

The Real Cost of “Ask Mike”

It feels efficient in the moment. Mike gives an answer in 30 seconds, and the job moves on. But here’s what’s actually happening to your margins:

• You’re paying your highest-earning tech to be a help desk. Every minute Mike spends on the phone with a tech who can’t find a shut-off valve is a minute he isn’t billing out at his premium rate.
• You’re building a “lazy” field culture. When the answer is always a phone call away, your newer guys stop trying to problem-solve. They lose the “hunter” instinct and become “order takers.”
• The Vacation Nightmare. You can’t let Mike take a week off because the wheels fall off the trucks the moment he hits the highway.

How to “Download” Mike’s Brain into SableCRM

Scaling past five trucks means you have to move away from tribal knowledge and into a shared system. You don’t need to clone Mike; you just need to digitize what he knows so the rest of the team can use it.

1. Kill the “Where is it?” phone calls. The #1 reason techs call the lead is for site context. Use the Site Notes and Photo features in SableCRM religiously. If a tech finds a hidden clean-out or a weird electrical sub-panel, they need to snap a photo and tag it to the property. Next time a junior tech rolls up, they see the photo in the app. No phone call required.

2. Standardize the “Mike Way” with Checklists. Mike doesn’t need a checklist, but everyone else does. Build out your workflows in the CRM so that a 2nd-year tech has a step-by-step guide that mirrors how Mike would do the job. It’s a safety net that builds confidence and cuts down on “Is this right?” texts.

3. Use the CRM as the “Source of Truth.” If your office staff is still asking Mike for status updates on other people’s jobs, your workflow is broken. When every tech updates their status and notes in real-time, the office sees exactly what’s happening. Mike gets to keep his hands on his own tools instead of playing “middleman” for the dispatcher.

The Goal: From Technician to Mentor

Eliminating the Shadow Dispatcher effect isn’t about making your lead tech less important. It’s about freeing them up. When Mike isn’t tethered to his phone answering basic questions, he can actually mentor your team in the field, handle the high-ticket “nightmare” jobs, and help you grow the company.

If your business stops when your lead tech’s phone battery dies, it’s time to get that knowledge out of their head and into your system.