How to set up a sales pipeline in a CRM
Setting up a pipeline in the CRM is configuring the stages, criteria, and rollup that turn deals into a forecast.
The quality of a pipeline comes from buyer-based stages with clear exit criteria, not from how many stages or fields you add.
Short answer
Set up a sales pipeline in a CRM by defining stages that mirror how buyers actually decide, writing clear exit criteria for each, keeping the stage count to five to seven, wiring the forecast rollup, and loading real deals. Base stages on buyer commitments rather than seller activities, and give each a clear exit test, so the pipeline is an honest forecast engine.
Step by step
Define buyer-based stages
Create five to seven stages that map to buyer commitments - took a meeting, agreed to a proposal - not seller activities like "sent email".
Write exit criteria
Give each stage a clear, objective test a deal must pass to advance, so stages mean the same thing to every rep.
Wire the forecast rollup
Connect stages to probabilities and the forecast, so the pipeline produces a weighted revenue view automatically.
Load real deals and keep it clean
Import open deals, age out stale ones, and keep the pipeline current so the forecast reflects reality.
Buyer-based stages with exit criteria
The two things that make a pipeline trustworthy are stages based on buyer commitments (not seller activity) and clear exit criteria for each. Activity-based stages inflate the pipeline and break the forecast; buyer-based stages with objective exit tests keep it honest and consistent across reps.
How Ardovo helps
Ardovo ships a deep deal object with configurable buyer-based stages, exit criteria, and forecast rollup, and Rook updates stages from real activity and flags stale deals. The pipeline stays an honest forecast engine rather than a list reps update by hope.
Frequently asked questions
How many stages should a sales pipeline have?
Five to seven for most B2B teams. Fewer than five hides where deals stall; more than seven creates busywork and forces reps to guess which stage a deal is in. Each stage should map to a distinct buyer commitment with a clear exit criterion.
Should pipeline stages be based on buyer or seller actions?
Buyer actions. Stages like "sent proposal" describe seller activity and inflate the pipeline; stages like "buyer agreed to a proposal" reflect real progress. Buyer-based stages with objective exit criteria produce an honest pipeline and a trustworthy forecast, which activity-based stages do not.
What makes a sales pipeline trustworthy?
Buyer-based stages, clear exit criteria for each, consistent application across reps, and freshness - stale deals aged out. Together these make the pipeline reflect reality rather than wishful data entry, which is what lets the forecast built on it be believed.