Sales pipeline stages in a CRM: how to set them up to match reality
How to set up sales pipeline stages in a CRM so they reflect the real customer journey instead of a generic status list with no clear transition rules
A CRM pipeline often copies a stage list from another project or from the system's own demo, rather than the real customer journey of a specific company. The result is predictable: deals get stuck on stages whose meaning no one can explain, the conversion report shows numbers that do not match what a manager actually sees, and reps end up inventing their own informal tags because the official stages do not describe the real process closely enough.
Why a copied pipeline does not work
A typical demo pipeline looks logical on paper: new lead, qualification, proposal, negotiation, closed. The problem is that these labels do not explain what specific action or agreement confirms a deal has actually moved to the next stage. If each rep decides on their own when a deal counts as being in negotiation, different reps do it differently, and the pipeline report stops being comparable across people.
A second common mistake is too many stages. A highly detailed pipeline with a dozen stages looks precise, but in practice reps just skip statuses or update them retroactively before a meeting so the report looks tidy.
How many stages are actually needed
The number of stages should come from the real sales process, not from a desire to show detail. For most B2B processes, a working range is four to seven stages: enough to track a deal's movement, and not so many that the team struggles to fill them in correctly.
| Question to test a stage | What it reveals |
|---|---|
| What specific event confirms the move to this stage | Removes a rep's subjective judgment about deal status |
| What data must be filled in at this step | Gives the next person or automation enough context to act |
| Can a manager understand a deal's state just from the stage name | Checks whether the stage carries management information at all |
| What happens if a deal sits at this stage too long | Defines the escalation or follow up rule |
If any of these questions has no clear answer, the stage most likely duplicates a neighbor or exists only on paper.
Who should agree the pipeline within the company
A pipeline should not be configured by a CRM administrator alone, without the sales lead and a few experienced reps in the room. The administrator sees the technical side of the system, but reps are the ones who know where the real conversation with a customer diverges from the diagram on paper. Agreeing the pipeline together with the team that will use it daily lowers the risk of rebuilding the structure right after launch.
Transition conditions and required fields
Every move between stages should be tied to a specific condition rather than a rep's arbitrary judgment. A move into proposal status, for example, can be tied to a quote actually sent to the customer, rather than a subjective sense that the conversation went well. Required fields at each stage, deal value, next contact date, owner, let the system check automatically whether a deal is ready to move forward, instead of relying on a rep's memory.
Companies serving several customer segments, for example enterprise and self serve, often need separate pipelines with a different number of stages, since the journey and transition criteria differ between them. How to determine the number of pipelines and fields for a specific business is covered in the material on CRM implementation: stages, budget and preparation.
What to do with lost and disqualified deals
A pipeline should not only show the path to a successful close. A lost or disqualified status with a required reason gives a manager data to analyze, rather than just hiding an unsold deal from view. Without that status, reps tend to leave failed deals open for months, which distorts the overall picture and inflates the count of deals that look active but are not.
How to tell a pipeline no longer matches reality
A few signs suggest it is time to revisit the pipeline: a large share of deals consistently stalls at the same stage, reps describe deal status in informal conversations using words that do not exist among the official statuses, or the conversion report triggers arguments in meetings instead of serving as a basis for decisions.
Setting up a pipeline in practice
In AKORDO's service line, the package turnkey CRM implementation covers pipeline, field, role, and access setup, data migration, and integrations with the website, telephony, email, and messengers. Its outcome is checked against the fill rate of required fields in deal records, the share of active deals linked to a scheduled next action, the speed of logging an inbound inquiry, and the number of duplicate contact records found after channels are synchronized. The catalogue reference starts at 4 weeks, the price for CRM implementation or a relaunch runs $1,100 to $2,700, and the exact amount is confirmed after the scope is assessed.
If the pipeline and field structure still need to be designed from scratch for your process, that is a separate service, CRM selection and design. And when the pipeline work needs to go hand in hand with rebuilding the team's own working standards, that becomes a turnkey sales department project.
Questions before you start
How many stages should a pipeline have
There is no universal number, but for most B2B processes four to seven stages are enough, each tied to a specific, verifiable event.
Can an existing CRM's pipeline be reconfigured
Yes, this is called a relaunch rather than a fresh implementation. The main point is to agree in advance how data and the status of active deals carry over into the new structure.
To discuss a pipeline structure for your business, book a free consultation.