Deal stage

A consulting firm analysed how long deals spent in each stage. Deals spent average 2 weeks in 'Scheduled', 2 weeks in 'Qualified', but 6 weeks in 'Negotiation'. This revealed that contract negotiation was a major bottleneck. They hired a dedicated contract negotiator to handle most template variations, reducing average deal time in 'Negotiation' to 2 weeks and improving overall sales cycle length by 20%.

A SaaS company defined deal stages with specific criteria: Lead (contact initiated), Qualified (confirmed need and budget), Scheduled (discovery call on calendar), Qualified Opportunity (completed discovery, working on proposal), Proposal (proposal sent), Negotiation (contract terms being negotiated), Closed Won (contract signed). Each stage advancement was documented with specific information confirming progression criteria. This clarity improved forecast accuracy from 65% to 82% year-on-year.

An enterprise software company expanded their deal stages from 5 to 7 after analysing where deals stalled. They added separate 'Evaluation' and 'Business Case Development' stages before 'Proposal', because they discovered that deals often stalled after discovery while prospects built business cases. Creating explicit stages for this work helped sales people recognise when deals were progressing normally versus actually stalled.

Define pipeline progression steps to standardise how reps advance opportunities and give managers visibility into where deals stall or convert unexpectedly.

A deal stage is simply a label for where a potential customer sits in your sales process, from "never heard of us" to "signed the contract". You line these labels up in order, and every deal moves left to right as it gets closer to a yes (or drops out as a no). Typical stages run something like: lead, qualified lead, discovery call booked, discovery done, proposal sent, negotiation, closed won (or closed lost). The exact names don't matter much. What matters is that each stage has a clear, checkable rule for what's true before a deal earns its way in.

Think of every stage as a gate. To move a deal from one stage to the next, something specific must have happened, not just a vague feeling that the prospect is "interested". "Qualified lead" shouldn't mean "seems keen". It should mean "we've confirmed they have a real need we solve, money set aside, and someone who can actually say yes". When the criteria are fuzzy, every rep interprets them differently and your pipeline numbers become fiction.

Done well, deal stages give you two things: a shared language so the whole team talks about deals the same way, and a map of where deals get stuck. If loads of opportunities pile up in "proposal sent" and never move, that's a signal something's off with your scoping or your pricing, not bad luck.

Why it matters

Deal stages are what turn a messy list of conversations into a forecast you can trust. If you know that historically 40% of "proposal sent" deals close within 30 days, and you've got 500,000 EUR sitting in that stage right now, you can reasonably forecast 200,000 EUR of revenue. That predictability is what lets you plan hiring, spend, and board reporting instead of guessing.

They also show you where to spend effort. Deals racing through the early stages but dying in discovery means you need stronger discovery, not more leads. Deals stalling in negotiation means your pricing or contract terms are out of step with what buyers expect. The stage data points straight at the bottleneck.

Say you're running your pipeline in Pipedrive. Each stage shows you the total value of deals sitting in it and how long they've been there, so a column that's swollen and slow is impossible to miss, that's your stall. The same view in a HubSpot deal board tells you the same story: where the money is bunching up and going cold.

How to apply it

Write down the exact criteria for each stage and don't move a deal until they're met. "Qualified" means need confirmed, budget confirmed, decision-maker confirmed, not "had a nice chat". These hard rules are what keep your pipeline honest across the whole team.

Make reps log a note every time a deal changes stage, explaining what actually happened. Say you're running outbound with Close. When a deal jumps from "discovery" to "proposal sent", the note should record what you learned in discovery that justifies sending a proposal. That history is gold for forecasting and for training new hires, and it stops deals quietly drifting forward on optimism alone.

Review your stages every quarter and prune. If two stages always flip in a day or two with no real difference between them, merge them. If a stage is permanently empty, delete it. And watch the time-in-stage data: if you spot, say in Folk, that deals sit twice as long in negotiation as anywhere else, that's your cue to fix the negotiation step, maybe a deal desk, maybe simpler contract terms, not to add another stage. Your pipeline should mirror how you actually sell, which changes as you grow.

Examples

SaaS sales pipeline design

A SaaS company defined stages with specific, checkable criteria: Lead (contact made), Qualified (need and budget confirmed), Scheduled (discovery call booked), Qualified Opportunity (discovery done, building a proposal), Proposal (proposal sent), Negotiation (terms being agreed), Closed Won (contract signed). Every advance had to be logged with the information confirming the criteria were met. That discipline lifted their forecast accuracy from 65% to 82% year on year.

Enterprise sales stage architecture

An enterprise software company grew its stages from five to seven after studying where deals stalled. They added separate "Evaluation" and "Business Case Development" stages before "Proposal", because they realised deals routinely paused after discovery while buyers built an internal business case. Making that work an explicit stage helped reps tell the difference between a deal progressing normally and one genuinely stuck.

Identifying pipeline bottlenecks via stage analysis

A consulting firm measured how long deals spent in each stage. Deals averaged two weeks in "Scheduled", two weeks in "Qualified", but six weeks in "Negotiation". The numbers exposed contract negotiation as the real bottleneck, so they hired a dedicated negotiator to handle the common template variations. Average time in "Negotiation" dropped to two weeks and the overall sales cycle shortened by 20%.

For B2B growth teams, deal stages drive forecast accuracy and identify pipeline gaps. If you're missing deals in 'proposal sent' stage, something is wrong with your discovery or scoping process. If deals are stalling in 'negotiation' stage, your pricing or contract terms might be misaligned with customer expectations. Deal stage data reveals these bottlenecks.

Deal stages also inform resource allocation. If deals are moving quickly through early stages but stalling in discovery, you might need more discovery resources (experienced sales people or customer success involved in sales). If deals are stalling in proposal negotiation, you might need a deal desk or pricing strategy review.

From a forecasting perspective, deal stages let you predict revenue. If you know that 40% of 'proposal sent' deals close within 30 days, and you currently have £500,000 in proposal sent deals, you can forecast £200,000 in revenue from those deals. This predictability is essential for financial planning and board reporting.

Define clear criteria for advancement to each deal stage. Don't just say 'qualified lead' means interested. Say: 'qualified lead means we've confirmed they have a need in our solution area, they have budget allocated, and they have authority to make the decision.' These specific criteria ensure consistency across your sales team.

Require deal stage changes to be documented in your CRM with notes about why the deal is moving forward or staying in place. This history is valuable for forecasting and for training new sales people. When a deal moves from 'discovery call' to 'proposal sent', the note should explain what was discovered that justifies advancing.

Review your deal stage definitions periodically. If deals are moving between two stages rapidly without clear criteria separating them, combine the stages. If a stage is empty or rarely used, remove it. Your pipeline should reflect your actual sales process, which changes over time as you hire new people, adjust messaging, or modify products.