What Is Speed to Lead? Definition, How to Calculate It, and Why Your CRM Gets It Wrong
Speed to lead is the time between a prospective B2B buyer raising their hand (submitting a web form, requesting a demo, calling, or starting a chat) and the first meaningful response from a person on your sales team. It is one of the simplest sales metrics to define and one of the easiest to measure badly. Faster is better, because buyer intent decays quickly and the first credible responder often sets the terms of the conversation.
This guide covers what speed to lead means for sales teams, what the research actually says, how to calculate it so the number is honest, and why the only reliable way to see your true speed to lead is to test it the way a buyer experiences it.
What is speed to lead, exactly?
At its simplest, speed to lead is a duration: response timestamp minus inquiry timestamp. The hard part is deciding which response counts. A useful definition has three parts:
- The start point is the moment the buyer acts: the form submit, the inbound call, the first chat message, the email to sales@.
- The end point is the first touch from a human who can move the deal forward. A confirmation email or an automated "thanks, someone will be in touch" does not count.
- The scope is per lead and per channel. A team can be fast on chat and slow on demo forms, and a single blended average hides that.
Some teams call this lead response time. The terms are used interchangeably. We cover the operational side in more detail in our guide to lead response time and how buyers experience it.
Why speed to lead matters: what the research says
The most cited research on the topic comes from a Harvard Business Review article, "The Short Life of Online Sales Leads" (Oldroyd, McElheran and Elkington, 2011). The authors audited 2,241 US companies by submitting a web lead to each and timing the response.
| Response to a submitted web lead (HBR audit of 2,241 US companies) | Share of companies |
|---|---|
| Responded within one hour | 37% |
| Responded within 1 to 24 hours | 16% |
| Took more than 24 hours | 24% |
| Never responded | 23% |
Among the companies that did respond within 30 days, the average response time was 42 hours. Nearly a quarter never replied at all.
The same article reported a companion analysis of 1.25 million leads. Firms that tried to contact a lead within an hour were nearly 7 times as likely to qualify it as firms that waited even an hour longer, and more than 60 times as likely as firms that waited 24 hours or more.
You will also see a "5 minutes" figure quoted often. It comes from the 2007 Lead Response Management study, which Oldroyd ran with InsideSales.com. It found the odds of qualifying a lead were 21 times greater when contact happened within 5 minutes rather than 30 minutes. It is useful directional evidence, but it is vendor data analyzed by an academic, not a peer-reviewed study, so treat it as a strong signal rather than a law.
The research points one way: the window to reach an interested buyer is measured in minutes and hours, not days. Most companies are slower than they think.
Why speed matters in a considered B2B sale
A buyer who fills out a demo request on a Tuesday morning is usually comparing options. They often submit to two or three vendors in the same sitting. The first vendor to call back gets the first conversation, gets to frame the evaluation criteria, and often gets the meeting booked before anyone else has replied. Slow vendors are not rejected, they are simply no longer in the room.
How to calculate speed to lead
The basic formula is:
Speed to lead = time of first qualifying human response minus time of buyer inquiry
Calculating it properly takes a few decisions up front. Get these wrong and the number will look good while buyers wait.
1. Decide what counts as a response
Count the first touch from a person: a live call that connects, a personal voicemail, or a written email or message that responds to what the buyer actually asked. Exclude autoresponders, generic nurture emails, and calendar links sent by a bot with no human follow-through. If your team uses an automated scheduling flow that books meetings well, track it, but track it as its own metric.
2. Choose clock time or business hours, and report both
Business-hours measurement pauses the clock overnight and on weekends. It is fair to reps, but it hides real buyer experience. A lead that arrives at 5:15 p.m. on Friday and gets a call at 9:30 a.m. Monday has a business-hours response of about 30 minutes and a clock-time response of more than 64 hours. The buyer only experiences the second number.
Report clock time as the headline, and business-hours time as a coaching metric. If after-hours leads are a meaningful share of volume, that is a staffing or routing decision, and it should be made with the real number in view.
3. Measure per channel
Web forms, demo requests, inbound phone, chat and direct email usually route through different systems and different people. Calculate speed to lead separately for each.
4. Use the median and the slow tail, not the average
Averages get distorted by a few very fast or very slow leads. Report the median, the 90th percentile, and the share of leads that never got a human response. The 90th percentile is where buyers are being lost.
| Channel | Start timestamp | End timestamp (first human touch) | Common trap |
|---|---|---|---|
| Web contact form | Form submit time | First personal call, voicemail or email | Counting the auto-confirmation email |
| Demo request | Form submit time | First call or personal email from a rep or SDR | Counting a self-serve calendar link as a response |
| Inbound phone | Call start | Live answer by a person who can help, or callback | Counting an IVR menu or general voicemail box |
| Website chat | First buyer message | First reply from a human | Counting the bot greeting |
| Email to sales inbox | Email received | Personal reply | Shared inbox nobody owns |
Speed to lead benchmarks: an honest view
There is no single industry benchmark you can trust for your market, and you should be skeptical of anyone who quotes one without a source. What the evidence supports is narrower:
- In the HBR audit, only 37% of companies responded to a web lead within an hour. Responding within an hour already put a company ahead of most of that sample.
- Contact within the first hour was strongly associated with higher qualification rates in the 1.25 million lead analysis.
- The 2007 vendor study suggests the first few minutes matter even more, with the caveat above.
A practical target for most B2B teams: a human response to high-intent inquiries (demo requests, pricing requests, inbound calls) within minutes during staffed hours, a defined plan for after-hours leads, and zero inquiries that go unanswered. Set your own targets by channel, then measure against them every month.
Why internal CRM timestamps mislead
Most teams pull speed to lead from their CRM or marketing automation platform. The report usually looks better than reality, for predictable reasons:
- Autoresponders log as activity. If the confirmation email or a sequence step is logged as a touch, response time looks like seconds.
- The clock starts late. Many systems timestamp lead creation after enrichment, deduplication or a routing queue, not at form submit. Delays upstream never show up.
- Activities get logged, not delivered. A rep can log a call that went to a dead number or an email that never arrived. The CRM records the intent, not the buyer's experience.
- Leads fall out of the funnel. Form submissions that fail validation, get routed to an unowned queue, or are flagged as duplicates may never become a record at all. They do not appear in the report as slow. They do not appear at all.
- Phone and chat are separate systems. Missed inbound calls and abandoned chats often never reach the CRM.
- Business-hours settings hide gaps. If the report pauses overnight, after-hours buyers look well served.
Your CRM tells you what your team logged. It does not tell you what a buyer saw, heard or waited for.
How a buyer-side test inquiry measures true speed to lead
The cleanest way to know your real speed to lead is to become the buyer. In a speed-to-lead audit, a trained evaluator poses as a realistic prospect, with a believable company, role, need, budget and timeline, and submits inquiries through your real channels. Every response is timestamped from the buyer's side.
A well-run test captures what internal data cannot:
- True start time. The evaluator records the exact submit time, call time or chat start.
- Every touch, in order. Automated emails, first human email, first call, voicemails, texts, and LinkedIn messages, each with a timestamp.
- Channel and time-of-day coverage. Inquiries are spread across channels, weekdays, evenings and weekends, so after-hours and routing gaps show up.
- Quality of the first response. Did the rep reference what the buyer asked? Did they propose a next step? A fast but generic reply is only half a win.
- Follow-up persistence. If the buyer goes quiet, how many attempts follow, and over how many days?
The output is a timeline per inquiry and a summary by channel. An example of what that looks like:
| Inquiry (illustrative example) | Submitted | First automated touch | First human touch | Clock-time speed to lead |
|---|---|---|---|---|
| Demo request, Tue morning | Tue 10:02 a.m. | 10:02 a.m. | Tue 10:41 a.m. (call) | 39 minutes |
| Contact form, Thu evening | Thu 7:48 p.m. | 7:48 p.m. | Fri 2:15 p.m. (email) | 18 hours 27 minutes |
| Inbound call, Mon midday | Mon 12:20 p.m. | None | General voicemail, no callback | No response |
| Chat, Wed afternoon | Wed 3:05 p.m. | Bot greeting | Wed 3:07 p.m. (human) | 2 minutes |
Run the same test again after you fix routing, staffing or rep habits, and you have before-and-after proof. Many teams fold this into a broader B2B sales mystery shopping program that follows the inquiry all the way through discovery, demo and proposal.
How to improve speed to lead
- Route instantly to a named owner. Every inquiry should land with a specific person, with a backup if they do not act within a set window.
- Remove upstream delays. Check how long enrichment, scoring and deduplication hold a lead before a rep sees it.
- Cover after-hours deliberately. Decide whether evening and weekend leads get a live response, a next-morning first call, or a scheduling option, then staff for it.
- Make the first touch personal. Reference what the buyer submitted and propose a specific next step.
- Measure from the buyer side. Test regularly with real inquiries so the metric reflects what buyers actually get.
Speed to lead is the first step. What happens after the first touch matters just as much. Our guide on how to follow up on sales leads covers the next 14 days.
Frequently asked questions
What is a good speed to lead?
There is no universal benchmark, but the research is clear on direction. In the HBR audit of 2,241 US companies, only 37% responded to a web lead within an hour. A practical target for high-intent inquiries such as demo and pricing requests is a human response within minutes during staffed hours, a defined plan for after-hours leads, and no inquiries left unanswered.
How do you calculate speed to lead?
Subtract the time the buyer submitted the inquiry from the time of the first response by a human who can move the deal forward. Exclude autoresponders. Calculate it per channel, report clock time as the headline and business hours as a coaching view, and track the median, the 90th percentile and the share of leads that never got a human response.
Is speed to lead the same as lead response time?
In practice, yes. Both describe the time from a buyer's inquiry to the first meaningful response from your team. Some teams use lead response time for the operational metric and speed to lead for the broader discipline of responding fast, but the measurement is the same. See our guide to lead response time.
Does an autoresponder count toward speed to lead?
No. An automated confirmation tells the buyer their form went through, but it does not answer their question or move them forward. Counting it makes response time look like seconds while the buyer is still waiting for a person. Track automated touches separately and measure speed to lead to the first human response.
Why does my CRM show faster response times than buyers experience?
CRMs often start the clock after routing or enrichment, log automated emails as activity, record attempted calls that never connected, and miss inquiries that failed to create a record. Phone and chat may live in other systems. A buyer-side speed-to-lead audit measures from the buyer's actual submit time.
See your process from the buyer's seat
We run buyer evaluations of B2B and considered-purchase sales teams. Tell us what you want to learn and we will scope a first round.
Book a scoping call