How to define sales stages
The single most common mistake in stage design is naming stages after what the rep is doing ("sent proposal") instead of what the buyer has committed to ("agreed to evaluate the proposal").
Buyer-based stages force the deal to reflect reality, which is the whole point of a pipeline.
Short answer
Define sales stages by naming each for a buyer commitment rather than a seller activity. Use five to seven stages, make the boundary between them a clear buyer action (agreed to a proposal, looped in budget), and give each an objective exit test. Buyer-based stages produce an honest pipeline and an accurate forecast.
Step by step
List the buyer commitments
From first contact to signature, write the sequence of things the buyer does: agrees to a meeting, admits a problem, involves a decision maker, accepts a proposal, signs. These become your stage boundaries.
Collapse to five to seven stages
Group the commitments into a manageable number. Too few and you lose signal; too many and reps guess. New, Qualified, Discovery, Proposal, Negotiation, Closed is a solid default.
Name each for the commitment
Use names that describe what the buyer has done, not the seller. "Qualified" (buyer confirmed fit and budget path) beats "Discovery call scheduled" (seller activity).
Write the exit test
Each stage needs a one-line, objective criterion to advance. The test should be something two reps would agree on, like "economic buyer identified and metric captured."
Signs your stages are wrong
Reps disagree on which stage a deal belongs in, which means the criteria are subjective.
Deals jump two stages at once or sit forever in one, which means the boundaries do not match how buyers actually move.
Keep stages honest
Audit quarterly: are deals meeting the exit criteria before they advance, or are reps sandbagging and happy-earing? A stage definition only helps if it is enforced, so inspect it in deal reviews.
How Ardovo runs this
Ardovo turns this from a slide no one opens into how the work actually happens. The stages, exit criteria, and plays live in the deal object, and Rook flags any deal that skips a step, drafts the next artifact, and keeps the data honest, so stages reflect buyer commitments, not busywork gets followed instead of forgotten.
Frequently asked questions
How many sales stages should I have?
Five to seven for most B2B teams. Fewer than five hides where deals stall, and more than seven forces reps to guess which stage a deal is in. The right number captures the real buyer commitments without creating data-entry busywork.
Should stages be named for the buyer or the seller?
The buyer. "Qualified" or "Proposal agreed" describes a buyer commitment and keeps the pipeline honest. "Demo scheduled" or "Sent quote" describes seller activity and inflates the pipeline with deals that have no real buyer intent behind them.
What makes a good stage exit criterion?
An objective test two reps would agree on, tied to a buyer action. "Economic buyer identified and pain quantified" is clear; "deal looks good" is not. If the criterion is subjective, stage data becomes unreliable and the forecast suffers.
How often should I revisit my stages?
Review them quarterly against how deals actually move. If deals routinely skip stages or stall in one, the boundaries no longer match your buyers' behavior and the stages need adjusting to stay an accurate map of the journey.