Sales pipeline stages should describe progress in a buying decision. Give each stage a clear entry rule, an exit rule and evidence that a teammate can check. “Sent three emails” describes sales activity; “buyer agreed to a discovery call” describes a change in the opportunity.
Review real deals before naming stages
Pick recent wins, losses and stalled deals. Ask what the buyer needed to decide, which people were involved and what moved the deal forward. Look for repeated decision points rather than copying another company’s CRM setup.
Keep early enquiries separate from qualified opportunities if they have not yet shown a suitable need. Your pipeline will be hard to forecast if every newsletter signup enters as an active deal.
Write a practical stage definition
For each stage, record the buyer’s situation, the evidence needed to enter, the next agreed action and the person responsible. Use as few stages as the buying process needs. Two stages that require the same evidence probably do not need separate labels.
Here is an illustrative sequence for a small service business. Adapt it to how your customers actually buy:
- Qualified enquiry: the team has checked service fit and confirmed that someone wants to discuss the work.
- Discovery complete: the buyer’s problem, desired outcome and main constraints are recorded. Important unanswered questions remain visible.
- Proposal under review: the proposal has reached the relevant buyer, and a next discussion or decision step is agreed.
- Decision pending: the remaining approvals or contract questions are known, with a named contact and follow-up date.
- Won or lost: the outcome meets your documented close rule, with a reason recorded for a loss.
Do not move a deal forward just because a proposal was generated. The buyer may not have received it, understood it or agreed that it addresses the need.
Make stalled deals visible
Record the last meaningful buyer interaction and the next action date. An overdue action should prompt a review, not an automatic stage promotion. Decide how to handle a buyer who pauses the project so the record does not sit indefinitely among active opportunities.
Ask reps to choose a useful loss reason and add a short explanation where needed. “No response after agreed follow-ups” and “selected another supplier” suggest different problems. Avoid forcing every loss into “price.”
Test the stages with the team
Have two teammates independently place the same sample deals. Discuss disagreements and tighten the definitions. Check whether required fields are available at the point you ask for them; otherwise people may enter guesses to get past the form.
If ownership is unclear, resolve it with lead routing rules. If existing records use several names for the same stage, plan a controlled CRM data cleanup.
Review outcomes before assigning probabilities
Compare stage progression, time in stage and final outcomes. Where you have enough consistent historical data, use it to inform forecast assumptions. With few deals or a changed sales process, describe uncertainty rather than presenting a stage percentage as a reliable prediction.
Keep the definitions near the CRM and record when they change. That gives the team a shared way to discuss progress and helps explain shifts in reports.