Speed to Lead: What the Research Says, What It Doesn't, and How to Get Under Five Minutes

Where the famous numbers come from

Two studies sit behind almost every speed-to-lead statistic, and they are routinely blended into one. They are different pieces of work.

The 2007 Lead Response Management study

Presented in October 2007 by Dave Elkington of InsideSales.com and Dr. James Oldroyd (then at MIT Sloan), this is the source of the "five minutes" figures. It reported that the odds of contacting a lead were roughly 100 times higher when the first attempt came within five minutes than after thirty, and the odds of qualifying the lead roughly 21 times higher. It is a vendor-produced dataset drawn from a small number of companies, and it was never published as a peer-reviewed paper.

The 2011 Harvard Business Review study

"The Short Life of Online Sales Leads" (Oldroyd, McElheran and Elkington, HBR, March 2011) is the better-documented one. It reports two separate findings:

• An audit of response times. The authors submitted a web inquiry to 2,241 US companies. Among those that replied within 30 days, the average response took 42 hours. Roughly a third responded within an hour, and a meaningful minority never responded at all.
• An analysis of 1.25 million sales leads across 29 B2C and 13 B2B companies. Firms that contacted a 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 24 hours or longer.

Note what the HBR article does not contain: the five-minute threshold and the 21x multiplier. Those belong to the 2007 work. When a blog post attributes "21x within five minutes" to Harvard Business Review, it has merged the two.

What the data does and doesn't prove

Treat the research as strong directional evidence with three honest limits.

• It is correlational. Companies that answer in minutes tend to be better organised in other ways: tighter routing, clearer ownership, more disciplined follow-up. Some of the lift attributed to speed is those habits. Speed is still worth buying, but expect less than the headline multiplier from speed alone.
• It is lead-type dependent. A demo request and an ebook download are not the same intent. The studies pool many lead types, so the steepest decay curve applies most to people who asked for something now.
• It is old and B2C-heavy. The HBR sample leans consumer, and buyer behaviour has shifted since 2011. Buyers now do most of their research before they raise a hand, which makes the moment they do raise it even more perishable.

The practical reading: the first hour is where the value concentrates, the first few minutes may be better still, and the next-day reply that the average company delivers leaves a lot on the table.

Where the hours actually go

Nobody sets out to take 42 hours. The delay accumulates across hand-offs, each one small enough to ignore. Trace a typical form-to-meeting path and the leaks are easy to find:

Step	Typical delay	What removes it
Form submitted, written to marketing automation	Seconds to minutes	Fine as is
Sync to CRM and lead creation	Minutes to hours (batch syncs)	Real-time webhook or native sync instead of a scheduled job
Lead assignment	Hours (manual triage or a queue nobody owns)	Rules-based routing with a named owner and a fallback
Rep notification	Hours (email notification in a full inbox)	Push to Slack or mobile with the lead context attached
First reply	Hours (rep batches follow-ups, researches the account first)	Pre-enriched account data, templates, or an AI first response
Finding a meeting time	Days (email back and forth)	Booking in the same session, with live calendar availability

The two biggest leaks in most teams are assignment and scheduling. Neither requires a rep to be faster. They require the system to stop waiting for a human to pick the lead up, and to stop negotiating times by email.

Not every lead deserves a five-minute SLA

A single response-time target applied to everything produces either an impossible standard or a meaningless one. Tier the commitment by intent:

Lead signal	Target first response	Why
Demo or contact-sales request	Under 5 minutes during coverage hours	Explicit request for contact; interest decays fastest
Chat started on pricing or comparison page	Immediate (live or AI)	The visitor is mid-evaluation and still on your site
Identified target account on a high-intent page	Within the visit if possible, otherwise within the hour	No request was made, but the moment is open
Content download or newsletter signup	Same business day	Early-stage research, nurture rather than chase

This is also where account-based routing earns its place: tier and page intent decide which row of this table a lead falls into before anyone has to read it.

The coverage problem nobody budgets for

A week has 168 hours. A team staffed Monday to Friday, nine to five, covers 40 of them, about 24%. B2B traffic skews towards working hours, so the real share of leads arriving uncovered is smaller than 76%, but it is rarely zero: different time zones, early starts, evenings when buyers research after their own workday. A leads-per-hour chart from your own forms and chat is the fastest way to size this for your site.

