Most teams try to win more deals by improving the pitch. The cheaper lever is usually further upstream: how long a new enquiry waits before anyone responds. A prospect who filled in your form has almost certainly filled in two others, and the ordering of those replies frequently decides the outcome before anyone has discussed price.

This is what actually causes slow response, and how to fix it without hiring.

Key takeaways

What speed to lead actually measures

The clock starts when the enquiry arrives and stops when a person makes contact — a call, a real reply, a message that is clearly not automated. An instant "thanks, we'll be in touch" does not stop the clock, because it does not answer anything.

That distinction matters. Teams often believe their response time is excellent because the autoresponder fires in seconds, while the first human contact happens the next afternoon.

Why the first reply matters more than the best reply

Someone comparing vendors is doing several things at once: shortlisting, forming an impression of what working with you would be like, and — crucially — losing interest. Each of those works against you as time passes.

The first substantive response gets to frame the problem. It sets the criteria the prospect then uses to evaluate everyone else. Arriving third means answering someone else's framing.

There is also a signalling effect that has nothing to do with the sales process. A fast, specific reply is evidence about how the company operates. A slow one is also evidence.

The four things that actually cause slow response

Nobody owns the first hour

The most common cause by far. Enquiries arrive in a shared inbox that is everyone's responsibility and therefore nobody's. Each person assumes another has picked it up.

The lead lands in the wrong place

Form submissions go to an inbox nobody watches, or a notification channel that is muted, or a CRM that only one person opens. The lead is not ignored so much as invisible.

Enquiries arrive outside working hours

For consumer and local businesses, a large share of enquiries arrive evenings and weekends. If the response window is Monday to Friday, nine to five, a Friday-evening enquiry waits sixty hours — and the competitor who answered on Saturday morning has already been chosen.

Reps are protecting deep work

This one is legitimate and often mishandled. Salespeople doing demos or writing proposals should not be interrupted constantly. The answer is a defined rota rather than an expectation that everyone watches the inbox permanently.

What to measure

Start with the last row. Almost every team that measures it for the first time finds a number greater than zero, and it is usually the cheapest thing on this page to fix.

Fixes, in the order worth doing them

• Assign an owner automatically at the moment of capture. Round-robin, territory, whatever fits — but never "the team". A lead with a named owner is answered; a lead in a shared inbox waits.
• Put the notification where that person already looks. Not a new inbox. Their phone, their existing channel.
• Set a visible target and report against it weekly. Response time improves substantially the week it becomes visible, before any tooling changes.
• Create a first-hour rota so reps doing focused work are not also expected to watch the queue.
• Give the first response something to say. A templated opener with the enquiry's specifics beats a generic acknowledgement and takes no longer.
• Cover after-hours deliberately. Either commit to a window and say so on the form, or automate the first touch.

Where automation genuinely helps — and where it does not

Automation is good at the parts that are structural: routing, assignment, reminders, and making sure a booking link reaches the prospect while they are still on the page. Those remove waiting without pretending to be human.

It is worse at the part people most want to automate — the response itself. An instant reply that obviously came from a machine answers a question nobody asked and can make the wait feel longer, because the prospect now knows a real answer is still pending.

The exception is a voice agent calling an inbound enquiry within a minute to confirm what the person needs and book time. That works because it is fast, it is genuinely useful, and it should say plainly that it is an AI. Applied to people who did not contact you first, the same technology is a liability.

Questions to ask before you commit

Whichever way you are leaning, these are the questions that change the answer. Work through them against your own numbers rather than anyone's feature matrix — including this one.

• What is our median time to first human contact? If nobody knows, that is the finding.
• How many enquiries got no contact within 24 hours last month?
• Who owns a lead in its first hour? A name, not a team.
• What proportion arrive outside working hours?
• Does our autoresponder stop the clock in our reporting? It should not.
• What does the first human message actually say? Read the last ten.

If you cannot answer the first three, you are not ready to choose between Scalry and your own funnel yet — you are still deciding what you need, which is a cheaper problem to solve first.

A two-week improvement plan

Deliberately unglamorous, and it works without buying anything.

Days 1–2: measure

Take the last fifty enquiries and record, for each, when it arrived and when a human first responded. Do it by hand if necessary — fifty rows in a spreadsheet is enough to find the pattern. Note the median, the worst five, and how many got no response at all.

Days 3–5: assign ownership

Pick a rule — round-robin, by source, by territory — and apply it automatically at capture. Put the notification where that person already looks. Do not add a new inbox for anyone to check.

Days 6–10: make the queue visible

A single view of enquiries awaiting first response, sorted oldest first, that the whole team can see. Visibility alone typically moves response times before any process change, because nobody wants their name against the oldest row.

Days 11–14: close the after-hours gap

Decide explicitly what happens to an enquiry arriving at 9pm Friday. The options are a stated response window on the form, a weekend rota, or automated first contact. Any of the three beats the current answer, which is usually that nobody has decided.

Re-measure at the end. Teams that do this honestly usually find the median improves modestly and the tail improves dramatically — and the tail is where the lost deals were.

Frequently asked questions

What is speed to lead?

The time between an enquiry arriving and a real human making contact. Automated acknowledgements do not count, because they answer nothing — measuring them as responses is the most common way teams overestimate how fast they are.

How fast should you respond to a new lead?

Faster than the competitors the prospect also contacted, which in practice means minutes rather than hours for inbound enquiries. Rather than chasing a benchmark, measure your own median and your 90th percentile, then work on the tail — that is where deals are quietly lost.

Why are we slow to respond to leads?

Usually ownership rather than effort. Enquiries land somewhere that is everyone's responsibility and therefore nobody's, so each person assumes someone else has it. The second most common cause is enquiries arriving outside working hours with no plan for them.

Should I use an AI to respond to leads instantly?

For inbound enquiries where someone contacted you first, an AI that qualifies and books time can work well — provided it discloses that it is an AI and hands off cleanly. For anything emotionally loaded, or for people who did not contact you, it does more harm than good.

Does speed to lead matter for long sales cycles?

Yes, though the mechanism differs. In a long cycle the first substantive reply sets the criteria the buyer uses to evaluate everyone else, and being third means answering someone else's framing. The deal is not lost in the first hour, but the position is.