How to Run a Pipeline Review That Finds Dead Deals Instead of Restating Them
Most pipeline reviews are a CRM readout with a manager nodding along. Here's a five-question interrogation that forces reps to prove a deal is actually alive.
Most pipeline reviews I've watched — and I include ones I ran badly early in my own career — go the same way. The rep pulls up the CRM, reads the stage, the close date, and the amount, adds "feeling good about this one," and the manager nods and moves to the next row. Twenty-five minutes later everyone's covered twelve deals and diagnosed none of them. Four weeks after that, three of those twelve get marked closed-lost with a reason code like "budget" that nobody predicted, because the meeting was never built to predict anything — it was built to restate what the CRM already said, out loud, to another human.
Why "where's this one at" doesn't work
It's an open question that lets the rep choose which facts to volunteer, and reps — reasonably, not maliciously — volunteer the facts that make the deal sound alive. "Where's this one at" gets you a summary. It doesn't get you evidence, and a manager can't cross-examine a summary because there's nothing underneath it to press on. The fix isn't a better version of that question. It's five specific, closed questions that force the rep to produce something they either have or don't have.
The five questions
- "What did they actually say last time you spoke — give me the sentence." Not a paraphrase, not "they were positive," the words. A rep who can't produce anything close to a quote either hasn't spoken to the buyer recently enough to be trusted on this deal's status, or is translating politeness into commitment. Reps who've had a real conversation almost always remember a specific line.
- "Who else at the account knows this deal exists, and what does each of them think?" This forces named people, not "the team is bought in." If the answer is one name, you've found a single-threaded deal wearing a multi-threaded label, and you now know exactly who the rep needs in front of before the next review.
- "What's the next step, and who put the date in the calendar — you or them?" A step the rep proposed and the buyer hasn't confirmed is a hope, not a next step. A step the buyer initiated or actively scheduled is a fact. This one distinction catches more phantom momentum than anything else on this list.
- "What has the champion done for this deal without you asking them to?" Enthusiasm is cheap and easy to perform in a sales conversation. Unprompted action — looping in their boss, chasing procurement, forwarding a business case internally — is the only reliable evidence the champion is actually spending their own political capital. If the answer is "nothing yet, but they're really keen," you have a cheerleader, not a champion.
- "If this closes on the date in the CRM, what has to be true between now and then that isn't true today?" This forces the rep to name the gap out loud — security review, procurement sign-off, budget reallocation, a second stakeholder who hasn't weighed in — instead of leaving it implicit. Most slipped deals slip on something the rep could have named in this question three weeks earlier, if anyone had asked.
What the answers actually tell you
| Question | Vague answer (red flag) | Evidence-backed answer |
|---|---|---|
| The quote | "They seemed really positive" | "She said, 'get me the security questionnaire and I'll take it to my VP Friday'" |
| Who else knows | "The team's bought in" | "Priya, the finance lead, and their ops director have all seen the proposal — ops director asked for a change to the SOW last week" |
| The next step | "I'm sending updated pricing over Thursday" | "She booked us in for the 14th to walk her VP through it" |
| Champion action | "He's really excited about it" | "He set up the call with his VP himself and sent us the internal deck he built to sell it in" |
| What has to be true | "I don't see any blockers" | "Legal still hasn't reviewed our DPA, and that's taken six weeks on their last two vendor deals" |
Running the meeting differently
Time-box it: eight minutes per deal, and only deals with genuine doubt get the full five. A deal where last review's answers were solid and nothing's changed gets a thirty-second spot check on questions one and three only — did the conversation happen, is the next step still buyer-owned. This stops the meeting sprawling across every deal at equal depth, which is exactly what makes people tune out by deal number seven.
Before the meeting, have reps come with question two already mapped out — a Multi-Threading Stakeholder Map Template takes ten minutes to fill in and turns "the team's bought in" into names you can actually check. For question four, a running Champion Tracker Template means the manager isn't asking the rep to recall it live and possibly round up.
What it costs you to skip this
The deals this catches are always the same shape: verbally "committed" for six straight weeks with zero calendar activity in that window, a champion who talks a good game but has done precisely nothing unprompted, a next step that exists only in the rep's task list. Left alone, they don't die quietly — they die in week eleven of a twelve-week quarter, taking the forecast number down with them and leaving no time to backfill. Caught in week three or four, through a Stalled Deal Revival Playbook or a straightforward kill decision, they cost you a line in the pipeline instead of a miss on the board.
The CRM will tell you a deal is in Stage 3. It will not tell you whether anyone on the buying side still wants it there. That's the only thing worth spending a pipeline review's time on.