Designing Sales Pipeline Stages That Mean Something
By CodexierPublished 5 min read
Open most small-company CRMs and the pipeline tells you how optimistic each salesperson is, not how close deals are to closing. Stages like Interested, Hot and Almost there mean different things to different people, so the forecast built on them is fiction. The fix is not a new CRM. It is defining each stage by something the buyer has verifiably done, with clear rules for moving in and out. This guide shows how.
Stages based on buyer actions
| Seller-based stage | Buyer-based alternative |
|---|---|
| Interested | Contact requested a call or replied to outreach |
| Hot lead | Discovery meeting held, needs and timeline documented |
| Proposal | Buyer asked for a quote and confirmed budget range |
| Almost there | Buyer has shared the quote with the decision maker |
| Closing | Buyer has requested contract or started procurement |
The test for every stage: could a colleague look at the deal and agree, from the logged activity, that it belongs there? If the answer depends on who you ask, the stage needs a sharper definition.
Entry and exit criteria
Criteria turn stage names into rules. Write them down, put them in the CRM's stage descriptions, and use required fields so a deal cannot move forward without the information the next stage needs.
| Stage | Enters when | Required before moving on |
|---|---|---|
| 1. Meeting booked | A first meeting is in the calendar | Company, contact role, source |
| 2. Needs confirmed | Discovery meeting held | Problem, timeline, who decides |
| 3. Quote requested | Buyer asks for a price | Budget range, scope summary |
| 4. Quote sent | Written quote delivered | Value, expected close date |
| 5. Decision stage | Buyer confirms quote is with decision maker | Next step and date agreed |
| Won / Lost | Signed, or buyer declined or went silent | Loss reason from a fixed list |
How many stages is right
- Too few stages, like Open and Closed, hide where deals get stuck.
- Too many stages create admin that salespeople skip, and data becomes unreliable.
- Five to seven open stages suit most small teams selling services or software.
- If deals often skip a stage, merge it with the next one. If deals sit for weeks in one stage with very different situations, split it.
- Different sales motions, such as quick one-off sales and long projects, may need separate pipelines rather than one long list.
Whatever the number, the stages only work if the team uses them. Our guide on getting the team to use the CRM covers the habits side.
Probability and forecasting
Most CRMs let you set a win probability per stage and multiply it with deal value to produce a weighted forecast. The default probabilities are guesses. Replace them with your own history as soon as you have enough closed deals: for each stage, how many deals that reached it were eventually won?
- Export deals closed in the last six to twelve months, won and lost.
- For each stage, count deals that reached it and how many of those were won.
- Use that ratio as the stage probability, and revisit it every quarter.
- Add expected close dates, and treat deals whose date has passed as a warning, not as still likely.
With few deals, the numbers will be rough. That is fine; a rough forecast based on real history beats a precise one based on hope.
Reviewing the pipeline weekly
- Which deals moved forward this week, and what did the buyer do?
- Which deals have no next step or a next step in the past?
- Which deals have not changed stage in longer than normal for that stage?
- Which deals should be closed as lost, and why?
- What does the weighted forecast look like against target?
Decision rule: a deal with no agreed next step and no buyer activity for twice the stage's normal duration gets closed as lost, with a reason. It can be reopened. When you do not need help: a team of two with a handful of deals can set this up in a day with the CRM's own settings. When the CRM has years of messy data, several pipelines or integrations feeding it, a CRM setup audit cleans up stages, fields and automation together. Run the CRM health checklist first, and book a short call if the result worries you.
Frequently asked questions
Should stages be the same in HubSpot and Pipedrive?
The principles are the same in any CRM. The tools differ in how required fields and automations are set up, but buyer-based stages with clear criteria work everywhere.
What if a deal needs to move backwards?
Move it. A pipeline that only moves forward hides reality. If buyers often return to an earlier stage, that is a signal about your sales process worth discussing.
How many loss reasons should we track?
Five to eight fixed reasons, such as price, timing, chose competitor, no decision and poor fit. Free text alone cannot be analysed, but you can add a comment field for detail.
When should a lead become a deal?
When there is a concrete buying situation, typically when a first meeting is booked. Before that, keep it as a contact or lead so the pipeline only shows real opportunities.
Pipeline you cannot forecast from?
In a free 15-minute call we look at your current stages and data, and tell you whether a settings change is enough or the CRM needs a proper clean-up.
Book a free 15-minute call