Skip to content

How to run a pipeline review that finds real risk

By · Published · 5 min read

Hand-drawn illustration for the guide: How to run a pipeline review that finds real risk

A useful pipeline review looks at the few deals that will decide the period and asks one question of each: what evidence do we have that this deal will close, when we say, at this value? It is an inspection of evidence, not a round of status updates. Hold it weekly, keep it under an hour, and leave every deal with a dated next step.

Below is an agenda, the questions to ask, the warning signs to look for and a worked example.

What a pipeline review is for

Most pipeline meetings drift into each salesperson reading out their deals while everyone else waits. That tells the manager what the CRM already says. A good review does three different things:

  • It finds risk early, while there is still time to act.
  • It tests whether each deal's stage and close date are supported by something the buyer has done.
  • It agrees the next action on deals that matter.

Keep coaching on skills and the forecast call separate. Mixing them makes the meeting long, and people defend their numbers instead of looking at their deals honestly.

Before the meeting

Ask each person to update the CRM by the day before. Then choose the deals to review. You do not need every deal. Pick:

  • The largest deals expected to close this period.
  • Any deal whose close date has moved more than once.
  • Deals that have sat in the same stage longer than your average for that stage.
  • New deals that entered the pipeline at a late stage.

For a team of six, that is usually ten to fifteen deals.

The questions to ask about each deal

  1. What happened last, and when? A deal with no buyer contact for three weeks is not progressing, whatever its stage says.
  2. What is the next step, and has the buyer agreed to it? "I'll follow up" is not a next step. "Demo with their operations lead on the 14th, in their calendar" is.
  3. Who signs, and have we met them? If the person who approves the spend has never been in a conversation, the close date is a hope.
  4. What problem are they solving, and what does it cost them to wait? Buyers move when doing nothing is expensive.
  5. Why now? Is there an event forcing a decision: a contract ending, a new regulation, a launch date?
  6. Who else are they considering, including doing nothing?
  7. What does their buying process look like after they say yes? Legal review, procurement and budget approval can add weeks.

You will not ask all seven every time. Use the ones the deal's stage makes most relevant.

Red flags

SignWhy it matters
Close date pushed twice or moreThe buyer is not committed to the timeline
No next step with a dateNothing is moving the deal forward
One contact onlyIf that person leaves or loses interest, the deal dies
Signer never metThe real decision has not started
Stage older than averageThe deal is stalled, not progressing slowly
Discount discussed before valuePrice is doing the work the problem should do
Late-stage deal that appeared this monthEither an exceptional opportunity or a data-entry shortcut; check which

A 45-minute agenda

  • 5 minutes: numbers at a glance. Pipeline for the period against target, and what changed since last week.
  • 30 minutes: the selected deals, about two to three minutes each, using the questions above.
  • 10 minutes: actions. Each deal discussed leaves with an owner, a next step and a date, recorded in the CRM before the end of the day.

A worked example

A team lead reviews five deals for the quarter:

DealStageValueWhat the review foundAction
Logistics firmProposal€40,000Close date moved twice; finance director never metAsk the champion to set up a meeting with the finance director this week
Hotel groupNegotiation€25,000Signed order form expected; legal review booked for the 20thKeep; confirm legal contact
Retail chainDemo done€60,000Last contact 24 days ago; no next stepMove back a stage; call to requalify
Clinic networkProposal€15,000Contract with current supplier ends next monthKeep; propose start date aligned to contract end
Software resellerNegotiation€30,000Entered at negotiation this week; no history in CRMCheck how it arrived; add contacts and history

The headline pipeline was €170,000. After the review, the team lead treats €40,000 (the hotel group and the clinic network) as well supported, €70,000 as at risk with clear actions, and €60,000 as needing requalification. That is a far more useful picture for the forecast than the total.

Common mistakes

  • Reviewing every deal. The meeting gets long and the important deals get the same two minutes as the small ones.
  • Accepting the stage at face value. Ask what the buyer did, not what the salesperson did.
  • Punishing honesty. If people are criticised whenever a deal moves backwards, they stop moving deals backwards and the pipeline stops reflecting reality.
  • No follow-through. Actions agreed in the meeting and never checked teach the team that the meeting does not matter.

What the evidence says

The structure and questions here are Practice: drawn from widely used sales management approaches rather than controlled research. Figures quoted online about how much pipeline "slips" each quarter mostly come from software vendors and are Weak; your own CRM history is a better guide.

Check yourself

  1. What is the main question a pipeline review asks of each deal? What evidence shows it will close, when we say, at this value.
  2. Which is a valid next step: "I'll follow up next week" or "Demo with their operations lead on the 14th, in their calendar"? The second: it is dated and agreed by the buyer.
  3. Why keep the forecast call separate from the pipeline review? Mixing them makes people defend numbers instead of examining deals honestly.

Go deeper: free sample lesson

The B2B Outreach and Business Development course covers building and qualifying pipeline you can trust.

Written by , founder of Dokimos. He is a senior product and UX designer based in Athens, and is studying for a BSc in Psychological Science.