Pipeline Review Questions That Surface the Truth

The best pipeline review questions ask what the buyer has done, what must happen before they can buy, and what evidence supports the next step. Run the meeting around those answers, then leave each deal with a decision, an owner, and a buyer-facing action.

Most reviews do the reverse. The manager asks whether the deal will close. The rep explains why it should. Everyone studies the same close date, which has apparently become a shared belief system.

I would rather hear that a deal is stuck while there is still time to fix it. That requires better questions and a manager who does not punish the answer.

What should reps prepare before a pipeline review?

Ask reps to update the deal record before the meeting. Do not make them build a separate presentation. The CRM already provides sufficient opportunity for administrative disappointment.

For each deal selected for discussion, require:

• Buyer goal: The problem they want to solve and what happens if they leave it alone.
• Last meaningful movement: A buyer action that moved the decision forward, with a link to the relevant note or email.
• Next commitment: What the buyer has agreed to do, who owns it, and when.
• Buying path: The people and approvals still needed.
• Current gap: What the rep does not know or needs help with.

Select deals because something needs attention: a missed commitment, an unexplained close date, a stage change without evidence, or a blocker the team can address. RevOps can flag these patterns before the meeting.

Do not read every opportunity aloud. Review the exceptions and decisions. Deal records can handle the attendance roll.

Which pipeline review questions reveal real buyer progress?

Start with movement, not confidence. Ask these questions in order.

What has the buyer done since our last review?

Look for actions that require effort: sharing internal requirements, bringing in an approver, completing an evaluation task, or confirming a decision meeting.

A rep sending a proposal is seller activity. A buyer circulating it to the budget owner and arranging a discussion is buyer progress.

If the answer lists only your team's work, ask: What response did that work produce? No response does not prove the deal is dead. It means progress is unverified.

What problem are they choosing to solve now?

Ask for the buyer's reason to act, not your product's benefits. A useful answer names the broken process, who feels the impact, and why waiting has become unacceptable.

Then ask: What happens if they do nothing? If nobody can explain the consequence, the deal may be interesting without being a priority. Another demo will not settle that question. Discovery might.

What is the next action the buyer has agreed to take?

Separate a planned follow-up from a commitment. Sending another email is your next action, not theirs.

A useful commitment names a person, a task, and a time. In a hypothetical software evaluation, that might be the operations lead agreeing to bring the budget owner to a requirements discussion.

If there is no commitment, the next step is to request one. Do not quietly promote an unanswered calendar invitation into mutual intent.

What should you ask about the buying process and close date?

Once you establish movement, test whether there is a credible route to a decision.

Who can approve the purchase, and what evidence do we have that they support it?

Knowing an executive's name is not access or approval. Direct contact helps, but buyer-confirmed decision criteria and a scheduled approval step can also provide evidence. An enthusiastic contact with an impressive title is not enough.

Who could stop this, and have their requirements been addressed?

Ask about finance, legal, purchasing, and the team expected to use the software. Bring the sales engineer into unresolved evaluation questions. Do not turn technical validation into a substitute for understanding who will fund the purchase.

What has our internal advocate actually done?

Look for introductions, internal feedback, and help coordinating the decision. A friendly contact may still be unable or unwilling to sell the change internally.

What must happen between now and signature, and who owns each step?

Work backward from the proposed close date. Identify evaluation completion, approval, contract review, and signature ownership. Confirm whether steps can happen together or must happen in sequence.

Why is this the close date?

A defensible date comes from the buyer's plan and the remaining work. Your reporting deadline is not their business event. If the sequence cannot fit, change the date or the plan. Confidence cannot shorten a required approval.

How do you decide whether a deal is stalled?

A quiet week is not automatically a stalled deal. Judge movement against the buyer's agreed process. A scheduled internal review may explain silence. Repeatedly missed commitments without a replacement plan are different.

Use the evidence to choose an action:

Evidence in the review	Manager's decision	Next action
Buyer completes agreed work	Keep the current plan	Confirm the next dependency
Buyer misses a commitment but explains why	Replan with the buyer	Agree on a replacement task and date
No access to approval or a confirmed approval path	Reassess stage and forecast	Ask the contact to arrange that path
Close date lacks a workable buying sequence	Correct the date	Validate remaining steps with the buyer
Repeated silence and no confirmed priority	Remove unsupported forecast confidence	Ask whether the initiative is still active

An unknown is not an automatic loss. It is a gap to investigate. The mistake is treating an unknown as favorable evidence.

For a stalled deal, define a recovery test: a specific buyer action that would justify continued investment. If the buyer will not confirm a next step, use your stage rules to move it backward, into nurture, or out of active pipeline.

How should a manager run the meeting so reps ask for help?

State the purpose plainly: accurate decisions and useful help, not a defense of last week's optimism.

Then make that promise visible:

• Thank reps for surfacing bad news early. Correct the record without turning the correction into a character assessment.
• Separate facts from interpretations. Ask what happened before debating what it means.
• Ask what help would change the outcome. Offer a specific introduction, evaluation resource, or negotiation plan, not generic encouragement.
• Keep accountability clear. The manager owns promised support. The rep owns the agreed follow-through.

End each deal discussion with a short decision record: what changed, what action comes next, who owns it, and when the team will check the result.

At the next review, start there. Did the action happen? What did the buyer do afterward? Repeating pipeline review questions without tracking the answers just produces a more elaborate status meeting.

FAQ

What are the most useful pipeline review questions?

Ask what the buyer has done, why they need to act, who approves the purchase, and what commitment comes next. Then test whether the remaining buying steps support the close date. These questions distinguish evidence from rep confidence.

How often should you run pipeline reviews?

Use a regular cadence that matches how quickly your deals move; weekly is a practical starting point for many teams. Discuss meaningful changes and blockers rather than reciting every deal. Handle urgent decisions between meetings.

How is a pipeline review different from a forecast call?

A pipeline review diagnoses deal health and decides what to do next. A forecast call estimates which deals will close within a reporting period. Keep those purposes distinct so an uncertain deal can receive coaching without becoming a debate about the number.