Speed to lead measures how fast someone replies to an inbound enquiry. It does not measure whether the buyer got an answer. A four-minute reply that offers a meeting on Thursday has not resolved anything — it has scheduled the resolution for three days later. Marklinea calls the number that actually matters speed to resolution: the time from enquiry to the buyer having the answer they came for.
Key takeaways
- Speed to lead measures the reply. Speed to resolution measures the answer. Most teams track the first and never the second.
- The statistics underpinning speed to lead are 8 to 19 years old. The 100× figure is from 2007. The 42-hour average is from 2011.
- The most-quoted number in the category — “78% buy from the first responder” — has no traceable primary source.
- Seven separate handoffs sit between a form submission and a human answering a question. A fast reply removes only one of them.
- You can measure speed to resolution this week with a stopwatch and one honest question.
What is speed to lead?
Speed to lead is the elapsed time between an inbound enquiry — a demo request, a form fill, a pricing enquiry — and the first response from the seller. Most B2B teams track it as a service-level target, commonly five minutes, and report it on a weekly dashboard.
The metric became standard because of a single piece of research. In 2007, Dr James Oldroyd's Lead Response Management study, run with InsideSales, found that contacting a lead within five minutes rather than thirty made contact roughly 100 times more likely and qualification about 21 times more likely.
That study is now nineteen years old. It predates the iPhone.
The other pillars are barely younger. Harvard Business Review's The Short Life of Online Sales Leads — the source of the widely quoted 42-hour average response time, and the finding that 23% of companies never respond at all — was published in 2011. Drift's survey, which found only 7% of companies replied within five minutes and 55% did not reply within five business days, ran in 2018.
What does speed to lead fail to measure?
Speed to lead stops its clock when the seller sends something. It does not ask what that something contained.
In practice, the first response to an inbound demo request is usually an email offering three time slots. That is a fast reply and a completed SLA. It is not an answer. The buyer wanted to know whether the product does the specific thing they need, roughly what it costs, and whether it works with the stack they already run. A calendar invite answers none of it.
So the dashboard turns green while the buyer waits.
There is a second problem worth naming, because it undermines the whole category. The single most-quoted statistic in speed-to-lead marketing — that 78% of customers buy from the vendor who responds first — has no traceable primary source. It is variously credited to McKinsey, Forrester, InsideSales and MIT. The attributions contradict each other, and the McKinsey study does not appear to exist.
Marklinea has cited that figure on its own website. We are removing it. A number nobody can trace is not evidence, however often it is repeated.
What is speed to resolution?
Speed to resolution is the time between a buyer's enquiry and the moment they have the answer they were looking for. Speed to lead stops when the seller replies. Speed to resolution stops when the buyer knows.
The two numbers can be minutes apart or weeks apart, and nothing on a standard sales dashboard distinguishes them.
A team can reply in four minutes and resolve in four days. Another can reply in an hour and resolve in the same hour, because whoever replied could actually answer the question. The second team wins the deal, and by the first metric it looks slower.
Marklinea uses speed to resolution because it is the only one of the two the buyer experiences. Nobody has ever chosen a vendor because the acknowledgement email arrived quickly.
How does speed to resolution differ from speed to lead?
| Speed to lead | Speed to resolution | |
|---|---|---|
| What it measures | Time to the seller's first response | Time to the buyer having their answer |
| When the clock stops | A message is sent | The buyer's questions are answered |
| What the buyer has | A meeting invitation, or an acknowledgement | The information they came for |
| Who it is convenient for | The seller — it is easy to instrument | The buyer — it is what they actually experience |
| Typical value | Minutes to hours, on teams that track it | Days, on almost every team |
The gap between the two columns is where deals are lost, and almost nobody measures it.
What are the seven delays before an answer?
Seven separate handoffs sit between a form submission and a human answering a real question. A faster first reply removes one of them.
Fill in the right-hand column for your own funnel. Most teams have never added it up.
| # | What happens | Who owns it | Your time |
|---|---|---|---|
| 1 | The form submits. The record lands in a marketing platform, not in a person's queue. | Marketing ops | |
| 2 | Enrichment runs. Firmographic lookup completes before the record can be scored. | Data / vendor | |
| 3 | Scoring and routing. Rules decide territory, segment and owner. | RevOps | |
| 4 | Assignment. Round-robin picks an AE — who may be in a meeting, asleep, or on holiday. | RevOps | |
| 5 | The AE notices. The notification competes with everything else in their day. | The AE | |
| 6 | First contact. Usually an email offering times. This is where speed to lead stops its clock. | The AE | |
| 7 | The meeting. The buyer's questions are finally answered. This is where speed to resolution stops its clock. | The AE |
Steps 1 to 5 are invisible on most dashboards. Step 6 is the one everybody optimises. Step 7 is the one the buyer cares about, and on most teams it lands days after step 1.
How do you measure speed to resolution?
You do not need new tooling. You need one honest pass over the last twenty inbound enquiries.
- Take the last 20 inbound enquiries. Not a sample you like — the last 20.
- Record the timestamp of the enquiry. Form submission, first email, whichever started it.
- Record the timestamp of the first substantive answer — the moment a human addressed what the buyer actually asked. A meeting invitation does not count. A brochure does not count.
- Subtract. That is speed to resolution for that enquiry.
- Compare it to your speed-to-lead number for the same twenty. The difference between the two averages is the number this article is about.
- Count the ones where step 3 never happened. These are usually the largest group and the most uncomfortable.
Do this for twenty enquiries and you will know more about your funnel than the dashboard has told you all year.
Why can't a human team respond fast enough?
The gap is structural, not a discipline problem. Blaming the AE misreads it entirely.
An enquiry that arrives at 9pm on a Sunday cannot be answered at 9pm on a Sunday by someone who is not working. An enquiry that arrives at the same moment as nineteen others cannot be answered immediately by one person. A question about a specific integration cannot be answered by whoever is on rota if they do not know the answer.
Every good team eventually arrives at the same three tools: an SLA, a round-robin, and a chatbot. The SLA speeds up step 6. The round-robin reshuffles step 4. The chatbot deflects the easy questions and hands the real ones to step 6 anyway.
None of them changes step 7, because step 7 needs someone who can hold a real conversation, available at the moment the buyer asked. That is a coverage problem, and coverage is the one thing headcount solves expensively and badly.
What changes about the first sales conversation?
If resolution is the metric, the first conversation has to happen at the moment of enquiry rather than after it. That is the whole change, and everything else follows from it.
It means the first conversation is not a qualification call in disguise. A buyer who asked a question and got asked eight questions back has not been resolved. It means whoever takes it needs to answer, not route — including showing the integration, the pricing page, the security document, whatever was actually asked for.
And it means the meeting stops being the goal and becomes the outcome. A buyer whose questions were answered in the first sixty seconds books a meeting because they want one, not because it was the only thing on offer.
Marklinea built Chloe to take that first conversation — on the page, in about thirty seconds, at whatever hour the enquiry arrives.
What do people ask about speed to lead?
Is speed to lead a bad metric?
No. Speed to lead is a useful operational metric and a team that ignores it will lose deals. It is incomplete rather than wrong. It measures the seller's responsiveness, not the buyer's experience, and a team that optimises it alone can hit every target while buyers still wait days for an answer.
What is a good speed-to-lead time?
The commonly cited target is five minutes, from the 2007 MIT/InsideSales study. It remains a reasonable operational goal. Be aware that the evidence behind it is nineteen years old and predates live chat, mobile-first browsing and AI assistants, all of which changed what buyers expect after they enquire.
How is speed to resolution different from first-response time?
First-response time and speed to lead measure the same thing — when the seller replied. Speed to resolution measures when the buyer got their answer. A reply that offers a meeting counts for the first two and not the third.
Why is the “78% buy from the first responder” statistic disputed?
Because no primary source for it can be located. The figure is credited to McKinsey, Forrester, InsideSales and MIT depending on where it is quoted, the attributions contradict one another, and the McKinsey study does not appear to exist. It should not be used as evidence.
Can AI reduce speed to resolution?
It can, if it answers rather than routes. An AI that qualifies and hands off still ends at step 6 of the seven above. An AI that holds a real conversation, answers the buyer's actual questions and shows them the relevant material moves step 7 to the moment of enquiry — which is the only structural fix available.
Measure your own speed to resolution.
Take your last twenty inbound enquiries and run the six steps above. Then take a call with Chloe and time that one too.
Sources
- Oldroyd, J. — Lead Response Management Study, MIT / InsideSales, 2007 — the 100× and 21× figures.
- The Short Life of Online Sales Leads — Harvard Business Review, 2011 — 42-hour average, 23% never respond.
- Drift — Lead Response Report, 2018 — 7% within five minutes, 55% not within five business days.