What makes a pipeline review question worth asking?
A question is worth asking if the answer can be wrong.That single test removes most of what gets asked in pipeline reviews. "Are you feeling good about this one?" cannot be wrong. "When did the buyer last respond to you, and to what?" can be checked, and it changes what happens next.
Good questions share two traits. They have verifiable answers, meaning a date, a name, an amount, or an event that either happened or did not. And they lead to an action, meaning the answer changes who does what before the next review. Questions that fail both tests turn the meeting into narration, and narration is why pipeline reviews have a reputation for wasting time.
What should you ask about timing?
Ask what has to happen between now and the close date, in order, with dates attached.- What is the next scheduled meeting with the buyer, and what date is it on? - Who signs, and have we been in a meeting with that person? - What is their procurement and legal path, and how long did it take on the last deal like this? - Has this close date moved before, and what changed when it moved?
The last question does the most work. A rep changing a close date is the single best signal that a deal is at risk, and a deal that slips from one quarter into the next is less likely to close even when it stays in commit. Ask about it every time a date moves, and record the reason. Patterns in those reasons will tell you more about your deal slippage than any stage-based report.
Watch for the quieter signal too. The earliest warning on a deal is the absence of anything: no activity, no field changes, no notes, no replies from the buyer. A rep who cannot name a buyer action from the past two weeks is describing a deal that has already stalled.
What should you ask to test the buying process?
Ask what happens to the buyer if they do nothing.Most lost deals are lost to inertia rather than to a competitor, and inertia does not show up in the CRM as a competitor field. Four questions expose it:
- What breaks for them if this slips two quarters? - Who else inside their company is affected by this decision? - What is the internal approval sequence, and who has been through it before? - Who have we spoken to outside our champion's immediate team?
The fourth question is a leading indicator of a category of loss you can act on. Deals held together by one contact collapse when that contact changes roles, and the failure arrives with no warning in the pipeline data.
What should you ask about the amount?
Ask what the deal will close at, not what it is entered at.Pipeline amounts drift upward because nothing forces them down until the contract is signed. The pattern is visible whenever open pipeline carries an average deal size of $80,000 while closed-won deals in the same segment average $40,000. Coverage looks fine, the revenue does not arrive, and the gap gets blamed on win rates.
Four questions on amount:
- What is included in this number, and what did the buyer ask to remove? - What discount has been discussed, and with whom? - How does this amount compare to our last three closed deals in this segment? - If the amount had to drop 30 percent to close this quarter, what would come out?
Amount discipline is what makes weighted pipeline meaningful. Weighting an inflated number produces a smaller inflated number.
Which questions should you retire?
The ones that reward a comfortable answer.| Retire this | Why it fails | Ask this instead |
|---|---|---|
| How confident are you? | Confidence rises under pressure and carries no evidence | What is the next dated step and who owns it? |
| Is this still on track? | Invites a yes | What changed on this deal since last week? |
| Can we pull anything forward? | Trains the team to trade future quarters for this one | What in next quarter would close early without a discount? |
| Any updates? | Produces narration | What did the buyer do this week? |
| Do you feel good about the quarter? | Aggregates guesswork into a single number | Which two deals decide whether you hit? |
How many deals can you cover in one review?
Budget four to six minutes per deal, and choose the deals before the meeting.Selection beats coverage. Reviewing every open opportunity guarantees a shallow pass on all of them. Pick from four buckets:
- Deals that changed forecast category this week - Deals whose close date moved - Deals above a size threshold you set for the segment - Deals with no change in stage, close date, or amount in 30 days
That fourth bucket is usually the largest and the least discussed. Across ORM's customer base, more than 10 percent of open pipeline has gone untouched for a year, and those deals are still sitting inside the pipeline coverage number being reported to the board.
What do you do with the answers?
Write them into fields, not into meeting notes.Next step date, confirmed economic buyer, expected close amount, and reason for any date change all belong in structured fields. Notes are invisible to every dashboard and every model you own, and a review whose output lives in a note has to be repeated from scratch next week.
Once the answers are fields, the next review opens with what changed rather than with a rep recapping the account. That is the difference between a review that compounds and a review that resets.
Frequently Asked Questions
What is the best question to ask in a pipeline review?
What is the next scheduled event with the buyer and what date is it on. The answer is verifiable, it exposes deals with no forward motion, and it cannot be satisfied with an opinion about how the deal feels.
Why should managers stop asking reps how confident they are?
Confidence is not evidence and it drifts upward as quarter-end pressure builds. Reps learn quickly that expressing doubt invites more inspection, so the answer converges on high confidence regardless of what the deal is doing.
How many deals should a pipeline review cover?
As many as fit at four to six minutes each, selected in advance. Choosing deals during the meeting wastes the hour, so pick them from category changes, close date changes, deal size, and age.
What question exposes a weak buying process?
Ask what happens to the buyer if they do nothing. A deal where the answer is vague is a deal competing against inertia, which wins more often than any named competitor.
Should pipeline review answers be written into the CRM?
Yes, into fields rather than notes. Next step date, confirmed decision maker, and expected close amount are fields you can report on. A note is invisible to every model and dashboard you own.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo