A pipeline is useful only when two people looking at the same deal would put it in the same stage.
Use observable stages
Avoid labels such as warm, interested or likely. They describe opinion. Prefer events: new enquiry, qualified, call booked, call attended, proposal sent, decision pending, won and lost. Each stage should have one entry rule and one exit rule.
Separate stage from task
“Follow up Friday” is not a stage. It is a task attached to a deal. Mixing actions with customer status makes reporting meaningless and leaves opportunities stranded when the task is completed.
Make ownership explicit
Every live record needs one owner, one next action and one due date. Automation can assign and remind, but it cannot rescue a process where responsibility is ambiguous.
Preserve the reason deals move
Require structured loss reasons and record the source, offer and expected value. Over time, that turns the CRM into a decision system: you can see which sources produce attended calls, which objections recur and where deals stall.
Start with fewer stages than you think you need. Add a stage only when it changes the work, the owner or the forecast.
If your CRM no longer reflects the way your team sells, tell us how the pipeline works today.