How do I run a 25-minute pipeline review that's actually useful?
Limit to one manager + their 2–3 top reps. Review 3–4 deals max. Ask "Why'd this move to Stage X?" not "When will it close?" Most pipeline reviews are theater because they focus on hope, not process.
Why 25 Minutes is the Right Time Any longer and you're swimming in deal narratives, not driving behavior change. Anything shorter and you're skimming.
The Format
Minute 0–2: Setup
- "We're reviewing your top pipeline opportunities. I want to understand your deal selection, not predict close dates. If a deal doesn't have clear next steps, that's the red flag we're hunting."
Minute 2–8: Rep-Led Walk (Deal #1) Rep talks through ONE opportunity (not all). They say: "This is a $50K deal at [Company]. We're at Stage 2 (Discovery). Here's what happened: I cold-called their VP Ops, they said they're exploring options for Q3, and we scheduled a full discovery call for next Thursday."
You ask, in order:
- "What did they say their problem is?" (Listening for whether the AE explored pain or assumed.)
- "What's your confidence they'll actually show up to the discovery call?" (Qualifier: is this a "real" meeting or a courtesy?)
- "Who else have you met, or will meet?" (Multi-threading check.)
- "What's the actual next step after discovery, and when will that happen?" (Forcing clarity.)
DO NOT ask: "When will this close?" or "How much pipeline do you have?" Those are hope, not process.
Minute 8–14: Deal #2 (Similar Flow) Rep presents a deal in a different stage (usually mid-cycle, like Stage 3–4). Same questions, but focus on deal progression.
You're hunting: "Did they move through discovery properly, or did they jump straight to proposals because the buyer seemed interested?"
Minute 14–20: Deal #3 (The At-Risk or Final Stage) If there's a deal near close or at risk, review it here. Ask:
- "What could still kill this?" (They should have 2–3 scenarios.)
- "Who has final authority, and have you confirmed budget?" (MEDDPICC: Authority + Money.)
- "What's your Plan B if they say no?" (Forcing realistic scenario-planning.)
Minute 20–25: The Takeaway Do NOT give feedback on each deal. Instead, give one behavioral observation: "I'm noticing that in Deals 1 and 2, you're not confirming timeline explicitly. In the next discovery call, add this question: 'If we solve this problem, how soon would you want to implement?' It changes everything."
One actionable insight beats ten generic compliments.
The Metrics You're Actually Checking
| Metric | What It Means | Red Flag |
|---|---|---|
| Clarity of pain | AE can articulate buyer's problem in one sentence | "They said they're exploring" (no pain) |
| Multi-threading | Deal has 2+ contacts, not just one | "Just met the VP" (single-threaded) |
| Next step in writing | Rep says "Next Tuesday, 2pm, we do X" | "They'll reach out" (vague) |
| Qualification signals | AE confirms timeline, budget, authority | "Seems interested" (hope) |
| Stage progression | Deal moved for a reason, not by default | "We've been here 2 months" (stalled) |
What Makes a Pipeline Review Useless
- Focuses on $ totals: "You have $200K in pipeline, need to get to $400K." (No process insight.)
- Asks for close date predictions: "When will Deal X close?" (Rep says "probably next month" = guessing.)
- Includes 10+ deals: Too much detail, no pattern, manager doesn't remember anything.
- Rep narrates, manager doesn't ask questions: Rep tells a story; manager nods. Zero coaching.
- Ends with "keep pushing": Most useless advice possible.
After the Review Rep leaves with ONE thing: "In your next discovery call, confirm timeline before we build a proposal."
That one thing, executed on 4 deals, changes their win rate 3–5 points.
TAGS: pipeline-review, coaching, sales-management, forecasting, deal-review