Nov 9, 2026
12 min read
B2B Sales Pipeline Stages: How to Define Yours
A B2B sales pipeline stage is a defined step in your buyer's journey that a deal enters only when specific, verifiable criteria are met. To define yours, work backwards from deals you have already won. Identify the commitments your buyers actually made along the way, then turn each one into a stage with clear exit criteria, a realistic win probability, and a maximum time limit. Most small and mid-sized B2B teams do best with five to seven stages, named for what the buyer has done rather than what the seller has done.
That sounds simple. In practice, most pipelines I review are a mix of default CRM labels, wishful thinking, and stages nobody on the team could define the same way twice. When I ask three reps what "Qualified" means, I often get three different answers. Then the forecast is wrong, the pipeline review turns into storytelling, and the founder starts doubting the team. This article walks through how to build pipeline stages that reflect reality, using a sample structure you can adapt and a step-by-step process for making it your own.
What is a pipeline stage, really?
A pipeline stage is not a description of activity. "Demo done" tells you what your rep did. It tells you nothing about whether the buyer is any closer to signing.
A good stage describes a change in the buyer's commitment. Moving a deal forward should require evidence that the customer has done something: confirmed a problem, introduced a decision-maker, shared a budget range, agreed to a timeline, or asked for a contract. Each of these is a small "yes" from the buyer, and those small yeses are what predict revenue.
This distinction matters because activity is easy to fake and commitment is not. A rep can run ten demos in a week and move ten deals to Stage 3. If none of those buyers agreed to a next step, the pipeline looks healthy but contains very little real revenue.
Why do default pipeline stages fail?
Most CRMs ship with a generic set of stages, something like "Appointment Scheduled, Qualified to Buy, Presentation Scheduled, Decision Maker Bought-In, Contract Sent, Closed Won, Closed Lost." Teams adopt them on day one and never revisit them. Here is why that causes problems:
- They do not match your sales motion. A company selling a 5,000 EUR/year SaaS tool to startups has a very different buying process from a company selling a six-figure software implementation to a manufacturing group. The same stages cannot describe both.
- They have no exit criteria. Without written rules, reps move deals forward based on gut feeling. Optimistic reps inflate the pipeline and cautious reps hide deals.
- Probabilities are made up. Default win percentages are placeholders, not your data. Forecasting on them means forecasting on fiction.
- They ignore time. A deal that has sat in "Proposal" for 90 days is not the same as one that entered yesterday, but most pipelines treat them identically.
If you are still choosing your system, setup flexibility should be part of the decision. I cover this in my guide on how to choose a CRM for a small sales team.
How many stages should your pipeline have?
For most B2B teams, the answer is five to seven active stages, plus Closed Won and Closed Lost.
With fewer than five, each stage covers too much ground. You can't tell where deals are stalling. With more than eight, reps stop updating the CRM because the distinctions feel artificial, and you end up with stages that contain one or two deals each.
A useful test: every stage should have a different next action for the rep and a different conversation in the pipeline review. If two stages trigger the same action, merge them. If one stage contains deals that need very different handling, split it.
A sample B2B pipeline you can adapt
Below is a structure I find works well for B2B companies with an average deal size between a few thousand and a few hundred thousand euros and a sales cycle of one to six months. Treat it as a starting point, not a template to copy blindly. The probabilities shown are illustrative. Yours should come from your own closed deals.
Stage 1: Meeting booked
Entry criteria: A prospect from your target account list has agreed to a first call with a confirmed date and time.
Exit criteria: The discovery call happened and you have documented the prospect's situation.
Some teams keep this stage outside the opportunity pipeline and track it as an SDR or outbound metric instead. That is a reasonable choice, especially if you book a high volume of first meetings. If your outbound team builds target lists from contact databases such as Apollo.io, keeping meeting-booked separate stops top-of-funnel volume from distorting your revenue pipeline.
Stage 2: Discovery completed
Exit criteria:
- The buyer has confirmed a specific problem in their own words.
- You know who else is involved in the decision.
- The buyer agreed to a next meeting with a date on the calendar.
Note the last point. A deal without a scheduled next step is not progressing, no matter how good the call felt.
Stage 3: Qualified
Exit criteria:
- The problem is significant enough that the buyer has a reason to act this quarter or next.
- A budget range has been discussed, even roughly.
- You have spoken to, or have a committed path to, the person who signs.
- The buyer's timeline is known.
You can use BANT, MEDDIC, or your own framework here. What matters is that "qualified" is a checklist, not an opinion.
Stage 4: Solution validated
Exit criteria:
- The buyer has seen a demo, pilot, or tailored walkthrough.
- Key stakeholders have confirmed the solution fits their requirements.
- Any technical, legal, or security review has started.
Stage 5: Proposal sent
Exit criteria:
- A written proposal with pricing has been delivered.
- The buyer has walked through it with you live, not just received it by email.
- Objections and open questions are documented.
A proposal emailed into silence should not count as progress. If you want to improve this stage, my article on writing a B2B sales proposal that gets signed goes deeper.
Stage 6: Negotiation and commit
Exit criteria:
- The buyer has verbally confirmed they intend to proceed.
- Commercial terms are being finalized.
- Procurement or legal is reviewing the contract.
- A target signature date is agreed.
Closed Won / Closed Lost
Closed Won means a signed contract, or a purchase order if that is how your customers buy. A verbal yes doesn't count. Closed Lost should always include a mandatory loss reason from a fixed list, such as: no budget, chose competitor, no decision / status quo, bad timing, poor fit, or lost contact. Over time, these reasons become some of the most valuable data you own.
How do you define your own pipeline stages? A step-by-step process
Here is the process I use when helping a team rebuild its pipeline from scratch.
- Pull your last 15–30 won deals. If you are early-stage and have fewer, use what you have and plan to revise later. For each deal, write down every meaningful buyer action from first contact to signature: the first reply, the first meeting, when a second stakeholder joined, when budget came up, when legal got involved.
- Look for the common milestones. You will usually see four to seven moments that appear in almost every won deal. For example, you may notice that every deal you closed included a call with the finance lead before the proposal. That moment deserves to be a stage, or at least an exit criterion.
- Do the same for 15–30 lost deals. Find where they stalled. If most losses died between demo and proposal, that transition needs stricter criteria. You may be advancing deals that were never really qualified.
- Write exit criteria as verifiable evidence. Every criterion should pass this test: could a manager confirm it by looking at the CRM record, an email, or a call recording? "Buyer is interested" fails. "Buyer introduced us to the IT lead by email" passes.
- Name stages after buyer outcomes. "Solution validated" is better than "Demo." "Commit" is better than "Closing." The name should remind the rep what the buyer needs to have done.
- Calculate stage probabilities from your history. Take every deal that reached a given stage over the past 6–12 months and see what share eventually closed. If 40 deals reached "Proposal sent" and 14 closed, that stage's historical probability is 35%. If you lack the data, start with conservative estimates and replace them after one or two quarters. My guide on forecasting sales revenue for a small B2B team explains how to turn these numbers into a forecast you can defend.
- Set a maximum age for each stage. Look at how long won deals typically spent in each stage. If won deals usually spend 10–20 days in "Qualified," set a flag at around 30 days. Deals past the limit get reviewed and are either advanced with evidence, pushed back, or closed lost.
- Document everything in one page. Stage name, definition, entry criteria, exit criteria, probability, maximum age, and the rep's typical next action. Put it in your sales playbook and make it the first thing new hires learn.
- Run it for one quarter, then revise. Your first version will be wrong in small ways. After 90 days, review which stages are bottlenecks, which criteria reps find confusing, and whether probabilities match outcomes.
How do you know if your pipeline stages are working?
Once the stages are live, track a handful of metrics monthly:
- Stage-to-stage conversion rate. What percentage of deals move from each stage to the next? A sharp drop shows you where deals die.
- Average time in stage. If deals in "Proposal sent" are taking twice as long as last quarter, something has changed, whether in pricing, competition, or buyer behavior.
- Deal aging. How many open deals are past the maximum age for their stage? A pipeline full of old deals overstates your future revenue.
- Stage skipping. Are deals jumping from "Discovery" to "Proposal"? Occasionally that is legitimate, but if it happens often, your criteria are being ignored.
- Forecast accuracy. Compare your stage-weighted forecast with actual closed revenue each month. If the gap narrows over time, your stages are getting more honest.
These numbers are also the backbone of a good weekly meeting. Instead of asking reps "how's it going?", you can ask "this deal has been in Qualified for 41 days, so what's blocking it?" I describe this format in how to run a weekly pipeline review that works.
What are the most common mistakes when defining pipeline stages?
- Building stages around your internal process instead of the buyer's. "Sent to solutions engineer" is your workflow, not a buyer milestone.
- Letting reps self-certify progress without evidence. Stages only work if exit criteria are enforced, at least through spot checks in reviews.
- Using the same pipeline for very different motions. If you sell both small self-serve upgrades and large enterprise contracts, consider two pipelines. Mixing them blends conversion rates and makes both forecasts worse.
- Never closing deals out. Many teams avoid marking deals as lost because it feels like failure. A dead deal sitting in the pipeline is worse. It misleads the forecast and wastes rep attention.
- Tying commissions to stage movement. Paying or praising reps for moving deals forward, rather than for closing, encourages inflation. Keep incentives tied to signed revenue.
Does the pipeline need to change for markets like Turkey?
The principles stay the same, but local buying behavior often shifts where the stages fall. In Turkey, and in many relationship-driven markets, I've seen a few patterns worth building into your stages:
- Relationships often come before qualification. Buyers may want a face-to-face meeting or a longer introductory conversation before discussing budget. Your "Discovery" stage may need more room, and your criteria should reflect that budget comes up later than it might with a US buyer.
- Decision-making can be highly centralized. In family-owned companies and holding structures, the real decision-maker is frequently a senior owner or board member. A "path to the signer" criterion is especially important here.
- Negotiation is expected. Price discussions in the final stage are normal, not a sign of a dying deal. Make sure your "Negotiation" stage has enough time budgeted, and prepare your reps to handle it well.
- Currency and payment terms matter. For cross-border deals, pricing currency and payment schedules often become their own discussion late in the process. Consider adding them as an explicit exit criterion before "Commit."
If you sell into multiple regions, compare stage durations by market. You may find that the same stage reliably takes longer in one country than another. That is useful for forecasting, not a problem to fix.
FAQ
What is the difference between a sales pipeline and a sales funnel?
A sales funnel usually describes the buyer's journey in aggregate, showing how many leads become opportunities and how many become customers. A sales pipeline tracks individual deals through defined stages, with values, owners, and next steps. The funnel is a marketing and planning view, while the pipeline is the operating tool sales teams use every day.
Should every deal pass through every stage?
Ideally, yes, because each stage represents a buyer commitment that predicts closing. Occasionally a deal moves quickly, for example with an inbound buyer who arrives already qualified. In that case, the rep should still confirm that each stage's criteria were met rather than simply skipping ahead.
How often should we update our pipeline stages?
Review stage definitions and probabilities once per quarter in the first year, then twice a year once they stabilize. Revisit them sooner if you change your product, pricing, target market, or sales motion, since any of these can shift how buyers move through the process.
Who should own the pipeline stage definitions?
The head of sales, or the founder in early-stage companies, should own the definitions. Reps who actually work the deals should have input. When the team helps write the criteria, they understand them better and are far more likely to follow them consistently.
Conclusion
Well-defined pipeline stages turn your CRM from a list of hopes into an honest picture of your business. The process is not complicated. Study the deals you have won and lost, identify the buyer commitments that matter, write exit criteria anyone can verify, and base your probabilities on real outcomes instead of defaults. Then run it for a quarter, measure where deals stall, and refine.
The payoff is more accurate forecasts, sharper coaching conversations, and earlier warning when a deal or a whole segment starts to slip. If you are rebuilding your pipeline or setting up a sales process for a growing B2B team and want a second opinion, feel free to [get in touch with me](/). I'm always happy to talk sales.