Skip to content
Sales Pitch

How to Run a Pipeline Review That Isn't a Status Meeting

Most pipeline reviews confirm what's already in the CRM. A format built to surface risk instead: time-in-stage signals, sharper questions, and a monthly check.

, 4 min read, Sales leadership

Also available in Français, Español

Share on LinkedIn, X, Facebook

Sales manager reviewing pipeline deals with a rep at a desk
Photo Trey Gibson, Unsplash

Key takeaways

  • A pipeline review that only confirms stage and close date produces confirmation, not risk detection.
  • Time-in-stage compared to your team's median is a faster risk signal than any conversation about confidence.
  • The review only improves if you track which flagged deals actually slipped and which didn't, then adjust the questions.

Every sales leader has sat through a pipeline review that was really just a rep reading the CRM out loud: stage, amount, close date, "still on track." Nobody in the room learns anything they couldn't have found by opening the tool themselves. Here's a format built to surface risk instead of confirming what's already on the screen.

Why the standard pipeline review fails

Most pipeline reviews are a rep narrating fields that are already visible before the meeting starts. A manager nodding along learns nothing new, and the meeting becomes overhead reps resent and managers dread. The point of a pipeline review isn't confirmation, it's finding the deal that's about to slip before it slips.

Start with what changed, not what's next

Flip the standard opening question. Instead of "what's the status," ask "what's changed since we last talked about this deal." A deal with nothing new to report in two weeks is itself the finding, whether or not the rep frames it that way. Silence in the CRM is a risk signal, not a neutral state.

Let stage velocity decide who gets airtime

Reviewing every open deal in stage order wastes the room's best attention on deals that don't need it. Pull each deal's time-in-stage against your team's median for that stage. A deal sitting in "proposal" for three weeks when your median is eight days deserves five minutes of real scrutiny; a deal that entered the stage yesterday doesn't need discussion at all this week.

SignalWhat it meansResponse
Time in stage 2x the medianDeal has stalled, cause unclearDeep dive this review
No activity logged in 10+ daysDeal may be dead or single-threadedAsk for the last real conversation
Close date pushed twiceRep's read on the deal is offRe-qualify from scratch
One contact, no internal championDeal depends on one relationshipCoach a multi-threading plan

Ask the questions that expose risk, not confidence

Replace "are you going to close this" with questions the rep can't answer with optimism alone: who else at the account has seen the proposal, what did the economic buyer say in their own words, what happens if the champion changes jobs next month. A rep who can't answer specifically is telling you the deal is thinner than the stage suggests, even if they don't say so directly.

Keep score on the review itself

A pipeline review that never checks its own predictions against outcomes never gets sharper. Once a month, look back at the deals flagged as at-risk four weeks earlier: how many actually slipped, how many recovered, and what the review missed. That feedback loop is what turns a weekly ritual into an actual sales-management tool instead of a meeting that exists because meetings exist.

Common pitfalls when you switch formats

Teams that move to a risk-based review often stumble in three predictable ways. The first is treating the new format as an ambush: reps who are suddenly asked pointed questions about the economic buyer or the champion's job security, without warning that the format has changed, feel like they're being tested rather than supported. Explain the shift before the first session, including why it's happening, so reps understand the goal is catching problems early, not catching them off guard.

The second pitfall is manager overcorrection: swinging from a status meeting into something that feels like an interrogation. The tone matters as much as the questions. A manager asking "who else has seen the proposal" in a curious, problem-solving voice gets a different answer than one asking it like a prosecutor building a case. If reps start hiding shaky deals rather than surfacing them, the format has failed even if the questions were right.

The third is applying the new scrutiny retroactively, using it to relitigate deals that already closed or already slipped under the old format. That turns a forward-looking tool into a blame exercise, and reps will route around a review they expect to be punished by. Start the new format with the deals currently open, and resist the temptation to score last quarter's calls against a bar that didn't exist yet.

Rolling the format out gradually also helps. Run it with one or two reps first, work out where the risk signals produce false positives (a deal genuinely can sit two weeks without an update and still be healthy), and adjust the thresholds before applying them team-wide. A format that flags too much noise trains reps to ignore the flags altogether, which defeats the purpose as thoroughly as a review that flags nothing at all.

Frequently asked questions

How long should a pipeline review take?
Enough for the deals that show real risk signals and nothing for the ones that don't. A weekly review of 30-45 minutes covering 8-12 flagged deals beats an hour spent walking every open opportunity in order.
Who should run the pipeline review, the rep or the manager?
The manager sets the agenda by pulling the risk signals in advance; the rep does the talking. If the manager is the one summarizing each deal from memory, the review has become a status update rather than an inspection.
How is a pipeline review different from a forecast call?
A forecast call asks what will close this period and rolls up a number. A pipeline review looks earlier in the cycle, across the whole pipeline, to catch problems before they ever reach the forecast conversation.