Why your pipeline review
is a status meeting.

I have sat in roughly four hundred pipeline reviews. The bad ones are not bad because the deals are bad. They are bad because the meeting has quietly changed jobs: it stopped being a forecasting instrument and became a place where people report that they are still working.

The tell is the verb tense. In a status meeting everything is present continuous. We are waiting on legal. They are looking at budget. I am chasing the CFO. Nothing in that sentence describes an event. It describes a rep's intention, and intentions do not close.

Replace every open-ended prompt with one question: what did the buyer do since we last spoke? Not what they said, not what they felt, not how the call went. What they did. Attended something. Sent something. Introduced someone. Signed something. Spent time or political capital.

Buyer effort is the only leading indicator that is expensive to fake. A prospect will tell you the project is a priority for free. Booking their security lead into a 90-minute review costs them something, and that cost is the signal.

Run your last review transcript through this. Most teams find that four out of five updates sit in the left-hand column.

A pipeline review should take forty-five minutes and cover fewer deals than you think. Walking the whole board is how you end up spending eleven minutes on a €4k renewal and ninety seconds on the deal the quarter depends on.

The agenda I install with clients:

Note what is missing: a lap of every rep giving a general update. If someone has nothing that meets the evidence bar, they say so in one sentence and the meeting moves on. That is not a punishment. It is the fastest way to find out you have a coverage problem in week two rather than week eleven.

The first time a team runs this, the pipeline shrinks. Usually between thirty and fifty per cent of open value fails the evidence test and moves out of the quarter or out of the board entirely. Founders find this alarming. It is the opposite of alarming: the pipeline did not shrink, the measurement improved. That revenue was never there.

The second-order effect is the one worth having. Once reps know the question that is coming, they start engineering buyer actions into every call, because that is what they will be asked about on Monday. The review stops being an audit and starts being the thing that shapes selling behaviour. Which is what it was supposed to be.

Do not rebuild the CRM first. Add one required field, last buyer action, with a date, and run one review where that field is the only thing you look at. You will learn more about your forecast in forty-five minutes than the last quarter of dashboards told you.

Then, and only then, wire the exit criteria into stages so the discipline survives without you in the room. That part is a RevOps job, and it is the second thing, not the first.