What does a sales pipeline look like? Examples and templates
Pipeline diagrams in marketing material tend to look the same: a clean five-stage funnel with names like Lead, Qualified, Proposal, Negotiation, Won. The reality of pipelines in working small businesses is messier and more specific to each sector.
This piece is the version of the question that small businesses ask: what does a real sales pipeline look like, for the kind of business I run, and how do I build mine?
There's a pillar piece on lead tracking and sales pipeline for the broader view.
What a sales pipeline is
A sales pipeline is a sequence of stages that a deal moves through from first contact to closed (won or lost). Each stage represents a meaningful change in the deal's state, and there are usually four to seven stages in a small business pipeline.
The point of having a pipeline is to give you visibility on where each deal sits, what's needed next to move it forward, and an overall view of your sales activity.
A pipeline isn't a project plan. It's not a marketing funnel. It's not a customer journey map. It's specifically about deals and how they progress.
What a generic pipeline looks like
The standard template most CRMs come with:
Lead. Someone you've identified but haven't actively engaged with.
Qualified. You've confirmed there's a real opportunity (budget, decision-maker, need, timing).
Proposal. You've sent a proposal or quote.
Negotiation. You're working through terms.
Won. They've agreed and committed.
Lost. They've gone elsewhere or decided not to proceed.
This is fine as a starting point. It's not particularly useful as a real pipeline because most small businesses don't have stages quite like this. Their actual sales process looks different.
Realistic pipeline examples by sector
A few examples drawn from real client setups.
Coaching business (long sales cycle, relationship-led)
Initial contact. Discovery call booked. Discovery call held. Considering. Programme proposed. Decision pending. Started. Lost or paused.
The "Considering" stage is the long one for coaching. People can sit there for months. The "Lost or paused" combination acknowledges that paused leads often come back, so they're not lost forever.
Recruitment agency (placement-focused)
Brief in. Qualified. Searching. Shortlisted. Client interviewing. Offer made. Placement confirmed. Placement fell through.
The pipeline reflects the recruitment workflow specifically. The "Placement fell through" stage handles offers that get withdrawn or candidates who decline late, which happens often enough to need its own stage.
Architectural practice (long projects)
Initial enquiry. Briefing meeting. Fee proposal. Decision pending. Won. On hold.
Architectural projects can sit in "Decision pending" or "On hold" for very long periods. The pipeline acknowledges this rather than trying to force every deal to close within a quarter.
HR consultancy (mix of retainer and project work)
Conversation. Scoping. Proposal. Decision. Project running. Retainer running. Ended or paused.
This pipeline has separate end states for project work and retainer work, because the two have different shapes. A project ends; a retainer runs continuously until it doesn't.
Solo consultant (referral-driven, short cycle)
Introduction. Conversation. Scope agreed. Started. Lost.
Simpler pipeline because the sales process is genuinely simpler. Most opportunities convert quickly or not at all.
What makes a pipeline work
Six principles I see in successful pipeline setups.
Stages reflect reality, not aspiration. The pipeline matches how the business sells today, not how it should sell. Reform the process if you want, but the pipeline tracks reality.
Each stage is meaningful. Each stage represents a real change in the deal's state, not just "the next thing to do". "Send proposal" is a task. "Proposal sent" is a stage.
Three to seven stages. More than seven and the pipeline becomes noise. Fewer than three and it doesn't help.
Clear definition of when a deal moves. Everyone on the team agrees what "Qualified" means or what counts as "Proposal sent". Without this, deals end up in the wrong stage and the pipeline can't be trusted.
Loss reasons captured. When a deal is lost, the reason gets captured. This is the data that improves your sales process over time.
Regular review. Weekly pipeline review surfaces stale deals, agrees next steps, and keeps the data current.
How to design your own
The approach I'd suggest.
Start by writing down what currently happens between "we first hear from someone" and "we've agreed to work together". Not aspirations, the real journey.
Identify the meaningful transitions in that journey. Where does a deal go from being a possibility to being a real opportunity? Where does it go from a real opportunity to being committed?
Name each transition as a stage. Use action-based language ("Proposal sent", not "Sending proposal").
Aim for five to six stages. Add stages only when there's a clear reason. Remove stages that don't represent meaningful transitions.
Define what each stage means. Write a one-line definition for each. Share it with the team. Make sure everyone agrees.
Refine over time. The first version of your pipeline won't be perfect. Adjust based on what you find as deals start moving through.
What to do next
If you're setting up a sales pipeline for the first time and you'd like help thinking through the right stages for your specific business, a discovery call is the no-pressure first conversation.
The pillar piece on lead tracking and sales pipeline goes into the wider question of what makes pipeline management work in practice.
The right pipeline is the one that matches how your business sells, not the one a template gave you. Take the time to design yours properly. The CRM you choose to put it in is the smaller decision.