A pipeline review is a recurring meeting where a sales manager and each account executive go through open opportunities to decide what every deal needs next. Done well, it uses buyer evidence rather than rep optimism, so stalled deals surface weeks before the close date moves instead of on the day it does.
This guide is for sales directors who run weekly pipeline meetings and leave them with status updates instead of decisions, and for the account executives who sit on the other side of the table. It covers what a pipeline review is for, how it differs from a deal review and a forecast call, the questions that expose a stalled deal, and how to prepare so the meeting is spent on strategy.
Key takeaways
- A pipeline review is a decision meeting: every deal discussed should leave with a next move, an owner and a date, or a decision to drop it.
- In a Gartner survey of sales operations, only 45% of sales leaders and sellers reported high confidence in their organization's forecasting accuracy.
- A deal stalls long before its close date changes: the earlier signs are a missed buyer commitment, a silent stakeholder or a next step with no date.
- The best pipeline review questions ask for buyer evidence, such as what the buyer did last week, rather than for the rep's opinion of the deal.
- A deal review goes deep on one strategic opportunity, while a pipeline review scans many deals to find the few that need attention.
What is a pipeline review?
A pipeline review is a scheduled conversation, usually weekly, between a sales manager and a rep or a team, about the deals currently open. Its job is to find out which deals are really moving, which are aging, and what the team will do about each one this week.
It sits between two other rituals. Our guide to building a sales pipeline covers stages and exit criteria, the structure the pipeline review relies on. The forecast call, on the other hand, turns the pipeline into a number for leadership. When the three blur together, the pipeline review becomes a forecast call in disguise, and nobody coaches anyone.
Pipeline review vs deal review vs forecast call
The three meetings use the same CRM data, but they answer different questions. Mixing them is the most common reason a pipeline meeting ends with a list of updates and no decisions.
A good rhythm uses all three: a weekly pipeline review to triage, a deal review for the two or three opportunities that matter most this quarter, and a forecast call that only uses deals the pipeline review has already tested.
Why pipeline reviews turn into status meetings
Most pipeline reviews fail in the same way. The manager asks “where are we on this one?”, the rep reads the CRM back aloud, and the meeting moves on. Forty minutes later the manager has collected updates and the team has made no decision.
Reps know the meeting rewards the right-looking number, not the right answer. Asked how they handle pipeline rules, one reply in an r/sales thread was blunt: “Most of us just lie.” Another rep in the same thread explained that they set opportunities far in the future “so I don't flag on any reports.” Those answers are not about honesty. They describe a meeting where saying a deal is at risk costs the rep more than hiding it.
The cost lands on the forecast. In a Gartner State of Sales Operations survey, only 45% of sales leaders and sellers had high confidence in their organization's forecasting accuracy. In Gong's Reality of Forecasting survey of 928 sales and revenue professionals, 52% said their organization regularly misses its forecast by more than 10%. A review built on opinion feeds a forecast built on opinion.
How to tell a stalled deal from a slow one
A slow deal is moving at the buyer's pace, with each side doing what it said it would. A stalled deal has stopped moving, but the CRM has not noticed yet. The close date is often the last field to change, which is why slippage feels sudden.
Look for these signs before the close date moves:
- A buyer commitment has passed without happening: the security questionnaire was due Friday and has not come back.
- The next step has no date, or the date is “after they discuss internally”.
- Only one person on the buyer side has replied in the last two weeks.
- The economic buyer has never been in a meeting, and nobody can say when they will be.
- Activity on your side is high and replies on their side are falling.
- The stage has not changed in longer than your typical time in that stage.
None of these signs is proof that a deal is lost. Each one is a question the pipeline review should ask out loud.
20 pipeline review questions that find stalled deals
These questions are grouped by what they test. A manager does not need to ask all twenty on every deal. Pick the group that matches the weakest signal, and ask for evidence every time: an email, a date, a name, a document.
Momentum: is the deal actually moving?
- What did the buyer do since last week, not what did we do?
- When was the last reply from someone other than our main contact?
- Which commitment did the buyer make in the last meeting, and has it happened?
- How long has this deal been in its current stage, compared with our usual time in that stage?
Buyer evidence: why would they buy, and why now?
- What problem did the buyer describe, in their words, and what does it cost them?
- What happens on their side if they do nothing this quarter?
- What event or deadline makes this date real for them, not for us?
- Has the buyer confirmed budget, or have we assumed it?
Stakeholders: who decides, and who have we not met?
- Who signs, and have we spoken to them directly?
- Is our contact a champion who sells for us internally, or a friendly contact who likes the demo?
- Which functions will review this before signature: finance, IT, security, legal, procurement?
- If our main contact left tomorrow, who else would we call?
Next step: is there a dated, mutual plan?
- What is the next meeting, on what date, with whom, and for what decision?
- Did the buyer agree to that step, or did we propose it and hear nothing?
- Is there a shared plan from today to signature, with dates the buyer has accepted?
- What has to be true for this deal to move to the next stage, and what is missing?
Risk and decision: should we push, change approach or drop it?
- Who else is the buyer talking to, including building it themselves or doing nothing?
- What is the one thing most likely to kill this deal, and what are we doing about it?
- What would make us drop this deal, and has it already happened?
- What help does the rep need from the manager this week: an executive call, a proof point, a pricing decision?
Question 10 is where many forecasts break. A contact who answers every email and loves the product is not the same as a champion who will defend the project in a budget meeting. Our guide to the MEDDPICC framework explains how to test the difference with evidence.
How to run a pipeline review in 45 minutes
The format matters as much as the questions. This structure keeps the meeting on decisions.
- Before the meeting, the rep updates the deals and flags the three that need help. The manager reads them in advance, so nobody reads the CRM aloud.
- Spend five minutes on movement: which deals changed stage, which slipped, which are new.
- Spend thirty minutes on the flagged deals and on any deal showing the stall signs above. Use one question group per deal.
- Spend five minutes on deals to drop. Closing a dead deal is a good outcome, not a failure.
- Spend the last five minutes confirming each next move, owner and date in writing.
One commenter in an r/sales thread on pipeline management described the right spirit: reps often fear pipeline reviews “because they think it's micromanagement when really it's a good way for your manager to identify blind spots and help direct where to spend time on.” The manager earns that trust by treating an honest “at risk” as useful information.
Example: a pipeline review on one stalled deal
Here is a short, fictional example built on our sample account, Helix Logistics. The rep reports the deal as on track for a close at the end of next month.
The deal is not lost. It is stalled, and the pipeline review found it before the close date moved. The rep leaves with three actions, each with a date, and the forecast becomes more honest.
How to prepare for a pipeline review as an AE
If you are the account executive, the best way to change the meeting is to arrive with the answers before the questions. For each deal you expect to discuss, write down:
- The last thing the buyer did, with a date.
- The next step, with a date and the people attending.
- The stakeholders you have met and the ones you have not.
- The single biggest risk and what you plan to do about it.
- The help you want from your manager, stated as a specific ask.
Flag your own stalled deals first. A rep who says “this one is slipping, here is why, here is my plan” gets coaching. A rep who defends every deal gets questions.
Keep deals moving between pipeline reviews
The weekly meeting can only find what the rep remembers. With twelve open deals, three stakeholders each and commitments on both sides, the signs of a stall are spread across the inbox, the calendar, call notes and the CRM. Reconstructing them before every review takes hours.
This is the work an AI sales agent is built for. Cobl, the AI sales agent for complex deals, watches your deals every day for silence, missed milestones and time in stage, and flags what needs attention by email, Slack or in Cobl (see manage deal momentum). It also separates a missing answer from a real risk and proposes one action per risk, so you walk into the pipeline review with the gaps already listed (see identify gaps and risks). It works like an AI sales assistant: Cobl prepares the next move, such as a follow-up draft or a business case outline, and you review it and decide what goes to the buyer.
Move a live deal forward. Try Cobl free for 15 days.
