If everyone is leaving the pipeline review simply feeling informed, that’s a problem.
The rep walks through the deals: stages, amounts, next steps. The manager nods, asks a few questions, writes some notes. The meeting ends. Nothing changes. No deal moves, no risk gets named, no one leaves with a different plan than they brought in.
That might feel useful. If nothing changes in the deals afterward, it was mostly a readout.
A good pipeline review should change what happens next. Every rep should leave knowing exactly what’s expected.
Three meetings, not one
Most teams collapse different conversations into a single pipeline slot. That’s where things break down. Consider separating the intent of your calls.
The forecast call asks what number you believe. Which deals are in commit? How confident are you? What could miss? It should be short. If you need long stories to justify the forecast, the forecast isn’t ready.
The pipeline review is diagnostic. You’re stress-testing deals: where are the gaps, what has the buyer actually confirmed, what risk are you carrying? RAIN Group calls this a pipeline stress test for good reason. You’re applying pressure to find what breaks, not rehearsing what feels comfortable.
Pipeline reviews are usually one-on-one. Some teams run them in a small group, which can work if the format stays tight and every deal still leaves with a clear next step. Either way, the outcome should be the same: inspected deals, named risk, and a specific move the rep owns.
You could also run a separate deep deal review when one opportunity needs proper strategy time: who else needs to be involved on the buyer’s side, where’s the competitive exposure, what’s the move to get this over the line? Some teams call this a Win Lab. It’s not standard everywhere, but it’s worth knowing about. That kind of session belongs outside the cross-pipeline review. If you try to strategy-work every deal in the same hour, you run out of time and change nothing.
If the pipeline review is doing its job, the forecast call gets shorter and sharper. The number is a rollup of inspected deals, not a negotiation over rep narratives.
Run pipeline inspection and forecast commit on different days if you can. They need different questions.
Rep confidence isn’t buyer evidence
Most pipeline reviews run on rep confidence. “They’re really interested.” “The champion is strong.” “We had a great demo.”
That’s not data. That’s a feeling. Reps often have “happy ears”: they hear what they want to hear, then build a forecast on it.
Pipeline inspection gets useful when the manager separates rep confidence from what the buyer has actually verified. A buyer verification is simple: confirmation that something is true, not that the rep believes it is true.
The buyer liked the demo. Good.
Did they say it addressed the problem they care about, or did the rep infer that?
The champion said the timing is right. Good.
Is there a critical event that makes this quarter matter to the buyer, or is the urgency mostly yours?
The problem is painful. Good.
Has the buyer quantified the impact with metrics that matter to them?
”Inspecting the deal rather than reciting it”
That’s how Andy Whyte frames what good sales leaders should expect from pipeline review. Not a rep walkthrough. An inspection.
MEDDPICC done properly isn’t a checklist for appearances. It’s a diagnostic. Letter by letter: where’s the gap between what the rep believes and what the buyer has demonstrated? That gap is the risk. You’re not asking whether a field is filled. You’re asking what the buyer confirmed.
Winning by Design’s SPICED framework approaches the same problem from a slightly different angle. Situation, Pain, Impact, Critical Event, Decision. The useful part for pipeline review is Impact and Critical Event: what’s the business outcome the buyer cares about, and what’s forcing a decision by a particular date? If you can’t answer both from something the buyer said, the urgency is probably yours.
- What has the buyer done, not just said?
- Which pain, impact, or critical event has the buyer confirmed in their own words?
- Who has changed their calendar, process, or priority because of this?
- Which approval path has been confirmed?
- What risk has the buyer named themselves?
- What would make this stage untrue?
Help the rep leave with a move
The manager’s job in a pipeline review isn’t to listen politely and move on, and it isn’t to hand the rep a to-do list. It’s to help uncover the move together, pressure-test it, and make sure the rep leaves with a specific next action that actually changes the deal’s trajectory.
Not “follow up with the champion.” That’s homework, not a move.
In the room, it often sounds like this:
What does your champion need from you to get internal buy-in this week?
What's the one thing that would make the economic buyer say yes right now?
If this deal doesn't close this quarter, what's the single thing that'll have caused it?
Those questions should surface something concrete. A move is specific enough that the manager can inspect it next week:
- Get the implementation owner into the next call.
- Confirm decision criteria before pricing is sent.
- Rebuild the follow-up around the pain the buyer named.
- Ask the champion what happens internally if this doesn’t move this quarter.
- Close the opportunity if there’s no buyer action after the agreed date.
The review should feel like inspection, not prosecution. It still can’t be a recital. The standard is simple: does something change because of this conversation?
If the answer is no, you ran a status meeting.
A simple format for your deal inspections
Try this structure for each deal that matters this quarter:
- Why is this deal in this stage? Not what the CRM says. What does buyer behaviour show?
- What’s the gap in your diagnostic? Walk MEDDPICC or SPICED methodically. Where can’t the rep answer with buyer evidence?
- What does the buyer believe right now? What have they confirmed back: demo fit, pain, impact, decision process?
- What’s the critical event? Is there a real deadline on the buyer’s side, or mainly internal quota pressure?
- What’s the specific next move? One action, owned by the rep, that changes this deal’s position.
The order matters. If the meeting starts with the rep’s narrative, the conversation gets pulled into the story. If it starts with evidence, it gets cleaner.
One-on-one deal inspections catch more real risk than group readouts. In a group, reps perform. In a 1:1, they’re more likely to be honest. Inspect the top deals by risk and close date with rigour. Spot-check the rest. Don’t read the whole pipeline aloud.
- Has each priority deal left with one named move and an owner?
- Can the rep point to buyer verification, not just rep confidence?
- Does any deal need a separate deep-dive session scheduled?
- Has the CRM been updated in the room, not "after the call"?
Keep the bar practical
Good pipeline review is mostly unglamorous. The manager runs the same questions, holds the same standard, and checks next week whether anything actually moved. That’s the job, week after week.
The payoff shows up gradually. Newer reps start walking in already thinking about buyer evidence, not just their own read on the deal. Experienced reps catch themselves narrating before the manager has to push. Over time, the forecast depends less on who’s sounding confident in the room and more on what got inspected.
That only works if you’re willing to kill deals that aren’t real. A rep holding onto an opportunity with no buyer verification isn’t being optimistic. They’re spending time that could go on something winnable. Letting it go early keeps the rest of the pipeline trustworthy, and it gives the rep a clearer week ahead.
By the time you get to the forecast call, the hard work should already be done. The number you’re committing ought to be a rollup of deals that survived scrutiny, not a negotiation over who told the best story. If everyone walked out of the review feeling informed but nothing in the pipeline changed, you weren’t inspecting. You were narrating.