Sales Process
Most CRM pipeline stages are vague labels that mean different things to different reps. Without entry and exit criteria, stage advancement is based on optimism — not evidence. Here's how to build stages that actually predict revenue.
Every stage needs two things: a clear entry point that defines when a deal belongs here, and an exit criterion that defines when it moves forward.
Entry: A company matching your ICP has been identified from a list, inbound lead, referral, or research. Exit: A specific contact has been identified and initial outreach has been sent. This stage is about volume — the goal is to move qualified targets into active outreach quickly, not to spend time on accounts that will never convert. Most founders let too many accounts linger here because there's no exit criterion forcing a next action.
Entry: Outreach has been sent (email, LinkedIn, referral introduction). Exit: A two-way conversation has started — the prospect has responded and expressed enough interest to schedule a discovery call. This stage separates volume from engagement. The key metric is response rate by channel and sequence. Without a clear exit criterion, reps often count any response as progress — including 'not interested' replies that should move to disqualified.
Entry: Discovery call has been scheduled and confirmed. Exit: You've confirmed the prospect has the problem you solve, the budget range to act, a timeline that makes the opportunity real, and a decision-making process you understand. This is the most important qualification stage. Moving an unqualified prospect past discovery wastes proposal time and distorts your pipeline forecast. Define the minimum qualification bar explicitly — and stick to it.
Entry: Qualified prospect has agreed to a presentation or demo. Exit: Prospect has provided substantive feedback on the presentation — questions about scope, pricing, timeline, or implementation indicate real evaluation. Radio silence after a presentation is not an exit to the next stage. This stage is where deals often stall because 'sent the deck' is treated as progress. True exit requires a two-way conversation about the solution, not just delivery of materials.
Entry: Prospect has requested a proposal or pricing conversation has begun. Exit: Written proposal has been reviewed and prospect has communicated their position — moving forward, requesting revisions, or declining. Many teams treat 'proposal sent' as a pipeline milestone, but a sent proposal with no response is worth nothing. The exit criterion is the prospect's explicit response. Deals that sit in this stage for more than two weeks without a response should be escalated or moved to at-risk.
Entry: Prospect has communicated a final decision. Exit: Contract signed and payment terms agreed (Closed Won), or opportunity formally disqualified with a recorded loss reason (Closed Lost). The Closed Lost stage is as important as Closed Won — loss reason data is the input to your win/loss analysis and the foundation of pipeline improvement. If you're not capturing loss reason consistently, you're flying blind on which objections to address and which competitor narratives to counter.
Pipeline stages are the backbone of sales forecast accuracy — and most companies set them up once, never revisit them, and wonder why their quarterly forecast is consistently wrong. The issue is almost never that reps are sandbagging or over-optimistic by nature. It's that the stages themselves don't enforce rigor. When 'Discovery' just means 'we had a call,' any call qualifies — including calls where the prospect showed no real interest. When stages are criteria-based, only qualified conversations count as Discovery, and the pipeline becomes a reliable predictor of revenue.
Well-defined pipeline stages also reveal where deals are dying. If 70% of your deals stall between Discovery and Proposal, the bottleneck is your qualification process or your presentation. If 60% stall between Proposal and Close, the bottleneck is your commercial conversation or your objection handling. Stage data is diagnostic data — but only if the stages mean something consistent across your team. See how pipeline stages affect your sales velocity →
The difference between a pipeline that predicts revenue and one that misleads you is in the rigor of your stage definitions.
Stages are named generically — 'Prospect,' 'Proposal,' 'Negotiation' — with no entry or exit criteria
Each stage has a defined entry criterion and an explicit exit action the rep must complete
Reps self-report stage — deals move forward based on optimism, not evidence
Stage advancement requires documented evidence: a response, a scheduled meeting, a signed document
Pipeline forecast is based on stage names — 'Proposal' = 40% close probability regardless of context
Close probability is calibrated against historical data — 'Proposal' closes at 28% based on actual outcomes
Deals sit in stages for months with no activity — pipeline is inflated with zombie opportunities
Each stage has a maximum time threshold — stalled deals are flagged and reviewed weekly
Loss reasons are not captured — 'lost' is an outcome, not a data point
Loss reasons are recorded at close — data feeds win/loss analysis and objection handling improvement
Pipeline reviews are subjective — forecast accuracy is consistently poor
Pipeline reviews are stage-criteria-based — forecast accuracy improves each quarter as patterns emerge
These patterns show up in almost every company that hasn't revisited their pipeline structure since initial CRM setup.
Your reps describe the same deal at different stages depending on who you ask
Deals sit in "Proposal Sent" for 30+ days with no follow-up action recorded
Your pipeline forecast has been wrong by more than 20% for three or more quarters in a row
You don't capture loss reason consistently — you know you lost, not why
New reps take 6+ months to understand how your pipeline stages work because they're not documented
Stage names in your CRM were set up years ago and nobody has reviewed whether they reflect how you actually sell
I'm Louie Bernstein — I have 50 years in business experience, including 22 as a bootstrapped founder. My Fractional Sales Leadership business has been helping founders since 2017.
Redefining pipeline stages is one of the highest-leverage interventions I make in almost every engagement. When a team starts using consistent, criteria-based stages, forecast accuracy typically improves within 60 days — not because the pipeline got better overnight, but because the data becomes honest. You can see where deals are actually dying, how long each stage takes, and which reps are moving deals forward vs. keeping them warm. That visibility changes everything.
Most $1M–$10M B2B companies operate well with 5–7 defined stages. Fewer than 5 and the stages become too broad to be useful — 'In Progress' tells you nothing. More than 7 and the stages become bureaucratic and reps stop updating them accurately. The right number is whatever reflects the distinct decision points in your actual sales process: the moment a prospect becomes a real conversation, the moment they become qualified, the moment a commercial discussion begins, and the moment a final decision is made. Count your decision points — that's your stage count.
A pipeline stage represents where the buyer is in the decision process — it's a status. A sales activity is something the rep does — it's an action. 'Discovery call scheduled' is an activity. 'Discovery completed with qualification confirmed' is a stage. The confusion between stages and activities is one of the most common CRM setup mistakes. When reps move deals forward based on activities (sent the email, made the call) rather than buyer-side outcomes (responded, agreed, committed), the pipeline loses its predictive value entirely.
The answer is exit criteria, not motivation. If a rep can advance a deal by self-reporting, they'll advance it based on optimism. If a deal can only move to 'Proposal' when a written proposal has been sent and a response has been received, then stage advancement is tied to a verifiable event — not a judgment call. Build exit criteria into your CRM as required fields or activity triggers. Review stage progression in weekly pipeline calls. Inspect the criteria, not just the stage name. Consistency follows accountability, and accountability requires criteria.
Not necessarily. If you sell to enterprise buyers with procurement processes and also sell to small businesses with a one-call close, forcing both into the same pipeline stages will distort your forecast and frustrate your reps. The right approach is to align stages to decision-making process, not product line. If your SMB deals move from discovery to close in two weeks and your enterprise deals require a pilot and a committee review, those are different sales motions and deserve different pipeline structures. Most CRMs support multiple pipelines — use them.
In 30 minutes I can audit your current pipeline stages, identify where your forecast is breaking down, and give you a criteria-based stage framework your team will actually use.