How to Set Up Pipedrive Deal Stages That Reps Actually Update

I have spent twenty years living inside sales pipelines, and the single thing that separates a forecast I trust from one I argue about is stage design. Pipedrive gives you a clean visual board, but the board only tells the truth if your stages mean something. If they don't, you get a wall of cards that nobody believes, least of all the rep who moved them.

So here is how I set up Pipedrive stages when I want the pipeline to be a record of what the buyer has actually done, not a record of how busy the team has been.

Stages should track the buyer, not your activity

This is the rule I never break. A stage is a place a deal sits because the buyer did something or committed to something. It is not where the deal sits because you sent an email or made a call. "Email Sent" and "Second Follow-Up" feel productive, but they tell me nothing about whether the deal is real. A deal in "Proposal Reviewed" tells me a lot.

When you anchor every stage to a buyer action, two good things happen. Forecasting gets honest, because each step forward represents real momentum from the other side of the table. And reps stop gaming the board, because there is no activity stage to hide a dead deal in.

Fewer, sharper stages beat more, fuzzy ones

The most common mess I clean up is a pipeline with either too few stages or too many.

• Too few, say three or four: everything piles into one giant bucket. "Negotiation" ends up holding a first proposal, a contract redline, and a deal that went quiet six weeks ago. You cannot manage what you cannot distinguish.
• Too many, say ten or twelve: reps quietly stop updating. Dragging a card through a dozen micro-steps feels like data entry for its own sake, so they skip it, and now the board lies in a different way.

Five to seven stages is the range I keep landing on for B2B. Enough resolution to see where deals stall, few enough that updating is a two-second decision, not a chore.

A stage template I would actually ship

Here is a six-stage structure built entirely on exit criteria. The rule for moving a deal forward is simple: it can only advance when the exit condition is genuinely met. If you cannot point to the buyer action, the deal stays put.

Notice every stage name describes a state the buyer is in, not a thing you did. "Solution Shown" rather than "Demo Sent." "Proposal Reviewed" rather than "Proposal Emailed." That wording is the whole game.

Keep probability honest

Pipedrive lets you attach a probability to each stage, and most teams leave the defaults forever. Don't. Pull your own closed-won and closed-lost history and look at what deals in each stage actually do. If deals in "Proposal Reviewed" close 45% of the time and your stage says 60%, your weighted pipeline is inflated by a quarter, and every forecast meeting starts from a lie.

Revisit these numbers a couple of times a year as your win rates shift. The point of probability is not optimism. It is so the number on your forecast matches what your own history says will happen.

Use rotting days so dead deals announce themselves

Pipedrive's rotting setting flags any deal that has sat untouched past a threshold you choose per stage. This is the cheapest pipeline hygiene tool you have, and it is off by default for most people. Set it to roughly how long a healthy deal should reasonably sit before someone has to act:

• Qualified: 7 days
• Discovery: 14 days
• Solution Shown: 14 days
• Proposal Reviewed: 21 days
• Terms Agreed: 14 days
• Contract Out: 7 days

A rotting flag is not a punishment. It is a prompt. Either there is a real next step you can take, or the deal has quietly died and belongs in Lost with a reason. Which brings me to the thing I am most stubborn about.

Never let a deal sit in a stage it has outgrown

The fastest way to rot a pipeline is to let deals park in a stage they have already passed through or fallen out of. A deal that went silent after the proposal is not still in "Proposal Reviewed." Either there is a live conversation moving toward terms, or it is Lost. Resist the urge to invent a "Waiting" or "On Hold" stage to hold these. Every deal is always waiting for something, so that stage becomes a graveyard that makes your board look fuller than it is.

And require lost reasons. Pipedrive supports this under Company Settings, and it is the highest-leverage data you will collect all year. Specific options like Lost to Competitor, No Budget, Bad Timing, Went Silent, and Chose to Do Nothing tell you whether your problem is the pitch, the price, or the targeting.

Required fields turn stages into a data discipline

Pipedrive lets you require fields before a deal can advance out of a stage. This is how you stop deals from sliding forward on vibes. I keep it light, just the fields a deal genuinely cannot move without:

• Leaving Discovery: require Budget Range and Decision Timeline.
• Leaving Proposal Reviewed: require Proposal Amount.
• Leaving Terms Agreed: require Expected Close Date.

Make the rep earn the advance. If they cannot name the budget or the close date, the deal is not where they think it is, and the required field surfaces that before it becomes a forecast miss.

One more thing about adoption

The best stage design in the world fails if reps do not keep the board current. The trick is not nagging. It is making the board worth updating. When stages map to real buyer commitments, the rep gets something back: a clear next step, a forecast their manager believes, and coaching aimed at the actual gap instead of a guess. Tie a quick weekly pipeline pass to your team meeting, and let the rotting flags do the pointing for you.

So before you redesign anything, ask one question of your current setup. Could a new rep, looking only at the stage names, tell you what the buyer has committed to at each step? If the answer is no, that is the work.