Skip to content

Sales pipeline stages: a simple set-up for a small team

How to define pipeline stages that mean something: five or six steps, each one proven by something the buyer did, plus next steps, weighted value and a weekly review.

Published on 4 min read

A sales pipeline only helps if its stages mean the same thing to everyone who reads them. “Proposal” should tell you something you can act on. On most small teams it means “I think this one might happen”.

Here’s a set-up that works without a sales operations team, and that you can have running in an afternoon.

Define each stage by what the buyer did

The usual mistake is to name stages after your own activity: called, emailed, sent. These measure effort. Better to move a deal when the buyer has done something you can point to.

Here’s the set a new workspace starts with in Soldlyne, which you can rename to match your business. The starting probabilities are the product’s defaults:

StageThe deal moves here when…Starting probability
IdentifiedYou’ve named the company and why it fits5%
ContactedYou’ve reached a real person, and no answer yet10%
ConversationThey answered, and the answer wasn’t no25%
MeetingA meeting has been held, not just booked40%
ProposalThey asked for a price, and have one60%
WonThey said yes100%
LostThey said no, or stopped answering for good0%

Seven names, but only five open stages. If you find yourself wanting a tenth, ask whether it changes what you’d do next. If not, it’s a note, not a stage.

Every open deal has a next step

This is the rule that matters most. A deal with no next step isn’t in your pipeline; it’s in your memory.

A next step has a verb, a person and a date: “Send Léa the revised quote, Thursday”. “Follow up” isn’t one. A good CRM should show you which deals have none, and Soldlyne flags them on the board and on its home page.

Notice what has stopped moving

Deals rarely die with a clear no. They just go quiet. So pick a number of days after which a deal in one stage counts as stuck; Soldlyne uses 14. Then, when one is flagged, either give it a next step or move it to Lost.

Marking a deal lost isn’t a failure. It keeps your numbers honest, and a good reason (too expensive, wrong moment, chose someone else) is the most useful thing a pipeline can teach you.

Use weighted value, carefully

Weighted pipeline value multiplies each open deal by the chance it closes, then adds them up. With made-up deals:

DealAmountProbabilityWeighted
Acme: first order€10,00060%€6,000
Northwind: pilot€20,00025%€5,000
Harbor: renewal€4,00040%€1,600
Total€34,000€12,600

The €34,000 is what you’d have if everything went right. The €12,600 is a more sober number for planning. It’s only as good as the probabilities, though: after a few months, compare them with your own stage-to-stage conversions and adjust. A default is a starting point, not a fact about your business.

Fifteen minutes a week

Once a week, open the board and go through it from right to left, starting nearest the money:

  1. Proposal. Does each one have a dated next step? Who’s waiting for whom?
  2. Stuck deals. Give them a next step, or close them.
  3. No next step. Same.
  4. What came in. Is anything worth moving up?

Skip the forecast meeting. The point is that the board is true when you close it.

What to measure, once there’s data

After about three months, three numbers tell you most of what you need:

  • Conversion from stage to stage, to see where deals fall out.
  • Time in each stage, to see where they wait.
  • Channel, to see which sources produce deals you win, rather than deals you open.

If you sell several products, look at them separately. A training day and an annual licence don’t move at the same speed, and averaging them hides both.

Common mistakes

  • Too many stages. If two people disagree on where a deal belongs, merge them.
  • Stages that depend on you alone. “Quote sent” is true even if the buyer never asked for it.
  • Never closing anything. A pipeline where nothing is ever lost is a wish list.
  • Copying a big company’s process. A ten-stage enterprise process on a two-person team mostly measures data entry.

Set it up on paper first, then in whatever tool you use. If you want to try it in Soldlyne, the stages and alerts are described here.

Related posts

What the Model Context Protocol lets an assistant do in your CRM, what to check before you connect one, and why what it can’t do matters as much as what it can.
A CRM is mostly personal data. The practical points for a small company: legal basis, how long to keep records, consent, rights requests and security. General information, not legal advice.
Before you compare feature lists, answer seven questions about who enters the data, how email gets in, where it lives and what it really costs. Then test on real deals.