A pipeline review exists to decide what will move a deal forward, not to find out where it stands. It differs from the forecast, which is an exercise in commitment: merging the two stops anyone admitting a deal is stalling. Five to eight deals per session, four questions each, and every deal leaves with a dated action and an owner.
We sit in a lot of pipeline reviews, and the scene repeats from one company to the next. The manager projects the deal list and asks each person where they stand. The first rep runs through fifteen deals, the third checks their phone, and by the end of the hour everyone knows what they knew walking in.
This is not a discipline problem. It is a purpose problem: the meeting has drifted into information gathering when it should serve decisions. A good review does not narrate deals, it moves them, and you recognise it by leaving with actions rather than with an updated table.
Separate the review from the forecast
This is the most expensive confusion, and it costs nothing to fix.
The forecast answers a leadership question: how much will we sign, and what can we commit to. It is an exercise where the rep defends a number. We detail its mechanics in making your sales forecast reliable.
The pipeline review answers a different question: on this specific deal, what needs doing this week. It is an exercise where the rep exposes difficulties and asks for help. The two cannot share a slot, because nobody admits a deal is stalling in the meeting where they are asked to commit to it.
So hold the forecast monthly, the review weekly, and tell the team explicitly that these are two different meetings. That is often the only change needed for people to start speaking.
Do not review everything
The second flaw is exhaustiveness. Running through forty deals looks rigorous and produces nothing: time per deal drops to a minute, nobody digs, and important deals get the same attention as small ones.
Pick five to eight deals, and announce them the day before so everyone arrives prepared. Three families deserve the slot. Those that must close this quarter, because that is where time pays most. Those with no event in two weeks, because silence is the beginning of loss. And one or two large young deals, better framed at the start than rescued at the end.
The rest of the portfolio does not need a meeting, it needs a well-kept system. If you use the review to find out what is happening, your data is not doing its job, and you pay for that flaw every week in team time. That is the subject of your revenue operations foundation.
The four questions
On each selected deal, four questions are enough. They take a few minutes and almost always reveal the real problem.
Who decides, and who else must say yes. This is the question that kills the most illusions. Many well-rated deals rest on one enthusiastic person with no power to sign. If the rep cannot name the final decision-maker and the people who can block, the deal is not qualified, whatever amount is recorded.
What is the next step, with a date accepted by both sides. Not “I will follow up next week”, which is an intention. “Framing workshop Thursday 2pm with the finance director, invitation accepted”, which is a fact. A deal with no dated next step is not moving, it is waiting.
What could make this deal fail. Asking for the risk rather than the probability completely changes the quality of the answer. A rep asked “how confident are you” gives a comfortable percentage. The same rep, asked what could go wrong, tells you they have never met the real decision-maker, or that the budget is not voted.
What do you need. This is the question that transforms the meeting. A call from the founder, a reference in the same sector, a technical colleague to reassure. If nobody ever asks for anything in your reviews, it is not that everything is fine: it is that asking for help reads as an admission, and you have a climate problem before you have a pipeline problem.
The format: 45 minutes, five rules
Format matters as much as content, because a ritual that overruns eventually gets dropped.
Fixed slot early in the week, 45 minutes maximum. Deal list sent the day before. Each deal gets a capped time, five to seven minutes, and the manager cuts when it is reached. No deal leaves without an action, an owner and a date, recorded during the meeting rather than after. And the next session opens on the previous session’s actions: that single point separates a ritual that produces from one that decorates.
One rule of conduct is worth setting in the first session: you talk about the deal, never about the person. As soon as a review becomes a tribunal, reps learn to present clean deals and hide the ones that are stalling, which are exactly the ones where you could help.
What the manager should and should not do
The review is the best coaching moment of the week, provided you resist two reflexes.
The first is taking the deal over: “leave it, I will call the client”. That unblocks one deal and teaches nobody anything. The second is turning each case into a lecture on your own method. Ask the four questions, let the silence do its work, and intervene only on the next step.
The deeper work does not happen here but in the one-to-one, where you handle skills rather than deals. The review handles deals, the one-to-one handles the person: merging them weakens both. It is also the ritual that structures a newcomer’s integration, as we describe in ramping a new sales rep.
The three numbers that say whether it works
None of them is a tool completion rate.
How many deals whose next step actually happened the following week. How many deals were removed from the pipeline because you decided they were not real, which is a sign of health rather than failure. And how many requests for help were made during the session.
If those three numbers are low, your review is a disguised status report. Drop it for two weeks, let the data do the reporting, and restart it with five deals, four questions and 45 minutes. The difference shows by the third session.
Where to start
At the next session, do not ask each person where they stand. Announce five deals the day before, and ask the four questions on each, without skipping one even when the answer looks obvious.
You will probably find that two of the five do not survive the first question. That is uncomfortable, and it is the best return on your week.
Frequently asked questions
- What is the difference between a pipeline review and a forecast?
- The pipeline review looks at each deal to decide what to do next: it is oriented towards action. The forecast aggregates deals to give leadership a number: it is oriented towards commitment. Holding them in the same slot pushes salespeople to defend their deals instead of asking for help.
- How many deals should you review?
- Five to eight per session, never all of them. Three families deserve the slot: those that must close this quarter, those that have not moved in two weeks, and one or two large young deals better framed early. Running through forty in a row moves none of them.
- How often should you hold a pipeline review?
- Weekly in most B2B teams, in a fixed slot of no more than 45 minutes. The right frequency follows the cycle length: a three-week cycle needs a weekly point, a twelve-month cycle can be steered fortnightly without losing anything.
- How do you know the review is working?
- Three numbers, none of which is a CRM completion rate: how many deals whose next step actually happened that week, how many deals removed from the pipeline because you decided they were not real, and how many requests for help were made in the session.