A pipeline should describe the customer's progress and the team's next responsibility. If every salesperson uses a stage differently, the reports may look organized while the process remains unclear.
Use the smallest number of stages that supports real decisions, coaching, forecasting, and follow-up.
Define stage entry and exit
For each stage, write what must be true to enter, what action is expected, what evidence is recorded, and what moves the opportunity forward. Do not make a stage a synonym for “someone sent an email.”
Assign ownership
Every open opportunity needs an owner, a next action, and a due date. Define what happens when someone is absent, a lead changes department, or a request is outside the business's service area.
Track time and stale work
Record when an opportunity enters a stage and how long it stays there. Create a review queue for overdue follow-up, missing next actions, no-response leads, and opportunities that have not changed.
The CRM selection guide and follow-up automation guide cover supporting systems.
Keep reports honest
Separate open pipeline, closed won, closed lost, unqualified, and paused work. Record loss reasons that the team can use without creating a long list nobody maintains.
Automate only clear rules
Automate reminders, assignments, acknowledgments, and cleanup when the trigger and owner are clear. Keep judgment-heavy decisions visible to a person.
Review the stages with the team
Compare stage definitions with real opportunities, ask where records get stuck, and revise one rule at a time. The pipeline should reflect the work people can actually perform.
Pipeline stages not matching the way work happens? Ask Vertinus to map the real process before changing the CRM.