How to run a 15-minute weekly pipeline review that actually works

The weekly pipeline review is one of the most consistently misused tools in sales management. In most teams, it works like this: each rep goes through their deals one by one, reads out the stage and value, says "I'm following up on Thursday," and the manager nods. Forty-five minutes later, nothing has changed and nobody is clearer on what to do next.

A well-run pipeline review should take fifteen minutes and leave every person in the room with a specific action they're taking before the next one. Here's how.

Why most pipeline reviews waste everyone's time

Most pipeline reviews fail because they're structured as reporting sessions, not decision-making sessions. The manager asks what's happening. The rep reports what's happening. The information was already in the CRM. Nobody needed a meeting for that.

The second problem: reviews focus on deals that are progressing well. Reps naturally gravitate toward their wins. The deals that need the most attention, the ones stuck in the same stage for three weeks, the ones the rep has been avoiding, tend to get glossed over.

A good pipeline review inverts this. It starts with the problems and ends with decisions.

The 15-minute format

This structure works for a team of two to eight reps reviewing together:

• Minutes 0–3: The board scan. Everyone looks at the pipeline, preferably a shared screen showing the kanban view. No talking. Just looking. Identify deals that have moved since last week (good) and deals that haven't (needs discussion).
• Minutes 3–10: Stuck deals only. For each deal that hasn't moved: what's blocking it? What's the specific next action and who owns it? Set a date. Move on. No deal gets more than 90 seconds unless there's a genuine decision to be made.
• Minutes 10–13: Close-this-week deals. Which deals are expected to close in the next 7 days? What needs to happen to make that happen? Remove any blockers.
• Minutes 13–15: One coaching moment. The manager picks one pattern they noticed, a deal stuck for the same reason as last week, a stage that's consistently full, and makes one observation. Not a lecture. One thing.

The five questions that actually matter

For any deal that comes up for discussion, these five questions give you everything you need:

1. What is the prospect's specific reason for buying? Not your pitch, their stated problem. If no one knows, the deal isn't qualified.
2. Who is the decision-maker, and have we spoken to them directly? Deals stuck in discovery are often stuck because reps are working below the decision-maker.
3. What's the agreed next step, and when does it happen? If the answer is "I'll follow up," that's not a next step. A next step has a date and a specific action.
4. What's the risk to this deal? Competitor, budget, timing, internal politics. Name it specifically.
5. What can we do in the next 48 hours to move this forward? One action. One owner. One date.

What to do before the meeting

The review is only 15 minutes if reps come prepared. Each rep should review their own pipeline before the session, flag any deals they want to discuss, and, if your CRM supports it, check the rotting alert list. Deals flagged by deal rotting alerts are your automatic agenda for the stuck-deals section.

In Klooser, the activity inbox and pipeline board give each rep a live view of their deals and outstanding activities. A two-minute scan before the review is all the prep needed.

How often and with whom

Weekly is the right cadence for most small teams. More frequent becomes overhead. Less frequent means deals go cold between reviews.

Keep the group small, sales manager plus the reps who own the deals being reviewed. No support, no marketing, no executives unless there's a specific reason. Every extra person in the room adds time and reduces the quality of the conversation.

The goal of every pipeline review is to leave with fewer stuck deals than you started with. If that's happening consistently, the format is working.