How to run a B2B pipeline review that actually moves deals
Most pipeline reviews are theatre. The 60-minute format that surfaces stuck deals, unblocks them in-meeting, and cuts cycle time by weeks.
The average weekly pipeline review is 90 minutes of status updates. Reps read the CRM out loud, managers nod, nothing changes. The best pipeline reviews are 60 minutes of decisions, no status updates, and measurable movement.
The rule that changes everything: status is read async before the meeting. Reps update the CRM by Sunday night. Manager reviews Monday morning. Meeting starts at the first decision, not the first update.
The agenda has three parts: stuck deals, at-risk forecast, and one deep-dive coaching case. That's it. Any status update in the meeting itself is a red flag — the async prep failed.
Stuck deals get the most airtime. A stuck deal is any opportunity with no forward motion in 14+ days. Each one gets a five-minute discussion, a clear next action, and a named owner. No 'let me check back next week.'
The at-risk forecast is the second segment. Reps highlight the deals they're least confident in for the current quarter. The manager decides whether to double-down, sideline, or de-risk with a specific move.
The coaching deep-dive is what separates senior managers from great ones. One deal per week, examined end-to-end: what worked, what didn't, what the rep will do differently. Rotate the rep each week.
The forbidden question is 'what's the update?' Replace it with 'what's the next move?' The first invites a story; the second forces a decision.
The tell that pipeline review is working: cycle time trending down quarter over quarter, forecast accuracy tightening, and rep satisfaction scores rising because the meeting actually helps them close deals.
Frequently asked questions
Sales Playbooks — answered
- Weekly or bi-weekly pipeline reviews?
- Weekly for growth-stage teams, bi-weekly for stable enterprise motions with 90+ day cycles.
- Should managers pipeline-review in a group or 1:1?
- Group for accountability and pattern-sharing, 1:1 monthly for deeper coaching. Both serve different purposes.
- How long should a pipeline review be?
- 60 minutes for a team of 6–10 AEs. Above that, split into subgroups.
- What's the most common pipeline review mistake?
- Letting status updates consume the meeting. Push status async; use meeting time for decisions.
Growth Broker editorial
Filed under sales playbooks