Speed-to-lead math: why the first 5 minutes win the job
Respond in under 5 minutes and you win most jobs you quote. Respond after 30 and you're quoting ghosts. The response-time math, worked out with honest numbers.
5 min readBy Nick Hayghe
This is the piece where we show the math. But first, the disclaimer up front: every number below is an illustrative example, not a study. I made the figures realistic, not magical. Run your own numbers with your own close rate and job value — the method is what matters, not my exact figures.
If you want the full system this math plugs into, start with Never miss another lead: the after-hours response guide. This post is the argument for why speed is the whole game.
The 11:48pm lead that books itself
Picture the lead from the pillar guide. Saturday, 11:48pm. Water heater burst. The customer calls you — voicemail. Calls a competitor — voicemail. Calls a third company whose system picks up, asks two questions, and books them for Sunday morning.
Here's the timeline, and it's the only timeline that matters:
> 11:48pm — lead calls you → voicemail ✗
> 11:51pm — lead calls competitor #2 → voicemail ✗
> 11:53pm — lead calls company #3 → answered, qualified, booked ✓ 12:01am
> Sunday 9:00am — you call back → "we already got it fixed" ✗
Company #3 wasn't better. They weren't cheaper. Their reviews weren't stronger. They were awake — or rather, their system was.
That's speed-to-lead. The job goes to whoever responds first, and the window is measured in minutes, not hours.
The decay curve
Every minute a lead waits, their chance of booking with you drops. Here's a rough picture of what that looks like, using round illustrative numbers:
| Response time | Your share of the lead's attention |
|---|---|
| Under 5 minutes | You're the frontrunner — they haven't called anyone else yet |
| 5–15 minutes | You're in the running — they've maybe called one competitor |
| 15–30 minutes | You're catching up — they've got another quote in hand |
| 30+ minutes | You're a backup plan — they've probably decided already |
| Next morning | You're calling back a ghost — job's done, customer moved on |
These aren't lab-tested figures. They're what happens when you talk to enough shop owners about enough lost jobs. The shape of the curve is what matters: it falls fast, and it doesn't come back.
After 30 minutes, you're not competing for the job anymore. You're competing for the customer's memory. "Oh yeah, that company did call back. The other guys already fixed it though."
Let's do your math
Grab a napkin. This is the whole decision.
Take your average job value. Say it's $450 for a service call. Now estimate how many after-hours leads you get per month that go to voicemail or sit in a form queue until morning. Say it's 8.
Not all 8 were winnable. Some were price shoppers, some were outside your area, some were wrong numbers. Say half were real — 4 leads. And say your close rate on a fast response is 50%. That's 2 jobs a month you're losing to the clock.
> math: 4 real leads × 50% close rate × $450/job = $900/month lost
> math: that's $10,800/year — for leads that already found you
These are example numbers. Yours will differ. But notice what I did: I used your close rate and your job value, and I discounted the leads by half before counting anything. If your number still comes out scary, you don't need a study to tell you there's a problem. You've got your own data.
Now the other side. What does it cost to fix? A response system — the text-back, the AI receptionist, the booking flow — typically runs a few hundred dollars a month once it's built, and the build itself is fixed-price. Compare that to your number above.
If your number is $900/month at risk and the fix costs $300/month to run, you don't need a spreadsheet. You need a Tuesday to set it up.
After 30 minutes, you're not competing for the job anymore. You're competing for the customer's memory.
The objection: "But I can't be awake all night"
Of course you can't. That's the whole point.
Speed-to-lead isn't about you working harder. It's about the system working while you're asleep. The system answers, qualifies, and books — and you wake up to a calendar, not a mystery.
Here's the reframe: that's not a staffing problem. It's a wiring problem. You're not short-staffed. You're short one automation.
The AI receptionist is the piece that covers the overnight shift honestly — what it handles, what it hands to you, and what it costs versus an answering service. The missed-call text-back is the smallest possible version: one automation, instant payback, no new hardware.
One honest caveat
Speed-to-lead doesn't fix a bad business. If your prices are wrong, your reviews are bad, or your techs don't show up, answering faster just loses jobs faster. The system multiplies what's already there. Make sure there's something worth multiplying.
But if your work is good and your reviews are strong — if the only problem is that nobody's there when the phone rings at night — then speed is the highest-ROI fix in your business. Nothing else you're spending money on converts leads that already found you.
The bottom line
The lead doesn't care about your hours. They care about their problem, right now. Respond in five minutes and you're the answer. Respond in the morning and you're a callback they politely ignore.
> 5 minutes → frontrunner ✓
> 30 minutes → backup plan ✗
> morning → ghost ✗
Do the math with your own numbers. If the answer scares you, the fix is one of the cheapest things you'll buy this year.
Get a free tool-stack audit
We'll look at your missed calls, your after-hours volume, and your current setup — then tell you exactly which fix pays for itself first. Book a free tool-stack audit.
