What is speed to lead?
Speed to lead is the time between a prospect filling in your form and the first time someone on your team tries to reach them. Here's what the research says a good response time looks like, what most companies manage, and how to shorten yours.

Speed to lead is how fast your team gets back to someone who has just asked to hear from you. It's one of the few sales numbers you can shorten without hiring anyone, and this page covers what it is, what a good number looks like, and how to measure and improve yours.
The short version
- Speed to lead is the time from a prospect's form submission to your team's first human contact attempt. Track time to first live conversation alongside it.
- The research points to minutes. In 2007 phone data, leads first called within 5 minutes had 100 times the odds of being contacted and 21 times the odds of being qualified, compared with leads first called at 30 minutes.
- Most companies are slow. In Harvard Business Review's 2011 audit of 2,241 U.S. companies, 37% responded to a test lead within an hour and 23% never responded.
- A workable standard: call high-intent requests within minutes during working hours, and never let any inbound lead wait past the same working day.
- Common delays sit between the form and the rep: syncs that poll on a timer, leads with no owner, alerts that only reach owners. Measure from the form, then fix the slowest step.
What is speed to lead?
Speed to lead, also called lead response time or speed to contact, is the time between a prospect submitting interest, usually through a web form or demo request, and your team's first human attempt to contact them, with the clock starting at the form submission.
The start point matters. A prospect doesn't see your CRM sync or your assignment queue. They see the time between pressing submit and hearing from a person, so that's where the clock starts.
So does the stop point. An auto-reply doesn't count. A call dialled or a message a person actually wrote does.
In practice there are two numbers worth tracking. Time to first attempt tells you how fast someone tries. Time to first live conversation tells you how fast someone actually talks to the prospect. They can be days apart, and it's the second one that moves a deal forward.
Why does speed to lead matter?
Speed to lead matters because your chance of reaching and qualifying an inbound lead drops within the first hour, and in phone data it drops within minutes.
The clearest published figure comes from Harvard Business Review. In a 2011 study of 1.25 million sales leads received by 42 U.S. companies (29 B2C and 13 B2B), firms that tried to contact a lead within an hour of receiving it were nearly 7 times as likely to qualify it as firms that tried even an hour later. They were more than 60 times as likely to qualify it as firms that waited 24 hours or longer.
The authors defined qualify as having a meaningful conversation with a key decision maker. It's a comparison between firms, measured in hours.
The minute-level figures are older. In the 2007 Lead Response Management study (InsideSales.com data analysed with James Oldroyd; six companies, phone dials only), leads first called within 5 minutes had 100 times the odds of being contacted, and 21 times the odds of being qualified, compared with leads first called at 30 minutes.
The gap between those two multiples is worth noticing. Waiting costs you the chance to reach someone far faster than it costs you the chance to qualify them.
How the odds fall when the first call waits
Odds relative to a first call inside the 5-minute window. Bar length on a log scale.
Contact
Odds of reaching the lead by phone
Qualify
Odds the dial led to a qualified lead
Waiting 30 minutes cut the odds of contact 100 times, and the odds of qualifying 21 times. Speed mostly buys the connected call.
Odds, not probability. Phone dials to web-form leads, six companies, 15,000+ leads. Contact: a connected call of 2 to 6 minutes. No base rate was published and the study did not measure closed deals.
Source: Lead Response Management study, InsideSales.com with James Oldroyd, 2007 (PDF, pages 2 and 5)
Two things to keep straight when you quote these. The 2007 figures are odds, and HBR's are probabilities, so "21 times the odds of qualifying" isn't the same as "21 times more likely". And qualifying a lead means getting a real conversation, not closing a deal. Neither study measured closed deals.
What is the average lead response time?
The published average lead response time is 42 hours, from HBR's 2011 audit of 2,241 U.S. companies, each sent one web-generated test lead, and it counts only the companies that responded within 30 days.
Here's how that audit broke down: 37% responded within an hour, 16% within one to 24 hours, 24% took more than 24 hours, and 23% never responded at all.
How fast 2,241 U.S. companies answered a test lead
Each company was sent one web-generated test lead. Share of companies by time to first response.
- 37% within an hour
- 16% 1 to 24 hours
- 24% more than 24 hours
- 23% never responded
Average response time among companies that replied within 30 days: 42 hours
The share with no reply at the end of each test
Five published audits. Each row names its own sample and cut-off.
HBR audit, 2011
2,241 U.S. companies. Reported as never responded.
InsideSales.com, 2013 audit (2014 report)
9,538 U.S. companies. Window not stated.
Drift, 2017
433 B2B SaaS companies. No response within five business days.
Drift, 2018
512 B2B companies. No response within five days.
Chili Piper, 2022
Software vendors, sample size not published. No response within seven business days.
Windows differ, so compare the pattern, not the exact figures.
Every test after 2011 was run by a vendor selling response, chat or routing software. A co-author of the 2011 audit was CEO of InsideSales.com, which ran the 2013 one.
Because companies that never answered can't have a response time, they drop out of the 42 hours. The figure describes the companies that eventually replied.
You'll also see 47 hours quoted, but that's a rounding of a different, unpublished vendor figure. The published average is 42.
An average is also a poor way to describe response times, because a few very slow companies drag it upward. InsideSales.com's 2014 report shows this clearly. Among the 2,142 companies that phoned a test lead in its 2013 audit, the median first call came at 3 hours 8 minutes. The average was 61 hours 1 minute, pulled up by late responders, and 162 of those companies took more than a week. The report itself says the median is the more informative number.
Median 3h 8m, mean 61h 1m. Same companies.
Of 9,538 companies sent a test web lead in 2013, 47% did not respond and 22% phoned at least once. Rows count those that phoned, by time to their first call.
Median: 3h 8m, half phoned sooner
Mean: 61h 1m, pulled up by the slowest
Rows are categories, not a time scale.
121 of the 2,142 phoned inside five minutes (calculated from the report's Figure 2).
Source: InsideSales.com, Annual 2014 Lead Response Report, fieldwork 2013, pp. 8 to 11 and Figure 2. Figure 2's columns sum to 2,143, one more than the 2,142 the report states.
Source: InsideSales.com, Annual 2014 Lead Response Report, fieldwork 2013, pp. 8 to 11 and Figure 2. Figure 2's columns sum to 2,143, one more than the 2,142 the report states.
That's why I report medians for my own measurements. One lead that sat over a long weekend can drag a month's average by hours.
Not responding at all is common too. In InsideSales.com's 2013 audit, 47% of 9,538 companies did not respond to the test lead.
What is a good lead response time?
For inbound leads, a good response time is minutes. That's where the research points, although no study sets a single number you have to hit.
The widely quoted 5-minute rule comes from the 2007 phone study, which grouped first dials into five-minute windows over the first three hours. Moving the first call from 5 minutes to 10 lowered the odds of contacting the lead by 5 times, and lowered the odds that a dial led to a qualified lead by 4 times. It often gets credited to Harvard Business Review, but HBR's 2011 article reported response in hours.
Newer data is thinner and points the same way:
On the published audits, the gap most companies have to close is between hours and minutes.
Here's the standard I'd work to. It's guidance built on the direction of the research, not a published benchmark:
- High-intent requests (a demo, pricing, contact sales): a call within minutes during working hours.
- Every other inbound lead: a human attempt the same working day, never later.
- After hours: a named person owns the queue, so nothing waits for whoever logs in first.
No published study sets a benchmark specifically for high-ticket sales. There's more on that at the end of this page.
Speed to lead statistics
These are the speed to lead numbers you'll see quoted most often, next to what each source actually measured. Where a quote has drifted from the original, the table gives the original wording and links to the document.
Nine speed to lead statistics, checked against their sources
- 1Holds
- 1Holds, narrower than quoted
- 5Misquoted
- 2No origin found
- 1
“Calling in 5 minutes makes you 21x more likely to convert”
Misquoted
What the source says: 21 times the odds of qualifying the lead, which is neither 21 times more likely nor a conversion, when first called at 5 minutes instead of 30. Phone dials, six unnamed companies, 2007. The study says it did not address close ratios.
InsideSales.com and James Oldroyd, 2007 (PDF) (opens in a new tab)
- 2
“100x more likely to reach the lead in 5 minutes than in 30”
Misquoted
What the source says: 100 times the odds of contact, which is not 100 times more likely. Contact means a live phone connection lasting 2 to 6 minutes. Same 2007 study, same six companies.
InsideSales.com and James Oldroyd, 2007 (PDF) (opens in a new tab)
- 3
“The average company takes 47 hours to respond”
Misquoted
What the source says: HBR published 42 hours, averaged only over U.S. companies that replied within 30 days, from an audit of 2,241. The 47 is a rounding of a vendor figure. Its closest real origin is 46 hours 53 minutes in a 2012 Forbes column by an InsideSales.com co-founder, with no published method.
Harvard Business Review, 2011 (opens in a new tab)Forbes column, 2012 (archived) (opens in a new tab)
- 4
“78% of customers buy from the company that responds first”
No origin found
What the source says: No report, date, sample or method has ever been published. Blogs credit a “Lead Connect survey”, and the trail ends at the homepage of a software product.
- 5
“35 to 50% of sales go to the vendor that responds first”
No origin found
What the source says: Earliest source is a 2010 vendor blog post crediting unnamed “sales studies”. It is about the agent who makes first contact, not about how fast anyone answers an inbound lead.
- 6
“Calling within a minute improves conversion 391%”
Holds, narrower than quoted
What the source says: Velocify’s 2013 chart does show 391% at one minute, but never states the baseline it is measured against, and calling at 30 minutes still shows a 62% improvement.
- 7
“HBR’s 5-minute rule”
Misquoted
What the source says: HBR measured response in hours: within an hour, one to 24 hours, more than 24. The 5-minute window comes from the 2007 phone study.
Harvard Business Review, 2011 (opens in a new tab)2007 study (PDF) (opens in a new tab)
- 8
“Your odds of qualifying drop 400% after 5 minutes”
Misquoted
What the source says: The 2007 study says the odds that a dial leads to a qualified lead fall 4 times from 5 to 10 minutes. A fall of 4 times is a 75% drop, not 400%.
InsideSales.com and James Oldroyd, 2007 (PDF) (opens in a new tab)
- 9
“Firms that try to contact a lead within an hour are nearly 7x as likely to qualify it”
Holds
What the source says: A separate HBR study of 1.25 million leads at 42 U.S. companies, compared with firms that tried even an hour later. Qualify means a meaningful conversation with a key decision maker.
Checked 28 September 2026 against the primary documents. ‘Narrower than quoted’ means the number is real but the usual wording claims more than the source measured.
Most of this research was published by companies that sell lead response or routing software, so read the multiples as direction rather than a forecast for your own team.
If you want the underlying datasets, here's each one in date order, with its sample and what it measured:
Every dataset behind the speed to lead numbers
Eleven datasets, oldest first. Results are in each source’s own terms. Every name links to the document it was read from.
- 2007Vendor data
Lead Response Management study, InsideSales.com with James Oldroyd
Sample: 6 companies, 15,000+ leads, 100,000+ call attempts
Measured: Odds of contact and of qualifying, by minute of first call. Phone. Close rates not measured.
- 100xodds of contact
- 21xodds of qualifying
First call at 5 vs 30 minutes
- 2011Edited, vendor co-author
The Short Life of Online Sales Leads, Harvard Business ReviewThe company audit
Co-author Elkington was InsideSales.com CEO
Sample: 2,241 U.S. companies, one test lead each
Measured: How long each company took to respond to a web-generated lead
- 37%within an hour
- 23%never
- 42haverage
Average counts companies that responded within 30 days
- 2011Edited, vendor co-author
The Short Life of Online Sales Leads, Harvard Business ReviewThe separate lead study, same article
Same authors as the audit
Sample: 1.25M leads, 42 U.S. companies (29 B2C, 13 B2B)
Measured: Qualifying, by hour of first contact attempt. Channel not stated.
- nearly7xas likely, within an hour vs an hour later
- more than60xvs 24 hours or longer
Qualify: a meaningful conversation with a key decision maker
- 2013Peer reviewed
Journal of Marketing study, Sabnis, Chatterjee, Grewal and Lilien
Sample: 461 reps at four large B2B firms, survey
Measured: Share of time reps give to marketing leads. Not response speed.
Time given to marketing leads rises most with how good reps judge marketing’s lead prequalification to be
- 2013Vendor data
The Ultimate Contact Strategy, Velocify
Sample: Almost 3.5M leads from H1 2012, 400+ client companies
Measured: Lead conversion by time of first call attempt. Phone. Conversion not defined.
- 391%“improvement” at one minute
Baseline not stated
- 2014Vendor data
Annual 2014 Lead Response Report, InsideSales.com
Sample: 9,538 U.S. companies, one test web lead each, audit run in 2013
Measured: Whether and how fast companies followed up. Secret shopper.
- 47%did not respond
- 3h 8mmedian first call
Median among the 2,142 companies that phoned
- 2017Vendor data
We Tested The Response Times Of 433 Sales Teams, Drift
Sample: 433 B2B SaaS companies
Measured: Response to lead, demo and sales-inquiry forms. Secret shopper. “Response” not defined.
- 7%within five minutes
- 55%no reply in five business days
- 2018Vendor data
The Drift Lead Response Report, Drift
Sample: 512 B2B companies
Measured: Response to a request sent through each website, over five days
- 10%in five minutes or less
- 58%no reply in five days
- 2020Vendor data
We Tested 114 B2B Companies’ Lead Response Times, Workato
Sample: 114 B2B companies, demo requests
Measured: Email and phone follow-up to a demo request. Window not disclosed.
- 31%responded by phone
- 0phoned within five minutes
- 2021Vendor data
Lead Response Management 2021, InsideSales (as XANT)
Sample: 5.7M leads, 400+ companies, own platform data
Measured: “Conversion” by time of first call. Conversion never defined.
- 8xconversion
First call within 5 minutes vs 6 minutes or later
- 2022Vendor data
Chili Insights: Average B2B Vendor Response Times, Chili Piper
Sample: Demo requests at software vendors. Number tested not published.
Measured: Time to respond to a manual demo request, over seven business days
- 7%under 60 seconds
- 4h 50maverage
Average counts companies that replied
10 of 11 datasets came from a vendor selling lead response, chat, routing or scheduling tools, or from an article co-written by one vendor's CEO. The one peer-reviewed study measured time allocation, not response speed.
Every dataset behind the speed to lead numbers
Eleven datasets, oldest first. Results are in each source's own terms. Every name links to the document it was read from.
- Published 2007
Lead Response Management study, InsideSales.com with James Oldroyd
Produced by: Vendor dataSample: 6 companies, 15,000+ leads, 100,000+ call attempts
What it measured: Odds of contact and of qualifying, by minute of first call. Phone. Close rates not measured.
Headline result:- 100xodds of contact
- 21xodds of qualifying
First call at 5 vs 30 minutes
- Published 2011
The Short Life of Online Sales Leads, Harvard Business ReviewThe company audit
Produced by: Edited, vendor co-authorCo-author Elkington was InsideSales.com CEOSample: 2,241 U.S. companies, one test lead each
What it measured: How long each company took to respond to a web-generated lead
Headline result:- 37%within an hour
- 23%never
- 42haverage
Average counts companies that responded within 30 days
- Published 2011
The Short Life of Online Sales Leads, Harvard Business ReviewThe separate lead study, same article
Produced by: Edited, vendor co-authorSame authors as the auditSample: 1.25M leads, 42 U.S. companies (29 B2C, 13 B2B)
What it measured: Qualifying, by hour of first contact attempt. Channel not stated.
Headline result:- nearly7xas likely, within an hour vs an hour later
- more than60xvs 24 hours or longer
Qualify: a meaningful conversation with a key decision maker
- Published 2013
Journal of Marketing study, Sabnis, Chatterjee, Grewal and Lilien
Produced by: Peer reviewedSample: 461 reps at four large B2B firms, survey
What it measured: Share of time reps give to marketing leads. Not response speed.
Headline result:Time given to marketing leads rises most with how good reps judge marketing’s lead prequalification to be
- Published 2013
The Ultimate Contact Strategy, Velocify
Produced by: Vendor dataSample: Almost 3.5M leads from H1 2012, 400+ client companies
What it measured: Lead conversion by time of first call attempt. Phone. Conversion not defined.
Headline result:- 391%“improvement” at one minute
Baseline not stated
- Published 2014
Annual 2014 Lead Response Report, InsideSales.com
Produced by: Vendor dataSample: 9,538 U.S. companies, one test web lead each, audit run in 2013
What it measured: Whether and how fast companies followed up. Secret shopper.
Headline result:- 47%did not respond
- 3h 8mmedian first call
Median among the 2,142 companies that phoned
- Published 2017
We Tested The Response Times Of 433 Sales Teams, Drift
Produced by: Vendor dataSample: 433 B2B SaaS companies
What it measured: Response to lead, demo and sales-inquiry forms. Secret shopper. “Response” not defined.
Headline result:- 7%within five minutes
- 55%no reply in five business days
- Published 2018
The Drift Lead Response Report, Drift
Produced by: Vendor dataSample: 512 B2B companies
What it measured: Response to a request sent through each website, over five days
Headline result:- 10%in five minutes or less
- 58%no reply in five days
- Published 2020
We Tested 114 B2B Companies’ Lead Response Times, Workato
Produced by: Vendor dataSample: 114 B2B companies, demo requests
What it measured: Email and phone follow-up to a demo request. Window not disclosed.
Headline result:- 31%responded by phone
- 0phoned within five minutes
- Published 2021
Lead Response Management 2021, InsideSales (as XANT)
Produced by: Vendor dataSample: 5.7M leads, 400+ companies, own platform data
What it measured: “Conversion” by time of first call. Conversion never defined.
Headline result:- 8xconversion
First call within 5 minutes vs 6 minutes or later
- Published 2022
Chili Insights: Average B2B Vendor Response Times, Chili Piper
Produced by: Vendor dataSample: Demo requests at software vendors. Number tested not published.
What it measured: Time to respond to a manual demo request, over seven business days
Headline result:- 7%under 60 seconds
- 4h 50maverage
Average counts companies that replied
10 of 11 datasets came from a vendor selling lead response, chat, routing or scheduling tools, or from an article co-written by one vendor's CEO. The one peer-reviewed study measured time allocation, not response speed.
How do you measure speed to lead?
Measure speed to lead on your own recent inbound leads, from the form submission timestamp to the first human contact attempt, and report the median.
Here's the method I use before changing anything:
- Take the last 100 inbound leads. Form fills and demo requests, not imported lists.
- Start the clock at form submission. Not at CRM creation or owner assignment.
- Stop it at the first human attempt. Separately, record the first live conversation.
- Report the median and the slowest 10%. The median is your typical lead. The slowest tenth is where the process breaks.
- Split by source, and by in-hours versus after-hours. This shows you which channel or time window is doing the damage.
- Count the leads nobody contacted. They have no response time, so they vanish from every average.
Where each response-time metric starts its clock
One inbound lead, top to bottom. Schematic, not to scale: the spacing shows order, not time. Each bar is one metric and spans the events it counts.
- A
- Invisible to the default reportForm to owner assigned. HubSpot’s Lead response time report never sees it.
- B
- Speed to lead, measured from the formStarts where the buyer’s wait starts. The one to report.
- C
- HubSpot Time to First Touch (Leads object)Starts at lead record creation. A property, not a report.
- D
- HubSpot Lead response time reportResets on reassignment. Dashed end: a task marked in progress can count as a response.
Source: HubSpot Knowledge Base, sales analytics reports and default lead properties, read 28 September 2026.
Source: HubSpot Knowledge Base, sales analytics reports and default lead properties, read 28 September 2026.
What your tool’s own number measures
HubSpot: Lead response time report
- Starts at
- When a contact is assigned to a user
- Stops at
- That user’s first qualifying interaction
If you use HubSpot, note what its built-in Lead response time report measures. It starts when a contact is assigned to a user and stops at that user’s first qualifying interaction, and it resets if the contact is reassigned. So any time a lead spends without an owner, including the time since the form was submitted, isn’t captured, and qualifying interactions include marking a task in progress or complete, so a response can register without anyone contacting the lead.
HubSpot: Time to First Touch
- Starts at
- Lead creation
- Stops at
- First outreach activity
HubSpot has a closer measure on the Leads object in Sales Hub Professional and Enterprise. The read-only Time to First Touch property records the time between lead creation and first outreach activity. If a workflow creates the lead record some time after the form submission, that delay still sits outside the clock, and it’s a property rather than a pre-built report.
Pipedrive: No native metric
- Starts at
- "Add time"
- Stops at
- "Marked as done time"
In Pipedrive, I couldn’t find a native lead response time or first-touch metric in its Insights documentation. Its activity reports expose timestamps such as "Add time" and "Marked as done time", so you compare those yourself.
Aircall: Last Aircall call timestamp
- Records
- Every call updates it
- Catch
- Holds the last call, not the first
If your team calls from Aircall with the HubSpot integration, Aircall updates a "Last Aircall call timestamp" property on the contact with every call. It holds the last call, not the first, so copy it into your own property with a workflow the first time it populates. Calls made outside Aircall won’t appear in it, and an inbound call appears to set it too.
Like several revenue operations KPIs, this is a number your CRM won't calculate on its own. You build it once.
How to improve speed to lead
You improve speed to lead by removing the waits between the form and the first call, one step at a time, starting with the slowest.

Slow response usually comes from the steps between the form and the rep rather than from rep effort. The HBR authors said so in 2011, noting that more research was needed, and listed these among the reasons:
Reasons include the practice of retrieving leads from CRM systems' databases daily rather than continuously; sales forces focused on generating their own leads rather than reacting quickly to customer-driven signs of interest; and rules for distributing sales leads among agents and partners based on geography and "fairness."
The tools have changed since then, but the shape hasn't. A lead travels from the form, into the CRM, to an owner, to an alert, to a person who's free, to a first dial, and each step has its own way to lose time.
Where the minutes go between a form and the first dial
The six hops a new inbound lead passes, what holds it at each, and the fix.
Hops 1 to 3 are not captured by HubSpot's Lead response time report
1. Form
Your clock starts here
Every later delay counts from the moment the form is submitted.
Fix: Keep the submission timestamp and measure from it.
2. Sync into the CRM · Your automation layer
Waits up to one polling interval
Zapier polling triggers check every 15 min on Free, 2 on Professional, 1 on Team and Enterprise. Make scenarios run every 15 min by default.
Fix: Switch to an instant or webhook trigger. Make runs a webhook scenario immediately.
3. Assign an owner · Your CRM
Can wait on daily pulls and routing rules
HBR’s authors, 2011: CRM leads pulled daily rather than continuously, and routing rules by geography and “fairness”.
Fix: Assign on arrival. Add a catch-all rule for any lead that matches no other rule.
4. Alert a person
The alert goes to nobody
In HubSpot, a form alert set only to “Notify contact owner” sends nothing when the contact has no owner.
Fix: Alert named users regardless of ownership, or send a workflow Slack alert with a Call contact button.
5. Book or reach the rep · Books a meeting from the form
The prospect cannot book
Routed to a Chili Piper rep without a Concierge licence, the prospect can’t book and drops to Not Scheduled.
Fix: Let high-intent demo requests book a meeting on the form.
6. First dial
Your clock stops here
Aircall writes a Last Aircall call timestamp onto the HubSpot contact on every call, so a lead with no Aircall call logged yet shows it empty.
Fix: It holds the last call, so copy the first one into its own property.
Sources: HBR, 2011 · HubSpot, Lead response time report · HubSpot, form notifications · HubSpot, Slack notifications · Zapier, how triggers work · Make, scheduling · Make, webhooks · Chili Piper, Concierge flows · Aircall, HubSpot properties.
Marks are each vendor's own trademark, shown to identify the product at the hop where it operates. No affiliation or endorsement is implied.
Sources: HBR, 2011 · HubSpot, Lead response time report · HubSpot, form notifications · HubSpot, Slack notifications · Zapier, how triggers work · Make, scheduling · Make, webhooks · Chili Piper, Concierge flows · Aircall, HubSpot properties.
Marks are each vendor's own trademark, shown to identify the product at the hop where it operates. No affiliation or endorsement is implied.
- Measure from the form
Run the measurement above first. Without a baseline that starts at the form, you'll fix the step that feels slow instead of the one that is.
- Replace polling with webhooks
Most Zapier triggers poll on an interval set by your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. A Make scenario runs every 15 minutes by default. A webhook fires when the form does. Zapier's webhook trigger needs a paid plan, Make runs a webhook scenario immediately by default, and in n8n the form should post to the production webhook URL, not the test one.
- Assign on arrival, with a catch-all
Every lead should get an owner when it's created, and a lead that matches no routing rule should still land on a named person. In GoHighLevel, the "Assign to User" workflow action rotates new contacts across the reps you pick, with the rep's notification placed after the assignment step. Who maintains these rules is a governance question as much as a routing one.
- Alert named people, regardless of ownership
In HubSpot, a form alert set only to "notify contact owner" sends nothing when the contact has no owner. Use "Add users to notify" so named users or teams hear about every submission. On Professional or Enterprise, a workflow can post new contacts to Slack with a "Call contact" button, so the alert is one tap from the dial.
- Let high-intent demo requests book on the form
Chili Piper Concierge checks a form submission against your routing rules, routes it to a rep and shows that rep's calendar. Every rep on a path needs a Concierge licence, or matching prospects can't book, and the mandatory Catch All path decides where everyone else goes.
- Cover after-hours with a human handoff
Leads that arrive at 21:00 still start a clock. Give them a named on-call person, a booking link on the form, and a morning queue sorted by submission time. The first contact should still be a person.
One peer-reviewed study adds the human side. In a Journal of Marketing survey of 461 reps at four large B2B firms (Sabnis, Chatterjee, Grewal and Lilien, 2013), the share of time reps gave marketing-generated leads rose most with how good they judged marketing's prequalification to be, which makes your qualification rules part of the fix.
Once the path is fast, clear exit criteria on your pipeline stages are what stop the lead stalling again one step later.
Speed to lead tools
There isn't one speed to lead tool. Speed to lead is a chain, and each link in it is a different kind of software.
Five jobs in the chain, and the software that does each one
Each row is one job. The tools in a row are alternatives: you pick one.
- CRM
HubSpot
Pipedrive
GoHighLevel
Salesforce
The CRM stores the lead, assigns it an owner and holds the timestamps you measure from. Assignment rules live here, so this is where an unowned lead sits waiting.
- Automation
Zapier
Make
n8n
Automation moves the form submission into the CRM and triggers whatever happens next. Whether it polls on a timer or fires on a webhook decides how long that first step takes.
- Alerting
Slack
An alert puts the new lead in front of a person, in the place they already work. It only helps if it reaches someone whether or not the lead has an owner yet.
- Scheduling
Chili Piper
Calendly
A scheduling tool lets a prospect pick a time with a rep instead of waiting for a callback. It’s most useful on high-intent requests, where the prospect already wants the meeting.
- Calling
Aircall
The dialler is where the first attempt actually happens, and its call log gives you the timestamp that stops your clock.
Which one to fix first? The step where your leads wait longest. A booking tool won't help much if leads sit in a queue with no owner before anyone sees them, and you'll only know where they wait once you've measured.
Does speed to lead matter for high-ticket sales?
Yes. Speed to lead matters for high-ticket sales because reachability drops fast and most companies are slow to respond, and nothing in the data suggests that changes when the deal gets bigger.

What doesn't carry over is the exact multiples. HBR's 1.25-million-lead study was 29 B2C companies out of 42, and the six companies in the 2007 study are unnamed. No study here measured closed revenue, and none looked at high-ticket sales specifically.
Speed gets you the conversation. The sales process decides the deal: who takes the call, what they know before they pick up, and what happens after it. A fast first call into a process that can't convert it just loses the lead sooner.
Sources
InsideSales.com and Dr. James Oldroyd, Lead Response Management study, presented October 2007. Odds of contact and qualification by first-call time, pages 2, 4 and 5; “This study did not address close ratios”, page 1. Read from the 2008 printout (2007)
Harvard Business Review, The Short Life of Online Sales Leads, Oldroyd, McElheran and Elkington, March 2011. The 2,241-company audit, the separate 1.25-million-lead study, and the authors' diagnosis (2011)
Velocify, The Ultimate Contact Strategy, Sales Optimization Study. Leads generated in the first half of 2012; Figure 1, improvement on lead conversion rate by time to first call (2013)
All 24 sources and how they were checked
Journal of Marketing, Sabnis, Chatterjee, Grewal and Lilien, on sales reps' follow-up of marketing leads, Vol. 77 No. 1, pages 52 to 67. Read from the abstract and the accepted manuscript (2013)
InsideSales.com, Annual 2014 Lead Response Report. 2013 audit of 9,538 U.S. companies; median and average first call, pages 8 and 9; Figure 2 histogram (2014)
Drift, We Tested The Response Times Of 433 Sales Teams, published 27 February 2017. Read from the archived original (2017)
Drift, The Drift Lead Response Report 2018, published 24 April 2018. 512 companies, five-day window. Read from the archived original (2018)
Workato, We Tested 114 B2B Companies' Lead Response Times, published 31 August 2020. Read from the archived page (2020)
Chili Piper, Chili Insights: Average B2B Vendor Response Times, 4 February 2022. Sample size not published (2022)
InsideSales (XANT), Lead Response Management 2021 infographic. The vendor-stated 8x conversion figure (2021)
Forbes, Ken Krogue, contributor post, 12 July 2012. The 46 hours 53 minutes figure. Read from an archived snapshot (2012)
InsideSales.com, Blog post, 19 July 2010. The earliest findable source of the 35 to 50% figure, attributed to unnamed “sales studies” (2010)
HubSpot, Create sales reports in the sales analytics suite, last updated 18 June 2026. Lead response time report definition (2026)
HubSpot, HubSpot's default lead properties, last updated 17 August 2026. Time to First Touch (2026)
HubSpot, Set up your form submission notifications, last updated 15 June 2026 (2026)
HubSpot, Manage your notifications in Slack, last updated 10 August 2026 (2026)
HubSpot, Choose your workflow actions, last updated 7 September 2026. Workflows require a Professional or Enterprise subscription (2026)
Pipedrive, Insights report types, last updated 3 September 2026, with the lead performance and activities performance report pages (2026)
Zapier, How Zap triggers work, updated 29 May 2026. Polling intervals by plan (2026)
Zapier, Trigger Zaps from webhooks. The Catch Hook trigger is listed for Professional, Team and Enterprise, not Free (2026)
Make, Schedule a scenario, updated 30 June 2026, and the webhooks help page (2026)
Aircall, HubSpot Workflows Custom Properties. Undated, accessed 28 September 2026 (2026)
HighLevel, How to automatically assign users to leads in workflows, modified 23 February 2024 (2024)
Chili Piper, Creating a Concierge Flow, edited 24 September 2026 (2026)
Every figure on this page was checked against its primary document on 28 September 2026 and is linked above. The multiples come from phone dials and from mostly consumer or undisclosed samples, and no dataset here measures closed revenue.
Common questions
If you want a second pair of eyes on your own setup, Salestruct runs a free diagnostic.
Read next.
All articlesCRM pipeline stages: give every one an exit criterion
Your CRM ships with stages named after things your rep did, and it multiplies your forecast by a number attached to each one. Booking a presentation does not make a deal 60% likely to close, but that is what the default pipeline asserts.
Revenue operations KPIs your CRM cannot calculate
Most RevOps KPI lists mix three different kinds of number: ones the CRM computes for you, ones it can compute once you add a field, and ones it will never hold the data for. Nobody labels which is which, so teams build dashboards on numbers the system was never able to produce.

