What is a good speed to lead for B2B inbound leads?

I get asked for a benchmark on almost every first call. I understand why. A number feels safe.

But the number someone else's company hit is not the number your company needs. What you need is a target your team believes, a way to measure it honestly, and a system that makes it the default instead of a heroic effort.

Here is what we have seen on real inbound queues.

What does slow speed to lead actually look like?

It looks like a queue nobody owns. At TVEyes, the average time to first touch on an inbound lead was about 1.2 hours. That sounds fine until you read the tails. A quarter of leads waited half a day. A tenth waited nearly three days.

The cause was not lazy reps. Both the SDR and the AE got the notification, so each one assumed the other had it. Leads that came in on Friday waited until Monday. The company's own target was 5 minutes.

That story shows up everywhere. The average hides the leads that matter. A buyer who raised their hand and waited three days did not wait quietly. They talked to someone else.

So the first job is not "go faster." It is to find out who owns the lead the second it arrives.

So what number should we pick?

Pick the number you can defend on a Monday morning. Then make the system hit it.

Here is how we set it with clients:

• Start with the best leads, not all of them. A demo request and a gated ebook download are not the same moment. At InCheck, the top provider leads need the fastest response, and routing for them is automated.
• Start at five minutes for hand raisers. That is what TVEyes wanted, and it is what we found in a technical assessment for another client: reps may need to respond in about five minutes. It is a starting point, not a law.
• Say it out loud. Write the target on one line, name the owner, and put it where the team sees it.
• Review it every month. If the team hits it easily, tighten it. If they miss it every day, find out why before you blame anyone.

I am deliberately not giving you an industry average. We have not seen one that holds up across a software company, a freight broker and a printer. Use your own data.

How do you measure speed to lead honestly?

Measure it on business hours, from the moment the lead arrives to the first real human touch, using timestamps the system captures on its own. Do not rely on reps to log it.

Two lessons came from client work.

First, the clock matters. At InCheck, the CRM ran on an around-the-clock clock. Reporting showed response times of 7.9 hours against a goal of 2 hours. The team was not that slow. Nights and weekends were counted against them. When we moved to business-hours SLAs, the reporting finally matched reality, and people trusted it.

Second, you cannot measure what reps do not log. In a technical assessment for another client, we found that response time could not be measured at all if reps did not log activity. The fix is to capture the timestamps from the dialer and from outbound email, so the CRM knows when a human actually reached out.

At WWL we built a custom timer object for email reply times for the same reason. The result was a reply time that went from 9.32 to 6.27 business minutes. That is customer replies, not new leads, but the lesson is the same: a number only changes when someone measures it every day. See the WWL case study.

Who should own the lead when it arrives?

One person. Always one person.

The TVEyes problem, two people notified and neither one moving, is the most common speed to lead failure we see. The fix is simple to say and easy to skip:

1. One owner per lead, assigned at the moment it arrives. Round robin, territory, or account owner. Pick a rule and write it down.
2. A different job for the second person. At TVEyes we simplified it. The AE gets the email, and the SDR gets a task called Call ASAP. Both have a clear job, and neither can assume the other has it.
3. A backup when the owner is out. The same technical assessment found that leads must be reassigned when the owner is out. If a lead sits with someone on vacation, the target is already missed.
4. An alert when the clock runs out. When the target passes, the lead moves to the next person and the manager sees it.

None of this needs new software. It needs a clear rule and a CRM that follows it.

What about nights, weekends and the leads humans cannot reach in time?

This is where an AI agent earns its place. People sleep. Friday leads should not wait for Monday.

At Terraboost, an AI SDR replies to inbound leads in under 5 minutes, and at that point it had booked about 90 meetings, with 17% of meetings turning into closed-won deals. It does not try forever. If the agent cannot book a meeting within a 12-hour, 3-touch window, the lead goes to a human rep. Terraboost's cold email replies also went from 4 to 5 days down to about 1 day, and the AI Email SDR has now won $109K across 246 meetings. The full story is in the Terraboost case study.

An AI voice vendor told us something similar from their side: the number one use case is calling engaged leads right away, even at 10 p.m. They also see no-show rates of 40 to 50%, which is why they push a warm transfer to the first rep who picks up.

A few rules we keep:

• AI drafts, a human approves, until trust is earned. At InCheck, the AI drafts follow-ups and a person approves them before anything goes out on its own.
• Cap the volume. InCheck limits each sender to 20 emails a day.
• Always hand off. The agent's job is to start the conversation and book the meeting. A human takes it from there.

What mistakes make speed to lead worse?

• Chasing one fast number and ignoring the tails. Averages hide the leads that waited days.
• Counting nights and weekends as misses. It makes the team feel they cannot win, and they stop trusting the report.
• Treating every lead the same. Your fastest response should go to your best leads.
• Fast but wrong. A quick reply that is a generic template is not a good response. Speed gets the first conversation. Relevance keeps it.
• No plan for no-shows. Getting the meeting booked fast is only half the job. Remind people immediately by email and text, and have a plan for when they do not show.

Where should you start this week?

Start with measurement. You do not need a new tool to do it.

1. Pull last month of inbound leads and compute the time to first human touch, on business hours.
2. Look at the slowest tenth, not the average. Find out who owned them.
3. Pick one target for your best leads and one owner for each lead.
4. Decide what happens at nights and weekends.

Do that, and you will know more than any benchmark can tell you.

Frequently asked questions

Is five minutes always the right target?

No. Five minutes is where we start for hand-raisers like demo requests, because it is what clients such as TVEyes asked for and what we saw in a technical assessment. Your sales cycle, team size and lead mix may support a different number. Set it with your own data, then tighten it once the team hits it.

Should speed to lead be measured on an around-the-clock clock?

Usually not for the target, but yes for visibility. InCheck's around-the-clock clock showed 7.9 hours against a goal of 2 hours, which was misleading. Business-hours SLAs fixed the reporting. If you want to watch overnight leads, cover them with an AI agent and track that lane separately.

Do AI SDRs really answer faster than people?

Yes, and they do it at any hour. Terraboost's AI SDR replies to inbound leads in under 5 minutes. The catch is the handoff: it must book the meeting or pass the lead to a human rep. Terraboost does that after a 12-hour, 3-touch window.

What if our reps do not log their calls?

Then capture the data without them. Pull call and email timestamps from the dialer and the email system into the CRM so response time is measured automatically. A target you cannot measure turns into an argument, and we have seen that go badly.

What happens to leads that come in on Friday?

They should not wait for Monday. Route them to whoever is on duty or to an AI agent that replies right away. At TVEyes, Friday leads sat until Monday, which was one of the reasons the average hid long waits.

Sources

• TVEyes inbound review and working session, 2026: about 1.2 hours average to first touch, a quarter of leads waiting half a day, a tenth waiting nearly three days, and the SDR and AE handoff fix.
• Terraboost, 2026: the AI SDR replies in under 5 minutes, the 12-hour, 3-touch escalation window and the 17% meeting-to-closed-won rate. See the Terraboost case study.
• InCheck, 2026: business-hours SLAs after the around-the-clock clock showed 7.9 hours against a 2-hour goal, the 20 emails a day cap and the human approval step.
• WWL case study: reply time from 9.32 to 6.27 business minutes.
• Harvard Business Review, The Short Life of Online Sales Leads: research finding that most companies do not respond to online leads nearly fast enough.