Speed to Lead: Definition, Statistics and How to Improve It

Speed to lead is the time between a buyer raising their hand and your team giving them a meaningful response. Here is the position I will defend in this guide: most B2B teams do not have a speed to lead problem during business hours. They have a coverage problem. The lead that waits is the one that arrives at 7pm, on a Saturday, or from a time zone your team does not staff, and no amount of rep discipline fixes that.

Below you will find a clear definition, a way to measure speed to lead that survives scrutiny, the research behind the "respond in five minutes" advice (with what those studies actually measured), and the process and tooling fixes that close the gap.

What is speed to lead?

Speed to lead is the elapsed time from the moment a prospect submits an inbound signal (a demo request form, a chat message, a meeting request, a trial signup) to the moment they receive their first meaningful response from your company. It is also called lead response time.

Two words in that definition do most of the work:

• Inbound signal. The clock starts when the buyer acts, not when the lead lands in a rep's queue. If your CRM syncs every hour, your speed to lead includes that hour.
• Meaningful. An autoresponder that says "thanks, someone will be in touch" is an acknowledgement, not a response. A meaningful response answers the buyer's question, moves them to a next step, or books time with the right person.

The term is used across industries (real estate, insurance, recruiting, home services), but this guide focuses on B2B software, where the inbound signal is usually a demo request, a pricing question, or a chat on your website. If you came here looking for lead response time, it is the same metric under another name, and the lead response time section below covers what slow response costs and how to diagnose where the delay comes from.

Why speed to lead matters

A buyer who fills out your demo form is at their peak of attention. They have your tab open, they have a problem in mind, and they have usually opened a competitor's tab too. Every hour that passes, their attention drifts back to the rest of their day.

The mechanics are simple:

• Intent decays. The question that made them reach out ("does this integrate with our CRM?", "what does it cost for a team of 20?") is most urgent right now. Answer it later and it may no longer be the question they care about.
• Contactability decays. Right after submitting, the buyer is at their desk and expecting a reply. Hours later they are in meetings, and your call goes to voicemail.
• First useful answer frames the evaluation. The vendor who answers first gets to set the criteria the buyer uses to compare everyone else.

This is not just intuition. Two well known studies put numbers on it, and it is worth reading them carefully.

Speed to lead statistics: what the research actually says

Most speed to lead statistics you see online trace back to two pieces of research led by James Oldroyd. Many blog posts repeat their numbers loosely or blend them together. Here is what each study found, quoted from the source.

1. HBR: "The Short Life of Online Sales Leads" (2011)

Published in Harvard Business Review in March 2011 by James B. Oldroyd, Kristina McElheran and David Elkington. The authors ran two pieces of research.

How fast companies respond. They "audited 2,241 U.S. companies, measuring how long each took to respond to a web-generated test lead." The results:

"The average response time, among companies that responded within 30 days, was 42 hours."

How fast leads go cold. In a separate study of "1.25 million sales leads received by 29 B2C and 13 B2B companies in the U.S.," firms that tried to contact potential customers within an hour of receiving a query "were nearly seven times as likely to qualify the lead (which we defined as having a meaningful conversation with a key decision maker) as those that tried to contact the customer even an hour later, and more than 60 times as likely as companies that waited 24 hours or longer."

The authors also named the causes, and they are still the causes today: "retrieving leads from CRM systems' databases daily rather than continuously; sales forces focused on generating their own leads rather than reacting quickly to customer-driven signs of interest; and rules for distributing sales leads among agents and partners based on geography and 'fairness.'"

2. The Lead Response Management Study (InsideSales.com and MIT, 2007)

This is the source of the "five minute rule." Dr. James Oldroyd, then a Faculty Fellow at MIT's Sloan School of Management, worked with InsideSales.com to analyze three years of data across six companies: over fifteen thousand web leads and over one hundred thousand call attempts. The study looked at leads captured through a web form and called at least once. Its headline findings, quoted from the study summary:

• "The odds of contacting a lead if called in 5 minutes versus 30 minutes drop 100 times. The odds of qualifying a lead if called in 5 minutes versus 30 minutes drop 21 times."
• "The odds of calling to contact a lead decrease by over 10 times in the 1st hour. The odds of calling to qualify a lead decrease by over 6 times in the 1st hour."
• "After 20 hours every additional dial your salespeople make actually hurts your ability to make contact to qualify a lead."

