Sales process / 5 min read
Sales pipeline stages for a small business, with examples
Build a pipeline that tells your team what to do next. Start with a few clear stages, define when a deal moves and keep an owner on every opportunity.
A sales pipeline is a view of open opportunities as they move towards a decision. It is useful when a stage tells the team something concrete about the customer’s progress. A board full of vague labels can look organised while leaving the next action unclear.
Start with the process your business already uses. You can add detail later when it helps someone make a decision. The example below is a suggested starting point, not a universal sales method.
Start with five clear stages
Stage | What it means | Example next action |
|---|---|---|
New enquiry | A potential customer has made contact | Assign an owner and arrange a reply |
Needs understood | You understand the requirement and fit | Confirm the scope or book a survey |
Quote or proposal sent | The customer has a defined offer to consider | Agree when to discuss it |
Decision pending | Questions are being resolved before a decision | Record the blocker and next conversation |
Won or lost | The opportunity has a recorded outcome | Hand over delivery or record the reason |
Some businesses will not need a separate decision-pending stage. Others may need a survey, compliance review or procurement step. Keep a stage only when it represents a real change in the work, with a clear reason for moving a deal into it.
Write a rule for moving into each stage
‘Looks promising’ is a personal judgement. ‘Customer has received proposal version two and agreed to discuss it on Thursday’ is a record that another person can use. Define the evidence needed to enter a stage and what should happen next.
Move a deal to Quote sent when the agreed version has been delivered to the customer, its amount is recorded and the next follow-up has an owner and date.
Avoid creating a new stage for every email or phone call. Those are activities within a stage. A pipeline should show the buying process; tasks should show the work required to keep that process moving.
Adapt the stages to your business
Trades: Enquiry → Survey booked → Quoted → Accepted. Keep scheduling and delivery work in the job system you rely on.
Agencies: Enquiry → Discovery → Proposal sent → Decision → Won or lost. Record the service and proposal version against the opportunity.
Consultants: Introduction → Discovery → Scope agreed → Proposal → Decision. Keep promised dates visible alongside client delivery work.
The labels matter less than whether everyone interprets them consistently. Walk through three recent opportunities as a team. If people put the same deal in different stages, clarify the rule before adding more fields.
Give every opportunity a next action
A stage alone cannot tell you when to act. Store an owner, a short next action and its due date. If a customer is waiting for internal approval, record that dependency and the date you agreed to check back. If the timing is unknown, make finding out the next action.
Customer and opportunity name
Current stage and relevant offer value
Person responsible for the next action
What that action is and when it is due
Last meaningful customer contact
These fields provide a useful starting record. Add a source or expected decision date when your team will actually use it. Requiring a long form for every enquiry can make the record harder to keep current.
Review movement, not just the total value
An open pipeline total is the sum of recorded opportunities. It is not revenue, cash in the bank or a guaranteed forecast. A large deal without a decision date or clear next step needs a different conversation from a smaller quote awaiting a final signature.
At a weekly review, look for overdue next actions, opportunities that have stopped moving and customers waiting on your team. Check whether the quoted scope or amount has changed. Close lost opportunities honestly so they do not inflate the view of active work.
If you use stage probabilities for forecasting, base them on your own observed outcomes once you have enough useful data. Do not treat arbitrary percentages as evidence of the likelihood that an individual customer will buy.
Make updating the pipeline part of the conversation
Update the record after the call, while the context is fresh. Vemkin’s current offer focuses on availability chasing and record admin for care-staffing booking teams. A scoped pilot measures coordinator minutes per shift request, including review and corrections, alongside response speed and record accuracy.
Try the same short test in any CRM you consider: save a fictional enquiry, assign its owner, record a quote and ask what needs attention tomorrow. That gives you a concrete way to judge whether the tool fits your team’s working day.
Further reading
Pipedrive’s own overview explains its pipeline approach. The stage examples in this guide are suggested workflows to adapt to your business.