The pipeline review when the CRM is wrong: how to run it without the storytelling
Short answer
When the CRM lags behind reality, the pipeline meeting turns into a spoken record update. Rebuild it: each deal discussed is tested by three facts — the client’s last reply, an agreed next step with a date, and what the client did at this stage. Deals that fail come out of the forecast. Discuss only the deals that need a decision, and update records before the meeting.
Lovely pipeline. The clients haven’t heard.
Monday. The manager puts the pipeline on the screen. First deal: “What’s happening here?” The rep explains. Second deal: “And here?” The rep explains. An hour later the records have been updated out loud, nothing has been decided, and everyone goes back to work slightly sadder.
That isn’t sales management. It’s very expensive voice data entry.
This piece isn’t about why sales reps don’t update the CRM. The situation here is different: the meeting is tomorrow, the data is bad and the forecast is still due. What to do about that right now.
How a pipeline review becomes a record check
The meeting replaces the record
Reps know they’ll be asked anyway, so they bring the news verbally. If you can say it, why write it. The meeting sustains the very problem it’s trying to solve.
People discuss what’s easy to discuss
Big deals get long airtime because they’re pleasant. Deals quietly dying get none. Otherwise someone would have to admit it.
The forecast is built from mood
“I think we’ll close this month” becomes a number, the number goes to the owner, the owner plans the money. The whole chain rests on “I think”. Solid engineering.
Three facts instead of a story
Any deal up for discussion passes one test. No opinions, no mood, three questions.
- When did the client last reply? The client, specifically. The rep’s messages don’t count: anyone can write into the void.
- What next step is agreed, and for what date? Agreed with the client, not invented by the rep. “I’ll call sometime this week” isn’t a step.
- What did the client do at this stage? Sent details, opened the contract, brought in the director, asked about payment. If the client did nothing, the stage exists only in the record.
Missing two of three answers means the deal is unverified. It isn’t discussed and it leaves the forecast until the next review. No drama, just the rule.
Take the answers from the conversation itself. Opening a chat is faster than hearing it retold, and a chat is never optimistic.
How to rebuild the meeting
Before
Reps update their records themselves, in advance. The manager scans the list and picks deals to discuss. If a record isn’t updated, the meeting won’t do it for them.
During
- Start with the money due in the coming weeks. Which deals hold the plan, and what could break them.
- Then the stuck ones. Where a deal has sat longer than usual, and what would move it.
- New deals last. They can wait. Nobody has had time to lose them yet.
One question per deal: what decision is needed from the manager? A discount, a call to the director, a different rep, close it. No decision needed, the deal moves on. How to build the meeting around exceptions per person is covered in a sales director who can’t see each rep.
After
Each decision is recorded with a name and a date. The next meeting opens with what got done. That’s usually where the review stops being a ritual and starts annoying people usefully.
Clear the dead pipeline
You’ll have to do something unpleasant once. Take every deal where the client has been silent for longer than your usual cycle and ask the rep one question: is this a deal or a memory?
- Alive: a recent client reply and a next step.
- Dormant: the client hasn’t refused but is silent. Separate list, return date, out of the forecast.
- Dead: close it and record the reason.
The pipeline will shrink. The owner will be upset. And for the first time the number will resemble money. If team metrics don’t match the bank at all, see how to tell a sales team is unhealthy.
Questions for yourself
- What did the last review decide, other than the date of the next one?
- How many forecast deals would pass the three-fact test?
- Who last closed a deal as lost without being reminded?
- Did last month’s forecast match what actually arrived?
If nobody wants to answer the last one, the meeting was useful after all: now you know what it should be about.
A pipeline tolerates anything. The bank doesn’t.
// Take it with you
A pipeline tolerates anything. The bank doesn’t.
Drop it in the team chat. Let them think you came up with it.
New articles, once a week, in Telegram.Subscribe →
Questions and answers
Why do pipeline meetings take so long?
Because they update data that isn’t in the CRM. Reps say out loud what should be in the record while the manager checks it against memory. There are almost no management decisions in a meeting like that.
What if sales reps don't update the CRM before the pipeline meeting?
Don’t update it for them in the meeting. A deal with no fresh fact counts as unverified and leaves the forecast until the next review. That rule works better than reminders because it has consequences.
How do I know a deal in the pipeline is alive?
Ask three things: when did the client last reply, what next step is agreed and for what date, and what did the client do at this stage. A rep’s promise doesn’t count as a fact.
How often should you clean the sales pipeline?
Regularly and by rule, not just before quarter-end. A deal with no client reply for longer than your usual cycle should move to closed or to a separate list, not sit in the forecast.