Operations · 5 min read
What a pipeline actually is, and why your CRM is not one
Most CRMs contain a list of names and a set of stages nobody trusts. A pipeline is something narrower and far more useful.
· Monastic
Ask most owners whether they have a pipeline and they will say yes, and show you a CRM. Ask them what the third-largest open opportunity needs next and when, and the answer usually requires opening someone’s inbox.
That gap is not a software problem. It is a definition problem.
A pipeline has four properties
- Every item has a next action. Not a status. An action, with a verb.
- Every next action has a date and an owner. "Following up" is not an action. "Call Dave Thursday morning" is.
- Stages describe what the customer has done, not what you have done. "Proposal sent" is about you. "Proposal reviewed with the decision-maker" is about them — and only the second one predicts anything.
- Anything without a next action is visible as a problem. A record sitting in a stage with nothing scheduled is the single most reliable early warning in a sales process, and most CRMs hide it perfectly.
Why teams stop using the CRM
Not because they are lazy. Because updating it costs them time and returns them nothing. A salesperson who updates a record and then still has to reconstruct the deal from email has correctly worked out that the CRM is overhead.
The fix is to make the CRM the place that answers "what do I do next", not the place that reports "what did you do last week". When the system tells someone what to do, they use it. When it only asks them to account for themselves, they do not.
The test
Can a competent person who has never seen a deal before open it and know what happens next, without asking anyone?
If yes, you have a pipeline. If no, you have a database of names and a set of stages that describe your activity rather than the customer’s. That distinction is also, incidentally, why the business cannot run while the owner is away: the next action lives in someone’s head.
A starting point
- Cut your stages down to the fewest that genuinely change what you would do next. Most pipelines have twice as many as they need.
- Rename every stage from the customer’s point of view.
- Make "no next action scheduled" a visible, uncomfortable state.
- Stop reporting on activity volume. Report on how many open opportunities have a dated next action — that number predicts revenue and activity counts do not.