Sales pipeline stages: how to build them, with exit criteria

Short answer

A sales pipeline is built from verifiable steps the customer takes towards buying, not from a manager's gut feeling. Each stage has an exit criterion — "the customer confirmed the budget", "a viewing date was set", "the proposal was sent and the customer confirmed receiving it". Six to nine stages are enough for a small or mid-sized business. Some stage transitions require a field, each stage has a normal duration, and "won" and "lost" are the terminal stages. A stage should answer "what did the customer do?", not "what did the manager do?"

How a stage differs from a status

A lead status is the state of the manager's work: new, working, unreachable. A stage shows where the customer is on the path to buying: interested, negotiating, deciding. Kept separate, the two measures answer two different questions in the report: "is the team doing its work on time?" and "where do customers get stuck?" Setting up statuses is covered separately in CRM lead statuses.

A stage is a verifiable customer step

In a weak pipeline, the stages are the manager's actions: "called", "proposal sent". They say nothing about whether the customer is interested — you can send a proposal the customer never opens. In a strong pipeline, each stage is something the customer did:

• "Stated the need" — the customer said what they want and when they need it.
• "Meeting agreed" — the date and time were confirmed by the customer.
• "Received the proposal" — the customer confirmed seeing it and asked a question.
• "Decision process known" — who decides, and when.

A sample pipeline: six stages

1. 11. New enquiryThe lead exists; the need is not yet known. Exit: the customer stated the need and timing.
2. 22. Need knownExit: a date for the next meeting, viewing or demo was agreed.
3. 33. Meeting / viewingExit: the meeting happened and the customer asked for a proposal.
4. 44. ProposalExit: the customer confirmed receiving the proposal; the decision date is known.
5. 55. NegotiationExit: terms agreed; payment or contract pending.
6. 66. Won / LostTerminal stages. "Lost" is never set without a reason.

Your stages will differ by sector: an "examination" in a clinic, a "viewing" in real estate, a "pilot" in B2B. The principle does not change.

Required fields on entering a stage

Moving into a stage should be tied to certain information. CRMs such as HubSpot let you set required properties per stage: if the field is empty, the record cannot move into that stage. A practical minimum:

• Need known → product or service type, approximate timing.
• Proposal → amount and expected decision date.
• Negotiation → the main objection or condition.
• Lost → close reason.

Probability and weighted value

Some CRMs give each stage a probability of closing and calculate the pipeline's "weighted" value by multiplying the amount in each stage by its probability. In HubSpot's default pipeline these probabilities start at 20% in the first stage and reach 100% at "won". Those are defaults — for your business, calculate them from your own history: of the leads that reached "proposal" in the last six months, what share was won?

With small numbers it is too early to calculate probabilities. Without at least a few hundred closed leads, do not lean heavily on a weighted forecast.

Time in stage

Each stage has a normal duration, and leads that exceed it are the part of the pipeline that needs the most attention. A lead sitting in "proposal" for three weeks is usually either already lost or being decided by someone else. Write a duration for every stage and show the overdue leads in a weekly list. To find where leads stall from the conversations themselves, see finding loss in the sales funnel.

Skipping stages and moving back

Sometimes a customer says "just send the proposal" and jumps two stages. That is fine — allow skipping, but the skipped stages' required fields still have to be filled in. Moving back is a signal: a lead that goes from negotiation back to "need known" usually means the need was misunderstood.

When a second pipeline is justified

If sales processes differ fundamentally — a one-day sale to consumers and a three-month tender with corporate clients, say — keeping them in one pipeline ruins both reports. Build two separate pipelines. But a different product does not need its own pipeline: a category field is enough for that.

An illustrative example

This is an illustrative example. A real estate agency's pipeline had the stages "called", "WhatsApp sent", "call back" and "interested". Most leads sat in "interested", but nobody knew how many ever came to a viewing.

The new pipeline: "enquiry → budget and area known → viewing booked → viewing held → deposit negotiation → won/lost". In the first month it became clear that the biggest loss was between "viewing booked" and "viewing held" — customers did not turn up. The team added a reminder the day before each viewing.

Common mistakes

• Naming stages after the manager's actions.
• Fifteen to twenty stages — nobody fills them in correctly.
• No exit criteria: each manager moves stages by their own judgement.
• Using default probabilities as a forecast without checking them against your own data.
• Allowing "lost" without a reason.

Limitations

A pipeline is only as accurate as the managers' timeliness in moving stages. If changing a stage is not a one-tap action, records stay in old stages and the forecast inflates. A pipeline also simplifies the customer's real decision process: in B2B the decision is shared between several people and does not fit a single stage.

The pipeline in Vexvon

In Vexvon, sales stages are held on the customer record. You start with nine default stages: New Lead, Waiting, Follow-up needed, Call needed, Interested, Negotiation, Won, Lost, Blocked. You then create, name, colour and order them yourself to fit your process. A manager can also change the stage with the buttons on a Telegram notification — meeting, proposal, closed, thinking, declined — and every change is written to the lead's activity log. More on Vexvon CRM.

Next step

List your current stages and note next to each which customer action ends it. Stages without an answer should change first. The overall logic of an AI CRM is in what is an AI CRM. More articles are in the lead management section, and we can build your pipeline together during a demo.