Affiliate Disclosure: We may earn a commission if you later purchase through a qualifying link, at no extra cost to you. No affiliate links are active in this article at publication. Recommendations and criticism are independent. See our editorial policy.
Part of our CRM Software Guides for Small Businesses library.
Cost evidence: A pipeline redesign can precede a software purchase. If you are also budgeting a platform, our 2026 CRM pricing dataset compares annual advertised seat costs for teams of 5, 10, and 20.
Search goal
Choose clear deal stages for a small sales team
Build clear CRM pipeline stages with entry criteria, exit criteria, probability rules, and examples for service, SaaS, and agency sales.
A pipeline should describe customer progress, not a salesperson’s optimism. If two reps interpret “qualified” differently, pipeline value and forecasts become fiction. The solution is not more stages. It is a small number of stages with observable exit conditions.
Quick reference
| Recommended starting range | Four to six open stages |
| Stage movement | Based on evidence, not elapsed time |
| Probability | Calibrated from historical conversion, not intuition |
| Required on every open deal | Owner, value, next action, and next-action date |
| Review signal | Age in stage plus missing next activity |
Editorial concept images for decision planning; they are not product-interface screenshots.
Example 1: professional services
Use Qualified inquiry, Discovery scheduled, Discovery completed, Proposal delivered, and Contract in review. A deal enters Proposal delivered only when a priced document has been sent to a named decision maker. “Working on proposal” is an activity, not customer progress.
Example 2: self-serve SaaS with assisted sales
Use Product-qualified lead, Discovery completed, Technical validation, Commercial review, and Procurement. Define the product behavior that creates a qualified lead, the success criteria for validation, and the stakeholder confirmation required before commercial review.
Example 3: marketing agency retainers
Use Fit confirmed, Strategy call completed, Scope agreed, Proposal sent, and Verbal approval. Track expected monthly retainer separately from one-time setup revenue. When a deal closes, trigger a delivery handoff rather than adding onboarding as another sales stage.
How to improve a broken pipeline
Export the last 50 closed deals and compare stage paths, time in stage, and losses. Merge stages that never change a decision. Split a stage only when it has a distinct customer milestone and owner action. Create separate pipelines only when motions truly require different stages, permissions, or forecasting.
Write a stage contract for every pipeline step
A stage contract prevents representatives from using the same label differently. It contains an entry condition, an exit condition, the evidence that must exist, the maximum acceptable age, and the next person responsible. Keep it to one screen. If the rule needs a training manual, the stage is probably combining several customer milestones.
| Stage | Entry evidence | Exit evidence | Age review |
|---|---|---|---|
| Qualified | Problem, fit, and named contact confirmed | Discovery meeting completed | Seven days without a booked meeting |
| Solution validated | Required workflow and decision criteria documented | Buyer confirms the proposed approach | Ten days without stakeholder feedback |
| Proposal delivered | Scope, price, and recipient recorded | Commercial review begins or deal is lost | Five days without a scheduled follow-up |
| Contract review | Commercial intent and approvers confirmed | Signature or documented loss reason | Seven days without a named blocker |
Separate activities from progress
“Called,” “emailed,” and “follow-up two” describe seller activity, not buyer progress. Keep them as tasks or timeline events. A deal advances only when new customer evidence exists. This distinction makes stage conversion meaningful and prevents a busy representative from appearing more successful merely by moving cards.
Define closed-lost before launch
Use a short controlled list: no fit, no budget, no priority, chose competitor, no decision, unreachable, timing, or duplicate. Add a note for context, but do not replace categories with free text. Review loss reasons quarterly. If “no decision” dominates, discovery or urgency may be weak; if “no fit” dominates, qualification or lead targeting may be wrong.
Calibrate probability from outcomes
Begin with rough probabilities only if the CRM requires them. After enough deals close, calculate the percentage that actually won from each stage. If 40 of 100 deals entering Proposal delivered eventually won, the historical conversion is 40 percent. Recalculate by sales motion when sample sizes permit; referrals, inbound trials, and cold outbound opportunities often behave differently.
Weekly pipeline hygiene query
- Open deals with no next activity.
- Deals older than the stage review threshold.
- Close dates in the past.
- Deals with no amount, owner, or source.
- Deals moved backward more than once.
- Deals repeatedly postponed without new buyer evidence.
The meeting should produce decisions: advance with evidence, schedule a concrete next action, correct the record, or close the deal. A pipeline review that only narrates every card adds reporting work without improving the forecast.
Original operating worksheet
Audit every pipeline stage with entry and exit evidence
A stage name is not a process definition. For each stage, document the event that allows entry, the action an owner must complete, the evidence required to exit, the maximum acceptable age, and the closed-lost reason used when work stops. This makes reporting consistent across users and prevents optimistic stage changes.
| Field | Example | Control question |
|---|---|---|
| Entry event | Discovery meeting booked | Can two users recognize the same event? |
| Required action | Confirm problem, authority, timing, and next step | Is responsibility assigned? |
| Exit evidence | Mutually agreed next meeting or documented loss | Is the record auditable? |
| Age threshold | Seven days without a scheduled next action | Will stale deals become visible? |
| Loss reason | No priority, no fit, no decision, competitor | Can the reason guide improvement? |
A monthly pipeline hygiene review
Count deals with no next activity, deals older than the stage threshold, close dates repeatedly moved, missing values, and records owned by inactive users. Review a sample rather than relying only on totals. The objective is not to make the dashboard look healthy; it is to make the underlying commitments explicit.
Official implementation references
- HubSpot: set up deal pipelines and stages
- Pipedrive: customize pipeline stages
- Zoho CRM: design a Blueprint
These product documents show available configuration patterns. Adapt the stage definitions to observable events in your own sales process.
Action checklist
- Use customer-verifiable milestones
- Write one-sentence exit criteria
- Keep activities out of stage names
- Require a next action on every open deal
- Define closed-lost reasons
- Review stage aging weekly
- Recalibrate probabilities from actual outcomes
Common mistakes to avoid
- Stages named Follow-up 1, Follow-up 2, and Follow-up 3
- Moving deals forward to make the pipeline look healthy
- Leaving dead deals open indefinitely
- Combining onboarding with pre-sale stages
Frequently asked questions
What are common CRM pipeline stages?
A simple B2B pipeline often includes qualified, discovery completed, solution validated, proposal delivered, and commercial or contract review.
How many stages are too many?
More than six or seven open stages often creates ambiguity for a small team, unless the sales process has genuinely distinct milestones.
Should every pipeline stage have a probability?
Probabilities can help forecasting, but they should be calibrated from historical conversion and not treated as certainty.
Put this guide into practice
Use the free planning tools
After defining stage evidence, use the free sales pipeline velocity calculator to compare qualified opportunity volume, deal value, win rate, and cycle length.
Continue your CRM research
Compare the software after defining the workflow.
Use these requirements and checklists before opening vendor pricing pages. Then test the same real-world scenario in each shortlisted product.
Editorial note: this guide was researched and reviewed by the Northstar Select editorial team on August 8, 2026. Commercial details should be reconfirmed before purchase.