A deal marked ‘80% likely’ is not useful if nobody can explain what happened to earn that confidence. The point of learning how to create deal stages is not to make a CRM look tidier. It is to give every opportunity a clear next step, a shared meaning and an honest chance of closing.
For a small sales team, a good pipeline removes the daily question: “What is actually happening here?” For an agency, consultancy or growing B2B business, it stops valuable conversations disappearing between calls, proposals and handovers. Simple structure. Better decisions.
Start with the buyer’s progress, not your internal tasks
Deal stages should describe a change in the customer’s position. They should not simply mirror what your team has done.
“Sent email” is an activity. “Proposal sent” may be a stage, but only if the buyer has received a defined offer and is considering it. “Discovery complete” works when you have established a genuine need, the right contact and a reason to continue.
This distinction matters because activity can create a false sense of movement. A salesperson might make three calls and update several notes without the deal becoming any more likely to close. Your pipeline should show buyer commitment, not busyness.
Before naming stages, look at a handful of recent wins, losses and stalled opportunities. Ask what was true at each meaningful point in the sales process. When did the prospect become qualified? When did they agree the problem was worth solving? When did commercial terms become real? The answers reveal the milestones your stages need to capture.
How to create deal stages around real decisions
Most small and mid-sized B2B teams need five to seven active stages. Fewer can hide important risk. More can turn ordinary progress into admin.
The right number depends on how people buy from you. A consultancy selling a six-month engagement may need a separate stage for scoping and a separate stage for proposal review. A startup selling a straightforward subscription may move from discovery to trial to commercial discussion far more quickly.
A practical pipeline could look like this:
- New enquiry - A potential opportunity has arrived, but there is not yet enough information to assess it.
- Qualified - You have confirmed a relevant need, a plausible fit and a route to the decision-maker.
- Discovery - You are clarifying requirements, priorities, timing and stakeholders.
- Solution agreed - The buyer accepts the proposed approach, scope or product fit in principle.
- Proposal sent - Commercial terms, pricing or a statement of work is with the buyer.
- Decision pending - The buyer is reviewing, negotiating or gaining approval. A defined decision date exists.
- Closed won or closed lost - The outcome is known and recorded.
Treat this as a starting point, not a template to copy blindly. The wording matters less than the definition behind each stage. If two people interpret “Qualified” differently, reports will be unreliable from the first week.
Give every stage an entry rule
A stage needs an observable entry rule. This is the proof that permits a deal to move forward.
For example, a deal can enter Qualified only when the team knows the customer’s problem, has identified a suitable contact and believes there is a reasonable fit. It can enter Proposal sent only when the buyer has received a priced, tailored offer. It enters Decision pending when a decision process and expected date are clear.
Avoid vague rules such as “feels promising” or “good conversation”. Sales involves judgement, but the pipeline needs evidence. This is how leaders can trust the view without checking every opportunity line by line.
Entry rules also make coaching easier. Rather than saying, “This deal seems stuck,” a sales lead can ask, “What needs to be true for it to move from Discovery to Solution agreed?” The conversation becomes practical.
Define the next step at the same time
Every open deal should have a named next action and a date. Stages tell you where the deal is. The next step tells you whether it is moving.
A proposal sitting in a customer’s inbox is not an active opportunity merely because it is in a late stage. If there is no agreed follow-up, no decision date and no fresh customer engagement, it may be stalled. Keep the stage accurate, but flag the risk.
This is especially useful for founders and account managers who handle sales alongside delivery. A clear next-step field turns a long list of contacts into a focused plan for the week.
Keep probability honest
Many CRMs allow you to assign a percentage probability to each stage. Used well, this can help forecast likely revenue. Used badly, it turns hopeful estimates into a polished fiction.
Set probabilities from your actual history once you have enough data. If 40 out of 100 qualified opportunities typically become customers, a 40% probability may be sensible. Until you have that history, use modest estimates and revisit them after a few months.
Do not confuse a late-stage deal with a certain deal. A proposal can be well received and still lose to a delayed budget, an internal change or a competitor. Forecasting should inform decisions, not reassure people.
There is also a trade-off. Stage-based probability is quick and consistent, but it cannot account for every deal’s specific strength. Some teams add a separate confidence assessment for larger opportunities. That can be useful, provided it does not replace the standard pipeline. One clear view is better than several competing versions of the truth.
Add closed-lost reasons without creating a chore
Closed-lost data is one of the most valuable parts of a pipeline. It shows whether you are losing on price, timing, fit, competition or something else. But do not ask the team to choose from a list of twenty reasons. They will pick the first one and move on.
Use a short set of meaningful options, such as no decision, budget, competitor, poor fit and timing. Include an optional note for context. Review patterns quarterly, not just individual losses. A cluster of ‘poor fit’ losses may mean marketing is attracting the wrong enquiries. A rise in ‘no decision’ could point to weak qualification or a market that needs more urgency.
Closed won deserves care too. Record the agreed value, start date, product or service sold and any commitments made during the sale. This creates a cleaner handover to delivery and reduces the awkward moment when a new customer has to repeat what they already told you.
Build stages for the whole customer-facing team
Sales stages affect more than sales. Marketing wants to know which sources produce qualified opportunities. Finance needs a credible view of expected revenue. Delivery needs clarity about what has been sold. Customer success needs the context behind the relationship.
That does not mean every department should add fields and approvals to the pipeline. It means the core stages should answer the questions those teams genuinely need answered.
Keep the structure lean. A deal record usually needs the account, primary contact, value, expected close date, stage, next step and key notes. Add fields only when someone will use them to make a better decision. Every extra field has a cost: more time, less consistency and more temptation to postpone updates.
Test the pipeline before making it permanent
Run your proposed stages with a small group for two or three weeks. Use real opportunities, not examples invented in a meeting. Watch where people hesitate, where stages are skipped and where definitions overlap.
If a deal regularly jumps from Qualified to Proposal sent, either Discovery is unnecessary for your sales motion or its entry rule is unclear. If opportunities linger in Solution agreed for months, the stage may be concealing different situations: perhaps some buyers are waiting for a proposal while others are waiting for internal approval.
Refine the language, not the principle. The goal is a pipeline that someone can update in seconds and another person can understand immediately. Monty CRM is built around that kind of clarity: connected customer information, without a screen full of clutter.
Review stages as your sales process changes
A pipeline is not a one-off project. It should stay stable enough for reporting, while changing when the way you sell genuinely changes.
Review it after a meaningful shift: a new service line, a larger average deal size, a move into a new market or a different buying committee. Do not redesign it because one unusual deal was awkward. Edge cases are normal. They do not always justify a new stage.
The best deal stages make progress visible without pretending sales is predictable. Give each stage a clear meaning. Require evidence before a deal moves. Keep a next step on every open opportunity. Then your pipeline becomes more than a list of possibilities. It becomes a calm, useful picture of what your team should do next.