A lead that waits two days for a first response is not a speed problem, it is a handoff problem. The widely-quoted benchmark is an average B2B first-response time of around 42 hours, and the bulk of that delay does not sit inside a rep’s calendar — it sits in the gap between “Marketing says qualified” and “Sales agrees to work it.” Fix the handoff and the clock fixes itself.
Most teams try to solve this by telling reps to move faster. That treats a structural leak as a motivation issue. The delay is manufactured upstream: by a definition nobody shares, an SLA nobody wrote down, reason codes nobody records, and a re-entry path that doesn’t exist. Each of those is diagnosable, and each of them leaks pipeline on its own.
Why the number is worse than it looks
The 42-hour figure comes from older lead-response research, so it is fair to ask whether it still holds. More recent data suggests it does — if anything it flatters most teams. When Workato ran demo requests against 114 B2B companies in 2026, the average phone response time was 14 hours 29 minutes, fewer than half of companies (42%) responded within the hour, and more than 99% missed the five-minute window entirely. Nearly one in five never replied by email at all.
The cost of that delay is not linear. The Harvard Business Review study that underpins most of this research analysed roughly 15,000 leads and 100,000 call attempts, and found the odds of qualifying a lead drop sharply as the minutes pass — the related MIT/InsideSales analysis put the fall at around 21 times when response slips from five minutes to thirty. The point is not that every lead needs a five-minute call. It is that the hours lost in the handoff are the most expensive hours in the funnel.
The four leaks inside the handoff
No shared definition of “qualified”
When Marketing’s definition of a qualified lead and Sales’ definition of one are different documents — or worse, different assumptions never written down — every handoff becomes a small negotiation. The lead arrives, the rep privately disagrees that it is ready, and it sits while nobody formally rejects it. A typical version of this: Marketing counts a content download as intent, Sales counts only a booked meeting, and the leads in between belong to no one. The fix is a single, jointly-signed definition of the qualification bar, with the specific fields that must be present before a lead is passed. If both teams cannot point at the same sentence, the handoff has no edge to defend.
No response SLA — so 42 hours becomes 72
A handoff without a clock is a handoff without accountability. If there is no agreed time-to-first-touch, the lead’s response time is set by whoever happens to be least busy, and it drifts. The fix is a written, mutual SLA: Marketing commits to a quality bar, Sales commits to a response window, and both are measured. The number matters less than the fact that it exists and is reported on. A team that commits to “first touch within four working hours” and actually tracks it will beat a team chasing five minutes with no clock at all.
No reason codes — so rejected leads vanish
When a rep declines a lead, where does it go? In most systems, nowhere useful. It is marked “unqualified” with no reason, and the signal that would tell Marketing why the bar was missed evaporates. Without reason codes — wrong persona, no budget authority, bad timing, duplicate — Marketing keeps sending the same misqualified leads and Sales keeps quietly binning them. The fix is a short, mandatory list of rejection reasons at the point of handoff. It turns a black hole into a feedback loop, and it is the single cheapest fix on this list.
No re-entry path — so “not now” means “never”
A lead that is genuinely not ready today is not worthless, it is early. But most handoffs have no route back into nurture. Rejected means dead. The pattern that follows is predictable: perfectly good leads with a six-month timeline get rejected as “not qualified,” drop out of every workflow, and are re-generated as net-new six months later at full acquisition cost. The fix is an explicit re-entry rule — rejected-for-timing leads return to nurture with a defined recycle date, not the bin.
What good looks like
A handoff that does not leak has four things the leaky one lacks: one definition both teams signed, one response clock both teams are measured against, one short list of reasons a lead can be rejected, and one route back for the leads that were simply early. None of it is technology. All of it is agreement, written down and reported on.
If you want to know how many of your “qualified” leads are actually sitting in the 42-hour gap right now, that is precisely what a Pipeline Leak Audit measures — where the lead stalls, why it stalls, and what it costs. For the definitional groundwork, start with what a sales-qualified lead actually is and why the MQL is dead but the handoff that killed it isn’t fixed. And if you want a structure to steal, the lead handoff process template lays out the SLA and reason-code fields in full.
The CRM is rarely the thing that is broken. The handoff is.
