I've sat through hundreds of pipeline reviews. The majority follow the same pattern: the manager opens the CRM, the rep reads out deal names and amounts, the manager nods, and the meeting ends. Nothing changes. The same deals show up next week. The forecast drifts.
A pipeline review isn't a report. It's a decision session. The goal is to come out of it with specific actions that will either close deals or remove them from the forecast. If you leave the meeting and nothing has changed — no action assigned, no deal updated, no blocker surfaced — you ran a status report, not a pipeline review.
What a Pipeline Review Should Accomplish
Three goals. If your pipeline review isn't achieving all three, fix the format before fixing the people:
- Identify stuck deals — deals that haven't moved in 14+ days need an honest diagnosis: are they stalled because of a blocker, or are they dead deals the rep won't admit to?
- Surface blockers — what is actually preventing this deal from moving? Is it a technical evaluation, a legal review, a budget approval, a multi-stakeholder alignment problem? The manager needs to know so they can help remove it or escalate.
- Calibrate the forecast — does the "Commit" column actually represent what will close this quarter? Commit means the rep is willing to be held accountable for it. If Commit is inflated, the forecast is a fiction, and planning breaks down.
A pipeline review is not a progress report. If the rep is narrating deal history, stop them. You want to know what's happening now and what will happen next — not what already happened.
Who Should Be in the Room
Keep it small. The wrong people in the room turn a 45-minute session into a 90-minute performance review.
- AEs whose deals are being reviewed — ideally one at a time if possible, or a small cohort of 2–3
- Front-line sales manager — this is their primary operating meeting, not a check-in
- RevOps — optional, but useful for forecast hygiene and CRM accuracy accountability
- CSM — only if an existing customer expansion deal is on the table
- Founder or VP Sales — for key deals above a certain ACV threshold, or when a deal requires executive engagement
Don't invite the whole sales team. Reps sitting through deals that aren't theirs is wasted time and breeds disengagement. If you want team-wide visibility, share a summary doc after the call.
The 45-Minute Pipeline Review Agenda
| Time | Section | What happens |
|---|---|---|
| 0–5 min | Forecast call | Rep states their Commit and Best Case for the week. Manager notes any changes from last week. No deal-level discussion yet. |
| 5–25 min | Commit + Best Case deals | Deal-by-deal review using the 5 questions below. Only deals in Commit and Best Case. Goal: validate, de-risk, or downgrade each deal. |
| 25–35 min | Stuck deals | Any deal that hasn't progressed in 14+ days. Honest diagnosis: stalled or dead? What's the next action and who owns it? |
| 35–40 min | Pipeline build | Top-of-funnel check. Are new deals entering pipeline at the right rate? Any coverage gaps for next quarter? |
| 40–45 min | Commit updates + close | Rep updates forecast category in CRM live. Manager confirms any deals that need executive support or escalation. Actions logged. |
The 5 Questions to Ask for Every Deal
These five questions cut through the narrative and force honest deal qualification. Ask them in this order for every deal in Commit and Best Case:
5 Diagnostic Deal Questions
What's the next step and when exactly?
Not "following up" — a specific action with a specific date. If the rep can't name it, the deal has no momentum.
Who's the economic buyer and have we spoken to them?
Champion ≠ buyer. If the rep has only spoken to an evaluator or influencer, the deal is at risk. The economic buyer controls the budget.
What's the compelling event?
Why does this deal need to close by the date the rep says it will? If there's no external forcing function — a contract renewal, a product launch, a regulatory deadline — slippage risk is high.
Is there a paper process / legal / security review pending?
These steps add 2–6 weeks to any deal and are often discovered late. Surface them now, not the week before close.
What would make this deal slip?
Ask the rep directly. The answer reveals both the real risk and how honestly the rep is thinking about their own book of business.
The Template (Copy-Paste Ready)
Send this as a pre-read 24 hours before the call. Reps fill it out for their Commit and Best Case deals. The meeting becomes a conversation about what's already been documented — not a live update session.
Common Mistakes
- Reviewing all deals equally. You have 45 minutes. A deal in pipeline stage 1 does not deserve the same time as a deal in Commit with a close date in 10 days. Prioritise by forecast category, not pipeline stage.
- No pre-read sent 24 hours before. If reps are filling in deal details live during the call, you've already lost 15 minutes and the session will feel reactive. The pre-read turns the meeting into a conversation, not a data entry session.
- Manager talks more than rep. The manager's job is to ask questions, not to tell the rep what to do. If the manager is explaining deal strategy during the review, the session has become coaching — schedule that separately.
- No CRM update required after the call. If the review produces no CRM update — no stage change, no next action logged, no forecast category change — the session produced no output. Make CRM updates during the last 5 minutes of the call, not afterward.
Before your next pipeline review, run a quick coverage check. If your pipeline is below 3x quota for the quarter, the review is treating a symptom, not the disease. Use the Pipeline Coverage Calculator to see where you stand.
FAQ
How often should you run a pipeline review?
Weekly for deals in Commit and Best Case categories. Monthly for early-stage pipeline health. The weekly review should cover deals that could close within the current quarter — not every deal in CRM. A quarterly pipeline review is a different, broader exercise focused on top-of-funnel build and ICP alignment.
Should pipeline reviews be one-on-one or with the full team?
Neither extreme works well. One-on-ones miss the cross-deal pattern recognition that happens when a manager reviews multiple reps' pipelines in the same sitting. Full team reviews waste time — reps sit through 40 minutes of deals that have nothing to do with them. The right format is the AE whose deals are being reviewed, their direct manager, and RevOps or VP Sales for key deals. Keep it small and deal-specific.
What's the most common pipeline review mistake?
Reviewing deals in order of stage rather than in order of close probability. You have 45 minutes. Spend 70% of it on deals that could close this quarter — Commit and Best Case — not on deals that entered the pipeline last week and are still in Discovery. Prioritise by forecast category, not pipeline stage.