Speed to Lead: Why B2B Demo Requests Go Cold in Hours

A buyer fills in your demo form at 10:14. At 10:20 they fill in a competitor's. Whoever replies first with something useful usually gets the first meeting, and the first meeting often shapes the shortlist. Speed to lead, the time between a prospect raising their hand and your team responding, is one of the few conversion levers that costs almost nothing to improve and is still neglected by most B2B teams.

This post covers what the research says about speed to lead, why the way most teams measure it hides the real problem, and the changes that matter more than telling SDRs to "be faster": instant booking, routing, and arriving with context.

What the Research Says About Response Time

The most cited study on this is still the one published in Harvard Business Review in 2011, "The Short Life of Online Sales Leads" by James Oldroyd, Kristina McElheran and David Elkington. Two findings matter:

• Most companies were slow. In an audit of 2,241 US companies, about 37% responded to a web lead within an hour, 24% took more than 24 hours, and 23% never responded at all. The average response time among companies that did respond within 30 days was 42 hours.
• Speed paid off sharply. In a separate analysis of 1.25 million leads, firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as firms that waited an hour longer, and more than 60 times as likely as firms that waited 24 hours or more.

The study is old, and buyer behavior has changed since. But the change makes speed more important, not less. 6sense's 2024 Buyer Experience Report found buyers are nearly 70% through their process before engaging sellers. A demo request in 2026 is a late-stage signal. The buyer is comparing vendors now, not next month.

The Measurement Mistake: Averages Hide the Leads You Lose

Most teams that track speed to lead report one number: average or median response time. That number looks fine while deals leak.

Here is a typical pattern. During business hours, SDRs respond in 10 minutes. Requests that arrive at 18:30 on a Thursday or on a Saturday wait until the next working morning, often 14-60 hours. The median stays low because most requests arrive during the day. The leads that wait are the ones the median ignores, and they are disproportionately lost.

Measure it this way instead:

• Share of hand-raisers contacted within 5 minutes during business hours
• Share contacted within 1 hour overall, including evenings and weekends
• Longest 10% of response times (the 90th percentile), reported every week
• Meeting rate by response-time bucket: under 5 minutes, 5-60 minutes, 1-24 hours, over 24 hours

Here is how a simple audit of 90 days of demo requests might be laid out. Fill it in with your own CRM export:

Two things to watch when you fill it in. First, define "response" as a real attempt by a person or a booking confirmation, not an automated "thanks, we'll be in touch" email. Second, split the table by business hours and out-of-hours. Most teams discover that their out-of-hours share is larger than they assumed, and that "never contacted" is not zero.

The last metric is the one that convinces leadership. When your own data shows that requests answered in five minutes book meetings at a clearly higher rate than requests answered the next day, you do not need to quote a 2011 study.

Fix 1: Remove the Gap with Instant Booking

The fastest response is the one that does not need a human. When a qualified visitor submits a demo form, show them a calendar on the thank-you step and let them book directly with the right rep. The lead goes from "waiting for a reply" to "meeting booked" in the same session.

Do this selectively. Instant booking works best for good-fit leads. Poor-fit leads (students, very small companies, competitors) should get a different path, or your AEs fill their calendars with meetings that should not happen. Use the fit data you already have from enrichment or company identification to decide which visitors see the calendar.

Personalize the step before it, too. A demo CTA that matches the visitor's situation ("See it running on your HubSpot data") converts better than a generic "Book a demo". Our 2026 B2B personalization research found that form completion rates increased 27% when fields were pre-filled or hidden based on enrichment data. Fewer fields means fewer abandoned requests to respond to in the first place. Our guide to data-driven personalized CTAs covers the CTA side.

Fix 2: Route Before Anyone Has to Think

Response time is often lost before an SDR even sees the lead. It sits in an unassigned queue, or it goes to a rep who is on holiday, or it is round-robined to someone who is not the account owner and has to be reassigned. Each hop costs minutes or hours.

• Match the request to an existing account and owner automatically.
• Give hand-raisers their own routing path with an SLA measured in minutes.
• Make routing availability-aware so out-of-office reps are skipped.
• Escalate automatically if the lead is untouched after the SLA (for example, notify the team lead after 10 minutes).

Our post on routing website leads by intent covers these rules in more detail.

Fix 3: Arrive with Context, Not Just Speed

Fast and generic loses to slightly slower and specific. A first email that says "Thanks for your interest, when can we talk?" adds nothing. A first email that references what the buyer actually looked at gives them a reason to reply.

Give the rep this context in the lead notification:

• Pages viewed before the request, especially pricing, integrations, and comparison pages
• Other people from the same company who visited recently
• The industry or segment variant the site showed them
• Self-reported source, if your form asks "How did you hear about us?"

Then write the first touch from it. Compare:

Before: "Hi Sarah, thanks for requesting a demo. Do you have time this week?"

After: "Hi Sarah, saw you and a colleague were looking at the Salesforce integration and the enterprise plan. I can show you how routing works on your Salesforce data. Thursday at 14:00 or Friday at 10:00?"

Markettailor's visitor identification provides the company match and page history behind that second email, including the visits from colleagues who never filled in a form.

Fix 4: Cover the Hours Nobody Covers

Evening and weekend requests are where the 90th-percentile numbers come from. Options, from cheapest to most expensive:

1. Instant booking (fix 1) handles most of it with no staffing at all.
2. An honest auto-reply with a booking link and a named rep, sent within a minute.
3. Staggered SDR shifts across time zones if you sell internationally.
4. An on-call rotation for hand-raisers from tier 1 target accounts only.

If you use an auto-reply, make it useful rather than a holding message. Name the rep who will follow up, say when, include a booking link, and add one relevant resource based on the pages the buyer viewed. A buyer who gets a named person and a calendar link at 19:00 is far less likely to book with the competitor who replies first the next morning.

If your SDR team is weighing which part of its stack to fix first (dialer, sequencing, routing), Dialbrew's map of the SDR tool stack is a useful way to see which layer is actually causing the delay.

What Good Looks Like

Targets depend on your sales motion, but these are reasonable starting points for a B2B team with an SDR function:

• Good-fit hand-raisers: booked instantly, or contacted within 5 minutes during business hours.
• All hand-raisers: a real first touch within 1 hour, including out-of-hours requests through instant booking or on-call coverage.
• 90th percentile: under one business day. Anything above that is a process failure, not a busy week.
• Never contacted: zero. Every request gets a response, even if it is a polite redirect to self-serve.

If you hit these and meeting rates do not improve, the problem is usually the first message, not the timing. Revisit fix 3.

A Two-Week Plan

1. Days 1-3: export the last 90 days of demo requests with submit time and first-touch time. Calculate the four metrics above.
2. Days 4-6: add instant booking for good-fit hand-raisers.
3. Days 7-9: separate the hand-raiser routing path and add an escalation after the SLA.
4. Days 10-12: add page history and colleague visits to the lead notification, and rewrite the first-touch template to use them.
5. Days 13-14: re-run the metrics and compare meeting rate by response-time bucket.

Speed to lead is not a motivation problem. It is a routing, tooling, and context problem, and all three are fixable in a couple of weeks. To see the account context your reps could have on every demo request, book a walkthrough from our pricing page.