Speed to lead is the time between a buyer reaching out (a demo request, a contact form, a chat message) and the first meaningful response from your team. The shorter your speed to lead, the more likely you are to talk to the buyer while they are still interested, and before a competitor does.
It is one of the cheapest levers in inbound lead generation: you do not need more traffic, only a faster and better answer to the people who already raised their hand. This article covers what the research says, what a realistic benchmark looks like in B2B, why most teams are slow, and how to fix it.
What is speed to lead?
Speed to lead measures one interval: from the moment a lead submits a request to the moment they get a real response. "Real" matters. A confirmation email that says "we will be in touch" does not stop the clock. A reply that answers their question, or a call from a rep, does.
The term comes from inside sales, where it was first applied to phone calls on web leads. Today it covers every inbound channel:
- a demo request or contact form;
- a question asked in a chat on your website;
- a reply to an email or an ad;
- a meeting request through a scheduling page.
The idea is the same everywhere. Interest is highest at the moment the buyer acts. Every minute after that, they read something else, open a competitor's site, or go back to their actual job.
Why speed to lead matters: what the studies show
Three studies come up again and again. They are not recent, but nothing published since contradicts them.
The Harvard Business Review audit (2011). Researchers tested 2,241 US companies by submitting web leads and timing the answers. The average response took 42 hours, and 23% of companies never responded at all. Companies that tried to contact a lead within an hour were nearly seven times as likely to qualify it as those that tried even one hour later, and more than 60 times as likely as those that waited 24 hours or more (Harvard Business Review, 2011).
The Lead Response Management study (MIT and InsideSales.com, 2007). It analysed three years of data from six companies, over 15,000 web leads and over 100,000 call attempts. The odds of reaching a lead were 100 times higher when called within 5 minutes rather than 30, and the odds of qualifying it were 21 times higher. The odds of reaching a lead also dropped more than tenfold during the first hour (Lead Response Management study, PDF).
The 6sense buyer research (2025). It explains why the delay costs deals and not just contacts. Buyers start most conversations themselves, late in their journey, and 94% of buying groups have already ranked their shortlist before talking to sellers. The vendor contacted first still wins about 8 deals out of 10 (6sense, Buyer Experience Report 2025).
Put together, the picture is simple. When a B2B buyer contacts you, they are usually far along, they are often talking to more than one vendor, and the first useful conversation has a strong advantage.
What is a good speed to lead in B2B?
The usual benchmark is "under 5 minutes", from the MIT study. It is a good target for forms and demo requests during business hours. For a question asked on your website, buyers expect an answer in seconds, like any chat.
Most B2B companies are far from both. In 2024, RevenueHero submitted demo requests to 1,000 B2B SaaS companies. Only 365 responded at all. The average first response took 1 day, 5 hours and 17 minutes. Of the companies that did respond, 172 answered within two minutes, while 41 took up to a week and 12 took longer than that. About 60% of first responses were automated (RevenueHero, 2024).
A realistic goal for most teams looks like this:
- Website questions: an answer in seconds, while the visitor is still on the page.
- Demo requests during business hours: a useful first response in under 5 minutes, ideally with a meeting slot.
- Requests outside business hours: an immediate reply that answers what can be answered and offers a slot, then a human follow-up first thing in the morning.
Why are most teams slow to respond?
When a team has a bad speed to lead, the instinct is to blame the reps. In practice, the delay is almost always built into the process.
- The form is a queue. A form collects the request and then waits. Nothing happens until someone opens the notification, which may be an hour later, or the next day.
- Routing is manual. Someone has to decide whose lead it is: which territory, which segment, which rep is free. Every manual step adds minutes, and leads sent to the wrong person add hours.
- Qualification comes before the first reply. Many teams check the company, the size and the fit before they answer anything. The buyer waits while you research them.
- Business hours and time zones. A lead submitted at 6 pm on a Friday may wait until Monday. For a team in Europe selling in the US, half the day's leads arrive at night.
- SDR capacity. When the people who answer inbound also do outbound, inbound loses whenever the calendar is full.
None of these is solved by asking people to "be faster". They are solved by changing the steps between the request and the answer.
How to improve speed to lead
Measure it first
You cannot fix a number you do not track. Log the time of each request and the time of the first meaningful response, then look at the median by source, by hour of the day and by team. The averages often hide the real problem: leads that arrive at lunchtime or after 5 pm.
Answer on the page, not after the form
The fastest response is the one that happens before the buyer leaves your site. If a visitor can ask their question and get an answer from your own content right away, there is no queue at all. This is what an AI agent for your website does, and it is the shortest possible speed to lead: the answer comes during the visit.
It is also what the Website Agent from Nudge is built for: it answers visitors while they read, cites the page each answer comes from, and books the meeting in the conversation, without a form.
Let the buyer book in the same flow
A response that says "when are you available?" starts an email ping-pong that can last days. Offer real slots in the first response, or let the buyer pick one directly. The meeting is booked while interest is high, and nobody has to chase it.
Automate the routing
Decide the rules once (territory, company size, existing account) and let a tool apply them. The lead should land with the right person, with a notification they actually see, in seconds.
Qualify through the conversation
Instead of researching a lead before answering, answer first and qualify as you go. A question like "Does this work for a team of 12 reps?" already tells you the team size. Ask only what is missing.
Cover the hours you are closed
Decide what happens to a request at 9 pm or on Saturday. At minimum, an instant reply that answers the obvious questions and offers a slot. Then a human follow-up at the start of the next business day, before anything else.
Make the first response useful
Speed only counts if the response moves things forward. A fast reply that asks the buyer to repeat everything they wrote in the form does not help. Start from what they said, answer it, and propose the next step.
Is speed to lead overrated?
Some sales teams push back on speed to lead, and they have a point. A fast but empty response does not help. A generic auto-reply in 30 seconds followed by a call two days later is not a 30-second speed to lead: it is a two-day one with a confirmation email.
The research supports this reading. The MIT study measured contact and qualification, not open rates on auto-replies. The value comes from a real conversation while the buyer still cares, not from the timestamp itself. So the right goal is not "reply fast", it is "give a useful answer fast". Speed and relevance work together.
There is also a point where speed stops mattering much. A lead downloading a guide from a blog post is not in the same place as a buyer asking about pricing on your pricing page. Prioritise the requests that show intent, and accept slower answers for the rest.
A concrete example
A head of finance at a 40-person company visits a software vendor's pricing page at 2:15 pm. The sales team is in its weekly meeting. Instead of a form, the page has an agent.
The visitor asks: "Can we import our expense reports from the current tool, and how long does the setup take?"
The agent answers in a few seconds from the vendor's own documentation, with a link to the import guide. The visitor asks one more question about user permissions, gets the answer, then accepts a 30-minute slot for the next morning.
When the meeting starts, the rep already knows what the buyer asked, what they read, and their concern about permissions. The speed to lead was a few seconds, and the first answer was useful. This is how a Nudge agent works on a B2B website.
How Nudge handles speed to lead
Nudge builds conversational AI agents for B2B sales teams, and speed to lead is the problem they start from. The Website Agent answers visitors in seconds, while they read, from your site and your documents, and each answer cites the page it comes from. When the visitor is ready, it books the meeting in the conversation, without a form and without a queue.
If the visitor leaves without booking, the Nurturing Agent picks up the conversation where it stopped, starting from the question they asked. And the Handoff Agent prepares the meeting for the rep: what the prospect wants, what they asked and the objection already raised.
Nudge installs on WordPress, Webflow, Framer or Shopify, or through Google Tag Manager. See how the Website Agent answers visitors and books meetings.
Frequently asked questions
What does speed to lead mean?
Speed to lead is the time it takes your company to respond to a new lead after they reach out, for example after a demo request, a contact form or a chat message. It is usually measured in minutes, from the moment the request is submitted to the first real contact by a person or an agent. The shorter it is, the more likely you are to reach the buyer while their interest is still high.
What is a good speed to lead?
The most cited benchmark is under 5 minutes, based on the MIT and InsideSales.com study, which found the odds of qualifying a lead drop sharply after that. For a chat or a question asked on your website, buyers expect an answer in seconds. For a form submitted at night, a realistic goal is a useful reply first thing in the morning, and an instant acknowledgement that says when they will hear from you.
How do you calculate speed to lead?
Take the timestamp of the lead's request and the timestamp of your first meaningful response, then subtract. Do it for every lead over a period and look at the median, not just the average, since a few leads answered days later can hide or exaggerate the real picture. Split the result by source, by hour of the day and by rep or team to see where the delay actually comes from.
Why is speed to lead important?
Because buyers move on. When someone fills in a form, they are often comparing several vendors at the same time. The Harvard Business Review study found that companies that tried to reach leads within an hour were nearly seven times as likely to qualify them as those that waited one hour longer. And 6sense reports that the vendor contacted first wins about 8 deals out of 10.
Does an automatic email count as a response?
Not really. An auto-reply that says "thanks, we will get back to you" confirms that the form worked, but it does not answer anything. The buyer still waits for the real response. Count the clock as stopped only when the buyer gets an answer to their question or a concrete next step, such as a meeting slot they can book right away.
