Your lead tech's head, turned into something the whole team can query.
Every AV company has one person who knows how everything was wired, where the passwords live, and which client hates the sound of a relay clicking. That knowledge works right up until he is on a ladder, on vacation, or on his way to another company.
This playbook walks you through building a Tech Brain from material your shop already has. No new software, no developers, no data migration. You gather what exists, load it into a project, and give it instructions so your team gets documented answers with sources instead of calling one guy.
Runs on Claude and Cowork from a plain conversation. Setup takes an afternoon. The result gets better every job you close out.
Tuesday, 10:15am. Your lead tech is elbow-deep in a rack build when his phone rings. It is the assistant tech at a job site asking which switch port feeds the media room. Your lead answers from memory, because the as-built never got made.
Twenty minutes later it rings again. Different tech, different job, and this one is not about your work at all. How do I silence the alarm on this UPS. How do I reset a Savant remote. Nothing in that answer is specific to your company. It is sitting in the manufacturer's documentation, and it still costs your highest paid tech ten minutes and his place in the rack.
Both calls have the same shape. A level two tech, a project manager, or an assistant tech needs one fact, and the only path to it runs through one person.
Model the cost from the interruptions. A lead tech fielding ten internal calls a day loses four to eight productive hours every week, which means the highest paid tech in the building spends thirty to forty percent of his day answering questions instead of installing. Those are modeled numbers, not measured ones. Run them against your own crew and see what you get.
The call itself is not the whole cost. He hangs up and he is not back yet. He has to find his place, retrace what he was doing, and get back into the flow he was in before the phone rang. The call was ten minutes. The interruption was thirty.
The bigger exposure never shows up on a P&L. When that person leaves, a decade of institutional memory walks out overnight and nothing on your balance sheet ever warned you.
He is not hoarding anything. He is the best tech you have, buried under every question in the building, because the company never built a place for what he knows to live.
| Category | What it captures |
|---|---|
| Standards | How your shop wires, labels, terminates, and names things. The conventions every tech should follow and nobody wrote down. |
| Procedures | Your SOPs. Rack build steps, network setup, commissioning, closeout requirements, service call protocol. |
| Product knowledge | Manuals and integration notes for the gear you actually install. This is the pile that kills the how-do-I-reset-this calls, because the answer was never company specific to begin with. |
| Job history | Structured records of what went where, room by room, with make, model, and location. |
| Client specifics | Preferences, quirks, access instructions, and the details that make a return visit smooth. |
| Recurring answers | The questions your lead tech gets asked most, answered once, in writing. |
Step 1. Start with what your team asks about. A Tech Brain is not a filing cabinet. It holds the answers people call about repeatedly. If nobody has ever asked about it twice, leave it out. Starting small is not a compromise here, it is the thing that makes this work.
Step 2. Gather the four piles. Your material is already scattered, so collect it in one pass rather than perfecting one source at a time.
SOPs and standards. Anything already written down goes in first. Most shops open the folder and find three documents where they thought they had thirty. That gap is normal, and you do not close it by scheduling a writing project, because that project never happens.
You close it one process at a time, and you do not have to type any of it. Download the AV SOP Builder from the vault, add it to Claude once, then: