Speed to lead: the real statistics, and where the minutes actually go

Speed to lead is the time between a lead arriving and someone on your team actually reaching them. Ask any sales or marketing leader what it should be and you'll hear the same answer, under 5 minutes, usually followed by a statistic about how fast leads go cold.

In my experience they target under 5 minutes because they read online that it's good. It's become almost like corporate jargon, because the reality is it never happens. I've submitted leads myself and it's taken weeks for anyone to get back to me.

The 5 minutes isn't wrong, but most of the numbers people quote with it are, and they point the effort at the wrong place. Teams spend their energy on how fast a rep picks up the phone, when the lead has often already waited hours before any rep even knows it exists.

The speed to lead figures that hold up go back to four sources. I went back to the original documents rather than the roundups that quote them, and this is what each one actually measured.

The sources, in order: the 2007 Lead Response Management Study, The Short Life of Online Sales Leads in Harvard Business Review, the 2014 Lead Response Report and the 2021 Lead Response Study.

One thing worth knowing: the 2007 study and the 2011 article share authors. James Oldroyd worked on both, and the article's co-author, David Elkington, was InsideSales.com's chairman and chief executive. They point the same way, but they aren't two independent pieces of evidence.

Then there are the figures that turn up on page after page, and trace back to nothing.

• "78% of customers buy from the company that responds first." None of the pages repeating it names a study that measured it, and I couldn't find an original.
• "Leads go cold 400% faster after 5 minutes." No study I found gives this figure. The 2007 study compared the odds of reaching a lead at 5 minutes against later times, and never put a percentage on how fast leads cool.
• "The average company takes 47 hours to respond." I couldn't find a study that gives this average. The closest real figures are the 42 hours in the 2011 audit and the 61 hours in the 2014 report, measured on different samples.
• "Harvard Business Review's 5-minute rule." The 2011 article talks about responding within an hour. It never mentions 5 minutes. The 5 minutes is from the 2007 study.
• "21 times more likely to qualify within 30 minutes." The 2007 study's 21 times compares calling within 5 minutes against calling at 30. It isn't a figure for answering within half an hour.

You'll also see a figure that most buyers choose the vendor they contacted first. That measures who the buyer reached out to, not how fast anyone replied, so it doesn't say anything about response time.

For web form leads you call by phone, 5 minutes is a fair working goal, and it's the one the evidence actually supports: in the 2007 study, the odds of reaching a lead were already 5 times lower at 10 minutes. If your current time is measured in hours, as it was for most of the companies in the 2011 and 2014 audits, getting inside the hour is the bigger win first.

There is a but though. The studies looked at phone calls to web form leads. They don't settle what a good reply time is for a B2B enquiry by email, an event list or a lead from a partner, and nobody has published a benchmark for those that I'd trust. Set a goal for each channel from your own numbers, then bring it down.

And one more thing. The 2014 study tracked both emails and calls, and its advice was to make first contact with a phone call. The default these days is an email, and an email is easy to ignore. Use the phone. If you capture a number, call them.

So if reps aren't the main problem, what is? The 2011 article gives a few reasons for slow response, and two of them have nothing to do with how fast anyone picks up the phone: pulling leads out of the CRM once a day rather than continuously, and rules that share leads out by geography and "fairness". Both sit before the rep. The delay is often in the plumbing.

Here's what that looks like in a normal week. This is an illustration, the company and the times are made up, but if you've run sales operations you'll recognize every step of it.

1. 01Monday, 9:02am. Someone fills in the demo form on the website. The form tool emails the notification to a shared inbox. Nobody owns that inbox in the morning, so it gets read at 11:40, copied into the CRM by hand at 12:15, and assigned to a rep at 2:30 once the manager has looked at the territory. The rep calls at 2:41.
2. 02Tuesday, at the event. Your team scans 300 badges at a trade show. The organizer sends the list on Wednesday, it sits in a marketing manager's downloads folder until Thursday, and then goes to Dave (not a real person), who does the imports, to be cleaned and loaded.
3. 03Thursday to Friday. Dave has a queue. The event list goes in Friday afternoon, after a vendor file that's been waiting since last week. Reps get their slice of the event leads on Monday morning, six days after the conversations at the booth.

Now look at that from the CRM's side. The Monday demo request shows a response time of 11 minutes, from assignment at 2:30 to the call at 2:41. The event leads show the same kind of number, a few hours from assignment to first call. The dashboard looks fine. The buyer waited more than five hours, and the event leads waited most of a week.

