Speed to lead is the time between a homeowner asking for help and your business giving a real answer. For most contractors it's the cheapest marketing improvement available, because you've already paid for the lead. A Harvard Business Review audit of 2,241 U.S. companies found that firms that tried to reach a web lead within an hour were nearly seven times as likely to qualify it as firms that waited even one more hour, and more than 60 times as likely as firms that waited a day or longer.1 The same audit found 23% of companies never responded at all.
This post separates what the research shows from what gets repeated on sales blogs, gives you a measurement definition that can't be gamed, and puts a dollar figure on a slow reply using a model you can fill in with your own numbers.
What the speed-to-lead research actually says
Two studies get quoted constantly. They're worth reading closely, because the details matter.
| HBR audit (2011) | Lead Response Management study (2007) | |
|---|---|---|
| Who ran it | James Oldroyd, Kristina McElheran, David Elkington, published in Harvard Business Review | James Oldroyd with InsideSales.com, using InsideSales.com's own call data |
| Sample | Web inquiries sent to 2,241 U.S. companies; a companion study used 1.25 million leads at 29 B2C and 13 B2B companies | 3 years of data, six companies, over 15,000 leads and over 100,000 call attempts |
| Headline finding | Contact within an hour: nearly 7x as likely to qualify as an hour later, 60x+ vs. 24 hours or more | Contact odds drop 100x between 5 and 30 minutes; qualification odds drop 21x |
| Response behavior found | 37% responded within an hour, 24% took over 24 hours, 23% never responded; average 42 hours | Not measured across companies |
| Caveats | Web leads across many industries, not home services specifically | Vendor-sponsored, six companies, not peer reviewed, 2007 data |
Source: HBR, March 2011; InsideSales.com/MIT Lead Response Management Study, 2007
The HBR audit sent web inquiries to companies and timed the replies: 37% responded within an hour, 16% within one to 24 hours, 24% took longer than 24 hours, and 23% never responded. Among companies that responded within 30 days, the average response time was 42 hours.1
The 2007 Lead Response Management study is the source of the "100 times" figure. It examined three years of data from six companies, more than 15,000 leads and more than 100,000 call attempts, all from InsideSales.com's system. It reported that the odds of contacting a lead dropped 100-fold between 5 and 30 minutes, and the odds of qualifying it dropped 21-fold. It also found contact odds fell five-fold between minute 5 and minute 10.2 It was sponsored by a vendor that sells sales-dialing software, it covers six companies, and it's from 2007. It's directionally useful. It isn't physics.
Google turned speed into a price
The most important speed-to-lead evidence for a contractor in 2026 isn't academic. It's Google's own documentation for Local Services Ads. Google lists "your responsiveness to customer inquiries and requests" as a ranking factor, alongside your bid.3 It calculates your average message response time during your business hours over the last 90 days, weighted toward recent leads, and says a consistently fast response time could help your ranking and lead volume. Your average response time may appear in the ad itself.45
And a missed call during business hours where the caller waits more than 20 seconds is a charged lead.6 So a slow office pays twice: once for the lead it didn't answer, and again in rank. Our Local Services Ads guide covers the billing side.
How to measure speed to lead without fooling yourself
Most "average response time" numbers in field service software are flattering, because they measure the wrong event. Here's a definition you can hold the office to.
Speed to lead (per lead)
Each part needs a rule.
- "First real response" means a person, or an agent able to book, replied to the customer's actual request: a live answered call, a callback that connected, or a text that offers a time. An auto-acknowledgment ("Thanks, we got your request!") doesn't count. It's useful, but it's not a response.
- "Arrived" means when the lead hit your inbox, phone or form, not when someone first opened it. For email-forwarded leads from marketplaces, that includes mailbox delay.
- Clock time, not business hours. Report both if you like, but the homeowner's clock doesn't stop at 5 p.m. A lead that arrives at 6:10 p.m. and gets answered at 8:02 a.m. took 14 hours, not two minutes.
Then report it the way that shows the problem:
| Metric | Why it matters | Example target |
|---|---|---|
| Median time to first real response | The mean gets wrecked by a few overnight leads; the median shows the typical experience | Under 5 minutes during staffed hours |
| Share answered within 5 minutes | Matches the window where the 2007 study saw contact odds collapse | 80%+ during staffed hours |
| Share never answered | HBR found 23% of companies never responded; your number should be zero | 0% |
| All of the above by lead source | Forwarded marketplace emails are usually the slowest | Same targets for every source |
| All of the above by hour of day | Shows lunch, shift change and after-4 p.m. gaps | No hour worse than 2x the median |
| Booked rate by response bucket (under 5 min, 5 to 30, 30+) | Your own proof of the curve, from your own leads | Use it to set staffing |
The targets are our suggestions for a staffed office, not industry benchmarks. The last row is the most persuasive thing you'll ever show your CSR team: your own leads, sorted by how fast you answered, with the booking rate for each bucket.
In TradesWork, the lead inbox records time to the first reply that actually went out (not an internal note), shows a live timer on waiting leads, and puts median speed and booked rate by source for the last 30 days in the sidebar. Speed to lead is also one of the defined metrics in the reports.
What a slow reply costs: a worked model
All numbers below are hypothetical. The structure is what matters.
Say a shop gets 300 paid leads a month across LSA, marketplaces and its website, at an average cost of $45 per lead. Its average job is worth $380 in gross margin once it's booked and completed. Now compare three response profiles. The booking rates by bucket are assumptions you should replace with your own data from the table above.
| Response bucket | Booking rate (assumed) | Shop A: share of leads | Shop B: share of leads | Shop C: share of leads |
|---|---|---|---|---|
| Under 5 minutes | 60% | 20% | 55% | 85% |
| 5 to 30 minutes | 45% | 30% | 30% | 12% |
| 30 minutes to 4 hours | 30% | 30% | 10% | 3% |
| Over 4 hours or never | 12% | 20% | 5% | 0% |
| Blended booking rate | 36.9% | 50.1% | 57.3% |
Worked example: 300 leads x blended booking rate from the table. Booking rates by bucket are assumptions, not study results.
| Shop A (slow) | 111 |
|---|---|
| Shop B (decent) | 150 |
| Shop C (fast) | 172 |
Shop C books about 61 more jobs a month than Shop A from the same 300 leads and the same $13,500 in lead spend. At $380 of gross margin each, that's roughly $23,000 a month, or about $278,000 a year, and that's before Google starts rewarding Shop C's response time with better placement.
Monthly value of faster response
Put differently: Shop A's cost per booked job is $13,500 ÷ 111 = about $122. Shop C's is $13,500 ÷ 172 = about $78. Shop A would need to cut its lead price by more than a third, from $45 to about $29, just to match Shop C's cost per job. That's the sense in which the first five minutes beat your ad budget.
Free calculatorLabor rate & flat-rate price calculatorFind the hourly rate you need to charge to hit your profit goal, then price any job.Where the minutes go: the five usual leaks
When shops pull their response times by hour and source, the same gaps show up.
- 1
Lunch and shift change
The 12 to 1 and 4 to 5 windows are when CSRs are away and leads are still arriving. Stagger lunches and assign a named backup for each hour.
- 2
Email-forwarded marketplace leads
Leads that arrive as notification emails sit in a shared mailbox. Route them into the same queue as calls, with the same timer.
- 3
Web forms after 4 p.m.
Homeowners fill out forms after work. If nobody covers 4 to 8 p.m., those leads wait until morning and call someone else.
- 4
Saturday
Many offices run a skeleton crew or none. A two-hour Saturday shift answering leads often pays for itself in the first month.
- 5
Leads that need a decision
A CSR who can't quote a window waits for the dispatcher. Give CSRs the capacity view so they can offer a real arrival window on the spot.
The fifth leak is the one most offices underestimate. A fast reply that says "someone will call you back to schedule" isn't fast. The customer wants a time. That's why the definition above counts a text that offers a time, and not a text that promises a callback.
Your options for covering the first five minutes
Ways to get faster
- Staffed queue with a named owner per hour and the timer on screen
- Missed-call text-back so a missed caller gets a reply in seconds
- Shared lead queue: calls, texts, forms and marketplace emails in one place
- An AI text agent that offers real arrival windows, with hard limits
- An answering service or AI receptionist for after-hours calls
Trade-offs to know
- An extra hour of coverage or a Saturday shift is real payroll, so size it from your own lead data
- Text-back only helps if someone answers the reply
- One queue requires every source to flow in, including forwarded emails
- Automated texting needs consent and registered business texting
- After-hours coverage that can't book is a message service, not speed to lead
About automation, two honest notes. First, an automated text is still a text: it needs the customer's consent and a registered texting number, and it must stop on STOP. Our post on texting customers legally covers the rules. Second, the value of an automated reply depends entirely on whether it can offer a real time. In TradesWork, the optional lead text agent replies to new leads, offers arrival windows from the same capacity engine as the dispatch board, books only after the customer picks one, and hands emergencies, complaints and opt-outs to a person. It doesn't make phone calls. The AI receptionist for after-hours calls is in early access, so confirm it's switched on for your account before you rely on it at night. Our post on after-hours calls looks at what those calls are worth.
A speed-to-lead routine for the office
Daily and weekly
- Every lead source flows into one queue with a visible timer
- A named person owns the queue each hour, including lunch
- Auto-acknowledgments are on, but don't count as a response
- CSRs can see capacity and offer a real arrival window on first contact
- Missed calls get an immediate text-back and a callback within five minutes
- Daily: review every lead that waited more than 30 minutes, and why
- Weekly: median response, share under five minutes, and never-answered, by source and hour
- Monthly: booked rate by response bucket, from your own data
- Business hours listed on Google match the hours you actually answer
Measure for two weeks before you change anything. The numbers will tell you whether you need another person, a Saturday shift, or just a lunch schedule.
Footnotes
-
The Short Life of Online Sales Leads, James B. Oldroyd, Kristina McElheran and David Elkington, Harvard Business Review, March 2011. ↩ ↩2
-
Lead Response Management Study, James Oldroyd with InsideSales.com (vendor-sponsored), presented October 2007. ↩
-
About ad rankings, Local Services Help, Google, accessed October 2026. ↩
-
Manage leads and jobs, Local Services Help, Google, accessed October 2026. ↩
-
Improve your Local Services Ads performance, Local Services Help, Google, accessed October 2026. ↩
-
How leads work, Local Services Help, Google, accessed October 2026. ↩