How Do You Calculate Speed to Lead?

Speed to lead is the time between when a prospect submits a form, calls, or messages your business and when a real reply reaches them. To calculate it, subtract the lead's timestamp (the moment they submitted the form, texted, or your phone rang) from the timestamp of your first substantive response, then average that number across a set period, like a week or a month.
What Exactly Counts as the Lead's "Start Time"?
The clock starts the instant the lead takes action, not when a rep notices it. That means the timestamp on the form submission, the inbound call log, the chat message, or the ad click-to-call, whichever channel brought the lead in. If your CRM timestamps leads a few minutes after they actually came in (common with batched webhook delivery), your speed-to-lead math will look better than reality, so it's worth checking that the source timestamp, not the CRM's "created" timestamp, is what you're measuring from.
What Counts as the "Response" That Stops the Clock?
An auto-reply or a generic "thanks, someone will be in touch" text doesn't count. The clock should stop at the first response that actually engages the lead: a question about their need, a scheduling offer, or an answer to something they asked. Teams that count autoresponders as the finish line end up with speed-to-lead numbers that look fast but don't reflect when a human (or a system acting in a rep's voice) actually started the conversation.
What's the Basic Formula?
For a single lead:
Response time = First meaningful reply timestamp − Lead intake timestamp
For a team or a time period, average those individual numbers:
Average speed to lead = Sum of all response times ÷ Number of leads in the period
It helps to break that average down further, because one slow outlier (a lead that sat overnight) can skew a weekly average even if most leads got a fast reply. Two numbers worth tracking side by side:
| Metric | What it tells you |
|---|---|
| Median response time | What a typical lead experiences |
| % of leads replied to within your target window | How consistent your team actually is |
How Do You Track It Across Channels?
Most businesses get leads through more than one door: web forms, phone calls, text, email, sometimes LinkedIn. Each channel needs its own timestamp pair, because a phone call that goes to voicemail has a different "start" than a form submission that sits in an inbox. If leads come in across SMS, MMS, email, voicemail, and LinkedIn, the simplest way to get one honest number is to pull all of it into a single conversation thread per lead, which is the approach fuelAI's platform takes, explained on the how it works page, rather than calculating speed to lead separately for every tool.
What Should You Do With the Number Once You Have It?
Once you know your real average and your worst-case outliers, the useful next step is finding where the delay happens: after-hours leads, leads that come in during a rep's existing call, or leads that land on a shared inbox nobody owns. A system that qualifies, replies, and books on a rep's behalf while they're unavailable closes that gap without needing a rep glued to their phone. That's the function covered on the features page, and it's built around the idea that the problem is usually presence, not effort: reps aren't ignoring leads, they're just not there the moment the lead shows up.
For aesthetics and med-spa practices specifically, lead timing tends to be even less predictable, since consults often come in during treatment hours when the front desk can't step away. The approach for that vertical is laid out on the aesthetics page.
If your leads come through a specific ad funnel or landing page, it's worth calculating speed to lead separately for that source too, since paid leads often decay faster than organic ones. See how that's handled on the lead page example, and browse how it's played out for other businesses in the case studies.
FAQ
Does speed to lead include weekends and after-hours leads? Yes, if you want an honest number. Excluding off-hours leads from your calculation hides exactly the gap that matters most, since that's when most leads go unanswered.
Should I calculate speed to lead per rep or for the whole team? Both. A team average can look fine while one rep is consistently slow, so per-rep tracking shows you where the real delay is happening.
What if my CRM doesn't log response timestamps automatically? You can still calculate it manually from call logs, text timestamps, and email send times, though it's slow to do by hand across a full month. Systems that handle replies directly, like the one described on fuelAI's site, log both timestamps automatically as part of the conversation.