A sales pipeline is the list of stages a deal goes through from first contact to signature. When stages are not clearly defined, the same deal shows up as “proposal” for one rep and “negotiation” for another; forecasts miss and managers cannot tell which deals need their help.
This post explains how to define stages, which exit criterion to give each one, and the common mistakes teams make in the first months.
1. Tie stages to the customer’s behaviour, not the seller’s
“Preparing a quote” is an internal task; a stage should change when something happens on the customer’s side, such as “The customer confirmed the requirement in writing” or “The quote reached the decision maker”. That way two reps put the same deal in the same stage.
2. Five to seven stages are enough
For most B2B teams this structure is a good starting point:
| Stage | Exit criterion (to move to the next one) |
|---|---|
| Prospecting | First conversation with the right person held |
| Qualification | Budget, authority, need and timing confirmed |
| Needs analysis | Scope agreed in writing |
| Proposal | Priced quote reached the decision maker |
| Negotiation | Commercial terms under discussion, objections known |
| Won / Lost | Order or rejection received in writing |
The more stages you add, the less reps update them; the fewer you have, the less managers can see.
3. Give each stage a probability — but don’t trust it blindly
Stage probabilities (for example 60% at proposal) are the basis of the forecast. Use them as assumptions for the first three months, then adjust them to your actual win rate. Measuring the win rate requires recording the outcome and reason of every closed deal; we cover that in win/loss reason analysis.
4. Prevent stage skipping with required steps
If deals move from qualification to proposal without a known budget or decision maker, the pipeline gets inflated. Define one or two required steps per stage (e.g. “Budget and authority confirmed”) and don’t allow progress until they are done.
5. Make stalled deals visible
A deal that has stayed in a stage twice as long as average is usually already lost. Discussing only those deals in the weekly meeting saves time and keeps the pipeline clean.
In CRModular
Under Settings → Sales Path (Ayarlar → Satış Yolu) you define guidance text and required steps for every stage; a deal whose required step is not done cannot move to the next stage. Probability is filled in automatically when a stage is selected, and deals can be followed in table, Kanban and calendar views. See the help article Sales process: stages and reasons for setup, and the glossary entry Sales pipeline for a short definition. The application interface is currently in Turkish.
Quick checklist
- Are stages tied to customer behaviour?
- Does every stage have a written exit criterion?
- Have probabilities been compared with the real win rate?
- Are deals that sit in a stage for too long discussed every week?