Your CRM Is Optimistic. Your Board Deck Inherited It.

Every serious pipeline review starts the same way: ask which deals in the CRM are real. The room goes quiet, then someone says 'well...'. That pause is the gap between your reported pipeline and your actual pipeline, and it is usually 30 to 50% wide.

Why nobody fixes it

CRM optimism survives because every actor in the system is individually rational. Reps keep dead deals alive because a thin pipeline invites uncomfortable one-to-ones. Managers tolerate it because their roll-up feeds a number they already promised upward. Leadership half-knows, applies a private discount, and moves on, which means the company now runs on two forecasts: the official one and the whispered one. No single person is lying. The system is. That is why hygiene campaigns and email reminders fail: they treat a structural incentive problem as a diligence problem. The fix has to change what the pipeline costs to inflate, not politely request accuracy. It is the same seam-shaped failure we describe in the handoffs piece: everyone owns their number, nobody owns the truth between the numbers.

How pipelines inflate

Deals age without exit criteria, so nothing ever dies. It just moves its close date. Stages are defined by seller activity ('demo done') instead of buyer evidence ('economic buyer engaged'). And weighted pipeline math launders all of it into a forecast that looks precise and means nothing.

Buyer evidence, stage by stage

Rewriting stages around buyer evidence is a one-page exercise. Discovery exits when the buyer has confirmed a problem worth money and a timeline, in their words, recorded verbatim. Evaluation exits when the economic buyer has joined a call, not been name-dropped. Proposal exits when commercial terms have been discussed with the person who can sign them. Commit requires a paper process actually in motion: security review started, procurement engaged, a date the buyer said out loud. Each criterion is checkable by reading the record, which means a deal review becomes an audit of evidence rather than a negotiation with optimism. Reps adapt within a month, because the new rules are clearer than the old politics.

Three fixes that hold

First: every stage gets a buyer-verifiable exit criterion, or it is not a stage. Second: any deal untouched for 21 days auto-flags for kill-or-commit review. Third: close dates can only move twice; the third move closes the deal as lost. Harsh rules produce honest data, and honest data produces forecasts your board can act on.

Running the amnesty

The transition needs a one-time amnesty, announced plainly: for two weeks, any deal can be closed-lost without explanation or consequence, and after that the new rules apply to everything that remains. Expect reported pipeline to drop by a third or more, and prepare the board for it in advance, because the drop is not bad news. It is the moment the number becomes real. Pair the amnesty with a re-baselined conversion history so quotas and coverage targets are set from honest data rather than from the old fiction. Skipping this step is why most hygiene pushes relapse: the rules changed but the inherited inflation stayed, so everyone quietly returns to managing the gap instead of the pipeline.

The payoff

Clean pipeline is not about tidiness. It changes decisions: where to hire, when to raise, which segment to double down on. A company that knows its real conversion rates and real velocity can plan. A company with optimistic CRM data can only hope.

What to automate, and what never to

Automation belongs on detection, never on judgement. The 21-day staleness flag, the close-date move counter, the weekly exception report of deals missing evidence: all of that should fire from workflow rules, because machines are better than managers at noticing decay and they do it without politics. But the moment a system starts writing the evidence itself, summarising calls into stage criteria or auto-advancing deals on activity signals, you have rebuilt the optimism machine with better tooling. The evidence must stay something a human heard a buyer say. A useful division of labour: software decides what gets reviewed, people decide what is true. Teams that invert this end up with immaculate dashboards describing a pipeline nobody has actually spoken to, which is the original disease wearing an AI badge.

The forecast meeting, after honesty

The reward for all of this arrives in the Monday forecast call. With evidence-based stages, the meeting stops being deal-by-deal interrogation and becomes exception review: the flags surfaced eight deals this week, here is what changed, here is the commit number and the two risks to it. Meetings shrink from ninety minutes to thirty. Sandbagging becomes visible because the evidence record does not support the pessimism, exactly as inflation became visible because it did not support the optimism. And the number handed upward starts landing within a narrow band quarter after quarter, which changes how the board treats every other number you bring them. Forecast credibility is a compounding asset, and it is bought with unglamorous hygiene, not with a better model.

Keeping it honest after the reset

Honesty decays without maintenance, so build three small rituals. A weekly deal-review cadence that samples five records and reads the evidence aloud, which keeps the standard visible at trivial cost. A monthly metrics check comparing stage-conversion actuals against the assumptions in your plan, so drift surfaces in weeks rather than at year-end. And a quarterly look at forecast accuracy itself: predicted versus landed, by team, published internally. Once the record is trustworthy, everything downstream improves at once, from attribution you can triangulate to expansion signals you can act on. Data quality is unglamorous exactly in proportion to how much it is worth.