Speed to lead is the time from an inquiry arriving to the first real reply, by a person or a system. Measure it from your own records: timestamp each arrival against its first reply, then report the median and the slowest case, with nights, weekends and each channel counted separately. That number is the baseline any fix is judged against.
An inquiry is demand you have already paid for: the ad, the listing, the referral, the van with your number on the side. In a business where buyers call down a list until someone picks up, the first answer often decides who gets the job. This topic is part of the field guide to sales automation. It shows how to measure your lead response time, where the delay comes from, and what closes it.
Measure your own speed to lead.
You do not need anyone else's benchmark to start. Your phone system, your CRM and your inbox already hold the numbers. Take four weeks of inquiries and work through six steps.
- Pull every arrival.Export the inquiries from every door: web form submissions, calls from the phone log with the missed ones included, emails to the sales or service inbox, and chats. Each one needs the date and time it arrived.
- Find the first real reply.For each inquiry, find the first answer that gave the buyer something to act on: a call back, an email from a person, or a system reply with a time slot, a price range or a question about the job. Decide up front whether an automatic receipt counts, and keep the rule the same every month.
- Report the median and the slowest reply.The median is the wait a typical buyer gets. The slowest reply shows what happens when the week gets busy. An average blends the two, and one lead left for three days can pull it far from what most buyers experience.
- Count nights and weekends on their own.Split the leads by whether they arrived inside your business hours. A burst pipe or a machine down does not wait for Monday, and a blended median hides the after-hours wait inside the daytime one.
- Break it down by channel.Forms, phone, email and chat each run on their own clock, owned by different people. One slow door can sit inside a respectable overall median, so look at each one.
- Count the ones nobody answered.A missed call with no voicemail and no call back never shows up as a slow reply. It shows up as no reply at all, so count those separately and treat them as the worst case.
The times are already on record. The CRM keeps the date and time each lead was created. The phone system's call log keeps every call, answered or missed, and when it was returned. The shared inbox keeps when each email arrived and when the first reply went out, and the chat tool keeps its transcripts. Export each one to a spreadsheet, one row per inquiry.
Write the numbers down before you change anything. They are the baseline every fix is judged against, and without them nobody can say what improved.
Run the lead response audit.
The audit below does the arithmetic for you. Enter the arrival and first-reply times for 20 to 50 recent inquiries, or paste them from a spreadsheet. It returns the median wait, the slowest reply, the share answered within five minutes and within an hour, and the split by business hours and by channel. It works in counts and minutes, and it puts no dollar figure on the result: that depends on numbers only you have, and the formula further down shows how to use them.
Tool
Measure how fast a new inquiry hears back.
Enter when each inquiry arrived and when it got its first real reply. Use 20 to 50 recent leads from every door: forms, calls, email and chat. The audit works out the median wait, the slowest reply and the split by hours and by channel.
Your entries stay in this browser. Nothing you type is sent to us.
01Your business hours.
Leads that arrive outside these hours are counted as after hours.
02Log the leads.
For each inquiry, take the time it arrived from the form, the phone log or the inbox, and the time a person or a system first answered it. Leave the reply empty and tick No reply yet for the ones nobody answered.
03Or paste them from a spreadsheet.
One lead per line: arrived, first reply, channel. Copy three columns straight from a spreadsheet, or type them with commas, such as 10/7/2026 2:05 PM, 10/7/2026 2:40 PM, Phone. Leave the reply empty, or write none, when nobody answered.
Your lead response, measured.
Log at least three leads to see your numbers.
Rather have your team fill it in over a week? The lead response log is the same audit as a spreadsheet, with the formulas in place.
What slows the first reply.
Most of the delay sits in how inquiries reach the team. Look for these five causes in your own log.
- Routing. Inquiries land in a shared inbox or on a general line, and nobody knows whose they are until someone sorts them.
- Ownership. When anyone can answer, nobody has to. A lead with no named owner waits for whoever is least busy.
- After-hours gaps. Calls after closing go to voicemail, and a form sent on Saturday sits until Monday.
- Qualifying before replying. Some teams hold the first reply until they have looked the buyer up or priced the job. The buyer sees only the silence.
- CRM hygiene. Duplicate records, missing phone numbers and leads logged after the fact make it hard to see who is waiting, and harder to measure the wait.
Put a price on the wait.
A faster reply is worth money only if it changes how many inquiries become jobs. Your CRM can tell you whether it does. Compare the close rate on leads answered quickly with the close rate on leads answered late, using the cut-off that fits your business. If the two rates sit close together, put your effort somewhere else first. If they are far apart, the formula below prices the gap.
We give you the formula and no outcome figures. Every input comes from your own records, and so does the answer.
If lead response is one of several workflows you are weighing, score it against the others with the Workflow Shortlist before you spend anything.
Three ways to close the gap.
Every fix does two things: it gets a useful first reply to the buyer sooner, and it makes sure a named person owns what happens next. The three below differ in what they ask of your team, and they stack. Start with the first.
- Ownership and a written response rule.Name who answers each door, in business hours and after them. Write down how fast, through which channel, and what the first reply has to contain. It costs nothing, and every other fix depends on it.
- The automation you already pay for.Most CRMs can send an instant reply to a web form and assign the lead to a rep. Many phone systems can send a missed call text back, so the caller hears from you while they are still working down the list. Switch on what you have before you buy anything new.
- An installed play.P07 Respond to new leads faster, from the StrikeArc PowerPlays Library, is a pre-built AI system we install and run for you. Leads from forms, calls and your website land in one CRM, deduped, enriched and scored. A missed call gets a text back, and the best leads go straight to your rep.
Respond to new leads faster
Leads from forms, calls and your website land in one CRM, deduped, enriched and scored. A missed call gets a text back, and the best leads go straight to your rep.
- Runs on
- Your web forms, phone line and CRM
- The rule
- Every lead is answered, scored and routed once. Nobody gets touched twice.
- What it reports
- Answer time, booked jobs and revenue per lead.
P07 Respond to new leads faster is installed where your team already works and run as a service, with results reported in dollars. Answer time, booked jobs and revenue per lead are reported next to every other play you run, and a person signs every figure.
It is $20,000 as a one-time install, or included in the $7,500 monthly subscription to the library, which installs one play per quarter. See the prices.
Whichever way you go, put the workflow on one page first. The Workflow Brief records who owns it, how it runs today and the numbers you measured, so any fix can be judged against them. To see the whole route on a made-up company, read responding to new leads faster, start to finish.
What to check in any lead-response system.
Whether you switch on a feature, buy software or bring in a partner, ask the same five questions before anything goes live.
| What to check | Ask | Why it matters |
|---|---|---|
| Where it reads leads from | Which forms, phone lines, inboxes and chat tools it watches, and which it misses. | A door it does not watch keeps its old wait. |
| How it hands off to a person | When a lead reaches a rep, with what context, and how the rep hears. | A fast first reply followed by a slow call back only moves the wait. |
| What it logs | Whether every touch, by a person or a system, lands on the lead's record as it happens. | Without the record you cannot measure the result or spot a lead touched twice. |
| Which approval rules it follows | What it may send on its own, and what waits for a named person. | Prices, promises and anything unusual should reach a person first. |
| How it reports results | Answer time, booked jobs and revenue per lead, against the baseline you took. | A count of messages sent says nothing about jobs won. |
The rule we work by on approvals is short. Every gate is a named human. Agents draft everything; they approve nothing.
Questions owners ask.
What is a good lead response time?
The one you can measure and then beat. Take the median and the slowest reply from your own records, split by business hours and by channel, and set a written target from there. Published figures count different things, so your own baseline is the number to decide on.
Does an automated reply count as a response?
Count it when it gives the buyer something useful: a time slot, a price range or a question about the job. A bare receipt only confirms the message arrived. Decide which one your numbers count, and keep the rule the same every month.
Should a lead be qualified before the first reply?
Reply first, then qualify. A short first answer that asks one or two questions about the job does both at once, and the buyer hears from you while they are still deciding.
How do we cover nights and weekends?
Set the after-hours policy first: who is on call, what the first reply says and what can wait until morning. Then cover it with a rota, an answering service, a text back on missed calls, or a system that replies and books the next step.
How do we measure speed to lead in our CRM?
Compare the time each lead was created with the time of its first logged call, email or text. If your CRM does not log the first touch on its own, export both times and run them through the lead response audit on this page.