Nobody is fudging the numbers here. The clock just starts in a different place. HubSpot's Lead response time property is the time it took the current owner to do the first qualifying engagement, and its sales analytics report counts from when the contact was assigned to a user. Reassign the contact and the clock resets. Everything that happened before an owner was set, the inbox, the downloads folder, Dave's queue, is invisible to it.

Salesforce doesn't have a standard field for it that I could find, so you'd build a report that compares when the lead was created with when it was first contacted. That starts at record creation, which is better, but a lead that sat in an inbox for three hours was still created three hours late.

The fix is simple to say: record when the lead really arrived, the form submit, the email landing, the file being dropped, and measure from there. How to measure speed to lead in HubSpot and Salesforce goes through the steps in each.

Something else makes speed to lead matter even more: the constant need for demo, demo, demo, and no clear pricing. When paying is gated behind demos and setup calls, the wait after the form is the whole buying process. So when did buying become so difficult? Why do so many SaaS companies (and now the new AI companies) have unnecessarily long sales processes for a prospect?

They make it as difficult as possible for a buyer because they're worried the buyer won't get value and won't commit beyond a trial. I get it, companies are focused on their conversion KPIs. But getting multiple stakeholders involved, planning way beyond a trial and fleshing out every detail of the system isn't quick. As a buyer, I just want to test that the system actually does what it says and is fit for purpose. Then at least a meeting has a targeted value after that.

Most buyers are educated in SaaS tools now and know how to use them. After a while they all look and feel similar, just with different features. Buyers don't need four meetings, constant back and forth over email and an hour-long demo unless they ask for one. A simple question of "how quickly do you want to get up and running?", and processes in place to act on the answer, does more. I know this isn't every SaaS product or company, however it feels like most sales processes now don't actually consider the buyer or their time anymore. It's why Operelio is self-serve.

If you do gate behind a call, the gate is where speed to lead counts most. Every day between the form and the first conversation is a day the buyer can spend looking at someone else.

Most of the fixes are in the plumbing.

1. 01Bring every source into one place. Forms, enquiry emails, event lists and vendor files should land somewhere that runs the same steps on each, not in five inboxes and a downloads folder.
2. 02Check the lead before it's routed. Is the person already in your CRM, or new at a company you already work with? Routing fast to the wrong rep wastes the minutes you saved.
3. 03Route by rule, not by hand. Write down who gets which leads and let the rules assign the owner. What is lead routing? goes through the options and what each costs.
4. 04Set a goal for each channel and cover the evenings. Decide what good looks like for form leads, enquiry emails and lists, and who picks up a lead that arrives at 7pm on a Friday.
5. 05Ask how quickly they want to get going. Then have a process for each answer, from a call today to a self-serve trial with no meeting at all.
6. 06Measure from arrival. Track arrival to owner and owner to first contact separately, so the delay shows up where it actually happens.

This is the part where I tell you about our product, so read it with that in mind.

An Operelio trail takes leads from Zapier, Make or your own code through its folder's webhook, and enquiries sent to the folder's own email address, and works on each one as it arrives. Before the push to HubSpot or Salesforce, the lead goes through the steps you put on the trail, things like cleaning, a score from the Scorecard, a check against your CRM and your routing rules. Lists and files go through the same trail, where you can also verify emails and remove duplicates.

For single leads, the Leads tab shows your speed to lead from the lead reaching Operelio to having an owner in your CRM, today's median beside the median for the 7 days before. That's the part of the wait your CRM's own report doesn't see.

Some leads wait on purpose, and I'd rather you heard it here. In a trail's first week live, every single lead is held for your review. By default a lead that scores 1 or 2 is held, and one that scores 3 goes to review. A folder getting more than 60 leads a minute or 1,000 an hour gathers the extra into one job every 10 minutes. Single leads go only to HubSpot and Salesforce, so on a Pipedrive trail they're held in Operelio and can't be sent yet. And a file or list waits 3 minutes after it lands in the folder, then runs on its own, usually picked up within about ten minutes.

Yes, absolutely, and the evidence for it is better than most of what gets quoted. Reach a web lead in minutes rather than hours and your odds of talking to them go up a lot.

However, if your team's response time already looks good on the dashboard, don't assume you're fast. Measure from when the lead arrived, not when it got an owner. That wait is often where the hours go.