What a pipeline stage actually is
A stage is not a mood or a feeling about a deal. It is a description of something that has happened. 'Customer seems interested' is a feeling. 'Customer has shared their requirement and budget range' is an event you could check.
Stages are useful for three reasons: they show each person what to do next, they let you see where deals get stuck, and they make a forecast possible. If stages are vague, all three break down at once.
A simple set of stages to start from
Most B2B small businesses can work with five or six stages. Adapt the names to how your customers really buy. A distributor, a software reseller and a training firm will not sell in the same steps, so treat the list below as a starting point rather than a template.
- New enquiry: someone has asked for information, nothing is verified yet
- Qualified: you know who decides, what they need and roughly when they need it
- Solution shared: a demo, sample, site visit or first quote has been given
- Proposal or negotiation: a written offer is with the decision maker
- Won or lost: a clear yes or no, with a reason recorded
Write an entry rule and an exit rule for each stage
This is the part most teams skip. For each stage, write one line saying what must be true before a deal can be placed there, and one line saying what must happen before it moves forward. For example, a deal moves from 'Qualified' to 'Solution shared' only after you have confirmed who else is involved in the decision.
Keep the rules short enough to fit on one page. Pin that page where the team will see it, and review it in your weekly sales meeting for the first month.
Track how long deals stay in a stage
Once stages are clear, an ageing view becomes useful. A deal that has been in 'Proposal' for twice as long as your usual sales cycle needs a conversation, not another reminder. Either the customer has gone quiet, or the proposal was missing something.
You do not need special software to start. A shared sheet with the deal name, stage, owner, value, date it entered the stage and next step is enough. Move to a CRM when the sheet becomes hard to keep current.
Common mistakes to avoid
Too many stages is the most common problem. Teams stop updating a fourteen-step pipeline within weeks. Close behind is moving deals forward to look good. If a deal sits in 'Proposal' only because someone does not want it to look cold, the pipeline value you report is fiction.
Another mistake is never marking lost deals. A lost deal with a reason, such as price, timing or competitor chosen, teaches you more than ten won deals that nobody reviewed.
- Stages named after activities instead of customer progress
- No named owner for each deal
- No next step and date recorded against each open deal
- Pipeline value counted without any view of stage-wise likelihood from your own history
Review the stages once a year
Your business changes, and so should your stages. If you add a new product, enter a new segment or start selling through partners, check whether the stages still describe how those customers buy. Ask the team where they feel the pipeline does not match reality. Their frustration is often the best sign that a stage is missing or badly named.
When you change a stage, update the written rules and tell everyone on the same day. Avoid changing definitions in the middle of a month, since it makes your numbers hard to compare. Note the date of every change in the sheet so you remember why a trend moved.
A good pipeline is short, specific and checked every week. Start with five stages, write an entry and exit rule for each, and record a next step on every open deal. Once the team trusts the stages, you can use your own history to judge how likely deals at each stage are to close. If you want help shaping stages around how your customers actually buy, a sales consulting conversation can be a practical starting point.