Fix Your Broken Sales Pipeline Stages

Q: How many deal stages should we have?

Most healthy pipelines have 5-8 stages. Fewer than 5 and you're hiding critical decision points. More than 8 and your team will start skipping stages or grouping them mentally. The right number depends on your sales cycle length and complexity.

Q: Should we include 'Closed Lost' as a stage?

Yes. Closed Lost is data you need. Track why deals were lost, how long they were in the pipeline, and at what stage they died most often. That information tells you where to invest in your process.

Q: What if our sales cycle varies wildly by customer size?

Create separate pipelines for different customer segments. A $5K deal and a $500K deal move differently. Forcing them into one pipeline destroys forecast accuracy and makes it impossible to see where each type actually gets stuck.

Q: How often should we update our pipeline stages?

Review quarterly. Look for stages where deals consistently get stuck, or where the next step varies wildly. If 50% of deals skip from one stage to another, consider merging them. If a stage means three different things, split it.

Most CRM pipelines look the same: Prospect, Qualified Lead, Demo, Proposal, Negotiation, Closed Won. It's a template that ships with every platform, and it's probably costing you deals. The problem is brutal: generic stages don't reflect your sales reality. They hide where deals actually stall, they make forecasting a guessing game, and they give managers no insight into why a deal is moving (or stuck). A prospect sitting in "Proposal" for 60 days because they're waiting for budget approval looks identical to one waiting on legal review — even though those are completely different situations requiring completely different action. When deal stages don't match your actual process, your team ignores them. They become theater: box-ticking to keep the CRM quiet, not a tool to move deals. Why Generic Stages Fail A deal stage is only useful if it answers three questions: What has to happen for this deal to move forward? (The real condition, not the name.) Who owns the next step? (Your team or theirs?) What's the likelihood of close? (Not a guess, but based on what you've actually seen.) "Proposal" fails all three. Does it mean you've sent a proposal? They've read it? They've shared it internally? You're waiting for feedback? Each is a different stage in a real sales cycle, and each has a different close rate. Template stages also assume all sales are the same velocity. A 3-week self-serve onboarding doesn't move through the same steps as a 6-month enterprise deal. If you're selling both, your pipeline is lying to you. The Right Way to Design Your Stages Start by mapping your actual sales cycle, not the one you wish you had. Go back through your last 20 closed deals. Write down every distinct decision point or action — the moments where something changed. Not stages: actions. For a SaaS product with a sales component, it might look like this: Prospect replies to outreach (they're real) Demo scheduled (they're serious enough to show up) Demo completed (they saw what we do) Custom proposal sent (we've priced it for them) Champion has champion (they've sold it internally) Legal review in progress (procurement is moving) Contract signed (deal done) For a B2B service business (design, consulting, dev), it looks different: Discovery call booked (they want to talk) Discovery completed (they've told us the problem) Proposal sent (we've scoped it and priced it) Proposal approved (they've agreed to the scope) Onboarding scheduled (they've signed and we're starting) For agency new business with a long sales cycle: Warm intro received (not a cold lead) First conversation scheduled (they agreed to meet) Pitch presented (we've shown what we'd do) Budget confirmed (they have money allocated) Committee aligned (stakeholders are on board) Contract sent (legal is done, waiting for signature) Signed (booked) Notice: each stage is specific, not generic. Each stage represents a genuine barrier or milestone. And each stage is independent of how long it takes . A deal can sit in "Pitch Presented" for 2 weeks or 4 months — but you'll see it sitting there, and you'll know exactly what needs to happen next (budget confirmation). Assign Realistic Close Rates Once you have your stages, look at your actual history. Of all deals that hit "Demo Completed," what percentage closed? That's your real close rate for that stage. For example: Demo Completed → 60% close (demos are your most important filter) Custom Proposal Sent → 40% close (not all proposals stick) Champion Aligned → 75% close (when they've sold it internally, you're close) Legal In Progress → 85% close (you're down to process now) These percentages are your reality, not industry averages. Use them to forecast revenue. A deal in "Proposal" with a 40% probability is worth $40K if it's a $100K deal — that's what it contributes to your forecast, not the full value. Real forecast example: You have 10 deals, totaling $500K. But they're at different stages with different close rates. Your real expected revenue is $380K, not $500K. That matters for hiring, budgeting, and knowing whether you're on track. Build Automation Around Stage Movement Once your stages are real, they become triggers for action. When a deal moves to "Proposal Sent," that's a moment: send a reminder task 5 days later if there's no response. When it hits "Legal Review," flag your ops team to follow up on signature status weekly. If you're using a CRM with workflow automation , set up triggers like: Deal moves to "Demo Scheduled" → send prep brief to sales rep Deal moves to "Proposal Sent" → set reminder for follow-up on day 5 (no response = at-risk) Deal sits in a stage for 21 days → escalation alert to manager Deal moves to "Contract Sent" → notify finance and set signature tracking task These automations are only useful if the stages themselves are real. With generic stages, you're automating noise. Handle Different Deal Types Separately If your pipeline has massive variation — some deals close in 2 weeks, others take 6