Speed to Lead Statistics: What the Studies Show
Speed to lead is the time between a new inbound lead arriving and the first real reply from your team. The research that every speed to lead statistic comes back to is older and narrower than most blogs admit, but it points one way: replies within minutes reach and qualify far more leads than replies hours later, and most companies tested still answer in hours, or never.
This post traces each figure to the study that produced it, says who measured what and when, and leaves out the numbers we couldn't trace. It's written for sales and marketing leads who want to set a response target their team can defend.
What is speed to lead?
Speed to lead, also called lead response time, measures how quickly a new lead gets a response from a person who can help. The clock starts when the lead arrives: a demo request, a contact form, a trial sign-up, or a chat. It stops at the first real reply, meaning a call or a written answer to what they asked, not an automatic "thanks, we'll be in touch".
It matters because an inbound lead is someone who has chosen to talk to you, right now. An hour later they may be in a meeting, on a competitor's site, or simply less interested.
Speed to lead statistics worth trusting
Four sources hold up when you trace them back. Each measures something different, so read them for direction rather than as one combined number.
The Lead Response Management study (2007): minutes matter
The most quoted speed to lead statistics come from a study by Dave Elkington of InsideSales.com and Dr James Oldroyd, then at MIT's Sloan School of Management, presented at a MarketingSherpa B2B summit on 16 October 2007. A copy of the original study write-up is still online.
- What it measured: three years of call data from six companies that generate and respond to web leads, covering more than 15,000 leads and more than 100,000 call attempts. It asked when to call a web lead for the best chance of reaching and qualifying it. It didn't look at closed deals.
- What it found: the odds of contacting a lead called within 5 minutes were 100 times higher than for one called at 30 minutes, and the odds of qualifying it were 21 times higher. Even between 5 and 10 minutes, the odds of contact fell by a factor of 5. After about 20 hours, more call attempts made contact less likely, not more.
- How to read it: the study is almost 20 years old, measured phone calls only, and used data from six companies on InsideSales.com's own system, which it doesn't name. The write-up says InsideSales.com's customers at the time were concentrated in mortgage and insurance. "Odds" in these figures aren't the same as "chances": a 100-fold change in odds is large, but it doesn't mean one in a hundred fast calls connects. And it shows an association in that data, not proof that speed alone caused the difference. It's still the most detailed public look at how quickly a lead cools.
Drift's lead response survey (2017): most B2B teams were slow
In February 2017, Drift had a secret shopper fill in lead, demo, and sales enquiry forms at 433 B2B software companies. Drift's write-up of the survey, now on Salesloft's site since the two companies combined in 2024, reported:
- 7% of the companies responded within five minutes.
- 55% didn't respond at all within five business days.
It's a test of software companies, with one enquiry each, so it says more about how common slow replies were than about any one company's performance.
Chili Piper's vendor response test (2022): fast replies were still rare
In February 2022, Chili Piper, which sells scheduling and routing software, published a test of B2B software vendors in which its team requested demos through vendors' forms and chat. It counted "instant" as under 60 seconds and "no response" as nothing within seven business days.
- 7% of companies responded instantly.
- About 55% took longer than an hour, and nearly 30% never responded.
- Among those that did respond, the average wait was 4 hours 50 minutes.
The article doesn't state the total number of companies tested, and the vendor sells a product that answers this problem, so treat it as a sample, not a benchmark.
Workato's demo request test: under five minutes almost never happened
Workato's team requested demos from 114 B2B companies of different sizes, industries, and regions. As the page reads in November 2026:
- Only 1 of the 114 sent a personalised email within five minutes.
- The average email reply took 11 hours 54 minutes, and nearly one in five never replied by email.
- Companies without a lead routing tool averaged nearly 13 hours; those with one averaged about 3 and a half hours.
Like the others, it's a small test run by a vendor, Workato sells automation software, and the routing comparison is a correlation, not a controlled experiment.
Figures we left out
You'll see other speed to lead statistics quoted widely. We left them out where we couldn't check them against the original:
- A 2011 Harvard Business Review article, "The Short Life of Online Sales Leads" by James Oldroyd, Kristina McElheran, and David Elkington, audited US companies' responses to web leads. Its figures are quoted everywhere, but the article itself is behind HBR's paywall, and the public page gives only its conclusion: that most companies weren't responding nearly fast enough. We haven't repeated its numbers because we couldn't read them in the original.
- "Most buyers choose the first company to respond." Several versions of this circulate with different percentages and sources. We couldn't trace one to a published study with a method, so it isn't here.
- Later reports from the same vendors, where the original pages have moved or gone and the figures now live only on other companies' blogs.
Lead response time: what to measure in your own team
The studies above tell you speed matters. They can't tell you your own number, and that's the one worth knowing. To measure it:
- Define the start. The time the lead was created in your CRM, from a form, chat, or demo request.
- Define the stop. The first logged call, email, or meeting booked by a person, not an automated acknowledgement.
- Measure the median and the slowest 10%. An average hides the leads that waited overnight. The median shows a typical lead; the slow tail shows the ones you're losing.
- Split by hour and day. Leads that arrive at 5:30pm on a Friday are the usual problem, and a weekday-hours average won't show them.
- Count leads that never got a reply. In the tests above, that was often the largest group.
Then set a target your team can meet in business hours, check it weekly, and look at every miss. A target is a promise you make to yourselves, not a guarantee to anyone else: some leads will always arrive at awkward times.
How to answer leads faster
Speed usually comes from the setup, not from people working harder:
- Route every lead to an owner at once, by territory, product, or round robin, so nobody has to decide who picks it up.
- Alert the owner where they work, in Slack or on their phone, not only in a CRM inbox.
- Prepare the first reply. Approved templates for common requests let a rep answer well in a minute.
- Cover the gaps. Decide who answers at lunch, at 5pm, and when the owner is away.
- Offer a booking link in the first reply, so a lead can choose a time without waiting for a second email.
Once leads are answered quickly, the next question is which ones deserve a sales call. Our guide to lead qualification covers that, and our look at the AI SDR covers what automated reply tools can and can't do.
Where Webika fits
Our HubSpot sales setup and speed to lead service puts routing, alerts, sequences, and response time reporting in place in your HubSpot, as a fixed-price project. If your team can't reply in time, our people can answer new leads in your business hours, against a response target we agree with you and report every week. It's a target, never a guarantee. Our founder also built SealRevenue, a HubSpot app that alerts your team when a lead waits too long; it's the founder's own product, sold separately on its own site.
Book a free call to find out how long your leads wait today.