The four places a lead dies
A lead dies in one of four places: never recorded, when it arrives by a channel nobody logs; never answered, when no first reply comes while it's still deciding; never followed up, when the conversation goes quiet with no next date; and never closed out, when the deal sits open with no decision. Count the first one first.
You know roughly how many leads came in last month and roughly how many became clients. Ask where the rest went and nobody can say. Some chose someone else, some were never a fit and some simply stopped, and the CRM can't tell those apart, so the gap between leads and clients looks like bad luck.
Why leads disappear without a trace
Think of the pipeline as a tank. Leads flow in at the top and signed work flows out at the bottom, and whatever is in the tank right now is your pipeline. In systems terms the tank is a stock, and the ways out of it are flows. The usual report counts only the two ends, leads in and clients won, while leads drain out through three outlets nobody records, and a fourth group sits in the tank long after it stopped moving.
- Never recorded: the lead arrives by a channel nobody logs.
- Never answered: no first reply while the lead is still deciding.
- Never followed up: the conversation goes quiet with no next step or date.
- Never closed out: the deal sits open with no decision, so it can't be won, lost or reworked.
The first leak hides the other three. A lead that was never recorded can't show up as unanswered, unfollowed or stuck, so every later count comes up short by however many leads never made it in. That's why I'd count it first.
What the leaks cost
Each leak costs something different. A lead never recorded or never answered is work you never got the chance to win. A lead never followed up is work you were halfway to winning when the conversation stopped. A deal never closed out does its damage another way: it keeps the pipeline looking full, so you plan from leads that left a long time ago and go looking for new ones later than you should.
How much each one costs you depends on your own pipeline, which is why I'd start by counting. The lead leak finder asks about yours and points to the place you lose the most.
What the system looks like
Each leak has its own fix, and they work in order from the top. Every channel a lead can use feeds one record in the CRM. Each new record gets a first reply inside the window you set. Every open conversation carries a next step and a date, and a deal that runs past your normal sales cycle comes up for a decision.
Each place can be counted this week with what you already have, and each count points at the system that closes it.
| Place | What it looks like | How to count it this week | The system that closes it |
|---|---|---|---|
| Never recorded | A lead that came by phone, a direct message, a referral by text or someone's personal email, and lives only in that person's memory | List every way a lead can reach you, then note each lead that arrives this week and check whether it reached the CRM | Every channel feeds the same record on its own, and a lead that arrives by hand gets a quick way in, such as forwarding it to a single address |
| Never answered | A lead that asked a question and is still waiting, or got an auto-reply and nothing after it | For each lead logged this week, note when it arrived and when the first written reply went out, and count the ones still waiting | A reply drafted from your rules as soon as the lead lands, which a person approves before it sends |
| Never followed up | A good conversation that went quiet after someone said they'd get back to the lead | Filter open deals for the ones with no next step date, or a date that has already passed | Every open conversation carries a next step and a date, and a nudge is drafted when the date arrives |
| Never closed out | A deal that has sat open for months with no word in either direction | Count open deals older than your usual sales cycle, then sort them into won, lost or still live | A deal past its normal cycle comes up for a decision, so it gets won, lost or reworked |
What stays with you
Counting, drafting and reminding can run on their own, and the decisions stay with people. The system puts each lead in front of the right person at the right moment, and a person approves anything before it's sent.
- Price, scope and tone in any reply. Drafts are approved by a person before they go out.
- Which leads to chase. The system shows you the ones with no date, and you choose what happens next.
- Closing out. Marking a deal lost is a judgment about the client, and a lost deal you can name tells you more than an open one you can't.
Questions
What is lead leakage?
Lead leakage is any lead that leaves your pipeline without a decision anyone made, because it was never recorded, answered, followed up or closed out. A lead you turned down on purpose has been handled, so it doesn't count as a leak.
Which leak should I fix first?
Count never recorded first, because a lead that was never logged can't show up in any other count. After that, fix whichever leak your counts say is biggest. If two counts come out close, start with the first reply, since every later step depends on it.
Why don't my CRM reports show these leaks?
A CRM report counts what's in the CRM: leads created, deals won and the stages in between. The first and last leaks hide from that view, because a lead that was never recorded has nothing to count, and a deal never closed out still looks like open pipeline.
Is a lost deal a leak?
A deal marked lost is a decision, and a decision is information you can use. The leak is a deal that sits open with no decision, because it can't be won, lost or reworked, and it keeps the pipeline looking bigger than it is.
Do I need a CRM to count this?
You can start without one. A spreadsheet with a row per lead, the date it arrived, the date of the first reply, the next step date and the outcome is enough to count all four places this week. A CRM makes it easier to keep counting after that.
Related
- The lead-response bottleneck: how fast to answer a new leadHow fast to answer a new lead, why a slow reply hands the decision to someone else, and a system that drafts from your rules for a person to approve.
- The follow-up bottleneck: why follow-ups fall through the cracksFollow-ups slip when the next step lives in someone's head. They hold when every open lead carries a next step, a date and a drafted nudge a person approves.
- Old leads in your CRM: how to reactivate themOld leads went quiet for different reasons. Group them by why, send a short note per group that a person approves, and put every reply back in the pipeline.
- Where do your leads leak?Twelve yes or no checks across the four places a lead dies: never recorded, answered, followed up or closed out. See your worst leak and what closes it.
- How a lead becomes revenue: an owner's mapMap the six steps from a new lead to a kicked-off project, time each handoff with a timestamp column, and fix the slowest one first.
- A drafted reply to each lead, approved from my phone before it sendsAI drafts replies to lead emails that pass a junk screen, from my business facts. Risky asks get flagged, and nothing sends until I approve it on my phone.
- Website form leads, scored and answered with a reply I approveA system I built: each website form lead is checked, added to HubSpot once and scored. Gmail sends the drafted reply when I approve it in Telegram.