Metrics
Speed to Lead
Speed to lead is the elapsed time between a prospect raising their hand and a sales rep making first contact, measured in minutes because buyer attention decays fast.
Speed to lead is the elapsed time between the moment a prospect raises their hand — a demo request, a pricing form, a content download — and the moment a rep makes the first genuine contact attempt. It is counted in minutes, not days. The number matters because buyer intent is perishable: the MIT Lead Response Management study found that reps who reached a web lead within five minutes were 21 times more likely to enter a real sales conversation than reps who waited thirty. Most inbound teams average over 40 hours.
How Speed to Lead Is Calculated
Subtract the lead-creation timestamp from the first-touch timestamp:
Speed to Lead = First Contact Attempt Timestamp − Lead Creation Timestamp
The honest version measures from when the lead became routable to when a human dialed, emailed, or texted — not when an automated confirmation fired. Mature teams compute it two ways: raw clock time and business-hours-adjusted time, so a lead that arrives at 11 p.m. Friday isn't scored against a Saturday-morning callback. Median is more useful than mean here; a single lead contacted three weeks late drags the average into nonsense while the median tells you what a normal prospect actually experiences.
Worked Example: Four Minutes Versus Four Hours
Two SDRs work the same inbound queue. One owns a routing rule that pings their phone; the other checks a shared list between cold-call blocks.
| Rep | Lead created | First dial | Speed to lead | Connect rate |
|---|---|---|---|---|
| A | 9:00:00 | 9:04:30 | 4.5 min | 38% |
| B | 9:00:00 | 13:10:00 | 4 hr 10 min | 9% |
Same leads, same script, same product. Rep A connects on better than one in three because the buyer is still on the pricing page. Rep B inherits a cold prospect who has already booked two competitor demos. The four-hour gap isn't a coaching problem — it's a routing and staffing problem wearing a coaching costume.
When Sales Teams Use Speed to Lead
RevOps owns the metric because it sits at the seam between marketing and sales, exactly where leads go to die. Demand-gen leaders watch it to prove their MQLs aren't rotting in a queue after a six-figure ad spend. SDR managers use it to justify round-robin routing, lead-routing software, and after-hours coverage. Founders quote it to investors as evidence the funnel converts intent into pipeline rather than letting it cool. A five-minute median on high-intent inbound is the practical ceiling worth chasing; past an hour, the sales-accepted-lead rate falls off a cliff and no cadence recovers it.
Common Speed to Lead Gaming Patterns
The clock invites cheating the second it becomes an SLA. The most common dodge is the auto-touch: an automated email or SMS fires the instant a form is submitted, the system logs "first contact," and the timer stops at zero seconds while no human has done anything. The dashboard glows green; the prospect hears nothing real. Reps run the manual version too — logging a one-second "called, no answer" task to satisfy the SLA, then never dialing again, which produces gorgeous speed-to-lead numbers and a dead pipeline.
Watch for definition-shifting, where teams quietly move the start clock from lead creation to lead assignment, hiding hours of routing lag. And speed without quality is its own trap: a fast, scripted, irrelevant touch closes the SLA but burns the lead. The metric tells you how fast someone reacted. It says nothing about whether the reaction was worth receiving.
Related terms
Ready to see your numbers?
Get your verified Alpha Score. Read-only CRM, score within minutes.
Get my Alpha Score