How small does my shop need to be before I need a handoff process?

If you have more than one person touching a lead between inbound and invoice, you need a handoff process — even a two-person shop. The owner-plus-spouse setup is where we see the worst leakage because everything lives in someone's head and nobody is officially responsible for what.

What's the single highest-leverage handoff to fix first?

Office-to-tech. Specifically, the moment between 'we have a booked appointment on the calendar' and 'the tech shows up at the right address with the right info.' If your techs are calling the office from the truck asking 'what's the address again,' you're losing time and customers.

Do I need a CRM to do this, or is a shared spreadsheet enough?

A shared spreadsheet works at one to three crews and breaks at four or more. The break point is when two people start editing the same row at the same time, or when the spreadsheet stops syncing to the truck. Once you're there, a real CRM (GHL, Service Titan, Housecall Pro, Jobber) pays for itself inside 90 days from saved time alone.

How to Hand Off Leads From Office to Sales to Crew Cleanly

You can have the best ad spend, the cleanest Google profile, and the fastest text-back system in your market — and still lose 20–30% of your booked work because the handoff between the office and the truck is broken.

This is the part of the Convert chapter most contractors underestimate. The lead made it through the funnel. It got captured. It got responded to. The customer said “Friday at 10am.” Then on Friday at 10:15am the tech is sitting in the wrong driveway and the homeowner is calling the office wondering where you are.

That’s not a marketing problem. That’s an operations problem. And it’s the cheapest one to fix.

Where the handoffs actually break

Across the contractor accounts we’ve audited, here are the five handoffs where leads and jobs leak the worst:

Inbound call → CRM record. Office takes the call but never enters the customer in the system, so nothing follows up.
CRM record → calendar booking. Customer is in the system but never made it onto a tech’s day.
Calendar → truck. Tech doesn’t see today’s schedule until they walk into the office at 7:30am.
Truck → invoice. Job got done, but nobody invoiced for two weeks.
Invoice → review request. Customer paid, but nobody asked them for the Google review while it was top-of-mind.

Each one is a 5–15% revenue or reputation leak. Stack them and a shop doing $1.2M is leaving $250–400K on the table every year.

The minimum viable handoff system

You don’t need Service Titan to run a clean handoff. You need three things:

1. One source of truth for “where is this lead right now?”

Pick one place — your CRM, full stop. Not your phone, not the office whiteboard, not the texts on the owner’s iPhone. The CRM is the lead. If it’s not in the CRM, it doesn’t exist.

Train every person who touches a lead to update the CRM before doing anything else. Office takes a call → enters the lead → then handles whatever the customer needs. Order matters.

2. A fixed pipeline with named stages

Stages we recommend for most service-trade businesses:

New Lead
Contacted (within 24h)
Estimate Scheduled
Estimate Sent
Won / Lost / Stalled
Job Scheduled
Job In Progress
Job Completed
Invoiced
Paid
Review Requested
Closed

Every lead lives at exactly one stage. When something changes, the stage moves. No lead sits at “Contacted” for more than 5 days without an automation kicking in to either move it forward or close it as Lost.

3. Triggers that fire when a stage doesn’t change

This is where 90% of shops drop the ball. The stages exist, but nobody enforces them. Set up automations that run when a lead hasn’t moved:

“Estimate Scheduled” → no movement in 48 hours → SMS reminder to customer + Slack ping to owner
“Estimate Sent” → no movement in 5 days → automated SMS asking for a decision
“Job Completed” → no movement in 24 hours → auto-create invoice and SMS the link
“Paid” → no movement in 24 hours → auto-fire the review request

When the system does the chasing, your office doesn’t have to.

The three handoff documents that change everything

Once the pipeline exists, the daily friction comes down to documentation. Three templates fix most of it.

The job ticket

Every booked job gets a single ticket the tech sees on the truck. It contains:

Customer name, address, phone (with click-to-call)
Time window
Reason for the call (in the customer’s own words, not “service”)
Equipment make / model / age if known
Last visit summary (if returning customer)
Owner notes — anything the office wants the tech to know

If the tech has to text the office to ask for any of this, the ticket is incomplete. Fix the ticket, not the tech.

The end-of-day update

Every tech submits a 60-second update at end of day:

Jobs completed (with photos)
Jobs that became larger / smaller than estimated
Customers who mentioned future work
Anything broken that needs follow-up

This kills two diseases at once: invoicing delays (the office can invoice tonight) and the slow death of “Mr. Henderson said something about his garage door but I don’t remember what” type leads.

The morning brief

Every morning, the office runs a 5-minute review:

Yesterday’s revenue
Today’s booked work (with any priority flags)
Stalled deals from the pipeline that need a phone call
Any customers waiting on a callback

If the brief takes longer than 5 minutes, your CRM dashboard isn’t set up right. Fix the dashboard. Don’t lengthen the meeting.

Where shops resist this — and why they shouldn’t

The pushback we get most often, almost word-for-word: “My techs aren’t going to do all this CRM stuff. They’re field guys.”

That’s a real concern, and the fix is simpler than most owners expect: make the CRM faster than the alternative. If updating a job in the CRM takes 30 seconds and not updating it triggers a Slack ping from the office, the tech updates it. If updating takes 5 minutes and there’s no consequence for skipping it, nobody updates anything.

Three rules:

The CRM has a mobile app on every truck — not a web link, the actual app
Updates can be made by voice-to-text whenever possible
Skipping the update has a visible consequence (the office sees the gap immediately)

We’ve installed this in shops where the owner swore his crew would mutiny. After 30 days, the techs liked it more than the office did, because they stopped getting interrupted by phone calls asking “where are you” and “did you finish that thing yet.”

The compounding effect

Clean handoffs do something most contractors don’t realize: they raise your effective close rate without changing a single thing about your sales pitch.

A shop that converts 25% of estimates to booked jobs and loses 20% of booked jobs to operational breakage is netting 20%. The same shop with a clean handoff converts 25% and keeps 95%, netting 23.75%. Same lead spend. 19% more revenue.

Multiply by the review-request automation (which raises your Google rating by 0.3–0.6 stars over six months), and you’ve now bought yourself another 8–15% in inbound leads at zero ad spend.

For the front-of-funnel piece that makes sure the lead got captured in the first place, read Missed-Call Text-Back: The 30-Second Setup That Saves 40% of Leads. For the calendar question that decides which scheduling style fits your shop best, see Calendar Booking vs Phone Booking: Which Wins for Service Calls?.

The whole system is in the Convert chapter of Why Your Website Isn’t Ringing. If you want the install done for you, book a strategy call and we’ll walk through where your handoffs are leaking.