If a meaningful share of high-intent leads arrive when nobody is online, no amount of rep discipline fixes that. You need one of three things: follow-the-sun coverage, an on-call rotation for hot leads, or an automated first responder that can hold a real conversation and book a meeting without waiting for morning.

Three ways to get under five minutes

1. Human SLA with escalation

Assign every high-intent lead an owner at creation, alert them where they actually work, and escalate to a backup if nobody acknowledges within a few minutes. This works for modest volume during staffed hours. It fails at nights, on weekends, and whenever the assigned rep is in a meeting, which is why the escalation step is not optional.

2. Instant scheduling after the form

Replace the "thanks, we'll be in touch" page with a calendar. The prospect picks a time immediately, the meeting lands on the right rep's calendar, and the first-response problem disappears because the response is the booking. The weakness is that it only helps people who finish the form, and routing needs the qualification data to exist before the calendar loads.

3. Conversation before the form

Engage the visitor while they are still on the page. A chat agent, human or AI, can answer the question that made them hesitate, ask the qualifying questions, and offer a time slot in the same exchange. This is the only approach that reaches the large majority of high-intent visitors who never fill out a form. It is also the one that needs the most care: a bot that wastes the visitor's time is worse than a slow human. See our guides to AI lead qualification and meeting booking automation for how to scope it so reps trust it.

Measure it properly or the number will lie to you

• Measure the first human or substantive response. An auto-reply email is not a response. Counting it makes the metric look excellent while the prospect still waits a day.
• Report the median and the 90th percentile. The average hides the lead that waited two days. Your tail is what loses deals.
• Split by lead type and by hour of arrival. A healthy overall number can sit on top of an after-hours cliff.
• Track time to meeting, not just time to reply. A fast reply that starts a three-day scheduling thread has not solved the problem.
• Pair speed with an outcome metric. Meetings held and opportunities created per hundred leads tell you whether going faster is helping or just creating noise.

Common mistakes

• Speed without relevance. A fast, generic reply that ignores what the prospect asked is slower in practice than a slightly later, specific one. The goal is time to useful response.
• Routing to an unavailable rep. The assigned owner is on holiday, in a meeting, or off shift, and the lead sits. Always route with an availability check and a fallback.
• Phoning people who wanted a calendar link. Some prospects want to self-schedule. Offering the booking option in the first reply respects that and removes a round trip.
• Treating speed as a rep problem. Most delay is structural: sync lag, unowned queues, scheduling threads. Coaching reps to type faster does not move the median.

How QualifyLoop approaches it

QualifyLoop attacks the three biggest leaks together. Routing playbooks decide on tier, page and campaign whether a conversation goes to a human or to the AI agent at the moment a visitor engages, with no lead queue to triage. The agent qualifies the visitor and, when they are ready, checks the connected calendar and books a real meeting inside the chat. The contact syncs to HubSpot or Salesforce and the full transcript is in the rep console, so the rep who takes the meeting is not starting cold.

Sources

• Oldroyd, McElheran and Elkington, "The Short Life of Online Sales Leads", Harvard Business Review, March 2011.
• InsideSales.com and Dr. James Oldroyd, Lead Response Management study, presented at the MarketingSherpa B2B Demand Generation Summit, October 2007. Vendor-produced data; cited here for the five-minute figures only.

Frequently asked questions

What is speed to lead?

Speed to lead is the elapsed time between a prospect expressing interest, such as submitting a demo request or starting a chat, and your first meaningful response. Teams usually track it as time to first human touch and time to first conversation, measured in minutes for high-intent leads.

Is the five-minute response rule backed by research?

Partly. A 2007 Lead Response Management study by InsideSales.com and Dr. James Oldroyd reported far higher contact and qualification odds when the first attempt came within five minutes versus thirty. A separate 2011 Harvard Business Review study of 1.25 million leads found firms that responded within an hour were nearly seven times as likely to qualify a lead as firms that waited one more hour. Both are correlational and the first used vendor data.

How fast should B2B teams respond to inbound leads?

For high-intent requests such as demos and pricing inquiries, aim for minutes, and treat one hour as a hard ceiling. Lower-intent leads like content downloads can tolerate a longer window. Define response targets per lead type instead of one number for everything.