Your deal pipeline should mirror how you actually sell, not how a sales consultant thinks you should sell. This guide shows you how to design pipeline stages that drive deals forward instead of creating busywork.
Why Most Pipelines Don't Work
You've probably seen (or built) a pipeline that looks like this: Prospecting → Qualification → Proposal → Negotiation → Closed Won/Lost. It's logical, sequential, and completely useless.
The problem? These stages describe what the rep is doing, not what the buyer is doing. Your pipeline should reflect buyer commitment, not sales activities. A deal moves forward when the buyer does something, not when you do something.
Good Pipeline: Stages named after buyer commitments ("Budget Approved," "Contract Under Review")
Pipeline Design Principles
1. Stages Should Represent Milestones, Not Activities
A stage change should mean something happened that moves the deal closer to closed. Sending an email isn't a milestone. Getting a meeting scheduled is.
Ask yourself: If I told my manager a deal moved to this stage, what would they assume happened? If the answer is unclear, the stage is poorly defined.
2. Each Stage Needs Clear Entry and Exit Criteria
Your team should know exactly what needs to happen for a deal to enter or leave a stage. No interpretation required.
- Entry: Demo scheduled with decision maker or champion
- Exit: Mutual understanding of problem, solution fit, and next steps documented
3. Keep It Simple: 5-7 Stages Maximum
More stages doesn't mean better visibility. It means more decisions your reps need to make, which means inconsistent data and deals stuck in the wrong stage.
If you need more granularity, use deal properties or tasks—not pipeline stages.
4. Pipeline Velocity > Number of Stages
The goal isn't to track every micro-step. The goal is to identify where deals stall and why. Fewer stages with clean data beats many stages with guesswork.
Sample Pipeline: B2B SaaS
This is a typical pipeline for B2B SaaS companies selling with an average deal cycle of 30-90 days.
What it means: Prospect has shown interest and is worth pursuing. Could be inbound lead, referral, or outbound response.
Entry criteria: Contact requested demo/info, responded to outreach, or was referred by customer/partner.
Sales action: Research company, confirm fit, schedule discovery call.
What it means: Having conversations to understand their problem, who's involved, and whether we can solve it.
Entry criteria: Discovery call scheduled.
Sales action: Understand pain points, stakeholders, budget, timeline, decision process. Confirm fit.
What it means: Showing them how we solve their specific problem. Tailored demo or proof of concept.
Entry criteria: Demo scheduled with key stakeholders (including at least one decision maker).
Sales action: Custom demo focused on their use case, answer technical questions, handle initial objections.
What it means: Formal proposal or quote has been delivered. Ball is in their court.
Entry criteria: Proposal sent with specific pricing, terms, and next steps.
Sales action: Follow up on questions, handle objections, negotiate terms if needed.
What it means: Deal is in their procurement/legal review. They've committed, now working through paperwork.
Entry criteria: Verbal commitment received, contract sent to their legal/procurement team.
Sales action: Work with their legal team on contract redlines, answer procurement questions, keep deal moving.
What it means: Contract signed, payment received (or committed), customer onboarding begins.
Required data: Close date, actual amount, win reason (dropdown: Better Fit, Pricing, Relationship, Other).
What it means: Deal is dead. Capture why so you can learn.
Required data: Close date, loss reason (dropdown: Budget, Chose Competitor, No Decision, Timing, Not a Fit, Other). Add notes on what competitor they chose or why they didn't move forward.
Sample Pipeline: Consulting / Services
For longer, relationship-based sales with custom scoping and larger contracts.
What it means: Prospect has reached out or responded. Relationship established.
Entry: Inbound inquiry, referral, or positive response to outreach.
Exit: Intro call scheduled to discuss their needs and our fit.
What it means: Understanding their situation, goals, constraints, and who's involved in the decision.
Entry: Discovery call scheduled with key stakeholder.
Exit: Clear understanding of project scope, budget range confirmed, and agreement to move to proposal phase.
What it means: Working on custom proposal, statement of work, or project plan.
Entry: They've requested a formal proposal with specific deliverables and pricing.
Exit: Proposal delivered and reviewed with stakeholders. Next step is their internal approval process.
What it means: They're interested but working through pricing, scope, or contract terms.
Entry: Proposal reviewed, they have questions or requested changes to scope/pricing/terms.
Exit: Agreement on final terms, moving to contract execution.
What it means: Final contract/MSA being reviewed and signed.
Entry: Final contract or SOW sent to client for signature.
Exit: Signed contract received, project start date confirmed (closed won).
Common Pipeline Mistakes
Mistake #1: Too Many Stages
Problem: You have 10+ stages trying to capture every nuance. Reps don't know which stage to use, so they guess or don't update deals at all.
Fix: Consolidate. Ask: "Does this stage require a fundamentally different action or represent a meaningful buyer commitment?" If not, merge it.
Mistake #2: Activity-Based Stages
Problem: Stages like "Sent Email," "Waiting for Response," "Called Prospect." These don't tell you anything about deal health.
Fix: Stages should reflect what the buyer did, not what you did. "Demo Scheduled" is buyer action. "Sent Demo Video" is your action.
Mistake #3: No Clear Exit Criteria
Problem: Reps ask "Should I move this to Proposal or Negotiation?" every week. Stages are subjective.
Fix: Document entry and exit criteria for every stage. Make it a checklist. When X happens, move to next stage.
Mistake #4: Optimistic Stage Movement
Problem: Reps move deals forward based on what they hope will happen, not what actually happened. "I think they'll sign next week" = moved to Contract Review prematurely.
Fix: Require proof. Can't move to Proposal stage without a proposal being sent. Can't move to Contract Review without a contract actually in review.
Mistake #5: One Pipeline for Multiple Deal Types
Problem: Trying to use the same pipeline for new business, renewals, and expansions. They have different buyer journeys.
Fix: Create separate pipelines for fundamentally different sales motions. Renewal pipeline might be: Up for Renewal → Proposal Sent → Closed Won/Churned.
Pipeline Health Metrics
Once your pipeline is set up, track these metrics to identify problems:
| Metric | What It Tells You | Red Flag |
|---|---|---|
| Conversion Rate by Stage | Where deals die in your process | Less than 30% from any stage to the next |
| Average Time in Stage | Where deals stall | Proposal stage taking 3x longer than expected |
| Stage Skipping | Whether reps follow the process | Deals jumping from Discovery to Contract Review |
| Deals Moving Backward | Process confusion or deal issues | More than 10% of deals move backwards |
| Stage Distribution | Pipeline balance | 80% of deals stuck in one stage |
Setting Up Stage Probabilities
Each stage should have a win probability that reflects historical close rates.
- New Opportunity: 10%
- Discovery: 20%
- Solution Presentation: 40%
- Proposal Sent: 60%
- Contract Review: 80%
- Closed Won: 100%
- Closed Lost: 0%
Use your actual historical data if you have it. These are starting points, not rules.
Pipeline Best Practices
- Review pipeline design quarterly—adjust stages as your sales process evolves
- Document entry/exit criteria in your CRM (use stage descriptions or help text)
- Require certain fields to move between stages (e.g., can't move to Proposal without a close date)
- Set up alerts for deals that haven't moved in 2x your average time in stage
- Track stage conversion rates monthly to spot where deals are getting stuck
- Train new reps on what each stage means (with real examples)
- Use deal rotation/reviews to ensure consistency in how stages are applied
Implementation Checklist
- Map your actual sales process (talk to your sales team, not a framework)
- Identify 5-7 key milestones that represent buyer progress
- Write clear entry and exit criteria for each stage
- Assign probabilities based on historical close rates by stage
- Document required fields for each stage transition
- Test with your team on 5 real deals before full rollout
- Train team on new pipeline (include examples of good and bad stage movement)
- Set up weekly pipeline review to catch issues early