What the review is for
A pipeline review is not a status meeting. Status is what a CRM is for, and if you are using this meeting to find out what happened, the data is the problem rather than the agenda.
The review exists to answer one question per deal: is this still moving, and if not, what happens this week? Deals rarely die from rejection. They die from sitting still while everybody assumes somebody is handling it.
The rule this article follows
Every deal leaves the review with a next action, a name, and a date, or it leaves with a changed stage. A deal that comes out of the meeting exactly as it went in has wasted its slot.
What has to be true before you start
The meeting is only as good as the data underneath it. Three things need to be current before anyone walks in, and it is worth being strict about this because the alternative is a meeting spent correcting records aloud.
- Every open deal has a stage that reflects what the customer has actually confirmed
- Every open deal has a next step with a date on it
- Deals that are genuinely dead have been closed, with a reason
If that is not the state of things, the first review is a data-cleaning session and everyone should know that going in. It is worth doing once. Our guide to CRM data hygiene covers the rules that stop it recurring.
The nine questions
Go in descending value order, and stop when you run out of time. The biggest deals get the attention; the tail gets a monthly pass instead.
What has the customer done since we last spoke?
Not what the rep did. What the customer did: replied, forwarded internally, asked for something, went quiet.
Buyer activity is the only reliable progress signal. A week of our activity with no customer response is a deal moving backwards, however busy it felt.
Ask first, every timeWhat is the next step, and is it in the diary?
A next step without a date is a hope. "Following up next week" has no forcing function and no way to tell later whether it happened.
If there is no booked next step, that is the thing to fix in the meeting. Do not move on until there is one or the deal has been reclassified.
Booked, not intendedWho else has to say yes?
Procurement, finance, legal, security, a manager who has never been on a call. Name them.
Deals stall at the point where an unknown stakeholder appears late. Asking every week is how you find them before they become a four-week delay.
Names, not rolesWhat did they say the timeline was, in their words?
Their stated timeline, not our hoped-for close date. If we have never asked, that is the action.
A deal where the customer has never named a date is not late. It was never scheduled, and treating it as a forecastable deal distorts everything downstream.
Their words, not oursWhat would make this fall over?
Budget cycle, a competing project, a champion who might leave, a technical requirement we have not confirmed.
Reps usually know. They rarely volunteer it, because naming a risk feels like predicting failure. Asking directly makes it safe to say.
Ask it plainlyHow long has it been in this stage?
Compare against your own median for that stage. Not a benchmark from someone else's business.
A deal well past the median for its stage is telling you something the stage label is not. This is the single most useful number in the review once you have 30 or 40 closed deals to draw it from.
Use your own medianIs the stage still honest?
Check the deal against the exit criteria for its stage. If the champion who confirmed the budget has left, it is not in negotiation any more.
Moving deals backwards is normal and healthy. A pipeline where nothing ever regresses is a pipeline being managed for appearances.
Backwards is allowedWhat do you need from me?
A price approval, an intro, a technical call, a reference customer, someone senior on the next call.
This is the question that makes reps want to attend. A review that only extracts information and gives nothing back gets treated as an audit within a month.
The question reps turn up forIf nothing changes, is this still open in 30 days?
The closing question, and the one that removes fiction from the forecast. If the honest answer is no, decide now: push it, change the stage, or close it lost.
Closing a deal lost is not a failure. Carrying a dead deal for two quarters is, because every plan built on that pipeline was wrong.
Forces a decision
Answers that should worry you
Some answers sound reassuring in the room and are not.
| The answer you hear | What it usually means |
|---|---|
| "They're really keen" | No confirmed timeline and no named decision maker |
| "Just waiting to hear back" | No booked next step. The deal has no forcing function |
| "I'll chase them again this week" | The third such chase. The deal needs a different approach, not another email |
| "Legal has it" | Nobody has asked legal for a date, and nobody knows who owns it there |
| "They said after the summer" | The close date is a guess dressed as a commitment |
| "It's a formality now" | The riskiest sentence in sales. Ask what is still unsigned |
None of these mean a deal is dead. They mean the deal has no mechanism, and the review is the place to give it one.
Keeping it to 30 minutes
Three rules hold the time, and they are the same rules that keep any recurring meeting from sprawling, covered in more depth in our guide to running a meeting people don't resent.
Do not solve problems in the room. When a deal needs strategy, name who is meeting about it afterwards and move on. Two people going deep while four wait is what turns a 30-minute review into an hour.
Do not review everything. Value threshold, plus anything stalled, plus anything closing this month. The rest gets a monthly sweep.
Write the actions as you go. Every deal exits with an owner and a date, captured live, not reconstructed afterwards. The same discipline that makes meeting notes turn into action items applies here, and a review whose actions evaporate teaches everyone that the meeting is theatre.
One last point on why the speed question keeps recurring in these reviews. Research published in Harvard Business Review, covering an audit of 2,241 companies, found the average response to a web lead was 42 hours, and that 23% of companies never responded at all. Firms that responded within an hour were around seven times more likely to qualify the lead. Most of what a pipeline review fixes is not strategy. It is elapsed time.
If your pipeline, meeting notes, and follow-ups sit in separate systems, the review will always start with reconciliation. Kin keeps contacts, pipeline, outreach, and meeting outcomes on one record, so the review starts from what is actually true.
Frequently asked questions
- How long should a pipeline review take?
- Thirty minutes for a team of two to five reps with a normal pipeline. If it runs to an hour, you are reviewing every deal rather than the ones that need a decision, or you are solving problems in the room instead of assigning them.
- Who should attend a pipeline review?
- The people who own deals and whoever can unblock them. Adding observers changes the tone: reps start presenting rather than flagging problems, which removes the entire value of the meeting.
- Should you review every deal every week?
- No. Review deals above a value threshold, deals that have not moved in two weeks, and anything closing this month. Everything else can be checked monthly. Reviewing all of it is what makes these meetings long and useless.
- What is the difference between a pipeline review and a forecast call?
- A pipeline review looks at deals and asks what to do about them. A forecast call looks at the total and asks whether the number is credible. Combining them tends to produce a meeting where nobody wants to admit a deal is weak, because it lowers the number in front of everyone.
- How do you stop reps from being defensive?
- Ask about the deal, not the person. "What is the customer waiting for?" invites information. "Why has this not closed?" invites a defence. The manager's tone in the first two reviews sets the pattern for the next year.