Why does pipeline feel weak when the team is prospecting?
Pipeline is not one number with one cause. It is a chain of conversion points, and volume can hide leakage at every one of them.
Originally published in GTM Launchpad · expanded for SD Lab V2
What this guide covers
- More activity can fill the top of the bucket. It does not fix the holes in the bottom.
- Eight common leak points, from aim through to inspection.
- For each leak: what it looks like, what leaders usually misdiagnose it as, and what to inspect.
- A recurring five-question Pipeline Leak Review you can run monthly.
- Sometimes capacity genuinely is the constraint, but that should be a conclusion, not an opening assumption.
A dry pipeline and a leaking one look identical on a dashboard
When pipeline comes in light, the default response is more: more dials, more sends, more accounts. Sometimes that is right. Often it pours water into a bucket with holes in it, and the only thing that changes is how tired the team is.
The useful question is not how much went in. It is where opportunity fell out. That is a diagnosis, and it takes evidence, conversations, not just counts.
More activity can fill the top of the bucket. It does not fix the holes in the bottom.
The SD Lab Pipeline Leak Map
Eight places outbound opportunity typically escapes. This is a diagnostic model, not a claim that every problem fits neatly into eight boxes, but in practice most of them start in one of these.
- AIM LEAK: wrong accounts, wrong personas, wrong priorities.
- RELEVANCE LEAK: nothing credible for the buyer to care about.
- ATTENTION LEAK: low connects, weak channel execution, openings that don't earn a second sentence.
- CONVERSATION LEAK: attention earned, then lost to thin discovery or unhandled resistance.
- ASK LEAK: the meeting ask is weak, premature or unclear.
- FOLLOW-UP LEAK: real interest that never converts because of timing, context or persistence.
- HANDOFF LEAK: quality and momentum die between the SDR and the seller.
- INSPECTION LEAK: managers can see totals but not the actual constraint.
Aim and relevance
An aim leak looks like flat effort across a flat list. Leaders usually diagnose it as low motivation or low volume. What to inspect: ask five reps why the account in front of them matters this week. If the answer is that it came from the list, you have found it.
A relevance leak looks like polite indifference, replies that go nowhere, calls that end without friction. It gets misdiagnosed as a messaging tone problem, so the copy gets rewritten with more personalisation and the same outcome. What to inspect: whether the message names something true about their situation or something true about your product.
- Aim: see Activity vs. Aim for the diagnostic and the inspection order.
- Relevance: see Relevance Over Personalization for what actually earns attention.
Attention and conversation
An attention leak is the one teams measure best, connects, opens, pickups. It gets misdiagnosed as list quality when the cause is often channel execution or an opening that asks for too much too early.
A conversation leak is the expensive one. The rep earned the attention and then lost it in the middle: no transition into discovery, resistance treated as rejection, value dumped rather than connected. Leaders usually read this as 'they need a better script'. What to inspect: the third minute of five real calls.
- Attention and transition: see The Cold Call Transition Problem.
- Conversation quality and the middle of the call: see Where Deals Actually Break.
The ask and the follow-up
An ask leak sounds like a good conversation that ends softly. It is misdiagnosed as a closing-confidence problem. Usually the ask arrived before the reason for it existed, or it asked for a commitment larger than the conversation had earned.
A follow-up leak is real signal going cold. Leaders read it as 'not interested'. What to inspect: what actually happened after the interest. How many touches, with what context, and whether any of them referenced the specific thing the buyer said.
- The ask: see Sell the Meeting, Not the Product.
- Follow-up and momentum: see Where Deals Actually Break.
Handoff and inspection
A handoff leak shows up as a strong meeting that the seller experiences as a cold start. Context, commitments and objections did not survive the transition. It is misdiagnosed as SDR meeting quality, when the meeting was fine and the transfer was not.
An inspection leak is the one that keeps all the others alive. If management reviews totals rather than conversations, the constraint stays invisible and every quarter's fix is a volume target. What to inspect: whether anyone in a leadership role listened to a full call this week.
The recurring Pipeline Leak Review
Five questions, monthly, with evidence on the table. It takes under an hour and replaces most of what a pipeline meeting currently is.
- Where did conversion fall most sharply?
- Is this a quantity, quality or process problem?
- What evidence supports that diagnosis?
- What is the ONE constraint we are addressing next?
- What metric or behaviour will tell us it improved?
If you address three leaks at once you will not know which fix worked, and the next diagnosis will be guesswork again.
Where these leaks showed up in live engagements
Operational examples only: read the reports for what the evidence actually supports.
- FusionAuth: targeting breadth and execution visibility across a live motion.
- Queryon: infrastructure installed, with outbound messaging signal still requiring another iteration.
- Visual Identity Group: founder-led workflow, ICP definition and operating cadence.
- Kustomer: coaching and conversation quality inside an existing team.
Sometimes it really is capacity
More activity is not inherently wrong. A team of two covering a large territory can execute every stage well and still be short, simply because there are not enough attempts in the week. That is a real constraint and it deserves a real answer.
The distinction is order. Diagnose first, then add volume to a system that converts, rather than adding volume and hoping the conversion problem gets outrun.
Related reading
Your pipeline doesn't need another pep talk. It needs a leak inspection.
The Revenue Rebuild starts by locating the binding leak in your outbound motion, then fixes that one thing before touching targets.