Why Pipelines Rot — Your Stages Describe Your Feelings, Not the Prospect's Behaviour
Sales PipelinePipeline ManagementKanbanSales ProcessLocal Sales

Why Pipelines Rot — Your Stages Describe Your Feelings, Not the Prospect's Behaviour

T. Krause

A board with sixty deals in "Interested" and four in "Proposal" is not a pipeline; it is a list of conversations somebody enjoyed. Rot is a definitional problem before it is a discipline problem, and stages defined by what the seller feels can never be audited.

Every rotting pipeline looks the same. One column is enormous. The columns after it are nearly empty. Cards in the big column have not moved in weeks, and every one of them has a plausible story attached — waiting to hear back, wants to reconnect after the holidays, very positive call, just needs to speak to their partner.

Nobody is lying. The rep believes each story, and several are true. The pipeline is still worthless as a forecast, because a stage that anything can enter and nothing must leave is not a stage. It is a folder.

The instinct is to fix this with discipline: cleanup days, stricter reviews, nagging. That works for about two weeks. Rot returns because the cause is not laziness. It is that the stages were defined in terms of seller sentiment, and sentiment cannot be audited, so nothing can ever be required to leave.

Sentiment Stages Versus Evidence Stages

The distinguishing question for any stage is simple: could a second person, looking only at the record, agree the deal belongs there?

"Interested" fails the test. Interest is an inference about someone's internal state. Two reps will classify the same call differently, the same rep will classify it differently on a Friday, and nobody can ever prove a deal should move out. This is the column that grows.

"Qualified" fails unless you define it. Nearly every team has this stage and very few have written what it requires. Undefined, it means "I feel good about this," which is the same failure with a more professional label.

"Sent proposal" passes. A proposal was sent or it was not. There is an artefact with a timestamp. Anyone can verify it.

"Meeting scheduled with a date in the calendar" passes. The date exists or it does not.

"Confirmed they have budget this quarter" passes if you record who said it and when. The evidence is a logged statement attributable to a person, not an impression.

The pattern: evidence stages are defined by something that happened, sentiment stages by something someone felt. Evidence stages can be audited by a third party, which means deals can be required to leave them. That single property is what stops the accumulation.

The Three Mechanisms of Rot

Rot is not one failure. It is three, and they have different fixes.

Accumulation without exit criteria. A stage that specifies entry conditions but no exit conditions grows without bound. Every stage needs a statement of what must be true to move forward and what must be true to move back or out. Without the second, the only exit is a human deciding to admit a deal is dead, which is a decision people are demonstrably bad at making.

Optimism asymmetry. Moving a deal forward feels like progress; moving it backward feels like failure. So deals ratchet in one direction and accumulate at the last stage before something objectively verifiable is required. If your big column is the one immediately before "Proposal," this is your mechanism — the pipeline is dammed at the point where a claim would have to become an artefact.

Absent time semantics. Most boards record when a card was created and when it last moved. Neither answers the question that matters: how long has this been in this stage, and how does that compare to deals that eventually closed? Without stage-age, "stalled" is a matter of opinion, and opinions do not clean up boards.

What Rot Actually Costs

The obvious cost is forecast accuracy, and for a small team that is genuinely the least of it.

It hides the real pipeline. Two hundred cards where fifteen are live means the fifteen are invisible. Reps then work whatever is on top, which correlates with recency rather than with value. The best deal in a rotten pipeline is frequently just not looked at.

It destroys the meaning of "follow up." When most of the board is dead, follow-up becomes a chore performed against a list nobody believes in. Cadence discipline collapses — reasonably, because the list does not deserve the effort.

It makes coaching impossible. You cannot tell whether a rep is bad at qualification or bad at closing when the stage boundaries are subjective. The data cannot separate them, so reviews revert to anecdote.

It quietly becomes a compliance problem. Dead leads sitting indefinitely in a CRM are personal data retained without a purpose. A pipeline nobody prunes is a retention policy nobody is following, and that is a different conversation than a sales one.

Rebuilding So Rot Cannot Accumulate

Define every stage by an artefact. Write the exit criterion as something checkable: a sent document, a calendar entry, a logged statement with an author and a date. If you cannot write it, the stage should not exist. Most teams find they have two or three real stages and several that were vibes with names.

Give every stage a maximum age, and enforce it in the system. A deal older than the limit for its stage is flagged automatically, not by someone remembering. The threshold should come from your own closed-won data — how long deals that eventually closed actually spent there — rather than from a round number someone liked.

Make the automatic action a decision prompt, not a deletion. When a card ages out, the system should require a choice: advance with evidence, set a dated callback, or close as lost with a reason. Three options, none of which is "leave it." Auto-deletion breeds distrust in the board; a forced choice breeds accuracy.

Treat "closed lost — timing" as a success outcome. Most rot is deals that should be dated callbacks. If the only respectable outcomes are won and lost, reps park deals in the big column instead of admitting a nine-month constraint. Make the dated callback a first-class, non-shameful outcome and the column drains itself.

Count stage transitions, not stage occupancy. A healthy pipeline is measured by flow — how many deals moved between stages this week — rather than by how many are sitting in each. Occupancy metrics reward accumulation, which is precisely the behaviour causing the problem.

Audit with a stranger's eye, once a quarter. Take ten cards at random and ask whether someone who was not on those calls would agree with their placement, using only what is recorded. The number that fail is your rot rate, and it is a considerably more useful metric than pipeline value.

A pipeline is not a record of your conversations. It is a model of which prospects are actually moving toward a decision, and a model that cannot be wrong is not a model. The discipline that keeps a board clean is almost entirely front-loaded into how the stages were defined — get the definitions right and the cleanup mostly stops being necessary, because deals can no longer accumulate in a column that nothing is ever required to leave.

Cookie settings

We use strictly necessary cookies to keep this site working. Optional analytics cookies help us improve it — they only load if you accept.

Read the cookie notice