How to run a weekly pipeline review: a practical playbook

The weekly pipeline review is the operating heartbeat of a sales team. Done well, it catches stuck deals early, calibrates the forecast, and gives managers specific coaching moments. Done poorly, it is a status-update meeting that everyone resents and nobody uses to make decisions.

Industry consensus from VC and consulting firms (Notion Capital, Stackmatix) converges on a specific shape: weekly, 30-45 minutes, deal-by-deal, tied to the qualification methodology. This post is a practical playbook for running that meeting well.

The job of a weekly pipeline review

Three things a weekly pipeline review should accomplish:

1. Catch stuck deals. Deals that have aged out of their expected cycle, lost momentum, or lost a champion. Flag early so there’s time to recover.
2. Calibrate the forecast. Rep commits, best-case, and pipeline buckets get reviewed. Manager adjusts based on judgment and signals. The output is the consolidated forecast for the week.
3. Coach reps on specific deals. The pipeline review is where managers do their most leveraged coaching: here’s the deal, here’s the risk, here’s what you should do next.

If your review does something else (team announcements, generic motivation, status updates for leadership) you have a different meeting that is pretending to be a pipeline review.

The reference agenda

For a weekly 30-45 minute pipeline review with 1-5 reps:

Minute 0-5: Baseline

Open with the week’s numbers. Weighted pipeline coverage, forecast delta vs. plan, top 3 at-risk deals from the AI/flag system, closed-won deals from the past week. 5 minutes maximum.

Minute 5-25: Deal-by-deal

Work through each rep’s commit and best-case deals. For each deal:

• Rep gives a 30-second summary: amount, stage, next step, risk flag
• Manager asks one or two targeted questions tied to the qualification framework (see Lead qualification framework: BANT, MEDDIC, and when each fits): “What’s the economic buyer’s signal this week?” “Have you confirmed the critical event?” “What’s the champion saying about budget approval?”
• If the answer is weak, the deal moves from Commit to Best Case or from Best Case to Pipeline, and a specific action gets assigned
• If the answer is strong, the deal stays in its bucket

20 minutes typically covers 15-25 deals across a 5-person team.

Minute 25-35: Pipeline health

Not deal-by-deal. The structural view:

• Stuck deals (dwell time > 2x median). who owns the plan to unstick each one
• Stale deals (no activity in 14+ days). move to best-case or close as lost
• Pipeline coverage ratio by segment and rep: flag anyone under 3x coverage for next quarter

Minute 35-40: Coaching moments

Pick one or two deals from the walkthrough where there’s a teachable moment. Walk through what the rep could have done differently, what to try next. This is where reps improve over quarters.

Minute 40-45: Buffer

Questions, follow-ups, action item review.

Common failure modes

Five mistakes that break pipeline reviews:

1. Treating it as a status update

If reps are reading from their CRM screens and managers are listening, you have a status meeting. Reviews require interrogation and decision-making. Managers should ask questions reps have to think about.

2. Not using the CRM data in the meeting

If reps are talking from memory and the CRM shows different numbers, the review is calibrating against two different realities. The CRM should be on screen, open to the deal under discussion.

3. No follow-through

Action items from the review need to show up in the CRM as tasks assigned to specific reps with specific due dates. If the action items live only in the meeting notes, they do not happen.

4. Too many deals, too fast

Trying to review every open deal in 45 minutes means spending 30 seconds per deal, which is a status update by another name. Focus on commits and best-case deals; let pipeline deals get worked without live review.

5. The wrong attendees

Pipeline reviews are rep plus their direct manager. Not the VP, not peers, not a presentation to leadership. Those are different meetings. Mixing audiences dilutes the coaching value.

Cadence beyond weekly

A healthy sales operating cadence usually has three loops:

• Weekly: pipeline review (above)
• Monthly: forecast review (consolidated across the team, run by VP or Director)
• Quarterly: business review (QBR with leadership, including win-loss analysis and planning for next quarter)

Each loop uses the data from the previous. Weekly reviews feed monthly forecasts; monthly forecasts feed quarterly planning. Teams that run all three in a disciplined cadence tend to forecast more accurately than teams that run only one.

How Strkr supports the weekly review

Strkr is designed to make the weekly review easy to run:

• Weekly submit workflow in AI-assisted forecasting runs on a configured schedule. Reps submit their forecast; managers see the roll-up by Monday morning.
• AI-flagged risk deals surface at the top of each rep’s pipeline, so the manager has a specific list to prioritize in the review.
• Formula reports produce pipeline coverage, forecast attainment, and deal velocity by rep and segment, scheduled to deliver via email or Slack before the meeting.
• Action items created in the review become tasks on the deal record, assigned to the rep, with due dates. Follow-up on next week’s review is one click.

The design target: a manager running a 30-45 minute weekly review for 5 reps should have the data on screen, the AI flags prioritized, the action items captured, and the next-week follow-up loop in place. All of it on one platform.

Related reading: How to choose a CRM: a practical buying framework covers the broader CRM buying question, and Lead qualification framework: BANT, MEDDIC, and when each fits covers the framework that pipeline reviews walk through.

Conclusion

A weekly pipeline review is the operating heartbeat of a sales team. 30-45 minutes, deal-by-deal on commits and best-case, pipeline health view, coaching moments, action items into the CRM. Done consistently, it catches stuck deals, calibrates forecasts, and improves rep performance over quarters.

Done as a status update, it is a meeting that reps resent and managers do not act on. The difference is whether the review drives decisions or just reports them.