Sales
Speed to Lead: Build a Reliable Inbound Response Plan
Build an inbound response plan with clear ownership, covered hours and honest response-time calculations instead of an arbitrary speed target.
What you will learn
- Separate receipt, assignment, acknowledgment and useful response.
- Design staffed coverage and an accepted backup handoff.
- Measure elapsed and covered-hours response time without hiding unanswered leads.
Speed to lead is the time between an inbound inquiry and a defined response. Improve it by making ownership, working hours and backup coverage explicit. An instant automated receipt is not the same as a useful reply, and a fast average is not meaningful if unanswered requests disappear from the report.
Define the clock before setting a target
Choose the exact start and stop events. Start might be successful form submission, not the time a seller notices a notification. Stop might be the first human reply that addresses the inquiry, not an automated acknowledgment. Keep assignment and acceptance timestamps separately so you can see where a delay occurred.
There is no universal response target that fits every team, time zone, inquiry and coverage model. Set an operating expectation your team can actually staff. Publish any customer-facing response promise only after the appropriate owner accepts it.
Inbound selling is discussed in Pete Kazanjy's Founding Sales chapter on inbound marketing. This lesson's event definitions, rota and calculations are original operational examples, not a research claim about the effect of a particular response speed.
Build a coverage and acceptance plan
| Coverage field | Fictional team agreement |
|---|---|
| Covered window | Monday through Friday, 09:00–18:00 America/New_York; holidays listed separately |
| Primary owner | Named daily inbox reviewer accepts each new inquiry |
| Backup | One named colleague accepts coverage before leave begins |
| Unaccepted request | Team lead reviews the queue using a team-agreed escalation interval |
| Outside coverage | Acknowledgment explains when staffed review resumes; no invented immediate-response promise |
| Completion evidence | Reply timestamp and message reference, not just “done” |
Assignment without acceptance can leave a request nominally owned but practically unattended. Make the backup handoff observable. A calendar entry alone does not confirm that the colleague has accepted responsibility.
How to calculate speed to lead?
This fictional audit uses the stated coverage window, no holidays and dates within Eastern Standard Time. Elapsed time includes the weekend. Covered-hours time counts only the specified staffed intervals.
| Inquiry | Receipt and useful reply | Elapsed time | Covered-hours time |
|---|---|---|---|
| A | Monday 09:05 to 09:22 | 17 minutes | 17 minutes |
| B | Friday 17:50 to Monday 09:15 | 63 hours 25 minutes | 25 minutes |
| C | Monday 11:20; no useful reply at the audit cutoff | Unanswered, still aging | Unanswered, still aging |
For B, covered time is 10 minutes on Friday plus 15 minutes on Monday. The median covered-hours response among the two completed cases is (17 + 25) / 2 = 21 minutes. That does not mean all three inquiries received a 21-minute response. Report the two completed cases, one unanswered case and the cutoff together.
Copyable AI prompt
Try this with Aurora AI in Finta, Codex, or Claude. Use only material you are authorized to share, and review the draft before using it.
Audit [authorized inbound event records] using [receipt definition], [useful-response definition], [time zone], [staffed intervals] and [cutoff]. Return receipt-to-assignment, acceptance and response delays, completed/unanswered counts and missing timestamps. Calculate elapsed and covered-hours time separately. Never reset receipt on reassignment or treat an automated acknowledgment as a human reply. Explain every calculation and draft a coverage fix for human review. Do not send messages or alter records.Find the delay without creating busywork
Look at receipt-to-assignment, assignment-to-acceptance and acceptance-to-useful-reply separately. A notification problem needs a different fix from an unavailable owner or a request that needs specialist input. Keep inquiries requiring more investigation visible rather than sending an irrelevant reply solely to stop the clock.
Common errors include resetting the start time after reassignment, using an acknowledgment as the stop event, ignoring duplicates and showing only successfully answered cases. Reconcile the inquiry count before drawing conclusions from a timing chart.
Keep routing decisions in your lead-routing workflow. Use the B2B sales guide for the wider process and the discovery guide for a useful next conversation. Clear response ownership should preserve context, not encourage a race to send more messages.