The Cost of a Missed Email Lead: Response-Time Maths

The cost of a missed email lead is not a mystery number you need a benchmark report to find. It is your average deal value multiplied by your close rate, multiplied by the number of inquiries that never got a reply. Every term is already in your CRM and your sent folder.

This guide builds that model from your own numbers. Then it does the harder part: working out whether your replies are arriving late or your inquiries are disappearing entirely. Those cost different amounts, and they have different fixes. Buying the wrong one is the expensive mistake.

The short answer#

One inquiry is worth your average deal value times your close rate. That is its expected value before anyone touches it. An inquiry that never receives a reply forfeits all of it.

An inquiry that receives a slow reply does not forfeit all of it. It forfeits the gap between what you close when you are fast and what you close when you are slow. That is a smaller number, and a much harder one to measure honestly.

So there are two costs hiding under the phrase "missed lead", and most business cases quietly add them together. Keep them apart — they point at different purchases.

Why the statistic in most speed-to-lead articles is not your number#

Nearly every page on this topic repeats the same finding, and it traces back to one source: "The Short Life of Online Sales Leads" by James Oldroyd, Kristina McElheran and David Elkington, published in Harvard Business Review in March 2011. It reported that firms contacting a web inquiry within an hour were roughly seven times as likely to qualify the lead as those that waited one hour longer, and more than 60 times as likely as those that waited a day or more.

That is real research and it is worth reading. But the pages quoting it usually drop three things.

It was published in 2011. It measured telephone contact on web-form submissions, not email replies to email inquiries. And it measured qualifying a lead, which is several steps short of closing one.

So treat it as directional evidence that speed matters — it plainly does — and not as a multiplier you can paste into a spreadsheet about your business. A model built on someone else's conversion curve produces a confident number that nobody in your finance team can defend.

Criteria that actually matter#

There are only four inputs worth arguing about, and one diagnosis that decides everything else.

• Inbound volume — how many genuine buying inquiries land in the mailbox in a month, after you strip out vendor mail, newsletters and internal threads.
• Leak rate — what share of those never receive any reply at all, from anyone.
• Latency — how long the ones that do get answered actually wait, measured as a distribution rather than an average.
• Close rate and deal value — taken from your CRM, filtered to email-sourced opportunities only, because blended figures flatter email.

Latency or leakage — which problem do you have?#

Almost every tool sold against this problem fixes latency. Routing, scheduling links, canned first replies, chat widgets: all of them shorten the gap between an inquiry arriving and a human touching it.

Very little fixes leakage, because leakage is not a speed problem. It is a visibility problem. An inquiry gets buried under forty notifications on a busy Tuesday, and nobody is late — nobody knows it exists. The revenue report cannot tell the two apart, which is why teams buy the wrong thing.

Where each number actually comes from#

The model is only as good as its sourcing. Here is where each input lives and how each one usually goes wrong.

Worked example: a 40-inquiry-a-month agency#

A four-person agency takes inbound through two shared addresses and a personal one. A hand audit of July found 40 genuine inquiries. Their CRM shows a median closed deal of $6,000 and an 18% close rate on email-sourced opportunities. So one inquiry carries $1,080 of expected revenue.

The same audit found three threads with no outbound message on them at all. That is a 7.5% leak rate, and $3,240 of expected revenue in a single month — just under $39,000 a year, assuming the leak rate holds.

Their median first reply was nine hours. What is the latency cost? They do not know, and the honest move is to leave that line blank rather than fill it with a borrowed multiplier. To find it they will split replies into under-one-hour and over-four-hour buckets and compare close rates across a quarter; until then, the leakage number is the defensible one.

How the revenue case compares to the cost case#

Most email-tool business cases are built on saved hours. That case is easy to construct and easy to dismiss, because saved minutes rarely turn into a smaller payroll.

Run it anyway for contrast. The BLS Employer Costs for Employee Compensation series put total compensation for civilian workers at $49.32 per hour worked in March 2026 — check the current release, as this updates quarterly. If triage eats 45 minutes a day across four people, that is about 63 hours a month, or roughly $3,100.

Almost the same figure as the leak. But the two arguments behave differently in an approval meeting. The cost case caps out at the hours available. The revenue case scales with volume, which is the direction the business is trying to go — and that is why sales-led teams approve it and finance-led framing of the same tool stalls.

One caution on borrowed time figures: the American Time Use Survey measures how the whole population spends its day, not how your team spends theirs. Good sanity check, bad substitute for a week of your own timesheets.

Red flags in your own model#

Revenue models get rejected for predictable reasons. Check yours against these first.

• The largest term is the one you measured least precisely — usually latency, usually borrowed.
• Every inbound email is counted as a lead, which inflates volume and hides the real leak rate behind a big denominator.
• Mean deal value is used where one deal is several times the size of the rest.
• A recovered lead is assumed to close at your normal rate. It will close lower. It already waited, and it may have already bought elsewhere.
• There is no plan to re-measure the leak rate 90 days after the fix, which means you will never know whether it worked.
• The model assumes the leak is random. Check first — leaks cluster around one inbox, one weekday, or one message shape.

What we'd pick and why (honest)#

The diagnosis decides the purchase, so the recommendation splits three ways — and for two of them you should stop reading this page.

If your leads arrive through a web form into a CRM, this is not an inbox problem and no email client will fix it. Chili Piper publishes exactly this: rules that qualify and route a form submission in real time and put the right rep's calendar in front of the prospect at the moment they submit. It is sold to sales organisations rather than individuals, so check their site for current packaging. Go and buy that instead.

If you need an auditable first-response-time report across a shared address with several people answering, Front is the better tool and we are not close. Front publishes time goal rules (previously named SLA rules), SLA warning tags for conversations approaching a breach, and pre-built analytics reports covering breaches and response time.

Their own help centre is candid that there is no SLA specifically for first replies — you use the first reply time metric and drill into the outliers. It is per-seat; check their pricing page. On the exact metric this guide is about, measured across a team, Front reports it natively and AI Emaily does not report it at all.

The third case is the one we are built for, and it is the most common shape of this problem: the inbox is the pipeline. A founder, a small sales-led team, an agency. Inquiries arrive as ordinary replies to ordinary addresses, there is no form, no SDR rota and no SLA to report on — there is just a mailbox that quietly loses three good threads a month.

That is leakage, and it is the term we work on. We build AI Emaily, so read this as the interested party's account of its own product.

Concretely, against the leakage term: triage that lifts a buying question above the noise instead of leaving it in arrival order, follow-up sequences that run on a cadence and stop the moment someone replies, and drafts written from a Context brain you fill in yourself plus per-client profiles — not from anything harvested out of your old mail, which we do not do. Copilot holds every draft for approval before it sends, there is an undo window after it goes, and an audit log records what went out and why. Packaging is a 7-day free trial on Pro and Autopilot, card required, $0 if you cancel before day seven; current plans are on our pricing page.

Where we are the wrong answer, plainly: we do not produce team SLA reports, we do not route form submissions, there is no native Linux build, and on Android we are a PWA rather than a native app. If any of those is the requirement, one of the two tools above is your answer and this one is not.