Designing pipeline stages your team will actually use

A pipeline is a shared vocabulary, not a progress bar. If two reps would put the same deal in different stages, the forecast built on top of it is decoration.

Define the exit, not the activity

Stages named after things your team does — called, demoed, followed up — describe effort, not progress. Stages named after what the buyer has done are verifiable. A deal leaves qualification when the buyer has confirmed a budget and a decision date, not when a rep has finished a call.

• Every stage needs one sentence describing what must be true to leave it
• Five to seven stages is usually enough; more invites guessing
• Losses should exit at the stage they died in, so you learn where deals stall
• If a stage never holds a deal for long, it is a checkbox, not a stage

Make the definition visible where the work happens

Stage definitions that live in a document get read once. Put the exit criteria on the stage itself, in the tool reps use daily, and the vocabulary holds. That single change usually does more for forecast accuracy than any weighting model.

A forecast is only as honest as the least-defined stage in your pipeline.