Speed-to-lead as a metric: how to measure it so it can be managed
Response time is easy to state and hard to measure honestly. The timestamps to capture, the definition of a 'response', the statistics that matter, and how to report it per person without turning it into surveillance.
25 Nov 2025 · 2 min read · by HeiSyn
Every team believes it responds quickly, and almost none can produce the number. Speed-to-lead is worth measuring because it is one of the few metrics that predicts conversion directly and that a team can change within a week. Measuring it well takes a few decisions up front.
Two timestamps
When the lead arrived: the form submission, the message received, the call missed — the moment the customer acted, not the moment a record was created after a sync. When the first meaningful response happened: an outbound call attempt, a personal email, a message from a person or a qualified agent — not the auto-acknowledgement. Both stored on the lead record.
Define 'response' strictly
An automated 'we got your message' is not a response; a call attempt that went to voicemail is; an agent conversation that qualified and booked is. Write the definition down and apply it in the automation that stamps the timestamp, so nobody is arguing about it in the meeting.
Report the distribution
Median tells you whether the system works. The 90th percentile tells you where it fails. Share within five minutes, within an hour, within a day is the version leadership understands. Cut by hour of day and day of week to find the gaps — evenings, weekends, one region — and by source, because portal leads and referrals may deserve different targets.
Per person, without the surveillance feel
Show each person their own numbers privately and the team's aggregate publicly. Use it to fix systems — routing, coverage, notifications — before using it to judge people. When the system is fixed, individual outliers are usually a workload problem, which the same data will show.
Questions people ask next
- Should automated acknowledgements count as a response?
- No, but they should be tracked separately as a service-level check — did every lead get an acknowledgement within a minute. The response metric is about a person or a qualified agent engaging; the acknowledgement metric is about the system working.
- What target should we set for out-of-hours leads?
- If an agent covers nights, the same as daytime. If not, a next-morning target with a hard ceiling — say, by nine — and an acknowledgement that states when they will hear from you. Being honest about the wait beats silence.
- How do we measure response for leads that reply to a sequence?
- The lead's reply is the arrival; the rep's first personal message or call is the response. Treat it exactly like an inbound lead in the metric, because it is one — and it is often the slowest category once measured.
Want this built for your team?
A free scoping call: we map your motion, name the number that should move, and quote a fixed-scope build.
Related
- Reporting go-to-market to a board or investors: the numbers, the cadence and the honesty
- Data quality monitoring for GTM systems: catching the silent failures
- Sales activity metrics without the micromanagement: what to track, what to show, what to leave alone
- Alerts on revenue metrics: knowing on Tuesday what you would otherwise learn at quarter end

