How to Run a Weekly Sales Pipeline Review (Deal-by-Deal, 60 Minutes)

Ask most B2B SaaS teams to describe their pipeline review and you'll hear the same meeting: the manager shares a spreadsheet, each rep reads their commit number, someone asks "what's the deal with Acme," the rep says "feeling good about it," and everyone moves on. Forty-five minutes, zero deals moved.

That's forecast theater. A real pipeline review is a working session that changes the state of the pipeline while the meeting is happening. Here's the structure that does that, tuned for velocity teams of one to ten reps.

What is a weekly pipeline review?

A weekly pipeline review is a recurring deal-by-deal working session where a sales team inspects every active opportunity against the pipeline's stage exit criteria, agrees on the single next action for each deal, and applies a stalled-deal protocol to anything that has stopped moving. It is distinct from a forecast call (which aggregates numbers for leadership) and from coaching (which develops rep skills using recorded calls). In a velocity sales motion, the review runs weekly, takes 45 to 60 minutes, covers deals individually rather than as a roll-up, and ends with every deal owning a named next step and a date. Teams that run it well see cycle times compress and slipped-deal rates fall within a quarter, because problems surface two stages earlier than they would in a forecast-only cadence.

How long should a pipeline review take?

Sixty minutes for a team of two to five reps, weekly. Under 15 active deals, 45 minutes is enough. If you can't get through the pipeline in an hour, you're either reviewing deals that are too small to discuss individually (set a dollar threshold and batch the rest) or the conversation keeps drifting into coaching (see below).

The cadence matters more than the length. Weekly is right for velocity motions because deals move in days, not months. A biweekly review on a 21-day cycle means most deals are born and die between meetings.

The 60-minute agenda

The 5 questions to ask on every deal

The power of the review is that every deal gets the same five questions. Reps learn to pre-answer them, which means the meeting gets faster every week and the CRM gets cleaner, because the questions map to fields.

1. What stage is it in, and does it actually meet that stage's exit criteria? Half of all "stuck" deals are just mis-staged. Check the criteria, not the vibe.
2. What changed since last week? If the answer is "nothing" two weeks in a row, it's a stalled deal regardless of what the rep feels about it.
3. What's the buyer's next step, in their words? Not the rep's next step. If the buyer hasn't committed to doing anything, there is no deal motion, only rep motion.
4. What could kill this deal? The rep names the biggest risk out loud. Deals lose to unspoken risks; naming them turns risk into a task.
5. What is the next step and when? Named action, named date, logged in the CRM before the meeting ends. A deal that leaves the review without one is stalled by definition.

Red flags to catch in the room

The stalled-deal protocol

A deal that exceeds its stage's time benchmark twice gets exactly three options, chosen in the meeting:

• Requalify. Run it back through the qualification rubric. If the trigger, authority, or timeline no longer holds, it was never a deal. Move it to nurture.
• Revive. One direct, honest touch: "It seems like this has lost momentum on your side. Should we close the file, or is there a real path here?" Buyers respect the question, and it converts stalls into answers.
• Close lost. The cheapest outcome for a dead deal is marking it dead. Every stalled deal carried in pipeline inflates coverage and corrupts the forecast.

What a pipeline review is NOT

It is not coaching. The moment the meeting becomes "let's work on how you handle pricing objections," you're developing one rep while three others check Slack. Coaching happens in separate sessions built on recorded calls; the review only surfaces what to coach later. The distinction sounds pedantic and is actually the whole game: teams that merge the two meetings get half of each. I wrote about the difference in Sales Coaching vs Pipeline Inspection.

It is also not a forecast call. Forecasting takes the review's output (clean stages, honest next steps) and aggregates it. If your stages are honest, the forecast takes ten minutes. If they're not, no amount of forecast meetings will fix it. (Read more: How to Forecast B2B SaaS Sales.)

Making it stick

Three implementation notes from teams that run this well:

• Open every meeting with last week's commitments. The read-back list from segment five becomes the accountability opener. Deals with missed next steps go first.
• Put the five questions in the CRM. When the questions map to fields, the review updates the system of record in real time instead of generating a to-do list nobody does.
• Track two numbers to know it's working: average time-in-stage and the percentage of deals with a dated next step. Both should improve within four weeks. If they don't, the meeting has drifted back to theater.

And if the review keeps surfacing the same root problems (mis-staged deals, junk pipeline, no documented exit criteria), that's not a meeting problem. That's a missing playbook. The SAILS engagement builds it: pipeline stages with exit criteria, the qualification rubric, and the meeting cadence, documented and installed with your team.