CRM pipeline stages are the columns on your opportunity board, and in the system each one is more than a label: it is a trigger for automations, a filter for reports and a checkpoint for the details a deal needs before it moves on. This article answers the configuration question: how do you set up stages in the platform's CRM so that moving a card does useful work, and how do you rename, reorder or remove stages later without breaking workflows or losing history? Deciding which buying moments deserve a stage is a design question, covered in mapping your sales process onto pipelines.
What a stage does inside the CRM
When a salesperson drags a card from one column to the next, four things can happen on the platform. A workflow triggered by that stage change can run. The time the card spent in the previous stage is recorded, which feeds stage-duration reporting. The card starts counting towards the new stage's total in pipeline reports. And if your forecast weights deals by stage, the expected value changes with it.
That is why stage changes deserve care. A stage that nobody moves cards into is just a column. A stage wired to automations is part of how the business runs.
A configuration pattern that works
For each stage, decide four things and write them in a single table before touching the settings.
| Stage | What triggers on entry | Fields to fill before moving on | Stale limit |
|---|---|---|---|
| Qualified | Owner task to book discovery, welcome email | Meeting date | A few days |
| Discovery held | Notes reminder, internal summary request | Budget band, decision maker | About a week |
| Proposal sent | Proposal follow-up series starts | Proposal value | About two weeks |
| Negotiation | Manager notified on large deals | Expected close date | About two weeks |
| Won | Invoice drafted, onboarding tasks, review request later | Final value | None |
| Lost | Loss reason required, nurture enrolment | Loss reason | None |
The table becomes the specification for your workflows and the reference for anyone who asks what a stage means.
Before you start
- The stage names your team already uses, agreed by the sales lead.
- The table above, filled in for your stages.
- Custom fields created for every field the table lists.
- Templates for the emails and tasks each stage triggers.
- A list of any existing workflows that reference stages, so changes do not break them.
How to configure stages on the platform
- Click Opportunities in the left sidebar and choose Pipelines at the top.
- Open the pipeline whose columns you are configuring.
- Type a Stage Name for each row of your stage table, clicking Add stage between them.
- Use the up and down arrows beside each stage to put the columns in buying order.
- If you want the board easier to scan, give each stage a colour.
- Save the pipeline, then open the board to check the columns read left to right in buying order.
- To retire a stage, click the delete icon next to it.
- Select the destination stage for the opportunities sitting in it.
- Confirm the deletion.
Keeping deals moving through those stages each week is covered in sales pipeline management. Building the board in the first place is covered in the sales pipeline guide.
Changing stages without breaking anything
Stages change as your process improves. Changing them safely follows an order.
Renaming a stage is safe in most cases, but check any workflow filters or reports that match on the stage name in text. Reordering is safe for history, but stage conversion reports will read differently, so note the date of the change. Adding a stage in the middle means existing cards need to be placed; decide which ones move. Deleting a stage is the risky one: move every card out first, pause or update any workflow that triggers on it, then delete.
Suppose the agency wants a scoping stage between discovery and proposal. It has 38 open cards in proposal sent, and 12 of them went out without a scoping call. The steps would be: add the new stage, move those 12 back into it, build a workflow that books a scoping call on entry, and change the proposal follow-up workflow so it only triggers from the new stage. Allow a couple of hours, including testing.
What it costs in time
Configuring a pipeline of six stages with entry workflows and stale checks takes a day, including testing. Running it costs nothing extra, because the stages do their work when cards move. Review the stage duration report monthly; a stage where cards sit far longer than its limit points to a problem in the process, not the configuration.
The mistake most people make
They wire automations to the stage before the stage definitions have settled. Every rename or merge then means editing several workflows. Run the pipeline for two or three weeks with minimal automation, adjust the stages, then add the workflows.
Triggering customer-facing emails on stage entry without a check. If a salesperson drags a card forward by mistake and back again, the client receives a proposal follow-up for a proposal they never saw. Add a short wait before customer emails and confirm the card is still in the stage.
When not to automate a stage
Leave stages manual where the right action depends on judgement, such as negotiation on unusual deals. A task reminding the owner is fine; an automatic email to the client is not. Automate the predictable stages first.
Troubleshooting
A workflow fires for the wrong pipeline. The trigger filters by stage name only, and two pipelines share that name. Add the pipeline as a filter.
Stage duration reports look wrong after an import. Imported cards record the import date as entry to their stage. Treat the first month of duration data as unreliable.
Cards seem to vanish after a stage was deleted. They went to the destination stage chosen at deletion, which is often not where the owner looks. Filter the board by owner and check that stage and the lost list.
Owners skip stages. The stage has no visible purpose for them. Make sure each stage triggers something that helps the owner, such as a ready-made email.
Frequently asked questions
How many stages should a CRM pipeline have?
Five to seven open stages plus won and lost. Fewer and the board does not show where deals stall. More and owners stop updating cards accurately.
Can a card skip a stage?
Yes, and the platform allows it. If skipping is common, the stage may be unnecessary. If it is rare but harmful, add a check that flags skipped stages.
Should every pipeline use the same stages?
No. Each sales motion has its own stages. Shared definitions of won, lost and deal value matter more than identical stages, as covered in pipeline management.
Where do stage probabilities come from?
From your own history: of the deals that reached a stage, how many were eventually won. Start with rough estimates and update them each quarter from the conversion report.