How to read these numbers honestly

Three honest takeaways. First, these studies are observational, so part of the effect may come from better-run teams being faster rather than speed alone. Second, they measure contact and qualification, not revenue. Third, they are old and phone-centric. But the direction is consistent across both studies: the first hour matters far more than the rest of the day, and the first few minutes matter most of all.

Lead response time: what it costs when it is ignored

Lead response time is the name most sales and RevOps teams use for this metric: the gap between a lead's inquiry and your first meaningful response. The research above explains why it matters. What it does not show is how common slow response still is, or what happens to a lead while it waits.

The problem has not gone away since the HBR audit. In March 2024, RevenueHero submitted demo requests to 1,000 B2B SaaS companies and found that 635 of them, 63.5%, never responded; among those that did, the average response time was 1 day, 5 hours and 17 minutes (RevenueHero, 2024). That is one vendor's test of one form type, so read it as directional, but it points the same way as the 2011 audit: a large share of inbound demand still gets no answer at all.

Slow response compounds rather than costing you a single metric. A buyer who submits a form at 9am and hears nothing until the next morning has spent a day in a different mental state:

• Lost momentum. They move from evaluating your product to comparing alternatives, and may already have calls booked with competitors.
• Eroded trust. A two-day wait before the sale raises a fair question about how responsive you will be after it.
• Harder conversations. The rep who finally calls inherits a colder, more skeptical prospect instead of an engaged one.
• Wasted acquisition spend. Every inbound lead was paid for with media, content, or events. A lead nobody answers turns that spend into waste before it has a chance to become pipeline.

The fix for each of those is the same: answer faster and more usefully, which starts with measuring the metric properly.

How to measure speed to lead

You cannot improve a number you are measuring wrong, and most teams measure speed to lead wrong. Here is a definition you can defend in a pipeline review.

Speed to lead = time of first meaningful response minus time of inbound signal.

Define the start and stop events

• Start: the timestamp the buyer submitted the form, sent the first chat message, or requested a meeting. Use the form or chat tool's own timestamp, not the CRM record creation time.
• Stop: the first two-way touch that is useful to the buyer: a live conversation, an answered question, or a confirmed meeting. Exclude automated acknowledgements and generic nurture emails.

Report the median and the tail, not the average

An average hides the problem. One lead answered in two minutes and one answered in three days averages to a day and a half, which describes neither. Report:

• Median response time (the typical experience)
• 90th percentile response time (the leads you are losing)
• Coverage rate: the share of leads that received a meaningful response within your target window
• No-response rate: the share of leads that never got a meaningful response

Segment before you conclude anything

