Pipeline stages that mean something: definitions, exit criteria and the automation that enforces them
A stage is a claim about a deal. When the claim is undefined, the forecast is fiction. How to define stages by evidence, automate the transitions, and stop deals sitting where they do not belong.
23 Oct 2025 · 2 min read · by HeiSyn
Ask five reps what 'Proposal' means and you get five answers, which is why a pipeline review turns into a negotiation about what is real. A stage should be a statement that a specific, verifiable thing has happened — not a feeling about how the deal is going — and the CRM should move deals based on the thing happening rather than on someone remembering to drag a card.
Define stages by evidence
Qualified: a discovery call happened and the notes contain a problem, a budget signal and a timeline. Proposal: a document was sent and opened. Negotiation: a redline or a pricing question came back in writing. Verbal: the buyer said yes in a logged conversation. Closed won: a signature exists. Each definition names the artefact; if the artefact does not exist, the deal is not in the stage.
Automate the transitions
The proposal tool's 'sent' event moves the deal to Proposal. The e-signature event moves it to Closed Won. A booked discovery meeting moves it to Qualified only after the call summary is written. Reps can still move deals by hand, but the system moves them forward on evidence and flags any hand-moved deal that lacks the artefact.
Catch the stalled ones
Every stage has a normal duration. A deal past twice the median gets a nudge to the rep; past three times, a note to the manager and a suggested action — a call, a re-qualification, or a move to Closed Lost with a reason. Stale deals inflate the pipeline and make the forecast worthless; the automation keeps the pipeline honest without a weekly cleanup meeting.
Report on definition compliance
Share of deals in each stage with the required artefact present. Share moved by system versus by hand. Average time per stage by rep. These three numbers tell a sales leader whether the pipeline can be believed, which is the only reason to have stages at all.
Questions people ask next
- How many stages should a pipeline have?
- Five to seven. Fewer and the forecast has no resolution; more and reps stop maintaining them. Each stage needs a verifiable artefact; if you cannot name one for a proposed stage, merge it into a neighbour.
- What do we do with deals that skip stages?
- Let the system move them through the skipped stages in order, stamping each with the same timestamp, so stage duration and conversion reports stay coherent. Skipping is normal — a referral may go straight to proposal — but the history should still be complete.
- Should we add a stage for 'closed lost — reason'?
- Not a stage, a required field on the loss: a picklist of reasons plus a competitor field, captured when a deal is closed lost. Losses with reasons are the most useful data in the CRM for fixing the product and the pitch; losses without are noise.
Want this built for your team?
A free scoping call: we map your motion, name the number that should move, and quote a fixed-scope build.
