Most "sales pipeline" advice you'll find online is a generic five-stage template โ New, Qualified, Proposal, Negotiation, Closed โ copy-pasted into every industry regardless of what selling actually looks like there. It's not wrong, exactly. It's just not specific enough to be useful. A pipeline that converts is one built around how your buyers actually make decisions, not a template borrowed from a SaaS company if you sell industrial equipment.
Start with the buyer's decision, not your process
Before naming a single stage, map out what a buyer actually does between "never heard of you" and "signed contract." Talk to a few recent customers and ask when they first realized they had the problem, what made them start looking for a solution, and what almost made them not buy. The stages in your pipeline should mirror milestones in their decision, not internal steps that only make sense to your team.
A pipeline structure that actually works
Here's a structure I've used across dozens of B2B teams, adjusted for their specific sale:
- Lead In โ someone has shown interest, but hasn't confirmed they have a real problem or budget yet.
- Qualified โ you've confirmed there's a real need, a rough budget, and a decision timeline.
- Solution Presented โ they've seen a demo, proposal, or quote specific to their situation.
- Verbal Commitment โ they've told you, in some form, that they intend to move forward.
- Closed Won / Closed Lost โ contract signed, or the deal is dead and marked as such.
Notice "Verbal Commitment" is its own stage. A lot of pipelines skip straight from proposal to closed, which hides a critical signal: deals that stall between a verbal yes and a signature usually have a hidden blocker โ legal review, a second stakeholder, budget approval โ that's worth surfacing early rather than discovering at the worst moment.
The stage where deals die tells you more about your sales process than the stage where they close.
Set clear exit criteria for every stage
A stage without a clear definition of "done" becomes a dumping ground. Every stage needs an explicit, checkable exit criterion โ not a feeling. "Qualified" shouldn't mean "the rep feels good about this one." It should mean something specific, like: confirmed budget range, confirmed timeline, and confirmed that the person you're talking to can influence or make the decision.
Write these down. Put them somewhere every rep can see. It removes the guesswork about when to move a deal forward, and it stops reps from inflating the pipeline with deals that will never close.
Review the pipeline weekly, not just at month-end
A monthly pipeline review is too slow to catch problems while they're still fixable. A short weekly review โ even fifteen minutes โ where each rep flags what moved, what's stuck, and what's at risk gives you time to actually intervene: get a second stakeholder on a call, sweeten an offer, or simply have an honest conversation with the prospect about what's holding things up.
Watch for stage inflation
Over time, reps under pressure will nudge deals forward that haven't really earned it, because a fuller-looking pipeline feels safer than an honest one. The fix isn't blame โ it's making the exit criteria specific enough that inflation is obvious when a manager looks at the deal notes. If a deal's been sitting in "Verbal Commitment" for six weeks with no signed contract and no clear next step logged, that's not really a verbal commitment anymore.
The bottom line
A converting pipeline isn't about picking the right template โ it's about mapping real buyer behavior, defining an honest exit test for every stage, and reviewing it often enough to catch stalled deals while there's still time to save them. Get the structure right once, and it becomes the clearest picture you have of the health of your entire sales operation.