Most sales pipelines use several stages such as prospecting, qualification, discovery, proposal, negotiation, close and post‑sale. The single design rule that makes them work is this: define every stage by a verifiable buyer milestone, not a rep task, and attach explicit entry and exit criteria you can check with a calendar invite, an email, or a signature rather than a gut feeling.
TL;DR:
- Verifiable buyer milestones should define each sales pipeline stage, with clear entry and exit criteria based on tangible actions like signatures or documented discussions.
- CRM fields must enforce these criteria, requiring documentation or buyer confirmation before progressing stages, which reduces subjective judgments and improves accuracy.
- Keep pipeline stages aligned with typical deal length, using fewer stages for quick cycles and more for complex enterprise deals, but avoid overcomplicating or merging stages without clear buyer decision points.
- Focus on pipeline metrics like velocity, stage conversion rate, and average deal size, calculated from verified opportunities, to achieve reliable revenue forecasting.
- Testing pipeline design against real deals and using automation tied to buyer actions ensures accuracy and prevents stage misclassification or stalled processes.
Table of Contents
- What are the canonical sales pipeline stages?
- Sales pipeline versus sales funnel: what each measures
- How do you write entry and exit criteria that actually hold up?
- How many stages should your pipeline actually have?
- Which metrics actually predict revenue?
- How do you build and test a custom pipeline?
- What pipeline design mistakes should you fix first?
- FlowLab in practice: turning buyer milestones into CRM evidence
- Why most pipeline rollouts stall, and how to avoid it
- Put stage evidence where your CRM can actually see it
- Sources
What are the canonical sales pipeline stages?
Each stage should describe something the buyer has done, not something a rep has attempted. That distinction sounds small. It changes how honestly your CRM reflects reality.
- Prospecting. A target account has been identified and a first outbound or inbound touch has happened. Exit criterion: the prospect responds and agrees to a conversation, evidenced by a calendar invite or a reply thread.
- Qualification. The buyer has confirmed a real problem, budget authority exists somewhere in the account, and timing is roughly known. Exit criterion: a named economic buyer or budget holder has been identified, not just a champion who “thinks” there’s money.
- Discovery. The buyer has walked you through their current process, constraints and success criteria in enough detail that you could brief a colleague on it without them. Exit criterion: a written summary of requirements has been shared back to the buyer and they haven’t corrected it.
- Proposal. A specific solution and price have been presented to the actual decision‑maker, not just the champion. Exit criterion: written acknowledgement of scope and cost, even an informal email saying “this looks right.”
- Negotiation. Terms, price, or contract language are actively being worked, with the buyer engaged in redlines or counter‑offers. Exit criterion: a legal or procurement contact has entered the thread.
- Close. Signature obtained, payment terms agreed. Exit criterion: signed agreement on file.
- Post‑sale / retention. Onboarding has started and the account is being tracked for renewal or expansion.
For a short B2B cycle, such as a $2,000 monthly tool, discovery and proposal often collapse into a single call. For an enterprise deal with a six‑figure contract, negotiation alone might span three internal stages, since buyers now perform the majority of their research without a rep in the room, which means the stages you can actually observe happen later and faster than they used to.
Sales pipeline versus sales funnel: what each measures
A pipeline tracks individual deals moving through buyer milestones towards a close. A funnel tracks aggregate volume dropping off at each awareness or conversion point, usually before a deal exists at all. Confuse the two and your forecasting breaks, because you’ll be averaging pre‑sales marketing metrics with post‑qualification sales metrics as though they measure the same thing.
Funnel metrics include visitor‑to‑lead conversion rate, cost per lead, and marketing‑qualified‑lead volume. Pipeline metrics include stage conversion rate, pipeline velocity, and average deal size, each tied to an identified, named opportunity. A multi‑channel funnel analysis sits upstream of your pipeline, feeding it qualified opportunities rather than raw traffic.
The practical fix: report funnel metrics up to the point a lead becomes a qualified opportunity, then switch entirely to pipeline metrics from qualification onward. Never blend a funnel conversion rate with a pipeline conversion rate in the same chart. They answer different questions for different audiences.
How do you write entry and exit criteria that actually hold up?
Vague stage names invite vague judgement calls. “Discovery” means something different to every rep unless you write down exactly what has to be true before a deal enters it and exactly what has to be true before it leaves.
Run the two‑rep test: hand your stage definitions to two different reps with the same deal file and ask them independently which stage it’s in. If they disagree, your criteria are too subjective. This single exercise catches more pipeline design flaws than any amount of manager review, because it exposes the words doing quiet interpretive work, like “engaged” or “interested.”
Three example checklists:
- Qualification exit criteria. Named budget holder identified; problem statement confirmed in writing; timeline within the next two quarters. All three, not two out of three.
- Proposal exit criteria. Pricing document sent to the decision‑maker directly (cc doesn’t count); a follow‑up meeting booked to discuss it; no outstanding “who else needs to see this” questions.
- Contract review exit criteria. Legal or procurement contact named in the CRM; redlines received at least once; internal signature authority confirmed on your side.
Enforce these with CRM fields rather than memory. A required field for “economic buyer name” that blocks stage progression until filled does more to keep a pipeline honest than any training session. Fields like “next scheduled action” and “last buyer‑initiated contact date” also flag stalled deals automatically, since designing stages around buyer commitments makes a pipeline far harder to game than one built around what a rep claims to have done.
Pro Tip: Make at least one exit criterion per stage something the buyer has to produce, such as a document, a reply, or a signature. Anything the rep alone can tick off will eventually get ticked off regardless of reality.
How many stages should your pipeline actually have?
There’s no universal number, but there is a workable rule of thumb tied to how long deals typically take to close.
For short cycles, roughly under a month, a few stages like qualify, demo or discovery, proposal, and close are usually sufficient. Adding more than that for a $500 monthly subscription just creates admin without adding forecasting precision. For mid‑market cycles running one to four months, multiple stages tend to fit, covering the canonical set outlined earlier with possible added splits.
Enterprise cycles of six months or more can justify several stages, but only if each additional stage represents a genuinely distinct buyer decision, such as security review or procurement sign‑off, rather than an internal rep milestone dressed up as a pipeline stage. The right stage count is calibrated to your average sales cycle length; too many stages for a short cycle causes reps to skip updating the CRM altogether, which is worse for forecasting than having too few.
Start smaller than you think you need. Split a stage later once you have real deal data showing it hides two distinct buyer behaviours, rather than guessing upfront.
Which metrics actually predict revenue?
Three numbers do most of the forecasting work once your stages are defined by verifiable milestones rather than rep activity.
Pipeline velocity measures how fast deals move through the whole pipeline and is calculated as (number of qualified opportunities × average deal value × win rate) ÷ average sales cycle length in days. A rising velocity number with a flat headcount usually means your qualification criteria have tightened, which is a good sign, not a red flag to investigate.
Stage conversion rate is the percentage of deals that exit one stage and enter the next. Track it stage by stage rather than as a single top‑to‑bottom figure, because a healthy overall conversion rate can hide one stage quietly leaking 60% of deals.
Average deal size should be tracked by segment, not blended across your whole book, since a single enterprise deal can distort the mean for an entire quarter.
Recommended reports to build in your CRM:
- Stage conversion rate by rep and by stage, refreshed weekly.
- Time‑in‑stage distribution, flagging deals sitting past twice the median.
- Win probability derived from your own historical close rates by stage, not CRM defaults.
Managing a pipeline without stage‑based entry and exit criteria leaves managers relying on optimism rather than evidence, because none of these three numbers mean anything if “qualified” or “proposal” can mean five different things depending on who logged the deal.
How do you build and test a custom pipeline?
Design your pipeline backwards from deals you’ve already won, then check it against deals you’ve already lost.
- Pull five to ten closed‑won deals and map, in order, the actual buyer actions that happened before signature: who asked for pricing, who introduced legal, who confirmed budget. This becomes your stage list.
- Write entry and exit criteria for each stage using the two‑rep test above, and map each criterion to a specific CRM field, such as “economic buyer name” or “redline received date.”
- Configure automation on stage transition, not on a timer. When a deal moves to proposal, trigger a task for the rep and a notification to their manager. Timer‑based automation just adds noise; transition‑based automation tied to actual buyer milestones keeps the noise down.
- Run a historical test sample. Take 10 to 20 closed deals, both won and lost, and manually walk them through your new stage definitions. Where criteria don’t fit or feel unrealistic, this test against historical deals is exactly where you’ll find it before it costs you a live quarter of bad data.
Pro Tip: Test with lost deals as deliberately as won ones. A stage design that only ever gets validated against wins will look fine right up until it fails to explain why deals actually die.
What pipeline design mistakes should you fix first?
Activity‑based stage names are the most common flaw, and the easiest to spot in an audit. “Proposal sent” describes a rep action, not a buyer commitment, so rename it to “proposal acknowledged by decision‑maker” and it immediately becomes harder to fake. The same applies to “demo scheduled,” which should become “demo completed with named stakeholders.”
A few other patterns worth checking in your own pipeline:
- Too many stages for the cycle length. Teams running five to seven stages tend to see higher CRM update compliance than those running eight or more on short cycles, because reps simply stop logging updates once the admin outweighs the value.
- No closed‑lost taxonomy. If every lost deal gets tagged “no budget,” you learn nothing. Build a taxonomy that maps to stage failure, such as “lost at proposal, no economic buyer engaged” versus “lost at negotiation, price.”
- Subjective criteria surviving the two‑rep test failure. If reps still disagree on stage placement after a criteria rewrite, the fix is often a “parking” stage for deals that have gone quiet, rather than forcing them to sit dishonestly in an active stage.
- Merging too aggressively. Two stages should only merge if no distinct buyer milestone separates them; don’t merge for the sake of a shorter list.
FlowLab in practice: turning buyer milestones into CRM evidence
Stage discipline only works if the evidence is actually captured somewhere reps can’t quietly skip. LeadsFlow assigns every enquiry an owner and a next move the moment it lands, which closes the most common gap in pipeline audits: deals sitting in a stage with no recorded action and no accountable person.
For the commercial stages, particularly proposal and close, running a sample sale from product to payment through POSFlow gives you a concrete, checkable business case rather than a verbal assurance that “the buyer’s keen.” It’s the kind of stage evidence a two‑rep test would actually pass.
Ronald’s view on rollout governance follows below, alongside where FlowLab’s demos and free app fit review into piloting this.
Why most pipeline rollouts stall, and how to avoid it
Get manager sign‑off before you touch the CRM, not after. Reps follow stage discipline when their manager reviews deals against the new criteria weekly, not when it’s announced once in a meeting and left to chance. Train on the two‑rep test itself, not just the finished stage list, so reps understand why each criterion exists.
Pilot with one team and 20 to 30 live deals before a company‑wide rollout. A small, measurable pilot surfaces criteria that sound sensible on paper but don’t survive contact with a real negotiation. Run a weekly deal review against the exit criteria, not against gut feel on “how it’s going.”
— Ronald
Put stage evidence where your CRM can actually see it
Most pipeline audits fail for the same reason: the criteria look fine on a slide, but nobody captures the evidence that would prove a deal genuinely earned its stage. There are products that plug that gap directly, without asking you to rebuild your CRM from scratch or sign up for a lengthy commitment.
LeadsFlow gives every enquiry an owner and a next move from the moment it arrives, so “qualification” stops being a guess and starts being a logged fact. POSFlow lets you run a sample sale from product through to payment, generating the kind of verifiable business case evidence a proposal or close stage actually needs. They are built for SMEs that want stage discipline without a six‑month implementation project.
If you’re not sure which one fits your current pipeline gaps, Flowlab’s complimentary app fit review will tell you plainly, including where a ready‑made product is enough and where it isn’t. Book a demo and see the sample sale run end to end before committing to anything.
Sources
For deeper detail on stage calibration and CRM implementation, see Rework’s guide to pipeline stages and 6sense’s research on B2B buying behaviour.