Why your install team keeps guessing what was sold
The sales to operations handoff breaks because a signed proposal is not the same as a documented scope. Sales closes on a conversation full of verbal promises: the rack location, the keypad placement, the client's preferences. None of it reaches the install team in writing, so the tech relearns the job standing on site on day one.
Why does the install team keep asking questions that should already be answered?
Because the answers exist, just not anywhere the install team can reach them. The salesperson knows the client hates visible keypads. He heard it on the walkthrough. He just did not write it down anywhere that follows the job into production, because the proposal software was not built to carry a preference, only a price. So the tech shows up on install day, sees a keypad location on the plan that the client already said he hated, and has two bad options: call the office and wait, or guess and hope he guessed right.
What does a bad handoff cost, beyond the awkward conversation on site?
The visible cost is the awkward conversation. The real one is quieter. Across the AV companies I have run and watched, a single bad handoff on a mid-size project usually costs somewhere between two and eight technician hours in rework, repeat trips and time spent reconstructing a scope that should have arrived documented, the same math that runs the leak calculator on the AV page. Multiply that across a dozen active jobs and the number stops being a rounding error. It becomes the gap between a project that should have been profitable and one that barely broke even, and almost none of it shows up as a single line anyone can point to.
What belongs in a kickoff packet?
| What operations needs | Where it usually lives now, unwritten |
|---|---|
| Exact rack and equipment placement | In the salesperson's memory of the walkthrough |
| Access notes: attic, crawlspace, gate codes | Wherever the client happened to mention it |
| Everything verbally promised, including the small stuff | Nowhere, repeated from memory at handoff meetings, if there is one |
| Anything the client hinted at wanting added later | Not written down until it becomes a change order dispute |
Is this the same as just holding a better handoff meeting?
A meeting helps, but it depends on the salesperson remembering everything in the room at the right moment, and memory is not a system. A kickoff packet pulls from the actual notes, messages and voice memos captured during the sale, not from what one person can recall weeks later standing at a whiteboard. The meeting can still happen. It just stops being the only place this information lives.
What does this look like inside a working shop?
On the jobs I ran that went smoothly, the tech walked in already knowing where the rack went, which client hated visible wiring, and which builder always moved the schedule at the last minute. On the ones that went sideways, that same tech was piecing it together from a proposal that only listed equipment and a price. The difference was never the crew. It was whether what sales knew ever reached the people doing the install. More on those twenty years is on the about page.
Is anyone else solving this, or is it just us?
The trade press has started treating AI as a regular beat instead of a novelty. CE Pro's own archive tagged for artificial intelligence runs 19 pages deep as of today (cepro.com, accessed September 17, 2026), most of it product news from vendors building AI into design and proposal tools. What is missing from that coverage is the handoff itself: almost nobody is writing about the gap between the sale and the install, even though it is where a lot of AV margin quietly disappears. That gap is exactly what a kickoff packet is built to close. A handoff that runs on documentation instead of memory is one piece of a business that runs without you catching every detail yourself.
What to do this week
- Pull your last three closed jobs and ask the install lead what he had to figure out on site that should have been in the proposal.
- Write down every verbal promise from your next three walkthroughs, even the small ones, in one place before the job gets scheduled.
- Book the free discovery call and bring both. We will show you what a kickoff packet looks like built from your own sales process.
Questions owners ask
Is this just a checklist my salespeople should already be filling out?
A checklist only works if someone remembers to fill it out under pressure. A kickoff packet pulls from what already gets said and written during the sale, so it does not depend on anyone remembering to do extra paperwork.
Does this slow down the sales process?
No. It runs alongside the sale, capturing what already gets said on the walkthrough and in follow up messages. Nothing about closing the deal changes.
What if the salesperson and the install lead are the same person?
The gap still exists, just inside one person's memory instead of between two people. A documented handoff protects against the day that person is out sick or on vacation and someone else has to run the job.
Can this catch change orders too, not just documentation gaps?
Yes. The same captured notes that document what was promised also flag what was added later but never priced, which is usually where unbilled work hides. If your install team keeps having to guess what was promised once they are on site, the free 30 minute discovery call is where that gets fixed.