How to measure speed to lead in HubSpot and Salesforce
Speed to lead is the time from a lead arriving to the first real contact. Measure it as two clocks: arrival to owner, and owner to first contact. In HubSpot, the Lead response time report gives you the second; a Time between property from First conversion date to Date of first engagement gives you the whole wait. In Salesforce, add a Date/Time field for the first contact and a report formula that subtracts Created Date and multiplies by 24 to get hours.
By Operelio team · Updated October 21, 2026
On this page10
- 1.What to measure
- 2.Decide what counts before you build anything
- 3.See HubSpot's Lead response time report
- 4.Measure the whole wait in HubSpot
- 5.Measure the wait before an owner in HubSpot
- 6.Record the first contact in Salesforce
- 7.Report on speed to lead in Salesforce
- 8.Read the numbers
- 9.Common problems
- 10.Frequently asked questions
What to measure
Speed to lead is the time between a lead arriving and someone on your team actually reaching them. Three moments matter: when the lead arrived, when it got an owner, and when that owner first made contact. The gaps between them are the two clocks.
CRM response time reports usually start the clock when an owner is assigned, so they only show the second clock. The first clock is where leads sit in a shared inbox, a downloads folder or an import queue, and it's often the longer one. Measure both, and keep them apart, because they have different fixes: a slow first clock is a routing and import problem, a slow second clock is a sales team problem.
Why the first clock matters, and what the research behind the 5-minute rule actually measured, is in speed to lead: the real statistics.
| Moment | HubSpot property | Salesforce field |
|---|---|---|
| The lead arrived | First conversion date, for form submissions; otherwise Create date, or a date property you fill on the way in | Created Date, or a Date/Time field you fill on the way in |
| It got an owner | Owner assigned date (the most recent assignment) | No standard field; track it with a custom field if you need it |
| First contact | Date of first engagement (the current owner's first engagement) | No standard field; add a Date/Time field for the first contact |
Decide what counts before you build anything
Most arguments about a speed to lead number are really arguments about its definition. Settle four things first and write them down where the team can see them.
When the clock starts
For a web form, the submission. For a lead that comes in another way, such as an email to a shared inbox, a chat or a list from an event, the moment it reached your company, which is usually earlier than the moment someone created it in the CRM. If you can't capture that moment, say so next to the number, because the number will look better than the buyer's experience.
When the clock stops
Decide whether a call attempt counts, or only a conversation, and whether an automated email counts. HubSpot's Lead response time counts a qualifying engagement such as an email, a call or a meeting. If your team sends an automatic "thanks for your interest" email the moment a form is submitted, decide whether that's contact or not, and leave it out if it isn't.
Calendar hours or working hours
A lead that arrives at 6pm on Friday and gets a call at 9am on Monday has waited 63 hours, or a few minutes of working time. Both are true. Report the one that matches your promise to buyers, and if you run a team across time zones, write down whose working hours.
Median, not average
One lead that waited three weeks will drag an average up so far it describes no lead at all. The median, the lead in the middle when you sort them by wait, is what a typical buyer experienced. Report the median, and next to it the share of leads reached inside your target.
See HubSpot's Lead response time report
HubSpot's sales analytics suite has a Lead response time report, available with Sales Hub Starter, Professional and Enterprise. It shows the time between a contact being assigned to a user and that user interacting with it: sending an email, making a call, using chat, marking a task as in progress or complete, or a meeting starting. If the contact is reassigned, the time resets.
That makes it the second clock only. It's the right report for coaching reps, and the wrong one for telling you how long buyers wait.
Open the sales reports
In your HubSpot account, click More, then go to Reporting > Reports. If More doesn't appear, go to Reporting > Reports directly. In the left sidebar menu, click Sales.
Pick the report
Select the Lead response time report. A preview shows in the center panel.
Filter it
On the Filters tab in the right panel, set the date range, group by owner or team, or pick reps and teams.
Save it
Click Save report to keep it in your reports list or add it to a dashboard.
Measure the whole wait in HubSpot
To see what the buyer experienced, from arriving to first contact, create a Time between calculation property on contacts. HubSpot already records both ends: First conversion date is when the contact first submitted a form, and Date of first engagement is when the current contact owner first engaged with them. Calculation properties need a Professional or Enterprise subscription.
Open properties
In your HubSpot account, click the settings icon in the top navigation bar. In the left sidebar menu, go to Properties, and choose Contact properties from the Select an object dropdown menu.
Create the property
Click Create property and enter the basic details, such as the name Speed to lead. Click the Field type dropdown menu and select Calculation, then click the Calculated property type dropdown menu and select Time between.
Set the two dates
For the Start date, select First conversion date. For the End date, select Date of first engagement. To count weekdays only, select the Exclude weekends checkbox.
Limit it to inbound leads
Under Conditional criteria, click Add condition if you want the calculation to run only for some contacts, for example contacts whose original source is a form on your site.
Save it
Click Create property, then add it as a column in a contacts view filtered to last month's new contacts.
Date of first engagement belongs to the current owner, so a contact that's been reassigned counts from its new owner's first engagement, not the first time anyone reached them. HubSpot stores Time between values in milliseconds and displays them in the largest unit that fits, so a wait of 2.5 hours or more shows in hours and a wait of a day or more shows in days. Exclude weekends treats 12:00am Saturday to 11:59pm Sunday in your account's time zone as weekend.
Measure the wait before an owner in HubSpot
To split the whole wait into its two clocks, create a second Time between property the same way, with Create date as the Start date and Owner assigned date as the End date. Call it something like Time to owner. If this number is most of the whole wait, the fix is in routing, not in your reps.
Create date is when the contact was created in HubSpot. For a HubSpot form, that's the submission. For a lead someone copies in from an inbox or a file, it's when they copied it, so the wait before that still doesn't show. To catch it, store the time the lead arrived in a date and time property of its own on the way in, and use that as the start date. Owner assigned date is the most recent assignment, so a reassigned contact counts from its newest owner.
Record the first contact in Salesforce
We couldn't find a standard Salesforce field for the time to first contact on a lead, so you need one of your own: a custom Date/Time field on leads, such as First Contact, filled in when the first call or email is logged. Use Date/Time rather than Date, or you can only measure in whole days.
How it gets filled depends on how your team logs activity. A common way is a record-triggered flow on tasks that writes the task's date to the lead's First Contact field, but only when that field is still blank, so later calls don't overwrite it. Ask your admin how your org records the first contact before you build a report on it, and check a few leads by hand once it's running.
If your leads arrive through a form or an import that creates them later than the buyer reached out, add a second Date/Time field for when the lead actually arrived, and fill it on the way in. Created Date is when the record was created, which for an imported list can be days after the event.
Report on speed to lead in Salesforce
With both ends recorded, a row-level formula in a leads report gives you the wait for each lead. In Salesforce, subtracting one date and time from another returns a number of days, and the part after the decimal point is the share of a 24-hour day, so 2.25 is 2 days and 6 hours. Multiply by 24 to get hours.
Start a leads report
Create a report on leads that includes Created Date and your First Contact field, then save it.
Add a row-level formula
In the Columns section of the Outline pane, click Add Row-Level Formula. Give the column a name, such as Hours to first contact.
Set the output
Set Formula Output Type to Number and Decimal Points to 1.
Write the formula
Subtract the created date from your first-contact date and multiply by 24, as in the example below. Insert both fields from the FIELDS menu rather than typing them, since formulas use API names, and your field's name will differ. Click Validate, then Apply, then Save & Run.
(First_Contact__c - CREATED_DATE) * 24
Salesforce doesn't convert time zones inside formulas, which doesn't change a gap between two date and time values but does matter if you build a formula that shows the hour of day a lead arrived. A plain subtraction counts nights and weekends, so for working hours only, ask your admin. A simple alternative is to report calendar hours with the share of leads reached the same working day alongside it. Check the result on a test lead you've timed yourself before you report on it.
Read the numbers
Export a month of leads with both clocks and look at them before you set a target. The table below is an illustration with made-up leads, to show the kind of pattern to look for.
The rep-side clock is fast for four leads of five. The whole wait is not: the average comes out at nearly 44 hours, when three of the five buyers waited under 5 hours. The median, 3 hours 30 minutes, is the honest headline. Then look at who waited longest and why: here it's the event lead and the out-of-hours lead, which is a routing and import problem, not a rep problem.
Once you have a month of numbers, break them down by lead source, by day of week and hour of arrival, and by owner. Check whether the sources that go through an import wait longest, and whether leads that arrive late in the day or on a Friday wait overnight. Set the target from your own median, then work on the slowest source first.
| Lead (illustration) | Arrived to owner | Owner to first contact | Whole wait |
|---|---|---|---|
| Demo form, Monday morning | 4h 28m | 11m | 4h 39m |
| Pricing form, Monday afternoon | 1h 50m | 8m | 1h 58m |
| Contact form, Tuesday | 3h 15m | 15m | 3h 30m |
| Trade show badge scan | 6 days | 2h | 6 days 2h |
| Demo form, Friday 5:40pm | 63h | 20m | 63h 20m |
| Median | 4h 28m | 15m | 3h 30m |
Common problems
Most strange numbers come from one of four things. Check these before you trust a month of data.
| What you see | Why | What to do |
|---|---|---|
| Imported leads look instant, or have no value | An imported lead's created date is the import, not the event, and First conversion date is only set by a form, so imported contacts have none. | Keep imports out of the inbound number, or fill an arrival date for them on the way in. |
| Some new leads have no value at all | A lead nobody has contacted yet has no Date of first engagement, so the Time between property has nothing to measure. | Count them separately as not yet reached, or your median will only describe the leads that got lucky. |
| Reassigned leads look fast | HubSpot's Lead response time resets when a contact is reassigned, and Date of first engagement and Owner assigned date both follow the current owner. A lead that sat with one rep for two days and was answered by the next in ten minutes reads as ten minutes. | If you reassign a lot, record your own arrival date and first-contact date that never change. |
| Every lead was contacted in seconds | A workflow emails every new lead as its owner, and the first engagement date is picking up that email. | Measure the first conversation, or the first call attempt, not the auto-reply. |
Frequently asked questions
What is a good speed to lead?
The best-known study found the odds of reaching a web lead called within 5 minutes were 100 times those of one called at 30, but it measured contact and qualifying, not closed deals. The 2014 Lead Response Report found the median first call, among companies that called, came after 3 hours and 8 minutes. So start from your own median and bring the slowest lead source down first.
Does HubSpot's Lead response time include the time before a lead has an owner?
No. The Lead response time property and report count from when the contact is assigned to a user, and the time resets if the contact is reassigned. To see the wait before that, create a Time between property from Create date to Owner assigned date, or from First conversion date to Date of first engagement for the whole wait.
Does Salesforce have a lead response time field?
We couldn't find a standard one. You can add a Date/Time field for the first contact on leads, fill it when the first call or email is logged, and measure from Created Date with a row-level formula in a report. Subtracting the two gives days, so multiply by 24 for hours.
Should I measure speed to lead in working hours?
Report whichever matches your promise to buyers, and say which it is. HubSpot's Time between property can exclude weekends. Salesforce formulas count calendar time, so working hours there need your admin. A simple option is calendar hours, shown with the share of leads reached the same working day.
Should I use the average or the median?
The median. A handful of leads that waited days will pull an average far above what a typical buyer experienced. Report the median and the share of leads reached inside your target.
Ready to get started?
Upload a file and run your first transformation. Free, no credit card required.