Sales Pipeline Audit · System 02 · naming the stall

Why Deals Actually Stall

“Went dark” is the most common entry in a lost-deal report and the least useful one. It describes what the buyer did, not why they did it, and every one of the real reasons underneath it needs a different response. Treating “went dark” as the finding is how a sales team ends up with a list of ghosts and nothing to do about any of them.

The idea in one line: a stalled deal has one of a small number of causes. Four sit on the buyer’s side, and finding out which one takes evidence. One sits entirely on your side, and it’s usually the easiest to fix and the most common.

01

Ghosting is a symptom, not a reason

Silence tells you a deal has stopped moving. It doesn’t tell you why, and a CRM loss reason of “went dark” or “other” usually means nobody found out.

Behind a buyer who stops responding is almost always one of the five reasons below — the deal lost priority, the internal case for it fell apart, budget disappeared, a competitor won, or the champion who was carrying it changed jobs. “Went dark” is where the investigation should start, not where the write-up ends. A loss-reason field with a real distribution across named causes is worth more than a close-rate percentage, because it tells you which lever to pull.

02

Four reasons that sit with the buyer

Each of these needs a different fix, and the evidence for telling them apart is usually already sitting in the CRM once you know where to look.

What to look for, per cause
Indecision, no internal consensus. Activity taper after a good discovery call. No executive ever joined a meeting. Close date has slipped more than once with no new objection raised each time.
No product fit, or a weak value case. Discovery notes have no quantified pain or cost of inaction. Pricing conversation started before the value conversation finished. Buyer keeps asking for features rather than asking about outcomes.
Budget or authority mismatch. Budget was never confirmed as approved or accessible. No one with financial sign-off has been in a meeting. No procurement path or decision date has ever been named.
Champion turnover or single-threading. One contact on the whole deal. That contact’s email starts bouncing, or their role changes on LinkedIn. Engagement stops all at once rather than tapering.
Any of these can also produce a deal that looks “lost to competitor” in the CRM, because a rep who doesn’t know the real reason will often guess the flattering one. Corroborate a competitor loss with something more specific than the rep’s impression — a named tool the buyer compared, evaluation criteria you can point to, or an actual procurement notice.
03

The one that sits with you

This cause has nothing to do with the buyer’s intent, and it’s usually the largest single bucket in a pipeline that hasn’t been audited before.

No dated next step. A deal can have a recent note, a logged email, even a good call, and still have nothing on a calendar. Open plus no future task, especially right after a customer-facing interaction, is the single most actionable stall signal there is — because unlike the four reasons above, it isn’t a diagnosis about the buyer at all. It’s a gap in the rep’s process, and it’s fixed by scheduling something, not by understanding the customer better.

Sort every stalled deal into this bucket first, before spending any time on the four above. A deal with no next step hasn’t been diagnosed yet — it’s just been dropped.

04

Two lenses for testing a stalled deal

Once a deal has a next step and is still stalled, use one of these to work out what’s actually missing. Pick the lens by how complex the sale is, not by habit.

BANT — fast qualification
Budget, Authority, Need, Timing. Four questions: can they pay, is the right person engaged, is there a real problem, is there a deadline. Use it for shorter cycles and lower-complexity deals, where one contact usually carries the whole decision.
MEDDIC — complex, multi-stakeholder deals
Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion. Six questions built to test whether the buyer’s organization can actually make the decision, not just whether one person likes the product. Use it once more than one stakeholder or a formal procurement process is involved.

Run whichever lens fits against every stalled deal, and treat an unanswered question as the finding rather than skipping to a guess. A deal in late stage where nobody can name the economic buyer isn’t “probably fine” — it’s a deal that failed MEDDIC’s most basic test three stages ago and nobody noticed because the stage name kept advancing anyway.

Seven questions for any deal past its expected stage age
1. Is there a dated, mutual next step on the calendar?
2. Has a buyer interaction happened recently, and is it actually tied to this deal?
3. Do we have a verified pain statement with a number attached to it?
4. Has the economic buyer been engaged, and is more than one stakeholder involved?
5. Is there an agreed decision process, procurement path, and target date?
6. Does the champion have the material and the internal standing to make the case without us in the room?
7. If the buyer stopped responding, which of the five reasons is most plausible — and what specific evidence supports it?
If questions 1, 4, or 5 come back unanswered, treat the deal as at-risk regardless of what stage it’s sitting in or what probability a rep has assigned it.
05

A worked example

Back to the 14-person services firm from System 01, and the 14 deals stalled in Proposal Sent. Running the seven questions against each one splits them cleanly.

6 deals: no dated next step

  • Recent activity, no calendar entry. Every one of these gets a call booked this week — nothing else has been diagnosed yet, because nothing else needed to be.

5 deals: budget or authority never confirmed

  • Proposal was sent to a single champion-level contact. No one with sign-off has ever joined a call. These get a multi-threading push before anything else, or an honest downgrade in probability.

The remaining 3 split further: one has a champion whose email started bouncing two weeks ago (turnover), one has had three close-date slips with no new objection raised each time (indecision), and one turns out to have a competitor’s tool named explicitly in the notes from the last call (competitor selected, and this time the evidence actually supports the label).

Fourteen deals that looked like one problem — “stalled in Proposal” — turn out to be three different problems needing three different actions, and only one of the fourteen needed the sales manager to get involved at all.

Naming the cause tells you what’s wrong with a deal. It doesn’t yet tell you what to do about it, and treating a coaching conversation the same way you’d treat a genuine gap in the process wastes the one thing this audit was supposed to save. System 03 covers the decision: which stalled deals need a rep to act, and which ones are telling you something about how the pipeline itself is run.

Next in the Sales Pipeline Audit · System 03Fix the Deal, or Fix the Process 8 min read