Speed to lead: where the minutes go

A demo request arrives at 10:02. Routing assigns it four seconds later. The alert lands in the rep’s inbox while they sit in a pipeline review, then lunch, then a block of calls. The first dial happens at 2:40, and by then the buyer has booked a demo with someone else.

Nobody decides to call a demo request four and a half hours late. Every system in that chain did its job, and the lead still waited, because the minutes collect in the handoffs around the routing rule and nothing is counting them.

What is speed to lead?

Speed to lead is the time between a buyer raising their hand, by filling in a form, starting a chat or requesting a demo, and the first real contact from someone on your team. It starts when the lead arrives, not when it’s assigned. It stops on a call, an email or a booked meeting, not when someone opens the record.

Why the first hour matters

The research most often quoted on this is old, and no rigorous public study has replaced it. A Harvard Business Review study of 1.25 million leads found that firms that tried to reach a lead within an hour were nearly seven times as likely to qualify it as firms that waited one more hour, and more than 60 times as likely as firms that waited a day or longer.¹

A 2021 study of 5.7 million inbound leads found that 0.1% got a response within five minutes, and 57.1% of first attempts came a week or more after the lead arrived.²

Treat both as a shape rather than a benchmark. Interest fades in hours, and most first attempts happen days later.

Where the minutes go

The routing rule is rarely the slow part. Follow one lead from form fill to first call, and the time collects in six places:

1. The lead waits to reach the CRM. The sync between the marketing platform and the CRM runs on a schedule, or a list is uploaded once a day. HBR found the same habit in 2011, with companies pulling leads from the CRM daily instead of as they arrived.¹
2. The lead waits for enrichment. Routing needs a territory, the enrichment call is slow or times out, and the lead sits unassigned until it comes back.
3. The alert is an email. It lands in a folder with every other notification, and nothing marks this one as a demo request from a target account.
4. The rep isn’t there. They’re in a meeting, on leave or out for the evening, and the lead sits with them anyway. Chat has the same problem: the rep on shift steps away, their status still says available, and the visitor waits until morning.
5. Nothing is timing it. Without a clock that starts on arrival, nobody knows a lead has waited three hours until someone pulls a report at the end of the month.
6. Opening the record counts as contact. The rep clicks into the lead, the status changes, and the report shows a fast response that never reached the buyer.

What it costs

The obvious cost is the deals that go to whoever called first. The less obvious one is what slow response does to the numbers. Marketing marks a lead source as weak when its leads waited a day for a call. Sales stops trusting inbound because the leads it works have gone cold. Both teams are measuring the delay and calling it lead quality.

The gap between slow and fast is large. Cisco made its lead response 80% faster. DocuSign rebuilt how leads reach sales:

“Before implementing Tray we were sending 90% of our leads to our sales team in under 10 minutes. After implementing Tray we are sending 99% of our leads to the sales team in under 3 minutes.”

What to fix first

1. Start the clock when the lead arrives. Stamp the arrival time on the lead and measure everything from it. The buyer started waiting when they pressed submit.
2. Move leads as they arrive. Replace scheduled syncs and daily uploads on the path to routing with a trigger on each new lead.
3. Never hold a lead for enrichment. Give the enrichment call a timeout, route on what you have, and update the record when the data comes back.
4. Send one alert where the rep works. Put it in Slack or Teams, with the name, company, what they asked for, the matched account and why it was routed to them, so the rep can call without research.
5. Set a target for each lead type. Minutes for a demo request, a day for a content download. A single target for every lead means either the hot ones wait or reps learn to ignore the alerts.
6. Escalate, then reassign. Remind the rep at half the target, tell the manager at the target, and pass the lead to the next rep in the pool at the hard limit. When the rep is out, reassign straight away.
7. Stop the clock only on real contact. A logged call, a sent email or a booked meeting.

The guide to building speed-to-lead alerts has the prompts for the alert, the clock, the escalation and the reassignment.

Where speed to lead fits

Speed to lead is the eighth of nine stages in lead routing, and it inherits every delay from the seven before it. A lead that arrives as a duplicate goes to two reps, or to the wrong one. A lead routed to a rep who left last quarter has nobody to alert. Event leads arrive in batches and go cold fastest.

After the first call comes the sequence, and the first touch only counts if the CRM and the sales engagement tool agree it happened. The sales engagement to CRM sync guide covers that handoff. Lead lifecycle management covers how each step feeds the next.

Which of your automations breaks first? Take the assessment. It ranks what your team already runs by who can change it, how you would find out it stopped, how many systems it touches, and what a break costs.

---

Sources

1. James Oldroyd, Kristina McElheran and David Elkington, “The Short Life of Online Sales Leads,” Harvard Business Review, March 2011. Based on 1.25 million leads at 42 US companies, and a response-time test of 2,241 companies.
2. XANT, Lead Response Report, February 17, 2021. Based on 55 million interactions and 5.7 million inbound leads across more than 400 companies.