50% of sales go to the first vendor to respond. The average B2B team responds in 42 hours. Here's the revenue math behind speed to lead — and how to close the gap.
In 2007, a study published in the Harvard Business Review tracked how response time to inbound leads affected the probability of making contact and qualifying a prospect. The findings were stark: companies that contacted leads within an hour were nearly seven times more likely to have a meaningful conversation than those that waited more than an hour. Companies that waited 24 hours or more were 60 times less likely to qualify the lead.
That study is nearly two decades old. The underlying dynamic it identified has not changed. If anything, it has intensified.
In 2025, buyers move faster. Attention spans are shorter. Competitive alternatives are more visible and more accessible. The window between "a prospect expresses interest" and "the prospect moves on" has not widened, it has narrowed.
Speed to lead is not a nice-to-have. For phone-first B2B sales teams selling to small businesses, it is the single most consequential variable in inbound conversion.
What is speed to lead?
Speed to lead is the time elapsed between a prospect expressing interest, submitting a form, requesting a demo, clicking on an ad, and a sales representative making first contact.
It is typically measured in minutes or hours, though at most companies it is measured in days without anyone realizing it.
The metric sounds simple. The operational reality of achieving it consistently, at scale, across markets, 24 hours a day, is not.
The numbers behind speed to lead
The research on lead response time is among the most consistent in sales literature. Several key findings have been replicated across studies and industries:
The 5-minute threshold Making contact within 5 minutes of a lead submitting a form increases the probability of qualification by 9x compared to waiting 10 minutes. The drop is not gradual, it is steep and fast. The first 5 minutes after a lead submits information represent a disproportionately high-value window.
The 30-minute cliff Contact rates drop by more than 80% when response time exceeds 30 minutes. After this point, the lead has moved on, mentally, and often literally. They've opened their inbox, switched tabs, taken a phone call, or walked away from their computer.
The 50% rule Research consistently shows that 50% of sales go to the first vendor to make meaningful contact. In competitive markets where multiple vendors are being evaluated simultaneously, speed is not just advantageous, it is determinative.
The industry average Despite this evidence, the average B2B company responds to inbound leads in 42 hours. The median is even longer. Most companies are operating with a speed-to-lead performance that, by the evidence, is surrendering roughly half their inbound pipeline to faster competitors.
Why speed to lead is so hard to achieve at scale
Understanding why the problem exists is important before addressing how to fix it.
The queue problem
Most sales teams manage inbound leads through a queue, leads arrive, they enter a list, SDRs work through the list in order. At low lead volume, this works adequately. A queue of 10 leads can be cleared in a morning. A queue of 200 leads on a Monday after a weekend of form submissions cannot.
The queue introduces lag as a structural feature of the process. The longer the queue, the longer the average response time, and as volume grows, the queue grows with it.
The availability problem
Inbound leads do not arrive on a schedule that matches SDR availability. A significant portion of form submissions happen outside of core business hours, evenings, weekends, and early mornings are common, particularly for small business owners who research solutions when they're not serving customers.
A lead submitted at 9pm on a Friday enters a queue that won't be worked until Monday morning. By the time a rep calls, the lead is cold, and has likely already spoken to a competitor who responded faster.
The consistency problem
Even when SDRs call quickly, the response is not uniform. Different reps call at different speeds, with different urgency, with different scripts. The fastest reps get to leads within minutes; the slowest take hours. Speed to lead as a team metric masks wide variation at the individual level.
The coverage problem
For companies operating across markets and time zones, achieving consistent speed to lead is even harder. An inbound lead from a Spanish market at 2pm local time may not be reached by anyone until the following morning if the Spanish SDR team is not working.
How voice AI solves the speed to lead problem
The speed to lead problem is, at its core, a capacity and availability problem. SDRs are humans with finite working hours and finite call capacity. The volume and timing of inbound leads doesn't respect those constraints.
Voice AI changes the constraint fundamentally. A voice AI system has no working hours. It has no queue. It does not have a finite number of simultaneous calls it can make. When a lead submits a form at 11pm on a Sunday in Madrid, the AI calls them at 11:00:04pm on Sunday in Madrid.
The mechanics:
- Lead submits form → CRM record created → AI system triggered → call initiated within seconds
- If the prospect answers: qualification conversation begins immediately
- If voicemail: personalized voicemail drop, call outcome logged, follow-up sequence initiated
- All outcomes logged in CRM with timestamp, recording, transcript, and qualification data
The result is that speed to lead, measured in seconds, not minutes or hours, becomes a structural feature of the process, not a performance metric that varies by rep availability.
The revenue math of speed to lead
Speed to lead is often treated as an operational metric. It is more accurately a revenue metric.
Consider a company generating 500 inbound leads per month with a 15% qualification rate and a 25% close rate on qualified leads. Average ACV is $6,000.
Current state: average response time 4 hours, contact rate 35%, qualification rate 15%
- Leads contacted: 175
- SQLs generated: 75 (assuming 15% of all leads, not just contacted)
- Deals closed: 19
- Monthly revenue from inbound: $112,500
Improved speed to lead: response time under 60 seconds, contact rate 65%, qualification rate improves to 25% (more leads contacted = more qualified)
- Leads contacted: 325
- SQLs generated: 125
- Deals closed: 31
- Monthly revenue from inbound: $187,500
The delta is $75,000 per month, $900,000 per year, from the same marketing spend, the same product, and the same sales team. The only variable that changed was when the first call was made.
This math is sensitive to the specific inputs, and your numbers will be different. But the directional reality, that speed to lead has a direct, calculable revenue impact, is consistent across industries and sales motions.
Speed to lead in practice, what good looks like
Under 60 seconds: achievable only with automation. No human SDR team can consistently call every inbound lead within 60 seconds of form submission at any meaningful volume. This requires a voice AI system triggered directly by CRM lead creation.
Under 5 minutes: achievable with a well-organized, well-staffed SDR team at low lead volume, under 50 leads per day. Requires dedicated inbound coverage during business hours and a clear SLA. Breaks down quickly as volume grows.
Under 30 minutes: the performance threshold most teams aspire to and few consistently achieve. Requires real-time lead assignment, immediate rep notification, and strong SLA enforcement. Still leaves significant gap for out-of-hours submissions.
Over 1 hour: where most companies actually operate. At this response time, the evidence suggests you've already lost a significant portion of your inbound pipeline to faster competitors.
Building a speed to lead SLA for your team
If you're not using voice AI automation, here's a practical framework for improving speed to lead with a human SDR team:
Step 1: Measure your current speed to lead Pull your CRM data for the past 90 days. For every inbound lead, calculate the time between lead creation and first logged activity (call, email, note). Average this across all leads. Most teams are surprised by how high this number is.
Step 2: Identify where the lag is coming from Is it lead assignment delay? Rep availability? After-hours volume? Queue size? The intervention depends on the source of the lag.
Step 3: Set a hard SLA and enforce it Define your target response time. Assign leads in real time (not in batches). Create a clear escalation for leads that breach the SLA. Track SLA compliance as a team metric, visible to everyone.
Step 4: Separate after-hours from business hours You cannot achieve sub-5-minute response time for out-of-hours leads with a human team unless you have 24/7 coverage. Acknowledge the gap and decide how to address it, whether through an AI system, an extended coverage model, or a clear expectation-setting email to after-hours submitters.
Step 5: Automate the first touch for volume above threshold Above approximately 200 inbound leads per month, manual SLA enforcement becomes increasingly fragile. At this volume, voice AI automation for the first touch becomes not just an efficiency play but a prerequisite for consistent speed to lead performance.
The bottom line
Speed to lead is one of the most evidence-backed levers in B2B sales. The research is unambiguous. The revenue math is straightforward. And the operational reality, most companies respond in hours, not minutes, means the opportunity is large and largely unrealized.
For phone-first B2B sales teams, the first 5 minutes after a lead submits a form are the highest-leverage window in the entire sales cycle. What happens in those 5 minutes, whether the prospect is reached, engaged, and moved forward, determines a disproportionate share of inbound revenue.
The teams closing that window fastest are not doing it with faster SDRs. They're doing it with infrastructure that doesn't have a response time problem.
See how Pyto's voice AI performs on real sales calls → Listen to a demo call
Ready to compare it against your current process? → Book a demo
Related reading: