
A landmark study conducted by InsideSales.com, now XANT, in conjunction with MIT examined more than 15,000 leads across multiple industries and produced one of the most durable findings in B2B sales research: the odds of qualifying a lead are 21 times higher if contact is made within five minutes rather than thirty. Harvard Business Review research reached the same conclusion independently. The decay is steep and front-loaded, with qualification odds dropping roughly tenfold inside the first hour.
Set that against observed behavior. The average B2B lead response time is around 47 hours. Only 23 percent of companies respond within five minutes. Analysis of response-time improvements suggests that compressing from the mid-forties of hours down to five minutes can lift qualified pipeline by 200 to 300 percent without generating a single additional lead.
Every revenue leader knows the five-minute statistic. Most have quoted it in a board deck. The interesting question is not why speed matters. It is why a well-documented, universally accepted finding has produced so little change in the measured average.
Why does a 47-hour average persist when everyone knows the research?
Because the standard interventions target effort, and the delay is not made of effort.
The usual responses are a service level agreement, a dashboard, and a conversation in a Monday meeting about picking up inbound faster. Each assumes someone is sitting on a lead they could have called. In practice, the lead was not sitting with anyone. It was in transit, or assigned to the wrong person, or assigned to the right person on the wrong day.
Break a typical inbound journey into its actual segments and the arithmetic becomes clear. A form submits. An integration picks it up on its next sync cycle, which might be fifteen minutes. Enrichment runs. An assignment rule evaluates and hands the record to a rep. A notification lands in an inbox or a channel the rep is not watching. The rep sees it, and calls.
The rep’s own response time, measured from the moment they became aware, is often minutes. The system consumed hours before awareness. Coaching the rep harder optimizes the one segment that was already fast.
The Monday failure modes
Routing systems are usually built for the clean case and then meet reality, which arrives in a small set of recurring forms.
Someone is on holiday, and a simple round-robin keeps feeding them leads that sit untouched until they return. A new hire receives the same volume as a senior rep in week one, and leads that needed an experienced conversation get a hesitant one instead. Two rules both match an inbound record and nobody can say which one should win. The queue skews because one rep worked a backlog and the rotation does not account for current load. A high-value enterprise inquiry gets treated identically to a student research request because the only field the rule reads is country.
None of these are exotic. They happen most weeks at most companies, and each one produces a lead that is technically assigned and functionally abandoned.
Ownership ambiguity is the expensive one
The worst case is the lead that arrives without a clear owner at all, because it matched no rule or matched a rule pointing at a disbanded team. It appears in a list nobody reviews. There is no alert, because nothing failed. Marketing counts it as delivered, sales never counts it at all, and the discrepancy surfaces a quarter later as an argument about attribution rather than a fix to a routing table.
These leads are invisible in response-time reporting, because most dashboards measure time-to-first-touch on leads that were touched. The ones never touched are excluded from the average, which means the real figure is generally worse than the reported one.
How this works in practice
Treating speed as a routing problem rather than a diligence problem changes what the software has to do. It has to handle the uneven case, cap what it hands to any one person, and be able to explain itself afterward.
Strkr’s routing module is built around those three requirements. Its queues use weighted round-robin rather than flat rotation, so a team can assign double volume to a senior rep and half-weight a new hire, and the published implementation explicitly respects time off rather than continuing to deal leads to an absent rep. Rules match on any field, including custom fields, and precedence is explicit: rules evaluate top to bottom with first match winning, which removes the ambiguity that makes conflicting rules unresolvable. The documented example routes on a compound condition, where industry equals healthcare, region equals west and amount is greater than 50,000 dollars, to a named rep.
Capacity guards address the overload case directly, capping weekly assignments per rep and pausing routing for anyone out of office, which the company frames as not drowning a top performer. Web forms, webhooks and manually created records all pass through the same router, so there is no second unmanaged path into the pipeline. Notifications go to Slack with a one-line preview and a direct link to the record, which targets the awareness segment where much of the delay accumulates.
The audit trail is the part most routing tools omit. Strkr logs which rule fired, why, who received the lead and what the alternative assignment would have been, which the company says resolves a disputed assignment in about 30 seconds. Dedicated lead routing software is commonly sold as a separately priced engagement cloud, and this platform instead ships the capability on its 59 dollar per seat Pro tier alongside custom objects, field-level permissions and AI forecasting, with a 14-day trial and no charge until day 14.
Routing logic cannot compensate for a team with no capacity to call. What it can do is ensure that the capacity which exists is pointed at the right record while the record is still worth something.
What to measure instead of average response time
Average time-to-first-touch is the wrong headline metric, for two reasons. It hides never-touched leads entirely, and a single long tail distorts it badly enough that a genuine improvement can look like noise.
Three measurements are more useful. First, the proportion of leads contacted inside five minutes, which converts the research directly into an operational target and is the figure where only 23 percent of companies currently clear the bar. Second, time from submission to assignment, measured separately from time from assignment to contact, which localizes whether the delay is in the system or in the team. Third, the count of leads with no owner after one hour, which is the number that most often turns out to be non-zero at companies confident their routing works.
Segmenting by day of week and hour tends to be where the specific defects surface. Response times that look acceptable on average frequently collapse on Friday afternoons and during holiday weeks, which is exactly when round-robin rotations that ignore availability do their damage.
Where this goes next
Two developments are changing the economics of this problem.
The first is that routing is becoming a scoring decision as well as a matching one. Rules that evaluate fields are deterministic and auditable, which is their strength, but they cannot weigh likelihood of conversion against current rep load. Systems that combine explicit rules with predictive weighting are more capable and considerably harder to debug, which is why the audit requirement grows rather than shrinks as the logic gets smarter.
The second is that buyer expectations have moved. A prospect who submits a form and receives an instant automated response from one vendor and a 47-hour silence from another has already drawn a conclusion about both, and that conclusion is about operational competence rather than response speed. With only 23 percent of companies inside the five-minute window, speed still functions as differentiation. That will not last indefinitely.
Frequently asked questions
What is a good lead response time in B2B?
Under five minutes is the benchmark the research supports. The InsideSales.com and MIT study of more than 15,000 leads found qualification odds 21 times higher at five minutes than at thirty, and odds decay roughly tenfold within the first hour. The current average sits near 47 hours, with only 23 percent of companies responding inside five minutes.
Does faster lead response actually increase pipeline?
Analysis of response-time improvements indicates that compressing from the mid-forties of hours to five minutes can increase qualified pipeline by 200 to 300 percent with no additional lead volume. The gain comes from qualifying leads that were already paid for and previously went cold before contact.
What causes slow lead response if reps are responsive?
Usually the delay sits before the rep is aware the lead exists: integration sync intervals, enrichment steps, assignment rules that match the wrong owner or no owner, and notifications landing somewhere nobody is watching. Measuring submission-to-assignment separately from assignment-to-contact localizes which segment is responsible.
What should lead routing software handle beyond round-robin?
Weighted distribution so senior reps and new hires receive different volumes, availability awareness so leads are not dealt to absent reps, per-rep assignment caps to prevent overload, explicit rule precedence so conflicts resolve predictably, a single path for forms, webhooks and manual records, and an audit log recording which rule fired and what the alternative assignment would have been.
The hours before anyone is at fault
The five-minute finding has been established, replicated and quoted for years, and the measured average has barely moved. That persistence is informative. It means the constraint is not awareness and not willingness, because both are already present in abundance.
What stands between a 47-hour average and a five-minute one is a sequence of unremarkable mechanical decisions: how often a system polls, which rule wins when two match, what happens when a rep is away, and whether anyone can reconstruct afterward why a lead went where it went. None of that is a performance conversation. All of it is configuration, and it is where the 21 times difference is actually won or lost.

Ricardo Tomaz is VP of Finance & Operations at Ztudium, the 4IR technology company behind Businessabc, Citiesabc, and IntelligentHQ. He owns the group's finance and operations function, spanning financial strategy, budgeting, reporting, and multi-entity operations, and works directly with leadership to align commercial goals with data-driven insight.
Working at the core of a technology group operating across AI and blockchain, Ricardo writes on the practical intersection of finance and emerging technology: how automation and digital transformation are reshaping business operations, what data-driven decision-making looks like in practice, and the questions of governance and ethics that come with AI-led systems.
