Most pipelines are named after what the seller did — contacted, presented, proposal sent. That produces stages that advance on activity rather than on progress, and a forecast that reflects effort rather than likelihood.
Design around buyer actions, not seller actions
Sending a proposal tells you the rep was busy. The buyer scheduling a review of that proposal with their finance lead tells you something about the deal. Stages defined by buyer behaviour forecast; stages defined by seller behaviour report activity.
What a working pipeline has
- Entry criteria per stage, written down, phrased as buyer actions.
- Exit criteria, so a deal cannot linger in a stage it no longer belongs in.
- Few enough stages that reps can hold them in their head — usually five to seven.
- A defined path for deals that stall, rather than an ever-growing middle.
- Probabilities derived from your own historical conversion, not from platform defaults.
The stalled-deal problem
Most pipelines have no mechanism for deals that are neither progressing nor lost. They accumulate, inflating the pipeline and destroying the forecast. A time-in-stage threshold that forces a decision — advance, disqualify or park — is one of the highest-value changes available and one of the least implemented.
Why default templates underperform
Platform templates ship with generic stages and default probabilities drawn from an aggregate of other businesses. Applied to your sales motion they produce a forecast calibrated to somebody else's market, and the miss gets attributed to the reps.
The difficulty is not knowing that criteria matter. It is writing criteria the team will actually apply consistently, deriving probabilities from your own closed data, and enforcing time-in-stage without turning the CRM into a policing tool.
What this means for your business
Rewrite every stage entry criterion as an observable buyer action this week. It is a short exercise and it usually exposes two stages that mean nothing. Our analysis of underperforming CRMs covers what happens when this layer is missing.