The Speed to Lead Playbook: Why 5 Minutes Beats 5 Hours

What the research actually proves#

Reply decay is steep, mostly inside the first hour. Three studies show contact odds collapsing in 30 minutes, qualification odds in an hour. MIT Lead Response Management (2007, 15,000+ leads): 5 min vs 30 min is 100x contact odds, 21x qualifying odds. HBR 2011 audit of 2,241 US firms: contact inside an hour is 7x more likely to qualify vs an hour later, 60x+ vs 24 hours.

The distribution matters. In Oldroyd's HBR study: 37% inside an hour, 16% 1-24 hours, 24% longer, 23% never. Among responders, average was 42 hours: lead rot. Drift's 2017 survey of 433 B2B SaaS: 7% replied in 5 minutes, 55% never replied in 5 days. Two decades of work, one result: the window is short and most sellers miss it.

Why the 21x is actually smaller#

The MIT finding of 21x is an odds ratio for qualifying a lead, not a conversion multiplier. Almost every post converts it to "21x more likely to convert," which misreads odds ratios for rates. Odds ratios only resemble conversion multipliers when the base rate is tiny. A team qualifying 10% of inbound at 30 min is not chasing 210% at 5 min; at 5 min they'd hit 70%, a 7x lift, not 21x.

Size your business case off your own volumes. A six-company dataset from 2007 is direction, not forecast. Still the highest-return process change most B2B teams have available.

How to instrument speed to lead#

Track two timestamps and one field: form submit time, first outbound send time, and channel. Everything else is derived. If your CRM can't produce these three cleanly, your speed number is a guess, probably flattering.

Throw out your average response time. Team A answers 90 leads in 60 seconds and 10 in 70 minutes (mean 7.9 min) is inside 5 min on 90% of leads. Team B answers all 100 at exactly 8 minutes is inside 5 min on 0%. Report P5 rate (share under 5 min) as your headline, P90 latency as your tail check. Skip the mean.

Hunt three bugs before trusting the data: measuring from CRM record creation instead of form submit, counting an autoresponder as the first touch, and counting a queued message as sent. All three flatter the number.

• lead_created_at: the form submit timestamp from the source system, not the CRM record creation time. Sync lag hides anywhere from 30 seconds to 15 minutes.
• first_touch_at: when the message was accepted by the sending provider, not when it entered your queue. Queued is not sent.
• first_touch_channel: text, email or call. Segment every downstream number by this.
• response_seconds: derived. first_touch_at minus lead_created_at.
• owner_engaged_at: when a human actually typed into the thread. This is the field that predicts booked appointments, and almost nobody tracks it.

Building the automation architecture#

Five stages, each with its own time budget. System speed is its loosest link; find the slowest stage and cut it, not stack more tools. Enrichment runs beside the first touch, never in front; a 12-second lookup plus retry converts a 2-minute SLA to 6 minutes. Reply detection must be event-driven, not polling; a 5-minute poll adds 5-minute average latency.

For sending: your CRM fires a messaging layer via webhook that reports delivery state back. Blue Reacher is native to GoHighLevel, HubSpot, Close, Salesforce, Pipedrive, Follow Up Boss; Zapier, Make, n8n and API/webhooks cover the rest. iMessage needs no A2P registration, so automation goes live in days, not after carrier review.

Why text beats email or calls first#

Text is read in the buyer's current posture; email gets triaged later on their schedule; calls from unknown numbers get screened. Hiya reports 86% of unknown calls unanswered. Text is the only one where a 5-minute response is experienced as 5 minutes. Chat delivers instant, in-context replies on your site; text delivers the same everywhere else, 40 minutes later when the tab is closed.

For US B2B lists, the iMessage case is arithmetic. iOS is 58.35% of US mobile OS share as of June 2026, so most prospects read the first touch in their normal blue thread. Typing indicators, read receipts and delivery states tell you the message landed and someone's writing back before they finish typing.

What the first message should say#

Name what they just did in the first eight words, say who you are in one clause, ask one closed question answerable with a thumb, under 300 characters with no link. Message one earns replies; booking is message three. Demo request example: "Hey Mark, Saad from Blue Reacher. Saw your demo request. Quick question, is this for SDR or account management?" Test your question mechanically: answerable in 3 seconds with a thumb, no extra tabs or calendar? Pass. Don't rewrite until it does.

• Trigger first. "Saw your demo request come through" beats "Thanks for your interest in our platform."
• One closed question. Open questions cost the buyer effort, and effort is the thing you're racing.
• A real human name or no signature at all. Brand-name senders read as a broadcast.
• No link in message one. A link turns a conversation into a task.
• Never open with the calendar. Ask for time after they've replied twice.

When speed makes things worse#

Speed multiplies whatever you're already sending. A 2-minute SLA on generic copy builds a machine for annoying people faster. Sending "saw you were interested" to someone who downloaded a PDF three weeks ago reads as surveillance. Set the response budget from trigger half-life, not company-wide SLA. Most teams apply their fastest playbook to their weakest intent.

Before switching anything on: if your message can't name what the buyer did and roughly when, don't send it fast. Honor STOP instantly and automatically, keep the opt-out trail on the record, don't restart sequences on people who went quiet on purpose. A fast channel with bad reputation stops being fast.

• Demo request, contact sales, pricing page: half-life in minutes. Budget two minutes, any hour of the day.
• Free trial signup or a product activity spike: half-life in hours. Budget under an hour during working hours.
• Content download or webinar registration: half-life in days. Same business day, and lead with the content rather than a demo ask. A two-minute text on an ebook download is a good way to burn a lead you just paid for.
• Cold, list-sourced contact: no trigger, so speed is worth zero here. Relevance is the only lever you have.

Build your own two-minute first touch#

Build this month: two timestamps, a webhook, and a first message that names the trigger. Blue Reacher adds the channel: iMessage from your CRM in one hop, no A2P registration, automation goes live in days. You paid for the lead; the channel is why they never replied.

Frequently asked questions