Sales Pipeline · CRM Strategy · Small Business
What sales pipeline stages should a small team use?
The short answer
A small sales team should usually use six pipeline stages: qualified, discovery completed, solution confirmed, proposal sent, negotiation, and closed won or lost. Each stage needs an observable exit criterion, not a vague feeling. Keep prospecting outside the opportunity pipeline and add stages only when they change how the team sells or forecasts.
A sales pipeline is the ordered set of steps an opportunity passes through from qualification to a decision. Its purpose is to show what has happened, what must happen next, and how much revenue is realistically in play. More stages do not make a pipeline more accurate; clear criteria do.
What are the six essential sales pipeline stages?
| Stage | Meaning | Exit criterion |
|---|---|---|
| 1. Qualified | The lead fits basic customer and opportunity criteria | Need, fit, and a plausible buying path are confirmed |
| 2. Discovery completed | The rep understands the problem and buying context | Discovery is documented and stakeholders are identified |
| 3. Solution confirmed | The buyer agrees the proposed approach could solve the problem | Scope and success criteria are accepted |
| 4. Proposal sent | A formal offer is with the buyer | Buyer confirms receipt and a review date is scheduled |
| 5. Negotiation | Commercial or legal terms are under active review | Terms are agreed or the buyer declines |
| 6. Closed won/lost | A final outcome is recorded | Contract/order completed, or a loss reason is captured |
Teams with very short sales cycles may combine discovery and solution confirmation. Complex sales may need a security review or procurement stage. Start with the six-stage model and change it only when a separate step improves execution or forecasting.
What belongs before the sales pipeline?
Raw leads and early prospecting usually belong in a lead queue, not the opportunity pipeline. A deal should enter the pipeline only after minimum qualification. Otherwise, the pipeline becomes a list of people a rep hopes might buy, inflating value and making conversion rates meaningless.
Define qualification with a small set of questions:
- Is there a problem the company can solve?
- Does the account match the target customer profile?
- Is there a person willing to participate in a sales process?
- Is there a plausible business reason to act?
Budget and timeline matter, but rigid qualification frameworks can exclude real opportunities too early. Use evidence appropriate to the business.
How do you define pipeline stage exit criteria?
An exit criterion is an observable event required before a deal advances. “Rep feels positive” is not observable. “Buyer confirmed success criteria in writing” is.
Good exit criteria are:
- Buyer-centered: they reflect buyer progress, not only seller activity.
- Verifiable: a manager can inspect the record and reach the same conclusion.
- Minimal: only information that changes the next action or forecast is required.
- Consistent: every rep applies the same rule.
Document the criteria in the CRM’s stage descriptions and reinforce them in pipeline reviews. If managers routinely move deals based on intuition, the written stages will not matter.
Should “proposal” be a pipeline stage?
Yes, when sending a proposal represents a meaningful commitment and the buyer has agreed to review it. No, when reps send generic quotes before discovery. The stage should signal buyer progress, so require a confirmed review date rather than merely an email attachment.
How should probabilities work in a sales pipeline?
Do not choose probabilities because they look tidy. After enough closed deals, use historical conversion from each stage. If 40 of 100 qualified deals eventually close, the evidence-based probability for that stage is about 40 percent, subject to segment and data-quality differences.
For a new pipeline, use conservative provisional probabilities and label them as assumptions. Review them quarterly after the team has enough outcomes. Deal-specific forecast categories—such as pipeline, best case, and commit—can complement stage probability but should not replace stage discipline.
What pipeline stages should you avoid?
- Contacted: an activity happened, but the buyer may not have progressed.
- Interested: the term is subjective and difficult to audit.
- Follow-up: every active deal needs follow-up; it is not a buying milestone.
- Stalled: use a status, reason, or closed-lost outcome instead of hiding inactive deals in the pipeline.
- 90 percent: probability is an attribute, not a business step.
Also avoid separate stages for every internal task. Use CRM activities and checklists for tasks that do not represent a new buying state.
How often should you review pipeline design?
Review the pipeline quarterly or when the sales process changes materially. Inspect time in stage, conversion rates, loss reasons, and deals that move backward. A stage with almost no deals, no distinct action, or no forecasting value may not be needed.
The pipeline must remain stable long enough to produce comparable data. Frequent renaming and restructuring destroys trend history, so record definitions and map old values before making changes.
If the team is setting up its first system, pair this model with the CRM implementation checklist. If a spreadsheet still handles the pipeline reliably, read when a business actually needs a CRM before adding software.