Stages describe the buyer, not the seller
The most common pipeline design error is naming stages after what your team is doing: contacted, working, chasing. These are not checkable, so nobody can tell when a deal should move, and deals accumulate in the middle.
Stages that describe the buyer's observable state work better. Has a requirement been confirmed? Has a proposal been received? Has procurement been engaged? Each of those has a yes or no answer someone outside the deal can verify.
What every opportunity needs to carry
A pipeline is only as useful as the fields on the deals inside it. Four attributes do most of the work.
- Value: what the deal is worth, ideally composed from products or services rather than typed.
- Stage: where it sits in the process, by a definition the whole team shares.
- Owner: one named person accountable for the next step.
- Expected close date: a specific date, revised deliberately rather than left to rot.
Movement is the signal
A healthy pipeline is not one with many deals in it. It is one where deals change stage. A CRM with sales pipeline views should make stagnation visible — deals that have not moved, and deals whose expected close date has passed without a decision.
Reviewing the pipeline by last activity rather than by value tends to surface more problems than reviewing it by size.
Closing well matters as much as closing
Deals end as won or lost, and both outcomes carry information. Recording a reason at close is a small discipline that compounds: after a quarter, the losses group themselves into patterns you can act on.
Capturing feedback at the point of closure — while the detail is fresh — is considerably more reliable than reconstructing it during a quarterly review.