Speed to lead: why the first hour wins (2026 guide)

What speed to lead means (and what it isn't)

Speed to lead (also called lead response time, or first response time when the context is support rather than sales) is the elapsed time between a new enquiry arriving and your first meaningful response to it. The enquiry might be a web form, an email to hello@ or sales@, a marketplace message or a voicemail. The response is whatever first moves the conversation forward: an answer to the question asked, a proposed time, a quote.

Three things it is not. It is not the time to an autoresponder, because a receipt answers nothing and the prospect knows it. It is not the time to close, which depends on a dozen things after the first reply. And it is not an average: one enquiry that sat over a bank holiday will drag a mean into the tens of hours while most replies went out in minutes, so measure the median and look at the misses separately.

Why the first hour matters: the evidence

The research on this is old, famous and still uncomfortable. A Harvard Business Review study of lead response ("The Short Life of Online Sales Leads", Oldroyd, McElheran and Elkington, March 2011) audited 2,241 US companies with a web-generated test lead. Only 37% responded within an hour; 24% took more than a day, and 23% never responded at all. Among companies that did respond, the average response time was 42 hours. The same authors' companion study of 1.25 million sales leads found that firms contacting a potential customer within an hour of the query were nearly seven times as likely to qualify the lead as firms that tried even an hour later, and more than 60 times as likely as firms that waited 24 hours or longer.

The earlier study behind that HBR piece, the Lead Response Management Study (leadresponsemanagement.org, conducted with Professor James Oldroyd, then at MIT, on InsideSales.com data; retrieved 23 September 2026), looked at three years of records from six companies, more than 15,000 leads and more than 100,000 call attempts. Two findings, quoted directly: "contact success dropped more than tenfold, while qualification success fell over sixfold in the first hour," and a "21-fold decrease in the odds of qualifying a prospect if the response time stretched from 5 to 30 minutes." Those figures describe phone contact, because that is how the sales teams in the data worked, so treat the exact multiples as a phone finding.

The shape of the curve is what transfers to email. A prospect who has just emailed you is thinking about the problem you solve, sitting at the device they wrote from, and very possibly composing the same email to two competitors. Ten minutes later they are in a meeting. Tomorrow they have a shortlist, and you are on it only if you replied. Those two studies are the only statistics in this guide; everything else is a target we recommend, labelled as such.

What good looks like: benchmark targets by channel and team size

These are targets, not industry averages. They follow from the research (the first hour is the cliff, five minutes is where the phone data peaks) and from what a small team can practically hold.

By team size: a solo founder can realistically hold four business hours by hand, and under one hour only by automating the first reply. A team of two to five with one person on the inbox can hold one hour in the day; five to ten with a rota can hold 15 minutes. In every case the after-hours gap is the same size, because it is set by the clock, not by headcount.

Why small teams are slow

Nobody decides to reply in two days. Slow speed to lead in a small business is almost always structural.

• The lead is buried in the inbox. A sales enquiry lands between a supplier invoice, a newsletter and a complaint, unmarked, and is not seen until someone reads the whole inbox.
• One person owns leads. Usually the founder or the best salesperson: the person least likely to be free when the email arrives.
• After hours and weekends. An enquiry at 8pm on Thursday is answered Friday morning at best; one at 11am on Saturday waits until Monday. By then the prospect has heard from someone else.
• Answering means looking things up. The reply needs a price, a date, a postcode check. If that lives in one person's head, the reply waits for that person.
• The first reply is over-engineered. Teams that want to send a perfect answer send a late one. The lead needed the price and a next step, not a proposal.

None of these are motivation problems. They are routing, triage, information and timing problems, and each has a fix.

The speed-to-lead playbook

Five steps, in order. The first three cost nothing and take an afternoon. The fourth closes the after-hours gap. The fifth is the point of all of it.

1. Route every lead to one inbox

Web form, contact page, marketplace notifications, the founder's personal address that ended up on the brochure: point all of them at a single shared address (sales@ or hello@) that more than one person can see. Forward rather than copy, so there is one thread and one owner.

2. Classify sales enquiries from everything else

A shared inbox full of everything is only marginally better than three inboxes. Make new sales enquiries visually distinct the moment they arrive: in Gmail, a filter that labels and stars messages from your web-form sender; in Outlook, a rule that categorises and flags them. Anyone glancing at their phone should see "new lead" without opening anything. An AI email agent classifies by content rather than sender rules, which matters once leads arrive as free-text emails no filter anticipated.

3. Acknowledge versus answer

Here is where most speed-to-lead advice goes wrong. The standard fix is an autoresponder: instant, and useless. The lead asked whether you have availability in November and got "thanks, we will be in touch". They are no closer to choosing you, and they know a machine sent it.

A first-reply template that answers the actual question is a different thing. Write one per common enquiry type, containing what you type every week: prices, what is included, how booking works, which areas you cover, and one question back. It still takes thirty seconds to send, but it lands as an answer, not a receipt.

Notice what the template does not do: it does not apologise for being fast, explain your history, or ask five qualifying questions first. Price, next step, one question. For when an acknowledgment genuinely is the right tool (holidays, closures, out of office), see the auto-reply email guide.

4. Automate the first reply, grounded in your own answers

Templates get you inside the hour when someone is watching the inbox. They do nothing at 8pm on Thursday. Closing that gap means letting software send the first reply, and the only version worth doing is one where the software answers solely from information you have approved.

This is what InReply does (our product, so weigh this paragraph accordingly). It connects to the Gmail, Google Workspace, Outlook or Microsoft 365 inbox you already use, via OAuth, so there is nothing to install. You upload the material your templates were built from (pricing, availability, service areas, FAQs, PDFs, a link to your website) and playbooks decide how each kind of email is handled. A pricing enquiry gets a reply built only from your price list; anything not covered is not guessed at, it is raised to a person as a draft or a tracked action item.

Two controls make it safe to switch on. Ghost Mode, on every plan, writes every reply as a draft for a human to approve, which is how most teams run for the first week or two. Autopilot, enabled per playbook, sends automatically, with human-like delays, business-hours awareness and a confidence threshold below which it falls back to a draft. Put plain pricing and availability questions on Autopilot first; keep anything contractual or unusual human-only. Setup differs slightly by provider: see the AI email assistant for Gmail or the Outlook equivalent.

5. Hand off to a human for the call

The fast first reply is not the sale. Its job is to keep the prospect in your conversation, rather than a competitor's, until a person can take over. The automated reply proposes a call, viewing or visit; the thread is flagged so the next available person sees it first; that person confirms the time and does the call. Booking the slot, updating a CRM, and following up if the lead goes quiet are all still human jobs. The difference is that the human walks into a warm conversation that started within minutes, instead of apologising for a two-day silence.

How to measure speed to lead in Gmail and Outlook without a CRM

You do not need reporting software to know your number (InReply does not provide response-time analytics either), so this manual method is the one we recommend. It takes about twenty minutes a week.

1. Pick the sample. Once a week, find the last 20 threads that began with a new enquiry. In Gmail, search your lead label from step 2, or to:sales@yourdomain.com newer_than:7d. In Outlook, filter by the category or flag your rule applies.
2. Record the inbound timestamp. Hover the time on the received message in Gmail; Outlook shows it in the message header. For exact times across time zones, Gmail's "Show original" and Outlook's message properties expose the raw Date header.
3. Record the first substantive reply. The timestamp on the first message from your side that answered something. An autoresponder does not count. An automated reply grounded in your own information (step 4) does, and is worth noting separately.
4. Put the difference in a spreadsheet. Four columns: received, first reply, minutes between, and whether the enquiry arrived in or out of business hours.
5. Report the median, and the misses. The median tells you what a typical lead experiences. The five slowest tell you why: nearly always a weekend, an evening, or one person being away. Fix the cause, not the number.

After four weeks you have 80 data points, a median for business hours and after hours, and a short list of the structural causes that apply to you, at no cost.

Speed to lead for specific businesses

The playbook is the same everywhere; what changes is which question the lead asks first and how fast the competition is.

• Real estate. Listing enquiries arrive in bursts the moment a property goes live, and the buyer has usually messaged three agents. InReply for real estate.
• Property agents and lettings. Viewing requests at evenings and weekends are the whole game. InReply for property agents.
• Agencies. New-business enquiries are rare and valuable, and land in an inbox full of client work. InReply for agencies.
• Gyms and studios. Membership questions come in after the evening session, when the front desk has gone home. InReply for gyms.
• Vacation rentals. Availability questions across time zones, with the guest booking whoever confirms first. InReply for vacation rental hosts.
• Sales teams. Pricing, demo and RFP emails each need a different playbook. InReply for sales teams.

Bottom line

Speed to lead is the time from enquiry to first real reply, and the research says the first hour is where the value lives. Route leads to one inbox, make them visible, write templates that answer rather than acknowledge, automate that first reply from your own approved information, hand the warm conversation to a person, and measure it by hand for a month. InReply starts at £39 a month per workspace with a 14-day free trial and no card required; the full breakdown is public.