Sales pipeline stages: define stages that reflect real buyer progress

A pipeline stage should tell you what the buyer has actually done or confirmed. Stages named after internal activity, such as 'email sent', can make a busy sales team look productive without showing whether customers are moving toward a decision.

Use a small number of meaningful stages

Start with enquiry, qualified, proposal under review, decision pending and won or lost. Adapt the names to how customers buy from you. Define the evidence needed to enter each stage. A proposal is under review only when the buyer has received it and agreed how the decision will happen, not merely when a draft exists.

Write an exit condition for each stage

The exit condition describes what must become true to progress. Qualification might require confirmed need, fit and a decision contact. Proposal review might require scope and decision timing. Keep the conditions observable. A salesperson's confidence can be recorded separately, but it should not replace evidence of the buyer's next action.

What has the buyer confirmed?
What is the next mutual action?
Who owns that action and when is it expected?
What would make us close or pause this opportunity?

Worked example: a commercial cleaning contract

A hypothetical cleaning company qualifies a lead after confirming the site, service frequency and decision contact. It moves to proposal review after a site visit and receipt of the quote. It stays there until the buyer confirms a decision meeting. A friendly phone call alone does not move the opportunity to 'decision pending'.

Watch time in stage, not just total value

An opportunity sitting in one stage for much longer than comparable deals deserves investigation. It may need a new contact, a revised offer or an honest close-out. Use your own historical deals to understand normal timing rather than adopting an arbitrary industry deadline. Distinguish a slow procurement process from a conversation that has stopped.

Keep forecast assumptions separate

Stage labels do not guarantee revenue. If you use weighted forecasts, explain how probabilities were chosen and compare them with actual outcomes. Small samples are noisy. Review losses and stalled deals alongside wins so the pipeline does not become a collection of success stories. The goal is a better decision about follow-up and capacity.