How to set up a sales pipeline your team will follow

How to design pipeline stages that match the way you sell, what belongs in each stage, and how to keep deals moving instead of sitting still.

A sales pipeline is a simple idea: a picture of every deal you’re working on and how far along it is. Done well, it tells you where to spend your time and where next month’s sales will come from. Done badly, it’s a list of stages nobody agrees on, with deals parked in the middle because nobody knows what comes next.

The software is almost never the problem. The stages are. Here’s how to design ones your team will actually follow.

What it has to answer

A pipeline should tell you three things: where each deal is, what has to happen for it to move on, and what it’s worth, both in total and at each stage. If yours can’t answer all three, it’s a list, not a pipeline.

Start from how you really sell

The most common mistake is copying a template: Lead, Qualified, Proposal, Negotiation, Closed. It looks tidy, but if your real process is different the team won’t follow it faithfully, and then the numbers mean nothing.

Instead, get everyone in a room and write down what actually happens between first contact and a signed deal. A business selling a service to other businesses might say: we get an enquiry, make first contact, find out what they need, send a proposal, follow up while they think, and they sign. That’s six stages in your own words, and it’s a better first draft than any template.

Rules for stages that work

A stage should be something that has happened, not something you’re hoping for. “Proposal sent” is a fact. “Likely to buy” is an opinion, and a pipeline built from opinions can’t be trusted.

Stages should be clearly different from each other. If two are hard to tell apart, merge them, or reps will pick at random. Fewer is better: five to seven is plenty for most small teams, and past eight people struggle to remember them.

Give each stage an exit condition, meaning what has to be true before a deal can move on. “Needs identified and budget discussed” is clear. “Going well” isn’t.

And include two endings. Every pipeline needs a Won and a Lost, and when a deal ends, record why. After a few months the reasons you lose deals are some of the most useful information you own.

A worked example makes it concrete. Take a team selling a service. New enquiry means a lead has arrived and has an owner, and it moves on when the first call is made. Contacted means a first conversation has happened, and it moves on once the need and the decision maker are understood. Qualified means we know what they need and that they can buy, and the exit is a quote sent. Proposal sent runs until the client replies, and Negotiating until terms are agreed. Then Won or Lost, with a reason. Yours will differ. What matters is that every stage states a fact and says what moves it on.

Give every deal a value, a date and an owner

A stage on its own isn’t enough. Each deal also needs a value, even a rough one, so you can see what’s in each stage. It needs an expected close date, which stops deals sitting indefinitely and makes forecasting possible, and one named owner, not a team. And it needs a next step with a date. That last one is the subject of how to stop leads slipping through the cracks.

If you sell more than one thing, one pipeline may not fit all of it. A quick one-visit product and a long multi-meeting contract have different stages and timescales, and putting them on one board makes both harder to read. In Henkan CRM each thing you sell is its own deal type, with its own stages and value type, and a lead can have a deal of each. You see them on the sales pipeline board, one deal type at a time, with the number and value of deals in each column.

Keep it moving

A pipeline fills up with stale deals unless somebody looks after it. Review it weekly from the board itself, starting at the end, and ask of every deal what the next step is and when. Look hard at anything that’s been in a stage far longer than usual: either find the next step or close it as lost. The reports show how long deals spend at each stage and which have stalled.

Close out the dead ones. A pipeline stuffed with deals that will never close overstates what you’ll win, and sooner or later somebody notices.

Once your stages are reliable you can attach a probability to each, perhaps ten per cent at Contacted and seventy at Negotiating, and multiply by value to get a forecast. It won’t be exact, but it’ll beat a gut feeling, and it improves as you learn what really closes from each stage. Base the percentages on what has happened to your own deals, not on optimism. Henkan CRM forecasts use the probabilities you set on each stage. You can change stages later, but do it deliberately: agree it as a team, move existing deals to the right new stage and note the date so later reports are read in context. The person who runs the weekly review should own the design, with input from the reps.

What goes wrong

Too many stages. Stages based on feelings, because “hot” and “warm” mean different things to different people. No ending reasons. One pipeline for products that sell differently. Never cleaning it. And designing it without the reps, who know how deals really go.

Get the team involved in naming the stages, run your meetings from the board and don’t add a stage without removing one. Getting your whole team to use the CRM goes further. And if you’re still working out what a small team needs from a CRM in the first place, see CRM for small sales teams.

What a stuck deal is telling you

A deal that sits in one stage is rarely just slow. If it’s stuck after the proposal’s gone out, it’s often because the real decision maker hasn’t seen it, or there’s a price objection nobody’s said out loud. If it’s stuck before the proposal, you may not have understood the need well enough to quote. Use stuck deals as a prompt for a question, not just a nudge: who else needs to agree, what would make this easy to say yes to, and what happens if they do nothing? The answers often point to a missing step in your stages.

To see your own stages built in Henkan CRM, book a demo and bring your process along.

See Henkan CRM set up around how you sell.

Book a demo and we will show you the product with your own sales process in mind.

Book a demo
  1. 01 Book a demo Tell us a little about your business.
  2. 02 See it around how you sell We show you the product with your sales process in mind.
  3. 03 We set it up for you Our team configures your account, from fields and stages to automations.