Illustrative composite: a VP of Sales opens the Monday dashboard and sees an average lead response time of 47 minutes. It looks respectable. Then someone pulls the raw records. Half of last week's demo requests got a human reply inside ten minutes, because they arrived on a weekday morning and matched a clean territory. The other half sat. Friday afternoon forms waited until Monday. Leads from accounts owned by a rep on leave waited until someone noticed. Eleven requests never got a human reply at all, because the auto-responder marked them as "contacted" and the sequence quietly ended. The average was real. It just described a team that did not exist.
This is the usual shape of the problem at a growing SaaS company: the team believes it is fast, and the number that says so hides the leads that cost pipeline.
It is worth separating what is known from what is repeated. The famous figure, that contacting a lead in five minutes rather than thirty makes you 21 times more likely to qualify it and 100 times more likely to reach the person, comes from the Lead Response Management study by James Oldroyd and InsideSales.com, run in 2007 on phone-led inbound teams. The second pillar is Harvard Business Review's 2011 article "The Short Life of Online Sales Leads," which audited 2,241 US companies: 37% responded within an hour, 23% never responded, and the average among those who did was 42 hours. Firms that tried to reach a lead within an hour were nearly seven times as likely to qualify it as those that tried an hour later, and more than 60 times as likely as those that waited a day or more.
The field has not moved as far as you might hope. Workato's published study of 114 B2B companies found the average email reply took 11 hours and 54 minutes, only 31% followed up by phone, and none called within five minutes. RevenueHero's 2024 test of 1,000 B2B SaaS websites found that 63.5% never replied, and the average for those that did was 1 day, 5 hours and 17 minutes. Chili Piper's 2025 B2B Buyer First Report, which reviewed the top 100 B2B SaaS websites, found that 16% did not respond to a demo request at all, and reported an average response time of about eight hours.
So "fast" in 2026 is not one number. It is a position in a field where most competitors take hours, many never reply, and the decay curve is steepest in the first hour.
Diagnosis: why most teams cannot say how fast they really are
Most RevOps leaders can quote a response time; fewer can say how it was calculated. At $3M to $30M ARR, the number usually comes from an old CRM report, and it fails in four predictable ways.
The average hides the tail
Response times are heavily skewed. A team that answers most leads in minutes and a handful in days reports a pleasant mean, while the slow leads, often after-hours or complex accounts, carry most of the lost pipeline. An average also ignores leads that were never touched, so unless the never-responded rate sits next to it, the dashboard rewards the team for ignoring the hardest leads.
The clock starts in the wrong place
Many reports measure from assignment or MQL status rather than from when the buyer pressed submit. Every minute in enrichment, scoring or a routing queue disappears from the metric. The buyer experiences the whole delay; the dashboard sees only the last step.
An automated email counts as a response
An instant confirmation email is useful, but it is not a response. RevenueHero found that companies which automated their first reply still averaged 17 hours and 20 minutes. If the stop condition is "any activity logged," the metric measures your email tool, not your team.
Routing breaks on exactly the leads that matter
The leads most likely to wait match an existing account, arrive outside working hours, or land with a rep who is out. These are often your best leads. A round-robin that works for net-new contacts can fail silently when the account owner is inactive or the account exists twice in the CRM.
The framework: speed-to-lead targets by ARR band
Three things set what "fast" should mean for your team: your stage, which sets lead volume and the coverage you can staff; your motion, which sets what the buyer is asking for; and the competitive baseline, still measured in hours in most categories. We use three measures, with targets for each by ARR band.
Median time to first meaningful touch (p50). Measured from form submission to the first human or genuinely conversational response: a call, a personal reply, or a confirmed meeting booked in the moment. Auto-acknowledgements do not stop the clock.
90th percentile time (p90). The time within which nine in ten leads get that touch. This is the number that captures nights, weekends, holidays and routing failures, and it is usually where the pipeline is lost.
Never-touched rate. The share of qualified inbound requests that receive no meaningful touch within seven days. Given that between 16% and 63.5% of B2B companies in the studies above never replied at all, this is often the cheapest place to win.
The targets below are a suggested starting point, not a benchmark. They are calibrated against the public research cited in this article, not against a VANDFORT dataset, and they apply to high-intent requests such as demo, pricing and contact-sales forms. Content downloads and trial sign-ups deserve their own, slower targets.
Suggested targets: p50 under 15 minutes in business hours; p90 under 4 business hours; never-touched rate below 5%.
Why: a founder or one AE can respond personally. The risk is coverage, not capacity: one person on a flight resets the curve. Self-scheduling on the form is often the biggest lever here.
Suggested targets: p50 under 5 minutes in business hours; p90 under 1 business hour; never-touched rate below 2%.
Why: this is where a dedicated inbound function exists and can be held to the first-hour window that Harvard Business Review's data shows matters most. The common failure is routing: territories and named accounts appear, and leads matching existing accounts start to stall.
Suggested targets: p50 under 2 minutes for instant-book or live routing; p90 under 30 minutes including after-hours coverage for your main regions; never-touched rate below 1%.
Why: volume and competition justify instant scheduling and follow-the-sun or on-call coverage. At this size the gap is rarely effort; it is the number of systems a lead passes through before a person sees it.
Motion adjusts these targets. A product-qualified lead often deserves a same-day touch rather than a five-minute call, because the buyer is already getting value. A contact-sales request from a named account deserves your fastest path, regardless of band.
Keep speed in proportion. 6sense's 2025 Buyer Experience Report, based on nearly 4,000 B2B buyers, found that buyers first contact sellers about 61% of the way through their journey, and the preferred vendor at the end of selection wins 77% of deals. A fast reply rarely creates preference; it protects the preference you already earned, which is what makes a slow reply so expensive.
Implementation: six steps to a response time you can trust and improve
None of this needs a new tool on day one: start with an honest baseline, then remove delays one by one.
Rebuild the baseline from raw timestamps
Export the last 90 days of high-intent form submissions with their submission time, and join the first human activity on each lead or contact: call, personal email, meeting booked. Calculate p50, p90 and the never-touched rate, split by business hours and after hours. The diagnose-before-you-build playbook covers how to do this read-only. Check: you can state all three numbers and explain how each was computed.
Map every hop between submit and a human
List each system a lead passes through, from form and enrichment to routing and notification, and time each hop on a sample of recent leads. Check: you know which hop causes most of the delay, rather than assuming it is the reps.
Fix the routing paths that stall
Handle leads that match an existing account, leads whose owner is inactive or out of office, and leads arriving outside working hours. Each needs an explicit rule and a fallback owner. Check: a test lead in each of these cases reaches an active person within your target.
Let qualified buyers book in the moment
Offer a calendar on high-intent forms for leads that meet your fit criteria, so the fastest response is the buyer choosing a time. Chili Piper's 2025 review found only 9% of the top 100 B2B SaaS sites offered booking from the form, so this alone can put you ahead of most of your field. Check: a meaningful share of qualified requests book without waiting for a rep.
Test the new flow on your own past leads before switching it on
Replay a set of recent leads through the new rules and confirm each would have reached the right person in time. We hold every system to the same bar: tested on around 20 of the client's own past cases, and 85 percent correct or it does not ship. Check: the routing matches the agreed outcome on past cases, and every miss has a written reason.
Publish the three numbers weekly, with alerts on breaches
Report p50, p90 and the never-touched rate every week, by segment and region, and alert a manager when any high-intent lead passes the p90 target untouched. Check: every breach in the first month has an owner and an explanation.
Workflow: the path from form submission to first conversation
A suggested design for each high-intent lead, with the clock running from the first stage. Adapt the details; keep the order and the owners.
What happens: the buyer submits a demo or contact-sales form. The submission time is stored on the record and never overwritten.
System role: start the clock and pass the lead on immediately, with no batch jobs or scheduled syncs in the path.
Owner: marketing operations owns the form and the timestamp.
What happens: the lead is enriched, matched to an existing account if one exists, scored for fit and routed to an active owner, or to a fallback pool if the owner is unavailable.
System role: complete matching and routing in seconds, and record the rule that decided the owner.
Owner: RevOps owns the routing rules and fallbacks.
What happens: qualified buyers can book a meeting on the spot; others receive a call or personal reply from the assigned rep, with account context already attached.
System role: notify the owner in the tool they actually watch and stop the clock only on a real human or booked-meeting touch.
Owner: the SDR or AE responds; their manager owns coverage.
What happens: any lead still untouched at the p90 target is escalated or reassigned. Every lead's timing and outcome feeds the weekly report.
System role: make sure no high-intent lead goes untouched unnoticed.
Owner: the head of sales development reviews breaches weekly with RevOps.
The board narrative
Three statements usually make this work credible to a board.
We now measure lead response from form submission to the first real conversation, at the median and 90th percentile, and track how many requests never got a response. Targets fit our stage and motion.
Buyers reach out late and usually contact the vendor they already prefer. A slow or missing reply gives away demand marketing has already paid for. Most B2B companies take hours to reply and many never do, so closing this gap is one of the cheaper advantages available.
We report p50 and p90 response times, the never-touched rate, the share of qualified buyers who book in the moment, and meeting and pipeline conversion by response-time bucket, so we can see the curve in our own data rather than relying on someone else's study.
With three or four quarters of clean timestamps, you can plot your own response-time-to-conversion curve by segment. Illustrative example, with made-up round numbers: a $12M ARR company receiving 400 high-intent requests a month might find that leads touched within an hour convert to a held meeting at 40%, while leads touched after a day convert at 20%. If 25% of requests currently wait more than a day, moving them inside the hour is worth roughly 20 extra held meetings a month in that example. Your own numbers will differ; the point is that the curve, not a general rule, should set your target.
Cross-domain: where speed-to-lead connects to the other systems
Response time is the first measurable moment in the revenue engine, which is why Speed-to-Lead is often the first system we build. It drafts and routes inbound responses with account context. Sending requires approval unless that boundary is widened in writing. The measurement design above is a proposed implementation, not a claim about every shipped installation.
It does not stand alone. The Handoff Orchestrator carries context from SDR to AE so the second conversation does not start cold. The Signal-Based Outbound Engine applies the same urgency to buying signals that never become a form, such as pricing-page visits from a target account. Further down the funnel, the Pipeline Hygiene Sentinel flags opportunities that came in fast and then went quiet. The wider picture sits on the GTM Operations page.
For who should own response time once it is instrumented, see the GTM engineer vs. RevOps manager vs. growth engineer decision tree. Our approach is forward-deployed engineering: build inside your existing CRM, test against your own past leads, and switch each change on only when it proves itself.
Sources: Workato, "We Tested 114 B2B Companies' Lead Response Times" (retrieved October 2026). RevenueHero, "We Tested Lead Response Times of 1000 B2B Sales Teams" (March 2024). Chili Piper, 2025 B2B Buyer First Report (top 100 B2B SaaS websites, April 2025). James B. Oldroyd, Kristina McElheran and David Elkington, "The Short Life of Online Sales Leads," Harvard Business Review (March 2011; 2,241 US companies audited). Electronics Cooling, secondary account of James B. Oldroyd and InsideSales.com, Lead Response Management study (2007). 6sense, 2025 B2B Buyer Experience Report (nearly 4,000 B2B buyers, 2025). The ARR-band targets and the conversion example are suggested starting points and illustrative figures, not benchmarks.