Split every number by business hours vs after hours (in the buyer's time zone, not just yours), by source (demo form, pricing page, chat, trial signup), and by owner or team. This is usually where the story changes. A team with a strong daytime median can have a terrible overall number because a large share of leads arrive when nobody is working.

Split processing time from rep response time

Most tools report one total, which hides where the delay lives. Measure lead processing time (enrichment, matching and routing, from signal to the lead reaching an owner) separately from rep response time (from the owner being notified to the first meaningful touch). They need completely different fixes: if processing is the bottleneck, coaching reps to move faster accomplishes nothing.

Then use SLA breaches as a diagnostic. Set a target per lead type and look at where breaches cluster:

• Breaches at the routing stage point to gaps in routing logic or batch syncs.
• Breaches at the rep stage point to workload distribution or notification design.
• Breaches you cannot attribute to either usually mean the two stages are not being timestamped separately yet.

An illustrative example

The numbers below are hypothetical, for illustration only. Imagine a team that receives 300 demo requests a month. During business hours, reps respond in a median of 8 minutes. That sounds excellent. But 120 of those requests arrive in the evening, on weekends, or from time zones the team does not cover, and those wait until the next working morning, a median of 14 hours. Blended, the team's p90 is measured in hours, not minutes, and 40% of its inbound demand is getting the slow experience. The daytime process is fine. The coverage is not.

The after-hours and time zone gap

This is where most B2B speed to lead is lost, and it is a structural problem rather than an effort problem.

Buyers research on their own schedule. In Storylane's own analysis of 8,211 AI sales agent conversations across 19 RepX deployments (June 2025 to August 2026), 64.5% of buyer questions, and 63.2% of whole conversations, arrived outside Monday to Friday, 09:00 to 18:00 in the seller's own time zone. A separate analysis of 1,332 RepX conversations across five B2B software vendors, measured in the buyer's local time, found 51.4% started outside weekday business hours, and those conversations were no less qualified. Both are first-party datasets from companies that deploy an AI agent, so treat them as directional for your own site rather than universal, and check your own timestamps.

Put that next to the research above and the implication is uncomfortable. If a large share of your inbound arrives when nobody is available, then for that share your speed to lead is not five minutes or even an hour. It is "next business morning," which in the HBR data sits in the bucket where qualification odds have already collapsed.

You have three ways to close the gap:

1. Staff it: follow-the-sun SDR coverage or an outsourced overnight team. Effective, expensive, and hard to justify below a certain lead volume.
2. Defer it gracefully: let buyers self-schedule a meeting instantly, so at least the next step is locked in while intent is high.
3. Answer it automatically: put an AI agent on the website that can answer the question, qualify the buyer and book the meeting at any hour.

What is a good speed to lead?

There is no single correct number, because the right target depends on intent. Based on the research above, here is the framework I recommend. These are targets, not benchmarks: set your own from your baseline.

The first row is the one that matters. A demo request is an explicit request to talk. Treat it like an inbound phone call, not an email to get to later.

How to improve speed to lead: process fixes

Start with process. Tooling on top of a broken process just makes the broken process faster.

1. Route instantly, not on a schedule

The HBR authors named batch retrieval of leads from the CRM as a core cause of slow response. Route every hand-raiser the moment it is created, straight to an owner, with a notification in the channel the rep actually watches. Our guide to lead routing covers the rules in detail.

2. Replace "fair" round robin with "available" round robin

Distributing leads for fairness, regardless of whether the rep is free, was the other cause the HBR authors named. Route to whoever is available now, and reassign automatically if the lead is not touched within your target window.

3. Give inbound a protected owner

Reps who also prospect will always have something more urgent than an inbound form. A dedicated inbound owner per shift, or a clear rotation, removes the ambiguity.

4. Make the first response useful

Speed without substance does not help. Use what you know (the page they converted on, their company, the question they typed) to make the first reply specific. If they asked about an integration, answer it. Our lead follow-up guide has timing and message templates for what comes after the first touch.

5. Stop dialing a dead lead

The MIT study found that after 20 hours, additional dials hurt the ability to make contact and qualify. Past that point, switch channels (email, a short video, a demo link) instead of calling again.

6. Put speed to lead on the dashboard

Review median, p90, coverage rate and after-hours coverage weekly, by source and owner. What gets reviewed gets fixed.

Speed to lead software: tooling fixes

Speed to lead software is not a single category. It is a set of tools that each remove one delay from the path. Pick them based on where your time is actually lost.

Speed to lead automation: what to automate and what not to

Automate the parts that are pure delay: routing, notifications, meeting booking, reassignment when an SLA is missed, and answers to common questions. Keep humans on the parts that need judgment: complex deals, negotiation, and anything where the buyer has asked for a person. The goal of automation is not to remove your reps from inbound. It is to make sure no buyer is left waiting while a rep is unavailable.

Why the response has to be meaningful, not just fast

A two-minute autoresponder does not count, and buyers can tell. The HBR researchers defined a qualified lead as "a meaningful conversation with a key decision maker," not a reply. The best first response does one of three things: answers the question the buyer came with, shows them the part of the product they care about, or books time with the right person.

Showing the product is often the fastest way to be useful. An interactive demo lets a buyer explore the workflow they asked about immediately, instead of waiting for a scheduled call. Here is an example:

Engagement data from a demo also tells the rep which features the buyer explored, which makes the human follow-up more specific.

Where RepX fits (full disclosure)

We build Storylane, so weigh this section accordingly.

RepX is an AI agent that sits on your website and responds to buyers the moment they engage, at any hour. It addresses the part of speed to lead that process alone cannot fix: the after-hours and time zone gap. Based on what RepX does today:

• Instant response, around the clock. RepX engages, qualifies and converts inbound buyers in real time, so the buyer who arrives at 10pm gets an answer at 10pm.
• Answers with the product. It is trained on your website, docs, decks, call scripts and interactive demos, and can pull up the relevant demo during the conversation.
• Qualifies on your criteria. You define your ICP in plain English and RepX runs discovery (pain points, current setup, timeline) through conversation rather than a form.
• Books meetings. When the buyer is ready, RepX pushes them to book a meeting, and qualified leads and conversation summaries flow to HubSpot, Salesforce and Slack.
• Text, voice or video. Buyers can type, listen or talk face to face.

Where it does not fit: if your inbound volume is low and all of it arrives during staffed hours, a disciplined routing process and a fast human team may be all you need. RepX is most useful when a meaningful share of your inbound lands when nobody is available, or when buyers want answers before they will book a call. For the operating model, see our playbook on real-time lead qualification.

Common speed to lead mistakes

• Counting the autoresponder. It makes the metric look great and changes nothing for the buyer.
• Measuring only business hours. This hides exactly the leads you are losing.
• Reporting the average. Use median and p90.
• Starting the clock at CRM creation. Sync delays are part of the buyer's wait.
• Treating every lead the same. A demo request and an ebook download need different responses and different targets.
• Buying tools before fixing routing. A chatbot that hands off to a queue nobody watches is still slow.

The bottom line

Speed to lead is one of the few sales metrics where the research, the buyer's experience, and common sense all point the same way: respond within minutes, and make the response useful. Most teams can hit that during the day with better routing and clear ownership. The real gains come from covering the hours when your team is offline, because that is when a large share of B2B buyers are doing their research.

If you want to see how an AI agent handles your after-hours inbound, book a demo of Storylane RepX.

FAQ

What is speed to lead?

Speed to lead is the time between a prospect submitting an inbound signal (a demo request, chat message, meeting request or signup) and receiving their first meaningful response from your company. It is also called lead response time.

What is a good speed to lead?

For hand-raisers such as demo requests and pricing questions, aim for a meaningful response in under five minutes, at any hour. The InsideSales.com and MIT study found the odds of contacting a lead drop 100 times when called at 30 minutes instead of 5, and HBR research found firms that attempted contact within an hour were nearly seven times as likely to qualify the lead as those that waited even an hour longer.

Is lead response time the same as speed to lead?

Yes. Lead response time and speed to lead describe the same metric: the time from a lead's inbound signal (a form, chat or meeting request) to the first meaningful response. Measure it with the median and 90th percentile rather than the average, and split lead processing time (routing and enrichment) from rep response time so you know which part of the delay to fix.

How do you calculate speed to lead?

Subtract the timestamp of the inbound signal (form submission, first chat message or meeting request) from the timestamp of the first meaningful response. Report the median and 90th percentile, split by business hours vs after hours and by lead source, and exclude automated acknowledgements.

What are the most cited speed to lead statistics?

The two most cited sources are HBR's "The Short Life of Online Sales Leads" (2011), which found 23% of 2,241 audited U.S. companies never responded to a web lead and the average response time was 42 hours among those that responded within 30 days, and the InsideSales.com and MIT Lead Response Management Study (2007), the origin of the five minute rule.

What is the average lead response time?

In HBR's audit of 2,241 U.S. companies, the average response time among companies that responded within 30 days was 42 hours, and 23% never responded. A March 2024 RevenueHero test of 1,000 B2B SaaS companies found 63.5% never answered a demo request, and the average among those that did was 1 day, 5 hours and 17 minutes.

What is speed to lead software?

Speed to lead software is any tool that removes delay between an inbound signal and a meaningful response: CRM alerts and workflows, lead routing and scheduling tools, live chat, and AI website agents that answer, qualify and book meetings instantly, including outside business hours.

Can speed to lead be fully automated?

The delays can be: routing, alerts, meeting booking and answers to common questions can all happen instantly. The judgment should not be. The best setup automates the first response and hands qualified buyers to a human with full context.

Sources

• James B. Oldroyd, Kristina McElheran and David Elkington, "The Short Life of Online Sales Leads," Harvard Business Review, March 2011.
• Dave Elkington and James Oldroyd, "Lead Response Management Study," InsideSales.com and MIT, presented at MarketingSherpa's B2B Demand Generation Summit, October 16, 2007.
• Storylane, "Sales agents vs human reps: 2 in 3 buyer questions arrive when your sales team isn't around," August 2026 (first-party data).
• Storylane, "5 learnings from 1,332 RepX conversations," September 2026 (first-party data).
• RevenueHero, "B2B lead response times," March 2024 study of 1,000 B2B SaaS companies.