The standard answer is 7 sales pipeline stages, with a note that 5 to 7 is typical. That leaves the real question open. How many should you build if you are the founder, the rep and the person checking the numbers? This post answers it.
Sales pipeline stages are the steps a deal moves through: prospecting, qualification, meeting, proposal, negotiation, closed won or lost and post-sale. Most guides teach all 7. A solo founder needs 4, a team of 2 to 3 needs 5 and a team of 4 to 10 needs 6 or 7.
What Sales Pipeline Stages Are and How They Work
Sales pipeline stages are the named steps a deal passes through, from the first conversation to signed and paid. Each stage is a state the deal is in, not a task you have to do. A deal sits in one stage at a time and it moves when something real changes.
That last part is where small pipelines go wrong. A stage is not a folder for your intentions. If a deal has been parked in “Follow up” for 3 weeks, the stage is not telling you anything you didn’t already know.
Pipeline and funnel get used as if they mean the same thing. A funnel counts volume across a whole audience, like 10,000 visitors turning into 40 leads. A pipeline tracks named deals you are working right now, each with a next step attached. The funnel tells you how many. The pipeline tells you who, and what you owe them next.
The 7 Sales Pipeline Stages in Order
One rule before the list. A deal leaves a stage when the buyer does something, not when you do. Sending a proposal is your action, so it doesn’t move the deal on its own. The buyer coming back with questions about the price is their action, and that moves it.
Stages describe what has already happened. The steps you take inside each one are your sales process, and mixing the two is how a pipeline turns into a to-do list.
1. Prospecting
You have a name, a company and a reason to reach out, but no reply yet. Cold email, LinkedIn, referrals and inbound forms all land here. Everything upstream of this stage is your pipeline generation strategy, which decides how many deals ever reach the second one.
The deal leaves when the buyer replies, books a call or fills in your form. A send is not an exit. The most common mistake here is counting every cold email as a deal, which inflates your pipeline with people who have never answered you.
2. Lead qualification
The buyer answered and now you find out if there’s a real deal. You’re checking 3 things: they have the problem you solve, they can pay for it and they can either decide or walk you to the person who can.
The deal leaves when the buyer confirms the problem is real and tells you who signs off. If they won’t answer either question, they’re not qualified, they’re polite.
3. Meeting or demo
A call is booked or has happened, and the conversation is now about fit instead of curiosity. For most small B2B teams this is one call, not a 3-call discovery sequence.
The deal leaves when the buyer asks what it costs, asks for a proposal or agrees to a next call with a date on it. “That was great, I’ll get back to you” is not an exit. It’s the same stage with a friendlier tone.
4. Proposal sent
The buyer has a written offer with a price on it. A 1-page email counts. So does a 12-page document with a scope table, because the stage is about what the buyer is holding, not how much work you put into it.
The deal leaves when they respond with a yes, a no or something to negotiate. Silence is not a stage. How long you chase before calling it lost is a follow-up question, not a stage question. If a deal has been sitting here longer than your normal close time, it belongs in lost or in a revisit stage with a date on it.
5. Negotiation and commitment
The buyer wants the thing and is working out terms, scope, start date or who signs. Small teams often skip naming this one, then lose the ability to tell a stuck deal apart from a nearly-done deal.
The deal leaves on verbal commitment or a signature. Procurement, legal review and “let me run it past my business partner” all live in here.
6. Closed won or closed lost
The deal is over, one way or the other. Both outcomes belong in the pipeline, because the lost ones are the only free research you get about your own selling.
Most CRMs treat won and lost as outcomes you mark rather than stages you drag a deal into, which is why a 4-stage pipeline is still a complete pipeline. Write the reason on every loss in 2 or 3 words. “Price” is usually not the real reason.
7. Post-sale and repeat business
The deal is won and, for a service business, the next sale is often to the same client. Delivery, onboarding, renewal and the second project all sit in this stage. Models that stop at closed won assume you sell to a stranger once and never speak again.
The deal leaves when the client buys again, refers someone or goes quiet long enough that they’re back in prospecting. If repeat work is most of your revenue, this stage is not optional.
How Many Pipeline Stages Do You Actually Need?
Here’s what I’d run at each team size. This is my recommendation from 3 years of B2B outbound work and the pipelines I’ve had to look at, not a study, and there’s no research sitting behind the numbers.
The rule under all 3 versions is the same. A stage earns its place if it changes what you do next. If it doesn’t, it’s a label you now have to maintain forever.
Solo founder: 4 stages
New, Contacted, Meeting booked, Proposal sent.
You know your deals by name at this size, so a 7-stage pipeline gives you 3 extra drag-and-drops per deal and hands nothing back. Build 4, keep them accurate daily and add a fifth when you can name the question it answers.
2 to 3 people: 5 stages
New, Contacted, Qualified and handed off, Meeting booked, Proposal sent.
The fifth stage exists because the person making the first call is often not the person who closes. Role separation is what creates a new stage, not deal volume, and it shows up at 3 people rather than at 10.
4 to 10 people: 6 to 7 stages
New, Contacted, Qualified and handed off, Meeting booked, Proposal sent, Negotiation, then Post-sale if you sell repeat work.
At this size someone is looking at conversion between stages every week and that person needs to see where deals get stuck. It’s also the size where a stage nobody updates starts costing money, because the forecast is built on top of it.
Why Fewer Pipeline Stages Usually Work Better
Pipeline stages exist so someone can measure the drop between them. That’s the whole job. If nobody looks at how many deals go from Meeting booked to Proposal sent, then Meeting booked is admin with no payoff and you’ll quietly stop updating it.
In 3 years running outbound at Fenixtal I worked with 50+ B2B companies, from marketing agencies to construction firms and e-learning companies. Most of them didn’t have clear pipeline stages defined at all. Not too many stages, none. Deals were either in a spreadsheet with a “status” column somebody filled in from memory, or in a CRM carrying the default stages nobody had touched since setup.
That’s the part most guides miss. The failure mode isn’t a team that built 7 stages and drowned in them. It’s a team that never defined any, then copied a 7-stage template when they finally tried, and stopped updating it inside a month.
So my bias is fewer stages, and it is a bias rather than a finding. Fewer stages are cleaner to look at, quicker to update and less work to hold in your head. A 4-stage pipeline you trust beats a 7-stage one you avoid.
Stop for a second. Can you say what share of your proposals closed last quarter without opening anything? If you can’t, a seventh stage won’t tell you either. The stage count isn’t the problem, the measuring is.
If you want to know what your current stages are worth, a pipeline calculator does the math in a minute and a forecasting calculator tells you what’s likely to land this quarter. A quota calculator works backwards from the number you need and tells you how many deals belong in the top stage.
An unupdated pipeline is worse than a short one because it lies with confidence. 4 stages that match reality beat 7 that describe last month.
How to Name Pipeline Stages So the Whole Team Uses Them
Pipeline stage names should describe what the buyer did, not how you feel about the deal. That one rule kills most of the bad names. If 2 people on your team would file the same deal in different stages, the name is broken.
The 2 most common stage names in small-team CRMs are “Interested” and “In progress” and neither one survives that test.
| Weak stage name | Why it fails | Strong stage name |
|---|---|---|
| Interested | Everyone in the pipeline is interested. It never says what happened | Replied to outreach |
| In progress | Progress toward what? Every open deal is in progress | Meeting booked |
| Follow up | It’s a task, not a state. All deals need a follow-up | Proposal sent |
| Hot lead | Your feeling about the deal, not something the buyer did | Asked for pricing |
| Nurture | Where deals go to die quietly, with no date attached | Revisit in Q4 |
Read your stage names out loud and ask what the next action is. “Proposal sent” tells you to chase a decision. “Hot lead” tells you nothing you can act on at 9am on a Tuesday.
The Stage Most Small Team Pipelines Are Missing
Handoff is the stage missing from almost every pipeline model, including the 7 above. It’s the moment a rep finishes a call and the deal moves to whoever does the next thing, and it appears the second a solo pipeline becomes a 2-person pipeline.
Michal Pliszka runs an advertising agency in Poland with a small cold calling team, himself plus 2 employees. The setup he described came down to one move. After a call, an employee would “assign the contact to me with a note” saying what came next, like sending an offer or calling back the following week.
None of the textbook models have a name for that moment. The deal isn’t in Meeting booked any more because the meeting happened, and it isn’t in Proposal sent either because nobody has sent one. Without a stage for the gap, the deal sits where the caller left it while both people assume the other one is handling it.
If 2 or more people touch the same deal, add the stage. Call it “Qualified and handed off” or “Ready for offer” and put an owner on it. The name tells both people whose turn it is, which is the only thing a stage really has to do.
How to Set Up Your Pipeline Stages in a CRM
Setting up pipeline stages is a short job when you do it in this order. The work is in the deciding, not the clicking. If you are still picking the rest of your stack, my sales tool list covers what is worth paying for early.
Step 1: List your last 20 closed deals
Open wherever your deals live and look at the last 20 that closed, won or lost. Write down the steps they actually moved through, not the template steps you meant to use. Patterns show up fast and you’ll usually find fewer real steps than you expected.
Step 2: Write each stage as a buyer action
Turn every step into something the buyer did. “Replied,” “Booked a call,” “Asked for pricing,” “Sent back terms.” If you can’t write a stage as a buyer action, it’s probably a task, and tasks belong in reminders or notes instead of on your board.
Step 3: Cut the list to your team size
Use the counts from earlier: 4 solo, 5 at 2 to 3 people, 6 to 7 at 4 to 10. If you’re over, merge the stages nobody measures. Two stages that always get updated on the same day are really one stage.
Step 4: Give every stage an exit rule
Write one line per stage saying what moves a deal out of it, then keep that list where the team can see it. This is the part that stops 2 people from filing the same deal differently, and it’s the difference between stages that hold and stages that drift.
Fluid CRM includes unlimited pipelines on both plans, so you can build the short version now and add a second pipeline later if you sell something that runs on different stages. Reminders sit on the deals themselves, which is what keeps a 4-stage pipeline honest.
Frequently Asked Questions
4 to 7, depending on how many people touch a deal. A solo founder does fine with 4, a team of 2 to 3 needs a fifth for the handoff and a team of 4 to 10 with someone watching conversion can use 6 or 7. Stages added past the point where someone measures them are admin.
A funnel measures volume across a whole audience, like how many visitors turn into leads. A pipeline tracks named deals you’re working right now, each one sitting in a stage with a next step. Funnels are for marketing math. Pipelines are for deciding who to call today.
Yes, and in small teams that’s the more common problem. Each extra stage is another thing to keep current, and a stage nobody updates makes the pipeline look accurate when it isn’t. If you can’t say what decision a stage changes, delete it and move those deals into the stage before it.
Most CRMs handle won and lost as outcomes you mark on a deal rather than stages you drag it into, so you don’t need to spend a stage slot on either. Recording why you lost matters more, in 2 or 3 words. Those notes are the cheapest sales research you’ll ever get.
No. A spreadsheet with a stage column works while you’re solo with a handful of deals. It breaks when a second person needs the same view or when you start missing follow-ups, because a sheet doesn’t remind you of anything. That’s the point where stages turn into a pipeline instead of a list. The tools that handle this for small teams are compared here.
Conclusion
Build the shortest pipeline that tells you what to do next, then add a stage only when you can name the question it answers. If your stages came from a template and you’ve stopped trusting them, Fluid CRM gives you a clear visual pipeline you can set up in minutes and keep updated.
Start your 7-day free trial here, no credit card required.