Every RevOps team has a lead response SLA written down somewhere — on a slide, in a playbook, in the onboarding deck for new reps. Almost none of them actually hit it consistently. That gap isn’t new. The research on it is nearly twenty years old, and 2026’s data says the gap hasn’t closed so much as it’s been rediscovered by a new generation of teams with a new generation of tools sitting unused in the stack.
The Original Numbers Are Older Than You’d Guess
The foundational research here comes from Dr. James Oldroyd, then at MIT’s Sloan School, working with behavioral call data from InsideSales.com covering 2004–2007: six companies, more than 15,000 leads, over 100,000 call attempts. The finding that’s been quoted in a thousand sales decks since: contacting a lead within five minutes instead of thirty made a rep roughly 100 times more likely to actually reach that person, and 21 times more likely to qualify them. Harvard Business Review ran an independent follow-up in 2011 covering 2,241 U.S. companies and found an average first-response time of 42 hours, with 23% of companies never responding to the inbound lead at all. Companies that responded within an hour were about 7 times as likely to qualify the lead as those that waited a day. Drift tested it again in 2017 with real form submissions to 433 B2B companies: only 7% responded within five minutes, and 55% hadn’t responded at all within five business days.
2026 Doesn’t Look Meaningfully Different
LeanData’s 2026 B2B State of Martech and Revenue Operations Report surveyed 201 senior marketing, sales-ops, and RevOps leaders at companies with 2,500+ employees across seven countries in April 2026, and the numbers land in almost the same place as the 2007 and 2011 studies. Forty-five percent of respondents name slow or missed follow-up on inbound leads as an active operational problem. Forty-seven percent say their lead processes are still manual and can’t scale with growth — the single most-cited gap in the report. Forty-two percent report poor alignment between marketing and sales on what actually counts as a qualified lead, and 40% cite data quality problems that prevent routing from working correctly in the first place. Thirty-two percent are dealing with duplicate or mismatched lead-to-account records, which is often the quiet reason a “fast” router still sends a lead to the wrong rep or the wrong queue.
The part that stands out most: only 11% of the leaders surveyed have AI-based SDR or lead-routing tooling in active use or pilot — the lowest adoption rate of any AI agent category in the report, well behind AI for content and campaign creation at 46% and analytics/reporting at 39%. RevOps teams have been handed AI tools for two years now, and they’ve pointed almost all of it at content generation and dashboards, not at the part of the funnel where the original research says the money actually gets left on the table.
Where the Time Actually Goes
In client engagements, the delay is rarely “a rep forgot.” It’s routing logic doing too much sequential work before a human ever sees the lead: dedup against existing records, territory and segment assignment, round-robin or capacity checks, enrichment calls to third-party data providers, and then a notification that lands in an email inbox or a queue view nobody has open. Each step is reasonable on its own. Stacked together, and running on batch jobs instead of real-time triggers, they’re how a lead that could be called in under five minutes sits for a day and a half instead — which lines up with LeanData’s finding that integration complexity, not budget or leadership buy-in, is the top-cited barrier to routing maturity at 51%.
What Actually Closes the Gap
LeanData’s report includes a named example worth citing directly: TetraScience took its inbound response time from roughly 24 hours down to under 5 minutes and saw MQL-to-SQL conversion improve by about 20% as a result — not from hiring more SDRs, but from collapsing the routing steps above into real-time rules and putting the notification somewhere a rep actually watches. That’s the pattern we see repeat: the fix is rarely more headcount or a flashier chatbot on the website. It’s enrichment and assignment running synchronously instead of on a nightly batch, notifications going to Slack or Teams instead of an inbox, and someone actually watching response-time as a weekly metric instead of a slide made once a year for the board.
Our Verdict
The lesson from 2007 hasn’t expired — it’s just been waiting for the tooling to catch up, and 2026’s data suggests most teams still haven’t picked it up. AI-based lead routing is one of the least-adopted AI use cases in RevOps right now precisely because it’s unglamorous: there’s no demo moment where a routing rule wows a room the way a chatbot does. But it’s also one of the few AI investments in the current stack with a clean, boring, measurable payback line — minutes shaved off response time convert directly into pipeline, the same way they did in 2007, 2011, and 2017.
If you want a straight read on where your own inbound leads are actually losing time between the form fill and the first call, that’s a conversation we have with clients every week.