TL; DR
The five-minute number is repeated on nearly every page about lead response and measured almost nowhere. Teams quote it in QBRs, set SLAs against it, and never check where it came from. It is worth checking, because the figure most often attributed to Harvard Business Review is not HBR’s, and HBR’s own number is both smaller and more useful.
What is speed to lead?
Speed to lead is the elapsed time between an inbound lead arriving and a qualified human or agent response reaching that lead. It is measured from the moment the lead is created, not from the moment it is assigned, and an automated acknowledgement does not stop the clock. Lead response time is the same measurement expressed from the marketing side.
The clock definition is where most reporting quietly breaks. A team that starts counting at assignment is measuring rep diligence. A team that counts an auto-reply as a response is measuring nothing at all. Neither number can be compared to anyone else’s, and neither tells you whether the buyer got what they asked for.
What the response-time research actually says
The credible figure is 7x. In The Short Life of Online Sales Leads (Harvard Business Review, 2011), Oldroyd, McElheran and Elkington found that firms attempting contact within an hour of a query were nearly seven times as likely to qualify the lead as those trying an hour later, and more than sixty times as likely as those waiting twenty-four hours or longer.
Two things make that figure usable where the popular one is not.
The methodology is stated. The researchers audited 2,241 US companies by submitting test web enquiries. A separate related study covered 1.25 million sales leads across 29 B2C and 13 B2B firms in the US.
“Qualify” is defined precisely. The authors mean having a meaningful conversation with a key decision maker. That definition is what makes 7x meaningful, and it is exactly what gets stripped out when the figure is recycled. A response that reaches a voicemail is not a qualification.
The same study found that among companies responding within thirty days, the average response time was 42 hours. That figure is from a 2011 audit and should be read as such rather than as a current benchmark.
The five-minute rule is not HBR, and it is not neutral
The claim that responding within five minutes makes you 100 times more likely to connect and 21 times more likely to qualify is routinely attributed to Harvard Business Review. It is not HBR’s number.
It comes from the 2007 Lead Response Management study, conducted by Dr. James Oldroyd in partnership with InsideSales.com, a company that sold sales engagement software. The two studies share a lead author, which is why they have been welded together in retelling, but they are four years apart, use different samples and measure different things.
A reader deserves to know that the study producing the most-quoted number in the category was co-run with a vendor selling the remedy. That is a conflict, not a disqualification, but it changes how much weight the number carries.
Seven, not one hundred. The more conservative result from the larger and more neutral study is the number to plan around.
How to measure speed to lead accurately
Measure from lead creation to first genuine contact. Everything else is a variation that makes your number look better and your reporting useless.
The auto-reply exclusion is the one that provokes argument. It should not. An acknowledgement tells the buyer their form worked. It does not answer their question, and counting it as a response converts an honest metric into a comfortable one.
What a good lead response time looks like by motion
There is no single correct target. A high-velocity self-serve sign-up and a seven-figure considered purchase have different tolerances, and applying one SLA to both guarantees you fail one of them.
The enterprise row is the one teams get wrong in both directions. Some apply a five-minute SLA and send a sequence to a CIO who filled in a whitepaper form. Others treat the long cycle as licence to answer on Thursday. Neither is right. The rule is that the response should arrive within the buyer’s working day and should demonstrate that someone read what they asked.
Why teams miss the target: the coverage arithmetic
Teams miss response targets because they are structurally absent for most of the week, not because reps are slow. This is arithmetic you can rerun with your own inputs, and the assumptions are stated so you can.
A week contains 168 hours.
A team covering 09:00 to 17:00, Monday to Friday, in one time zone is available for 40 hours, which is 23.8% of the week.
Therefore roughly 76% of the week is uncovered, before holiday, sickness, meetings, lunch breaks or queue depth are considered.
These are illustrative assumptions. Substitute your own working hours, time zones and headcount and the shape holds even when the percentage moves. A second time zone improves it. It does not close it.
This is arithmetic from stated assumptions, not a benchmark, not an industry average and not a fifth performance figure. That is precisely why it is worth showing.
What makes it worse than the raw number
Six causes account for most slow responses:
Holiday and handover compound the first. Queue depth compounds all of them, because a backlog built overnight is worked in arrival order while new leads keep landing behind it.
Now put the buyer in the picture. Gartner finds that 75% of B2B buyers prefer a rep-free sales experience, and in a Gartner survey of 148 respondents involved in technology purchase decisions, 64% preferred a fully digital buying experience when already familiar with the product, driven by speed, convenience and a preference for self-research. A buyer who submits a form at 22:00 has already told you how they want to buy. A reply at 09:30 the next morning is not slow service. It is a different service from the one they asked for.
Routing is the second bottleneck
Even inside working hours, the response clock runs while routing logic decides who owns the lead. Territory rules evaluate, round-robin assigns, and the record sits in a queue until the assigned rep next opens the CRM.
Reassignment is the expensive part. A lead routed to the wrong territory, worked briefly, then handed on, has consumed the whole first-hour window before anyone with the right context has seen it. Because most reporting restarts the clock at reassignment, this delay is usually invisible in the dashboard that is supposed to catch it.
Three checks worth running against your own routing:
- How long between lead creation and assignment, measured separately from total response time?
- What percentage of leads are reassigned at least once?
- Does enrichment run before or after assignment, and how long does it take?
How to get response time under five minutes without adding headcount
A structural absence cannot be closed by effort. If 76% of the week is uncovered under stated assumptions, no amount of SLA training, dashboard pressure or rep coaching changes the arithmetic. Hiring across time zones changes it, expensively and slowly. The only other mechanism is a first touch that does not depend on a person being awake.
That is what autonomous first-touch qualification does. An agent receives the enquiry as it arrives, engages the buyer, asks the qualifying questions a rep would ask, and either books time or hands a qualified record to the right owner with the exchange attached. Sales AI / Inbound AI is the family here: agents that search, reason and act, turning inbound traffic into qualified pipeline around the clock.
Fast and wrong is still wrong
Speed only pays if the thing arriving fast is right. A five-minute response that books an unqualified prospect into an AE calendar has not improved anything. It has moved the waste from the SDR queue to the most expensive hour in the company.
Guardrails that keep speed honest:
A team that hits five minutes and fills the AE diary with the wrong meetings has optimized the number and damaged the funnel.
Worked example one: high-velocity inbound
A software company receives most demo requests outside 09:00 to 17:00 UK time, because a meaningful share of its traffic sits in North America and APAC. Under the coverage arithmetic above, those enquiries land in the uncovered 76%.
The morning queue is worked in arrival order. The 22:00 enquiry is answered at roughly 09:40, eleven and a half hours after the buyer asked, well outside the within-the-hour threshold behind the 7x finding. The rep is not slow. Nobody was there.
Worked example two: considered purchase
A construction supplier receives a technical enquiry about a product configuration late on a Friday. A five-minute generic reply would be worse than useless, because the question needs a real answer.
The workable pattern is a first touch that acknowledges the specific question, gathers the qualifying detail, and books the technical conversation for Monday morning with context attached. The buyer gets a substantive response inside their own window. The specialist arrives prepared instead of cold. Speed and relevance are not in tension here, but they are different things, and only one of them is on the dashboard.
Conclusion
Speed to lead is a coverage problem. Measure it from lead creation to genuine contact, exclude auto-replies, set targets by motion rather than by folklore, and plan around the 7x within-the-hour figure rather than the vendor-partnered hundredfold claim. Then be honest about the arithmetic: a single-time-zone team cannot cover a 168-hour week by trying harder.
FAQs
Q1. What is speed to lead?
Speed to lead is the elapsed time between an inbound lead arriving and a qualified human or agent response reaching that lead. The clock starts when the lead is created, not when it is assigned, and it stops at genuine contact. An automated acknowledgement does not stop it.
Q2. What is a good lead response time?
It depends on the motion. High-velocity inbound needs minutes, mid-market within the hour, and enterprise considered purchases the same working day with a substantive reply. Enterprise differs because relevance outweighs raw speed. A fast generic response to a complex enquiry damages credibility rather than building it.
Q3. How much does conversion fall after the first hour?
Harvard Business Review’s 2011 study found firms contacting a lead within an hour were nearly seven times as likely to qualify it as those trying an hour later, and more than sixty times as likely as those waiting a day. Qualify means a meaningful conversation with a key decision maker.
Q4. What is the average B2B lead response time?
Reliable current public averages are scarce. The most credible figure available is HBR’s 2011 audit, which found an average of 42 hours among companies responding within thirty days. That is a 2011 measurement and should not be presented as today’s benchmark. Measure your own instead.
Q5. How do you measure speed to lead accurately?
Start the clock at lead creation. Stop it at genuine qualified contact. Exclude automated acknowledgements, booking-link auto-replies and enrichment time, and never restart the clock on reassignment. Measuring from assignment tells you about rep diligence rather than about the buyer’s experience.
Q6. What causes slow response most often?
Coverage first, routing second. A team working one time zone is absent for most of the 168-hour week, so leads arriving out of hours wait by default. Within hours, manual routing, territory reassignment and queue depth add further delay. See the coverage arithmetic above.
Q7. How do you get response time under five minutes?
Structurally, not motivationally. Autonomous first-touch qualification answers enquiries as they arrive regardless of hour, and automated routing removes the assignment delay behind it. Together they close a gap that effort cannot. See how autonomous first-touch qualification works at /solutions/sales-ai.
