Direct answer
Speed to lead is the time between a person raising their hand and a human being responding to them. The research points to minutes, not hours. To fix it, measure your number first, route every new lead to an owner automatically with a 15-minute task and an escalation, send an instant acknowledgment with a specific promise, and let AI draft the first reply for a human to approve. Then watch the number every week.
Somebody fills out your form. They want a quote, a demo, or an answer. Then what?
If you can’t say exactly what happens next, and how long it takes, you have a speed to lead problem. You are in good company. Most teams have never measured it.
From an audit this year
I’ve seen what this costs. This year I audited a B2B company that had acquired another company. About 300 leads were missed because the form was not routed to the right person. That’s a speed to lead problem at its worst. Those leads didn’t get a slow reply. They were missed, and the cause was routing.
Here’s the short version. Speed to lead is the time between a person raising their hand and a human being responding to them. The research is old in places and the vendors who ran it have something to sell, so I’ll be careful with it. But the direction is the same in every study I could verify: the longer a lead waits, the less likely you are to ever have a real conversation.
Below I’ll show you what the numbers say (and what they don’t), how to measure your own speed to lead in an afternoon, how to fix it with HubSpot workflows plus an AI first-draft reply that a human approves, and a checklist you can run this week. It’s written for small and mid-sized B2B teams, where the owner or a couple of reps are doing everything and leads fall through the cracks quietly.
Every new lead moves through the same four stages, and each one has its own way of breaking. Here is where leads get lost and what fixes each stage.
The Lead Clock
Stage 2 is where the 300 leads in my audit were missed.
Stage 1: Form submitted
The clock starts the moment they hit submit, but nobody on your side knows it. The lead sits in a shared inbox, or in a CRM list that gets pulled once a day instead of continuously.
The fix: Trigger a workflow on the form submission itself, so every lead enters your process the second it arrives.
Stage 2: Routed
The form goes to the wrong person, or to nobody. This is the stage where the 300 leads in my audit were missed: the form was not routed to the right person. Nothing downstream can save a lead that never reaches an owner.
The fix: Assign an owner automatically within seconds, notify them, and create a task due in 15 minutes. Then test the form yourself to confirm it lands with the right person.
Stage 3: First reply
The owner sees the lead but is busy chasing their own leads, or is staring at a blank email. Silence fills the gap, and the task slides past its due time.
The fix: Send an instant acknowledgment with a specific promise, escalate at 15 minutes and at an hour, and have AI draft the first reply for the owner to approve.
Stage 4: Conversation
The reply goes out, but it is generic, or it promises something you can’t keep. Or nobody tracks it, so you never learn whether speed is improving.
The fix: Give the AI standing instructions on tone and what it may promise, and track median time to first human response every week with one person owning the number.
Stages and fixes are drawn from the setup described in this article.
Notice where the clock breaks hardest. A slow reply at stage three still gets you a conversation sometimes. A lead that is never routed at stage two never gets a reply at all. Most teams focus on how fast reps type, when the bigger losses are upstream, in the handoff nobody is watching.
Curious where your own form lands? Take the $10 Speed to Lead test.
What the research actually says about lead response time
I’ll start with the best-known study, because it’s the one people misquote.
In 2011, Harvard Business Review published “The Short Life of Online Sales Leads.” It had two parts.
Part one was an audit. The researchers sent a test lead through the websites of 2,241 U.S. companies and timed the reply. Only 37% responded within an hour. Another 16% took between one and 24 hours. 24% took more than a day. And 23% never responded at all. Among the companies that did respond within 30 days, the average wait was 42 hours.
The HBR audit
How fast 2,241 U.S. companies answered a web lead
Share of companies by time to respond to one test lead.
Source: Harvard Business Review, March 2011, audit of 2,241 U.S. companies. The 42-hour average counts only companies that responded within 30 days.
Part two looked at what speed did to results. Across 1.25 million sales leads at 42 U.S. companies, firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as firms that waited even one more hour. They were more than 60 times as likely as firms that waited 24 hours or longer. HBR defined “qualify” as having a meaningful conversation with a key decision maker.
Notice what is missing. The HBR piece doesn’t say “five minutes.” That famous number comes from an earlier study, presented in 2007 by InsideSales.com and an MIT researcher, using three years of data from six companies. It found the odds of qualifying a lead called within five minutes were 21 times higher than a lead called at 30 minutes. That’s a real finding. It’s also a vendor study of six companies, and it measured qualifying, not closing. It never claimed anyone was “21 times more likely to buy,” even though that’s how it gets repeated.
So here’s my honest read. These are association studies. Teams that respond fast might also just be better run. I’d still bet on speed, because the cost of being wrong is tiny (you answer a little sooner) and the cost of being slow is a lead that never talks to you.
Are teams any faster today?
Not much. Two newer vendor tests secret-shopped real companies by filling out their demo forms.
Chili Piper tested B2B software vendors in 2022. Only 7% responded instantly (under 60 seconds). About 55% took longer than an hour. Nearly 30% never responded at all, and the average reply for those that did was 4 hours and 50 minutes. Mid-sized companies struggled. Among companies with 101 to 250 employees, the biggest group in the study, only 13% answered within five minutes and 21.7% never answered.
Workato ran the same kind of test in 2026 on 114 B2B companies. More than 99% didn’t respond within five minutes. Only one company sent a personalized email in that window. Companies with a lead routing tool still took 3 hours and 32 minutes on average, but that beat the nearly 13 hours for companies without one.
Both studies are from vendors who sell tools that fix this, so take the exact numbers with salt. The pattern is what matters: the bar is low. If you reply in minutes, you are already ahead of most of the people you compete with.
So where does your team sit? Slide to your typical reply time for a new web lead during business hours. The status bands are a plain-language read, not a score, and every number shown comes from the studies above.
Interactive
Where does your reply time land?
Move the slider or tap a time band.
You’re answering inside the first hour.
That puts you ahead of most companies. Tighten it further by giving every lead an owner and a 15-minute task.
From the research: Only 37% of companies in the HBR audit responded within an hour.
Status bands are qualitative. They are not a prediction of your results.
If you landed anywhere past the first hour, don’t read it as a verdict on your team. Read it as a routing and ownership problem, which is the fixable kind. And if you couldn’t pick a band because you don’t actually know your number, that’s the first thing to fix.
First, measure your speed to lead
I’m a HubSpot nerd, so I’ll say this plainly: you can’t fix a number you don’t track. Back in 2007, when Dr. Oldroyd’s survey asked 495 companies how long it took them to make a first call attempt, 38% answered “don’t know,” “don’t measure,” or skipped the question. I doubt it has changed much.
Here is the one-afternoon version.
Step 1: Run the HBR audit on yourself
Submit one test lead through your own website form, from a personal email, at a normal business hour. Write down the time. Then wait and see who responds, how, and when. That is literally the method HBR used on 2,241 companies. Do it again after hours on a weekend. The gap between those two results is your real problem.
Step 2: Put the timestamps in your CRM
You need two times: when the lead arrived and when a human first responded. In HubSpot, the pieces already exist:
- Create date and First conversion date tell you when the lead showed up.
- Date of first engagement records when the contact’s current owner first engaged with them.
- Lead response time is a default contact property that stores the time it took the current owner to do a first qualifying engagement.
- Contact unworked? flags contacts that have no owner, or no sales activity since the latest owner was assigned. That one is a ready-made “nobody touched this” list.
A few cautions. Date of first engagement belongs to the current owner and clears if the owner is removed. And the “time between” calculated properties need Marketing Hub Professional or Enterprise. If you can’t get a clean number in HubSpot, a spreadsheet works. Pull 30 days of leads and compute the gap by hand.
Step 3: Report four numbers every week
- Median time to first human response. Use the median, not the average, because one lead that sat for nine days wrecks an average.
- Percent answered within 5 minutes and within 1 hour during business hours.
- Number of leads never touched. HBR found 23% of companies never responded. Know your own count.
- After-hours gap. Compare leads that came in nights and weekends to the rest.
Put one person’s name on those numbers. A number nobody owns does not move.
Why leads sit
A few common practices slow teams down, whatever their size:
- Leads are pulled from the CRM once a day instead of continuously.
- Sales teams focus on generating their own leads instead of reacting quickly to people who just showed interest.
- Rules for splitting leads among reps and partners (by geography or “fairness”) slow things down.
Each of these has a direct fix, and none of them needs new headcount. Here is the fix for each practice, plus one more.
Practice 1: Daily CRM pulls
Leads are pulled from the CRM once a day instead of continuously. A lead that arrives just after the pull waits for the next one, and the clock runs the whole time.
The fix: Trigger a workflow on the form submission. Every lead enters the process the moment it arrives, with no batch to wait for.
Practice 2: Chasing own leads
Sales teams focus on generating their own leads instead of reacting quickly to people who just showed interest. Inbound leads get handled when there is spare time, which is never.
The fix: Give every inbound lead an owner and a task due in 15 minutes, so reacting is scheduled work instead of spare-time work.
Practice 3: Slow split rules
Rules for splitting leads among reps and partners (by geography or “fairness”) slow things down. Every extra rule is another place a lead can stall.
The fix: Use a simple, fast routing rule. Rotate record to owner hands leads out in turn, and a team of one or two can just assign the owner directly.
Practice 4: No clear owner
Nobody is sure whose lead it is, so everybody assumes somebody else has it. In a team of five, that’s the whole problem.
The fix: Add the escalation. If the task isn’t done in 15 minutes, notify a backup. If it still isn’t done in an hour, notify the owner of the business.
Fixes map to the HubSpot setup in the next section.
The pattern across all four is the same. Speed to lead breaks when a lead depends on someone remembering to look. Every fix replaces remembering with a rule: a trigger, an owner, a task with a clock on it, and an escalation when the clock runs out.
Watch for one more: nobody is sure whose lead it is, so everybody assumes somebody else has it. In a team of five, that’s the whole problem. Nobody owns the lead for the first ten minutes, and ten minutes becomes a day.
How to fix speed to lead with automation (the routing part)
Routing is a perfect automation job. It’s the vending machine from my AI agent vs automation guide: same trigger, same steps, same result, every time. No judgment needed, so don’t pay for an agent to do it.
Here’s the setup I’d build in HubSpot.
1. Trigger on the form submission. Build a contact-based workflow that enrolls anyone who submits your demo, quote or contact form.
2. Assign an owner instantly. Use the Rotate record to owner action to hand the contact to a rep or a team in turn. Two limits to know about. The action is available with Sales Hub or Service Hub Professional or Enterprise, and it only assigns to users who have a paid Sales or Service seat. If you’re a team of one or two, you may not need rotation. Just assign the owner directly.
3. Tell the owner right now. Add a notification step that pings the new owner (an in-app or internal email notification) and Create task with a due time of 15 minutes. A lead with an owner and a task is a lead with a clock on it.
A lead with an owner and a task is a lead with a clock on it.
John Stephenson
4. Send an instant, honest acknowledgment. An automated email that says “Got it, here’s who will reach out and when” beats silence. Be specific. “A member of our team will be in touch” is the silence you were trying to avoid. “I’ll reply by 10:30 this morning” is a promise you can keep. Offer a booking link if a call is the next step.
5. Add the escalation. If the task isn’t done in 15 minutes, notify a backup. If it still isn’t done in an hour, notify the owner of the business. This one step catches the lead that nobody picked up.
6. Handle the after-hours leads. Decide the rule before it happens. Maybe the acknowledgment goes out instantly, and the first human reply is due by 9:00 the next business morning. Write that down and measure against it.
Here is the whole thing on one page, including where automation stops and a person takes over.
Workflow
The speed to lead workflow
Top to bottom, from form to sent reply.
- Form submittedAutomation
- Owner assigned instantlyAutomation
- Owner notified, 15-minute task createdAutomationSide branchNot done in 15 minutes? Backup notified. Not done in 1 hour? Owner of the business notified.
- Instant acknowledgment email with a promiseAutomation
- AI drafts a replyAI, with approval
- Human approves and sendsHuman
Four of the six steps need no judgment at all, so they belong to automation. The escalation branch is what keeps a missed task from turning into a missed lead. Only the last two steps involve thinking, and that is where AI and a person split the work.
Where AI fits: the first-draft reply, with a human approving it
Routing gets the lead to a person fast. But a person staring at a blank email is still slow. That’s where AI can help, and it’s a different job from routing.
Writing a good first reply takes judgment. It means reading what the person wrote, picking the right detail from your site, and sounding like a human. That’s work for an AI tool, not a fixed rule.
Here’s the setup I’d use:
- The lead’s form answers (and anything you know about their company) go to an AI step.
- The AI writes a short, specific first reply and saves it as a draft or a task note. It does not send.
- The owner gets the notification, reads the draft, fixes anything wrong, and hits send. Total time: a couple of minutes instead of twenty.
How you wire it depends on your stack. I’ve used HubSpot workflows, Zapier, Make and n8n for years, and the shape of this is the same in all of them: trigger, gather context, draft, notify the human.
The approval step is not optional. Same rule I gave in the AI agent guide: nothing leaves the building until a person says yes. An AI draft that’s wrong about the lead’s problem is worse than a slow reply, because now it’s fast and embarrassing. Start by reviewing every draft. Loosen it later, only for low-stakes cases, once you’ve watched the drafts hold up for a few weeks.
Give the AI standing instructions too: your tone, what it may promise, what it must never say (pricing you haven’t approved, delivery dates, anything legal). If your team doesn’t have those written down, that’s an SOP problem, and my guide on how to write SOPs with AI shows you how to get a process out of your head in about an hour. A clear SOP is also the best set of instructions you can hand an AI tool.
What to be careful with
- Texts and calls have rules. Get consent before you text or auto-dial a lead, and check the rules that apply to you. Email is the safer first automated touch.
- Don’t fake personal. If the first message pretends a human wrote it in four seconds, people can tell. Say it’s an acknowledgment, then follow with a real reply.
- Don’t chase a perfect process. A simple, fast routing rule beats a smart scoring model that nobody finished building.
The speed to lead checklist
Run through this in order. Most small teams can finish it in a week.
Interactive
The bottom line
Your leads are already telling you they’re interested. The only question is whether a human answers while that interest is still warm.
The only question is whether a human answers while that interest is still warm.
Measure your number.
Route every lead to an owner automatically.
Let AI draft the first reply, and let a person approve it.
Then watch the number every week.
The Lesson
Speed to lead is a routing problem before it is a people problem.
The 300 leads in my audit were missed because the form was not routed to the right person. Working harder doesn’t fix that kind of failure. A simple routing rule does.
Give every lead an owner, a clock and an escalation. Then measure the number every week, with one person’s name on it.
Test your own speed
See how fast your team really answers a new lead.
The $10 Speed to Lead test sends one test inquiry through your form and logs what comes back, so you have a real number instead of a guess.
FAQ
What is speed to lead?
Speed to lead is how long it takes your business to respond to a new lead after they submit a form, request a demo or reach out. It’s measured from the moment they raise their hand to the first human response.
What is a good lead response time?
Research points to minutes, not hours. A 2007 InsideSales.com and MIT study found qualification odds were 21 times higher at five minutes than at 30. HBR found contacting a lead within an hour made a firm nearly seven times as likely to qualify it as waiting one more hour. Both are older studies, so treat them as direction, not a promise. My own target for a small B2B team: an instant acknowledgment, and a human reply within 15 minutes during business hours.
How do I measure lead response time in HubSpot?
Use default contact properties like Create date, First conversion date, Date of first engagement and Lead response time, and watch the Contact unworked? flag. Keep in mind that Date of first engagement belongs to the current owner and clears if the owner is removed. A weekly spreadsheet pull works if the CRM numbers are messy.
Can AI respond to leads for me?
It can write the first draft. I’d keep a human approving what gets sent, at least at first. AI is great at drafting a specific reply fast. It’s not great at knowing what you can promise.
Should I use an AI agent or an automation for lead routing?
Automation. Routing is a fixed rule: new lead in, owner assigned, notification out. Save the AI for the drafting step, where judgment helps. My AI agent vs automation guide has a 30-second test for picking.
Do I need HubSpot to do this?
No. The same pattern works in any CRM that can trigger on a form, assign an owner and send a notification. HubSpot is what I know best, so that’s what I walked through.
Sources
- Harvard Business Review, “The Short Life of Online Sales Leads,” March 2011: hbr.org
- InsideSales.com and MIT Lead Response Management study, Oct 16, 2007: MarketingSherpa PDF
- Chili Piper, “Chili Insights: Average B2B Vendor Response Times,” Feb 4, 2022: chilipiper.com
- Workato, “B2B Lead Response Times: What We Learned from 114 Companies,” Mar 19, 2026: workato.com
- HubSpot Knowledge Base, assign and rotate record owners using workflows: knowledge.hubspot.com
- HubSpot Knowledge Base, default contact properties: knowledge.hubspot.com
Get the Operator Brief
Every week I share what’s actually working (and what isn’t) in how I run my business with AI and automation, in the Operator Brief. It’s short, practical, and written for operators.
