Configure CRM Pipeline Stages
Add, reorder, color, and describe deal stages.
Pipeline stages help the team understand where each deal is in the sales process.
Stages should describe real customer progress. Good stage names make it obvious what has happened and what the next action should be.
Plan the Pipeline
Start with the sales path your team already follows. Write the stages in order from first qualification to won or lost. Each stage should answer one question: what must happen before the deal moves forward?
Keep the stage list short enough for the board to stay readable. If two stages trigger the same work and reports do not need to distinguish them, combine them.
Add Or Edit Stages
- Open Settings.
- Go to Pipelines.
- Create or edit a pipeline.
- In the stage editor, add stages.
- Enter each stage name.
- Set order, probability, color, and description where useful.
- Save the pipeline.
After saving, open the deal board and confirm the columns appear in the expected order. Move one test deal through the stages before asking the whole team to use the updated pipeline.
Stage Probability
Probability is a percentage from 0 to 100. Use it to show how likely deals in that stage are to close.
Keep probability realistic. If every open stage is set too high, forecast and pipeline reports become misleading.
Use probability consistently across pipelines. If Proposal Sent means 50% in
one pipeline and 90% in another, sales reports become harder to compare.
Stage Order And Color
Keep stage order aligned with the real sales process. Use colors to make stages easy to scan, but keep names clear because reports and users rely on the names.
Use stronger colors only for stages that need attention, such as negotiation, stalled, won, or lost. Avoid relying on color alone because team members may view the pipeline in reports, exports, or smaller screens.
Before Changing Existing Stages
Check which deals currently use the stage. Renaming a stage can be safe, but removing or replacing stages may affect reports, saved views, automations, and team habits.
If you are redesigning the process, update workflows, reports, and sales playbooks at the same time so the team does not work from old stage names.
Updating Active Deals
When a stage is removed from the process, move active deals into the new equivalent stage before deleting or hiding the old one. If the pipeline has many deals, filter by the old stage and bulk update in controlled groups.
For historical reporting, prefer renaming a stage when the meaning is the same. Create a new stage when the business meaning changed.
Stage Change Checklist
Before publishing a stage change:
- review active deals in the affected pipeline
- map old stages to new stages
- update automations that watch stage changes
- update saved views and sales dashboards
- tell sales users what changed and when to use each stage
After publishing, move one test deal through the pipeline and confirm reports, views, and workflow triggers still behave as expected.
Troubleshooting
If a deal appears in the wrong column, open the deal detail and check its pipeline and stage. A workspace can have multiple pipelines, and stages with similar names may belong to different pipelines.
If reports look wrong after stage edits, review probability values and confirm won/lost stages are still represented consistently.