The tech everyone calls when something breaks
Every AV and trades company has one person the whole crew calls when a job goes sideways. Reducing dependency on him does not mean managing him out or hoping he never leaves. It means capturing what he knows, while he is still doing the job, so the answer lives in a system instead of only in his head.
Why does one tech end up carrying the whole company?
It happens gradually, and it happens because he is good at the job. He has been on more installs than anyone else, so he remembers which client hates visible keypads and which builder always changes the rack location on the walkthrough. Nobody assigned him the job of being the answer to every question. He just answered enough of them, for long enough, that asking him became the fastest path to a fix. Junior techs stop trying to solve a problem themselves the moment they know a phone call gets them the real answer faster. That habit is not laziness. It is a rational choice inside a company where the documented answer does not exist.
What does it cost when he is the only source?
On a typical week, a senior tech fielding a steady stream of internal calls from the field loses hours he should have spent on paying work. Across the AV companies I have run and watched closely over twenty years, that pattern usually costs a senior tech somewhere between four and eight hours a week, time that should have gone into installs the company can bill. It rarely shows up as one big number on a spreadsheet. It shows up as a schedule that always runs a little behind, and nobody can say exactly why. It is the same kind of leak the calculator on the AV page puts a number on. The same pattern shows up in how long your quotes take to reach a client, which is not a coincidence. Both start the same way, an answer that only lives in one place.
Here is where that knowledge tends to live right now, unwritten, and where it should live instead.
| What junior techs call about | Where the answer should live instead |
|---|---|
| Which processor reset sequence works on this brand | A documented fix pulled from past service notes |
| Where the rack goes in this particular house style | The as-built record from a similar past job |
| Which client hates visible keypads | Client preference notes captured at the last visit |
| What password gets this panel talking again | A credential record tied to that address |
Is documenting his knowledge the same as replacing him?
No, and treating it that way is why most companies never do it. Nobody wants to feel like the company is building a way to work around them. The system is not built to replace him. It is built so the parts of his knowledge that repeat, the ones he answers three times a week without thinking, stop needing him specifically. He still handles anything unusual. He just stops being the default answer for questions that already have a right one on record.
How do you capture what is in his head?
Not with a sit-down interview. Record him while he works. A phone video of him walking a rack build, a quick recording right after a service call explaining what he found and how he fixed it, the notes he already types into a ticket. Feed that into a system built to turn it into a documented answer, tagged to the job, the brand and the symptom. He keeps doing his job exactly the way he already does it. The only change is that this time, what he says gets kept.
What does this look like inside a working shop?
In the company I ran for twenty years, the fastest fixes always came from the same two or three people, and everyone knew it. A service call that took a new hire ninety minutes took one of them twelve, because they had seen the exact symptom before. The company was not smarter. It just had memory that lived in a few heads instead of anywhere else. Once that memory gets pulled into a system every tech can reach from the truck, the gap between a new hire's twelfth month and his second month gets a lot smaller. More on how that company ran is on the about page.
Is this urgent, or can it wait until he leaves?
Waiting is the default, and it is expensive. Your techs already ask a question and expect a direct answer. Today the only place that answer lives is his head, so the question becomes a phone call and the answer costs both of them ten minutes. Juan's experience from 20 years running an AV company: the senior tech loses 30 to 40 percent of his day to those calls, and none of it shows up on a timesheet. If a documented answer does not exist for them to ask, they will keep calling him, right up until the day he does not answer, and that day always arrives with no warning.
What to do this week
- Ask him to record a two minute voice memo after his next three service calls: what broke, what he checked, what fixed it.
- Pull the last ten tickets he closed and write down what a junior tech would have needed to know to close them without calling him.
- Book the free discovery call and bring both. We will show you what a knowledge base built from that looks like.
Questions owners ask
Will he feel like I am trying to replace him?
Only if you frame it that way. Most senior techs like being asked to show, not tell, and most of them are tired of the phone ringing on their day off. Frame it as protecting what he built, not working around him.
What if he does not want to participate?
Start with what he already produces: tickets, notes, texts to the office. You can build a first version from what exists before you ever ask him to record anything new.
Does this work if I only have two or three techs?
Yes. Smaller crews depend on one person even more, so the payoff shows up faster. The system does not need a large company to be worth building.
How is this different from a shared folder of documents?
A folder holds files nobody reads under pressure. A knowledge base answers the specific question a tech is asking, in the moment he is standing in front of the problem, pulled from your own job history. If the same person always ends up on the phone when something breaks, the free 30 minute discovery call is a good place to find out what that is costing you.