How to Set Up Deal Stages in Pipedrive to Match How You Sell

To set up deal stages in Pipedrive, open the Deals area, choose a pipeline, then use the pipeline settings to add, rename, reorder, and assign probabilities to its stages. Build those stages around buyer milestones your reps can verify, not around internal tasks such as calling, following up, or waiting. A short pipeline with shared definitions is usually more useful than a detailed one that reps interpret differently.

Before you add stages, map the moments that move a deal forward

Start with your sales process, not Pipedrive’s default stage labels. Each stage should mark a meaningful change in the buyer’s commitment, understanding, or buying process. If nothing has changed for the buyer, it usually does not need its own stage.

Before you begin, make sure you have:

• A Pipedrive account with permission to view and edit pipelines; workspace or account administrators commonly have this access.
• A list of the steps your team uses to move an opportunity from first contact to a closed sale.
• A clear definition of what counts as a qualified opportunity for your business.
• Recent won and lost deals, if you have them, so you can base stage probabilities on real outcomes rather than optimism.
• Agreement from the salespeople who will use the pipeline, especially if they own different parts of the sales process.

Write down buyer-confirmed milestones before opening Pipedrive settings. For example, your team might identify these points: a lead has been reviewed, the buyer has confirmed a relevant need, a discovery conversation has happened, a proposal has been received, commercial terms are being discussed, and the deal is won or lost.

Do not create a stage for every task a rep performs. “Called prospect,” “sent follow-up,” and “waiting for reply” describe work or deal status, not progress in the sale. Track them with activities, reminders, notes, or fields instead.

Use a simple test: could two reps look at the same deal and point to evidence that it has reached this stage? “Discovery completed with the budget owner” is evidence-based. “Working on it” is not.

How to create, name, reorder, and assign probabilities to deal stages in Pipedrive

Use pipeline settings to create a new pipeline or edit the pipeline your team already uses. Pipedrive labels can vary slightly by plan or interface version, but pipeline management is generally available from the pipeline view through its pipeline selector or from the company settings area.

1. Open the Deals area and select the pipeline you want to edit from the pipeline dropdown.

2. Open the option to edit pipelines or pipeline settings.

Deals > Pipeline selector > Edit pipelines

3. Create a new pipeline if this sales motion needs its own process, or select an existing pipeline to change its stages.

4. Add the first active sales stage and give it a name based on a buyer milestone.

5. Add the remaining stages in the order deals normally progress through your sales process.

6. Drag the stages, or use the available ordering control, to place them from earliest to latest.

7. Enter a win probability for each open stage.

8. Save the pipeline configuration.

9. Confirm that Won and Lost remain final outcome categories rather than ordinary working stages.

For example, a team selling a service through an initial qualification call, a needs conversation, a proposal, and commercial approval could start with this pipeline:

Treat these percentages as examples, not defaults to copy. A probability estimates the share of deals that eventually close after reaching that stage. If 10 deals reach Proposal and only four are won over time, a 40% probability may be closer to reality than 60%.

Pipedrive can use stage probabilities to calculate weighted values. A deal valued at $10,000 in a 40% stage contributes $4,000 to weighted pipeline value. This makes forecast totals more useful only when reps move deals promptly and apply the same stage definitions.

Use stage names your reps can apply the same way every time

A stage name should state what has become true for the buyer, not what the rep plans to do next. The wording does not need to be clever; it needs to help two people put the same deal in the same stage when they have the same facts.

For each stage, write a short entry rule and exit rule. Keep these in a shared sales playbook, a pinned internal document, or your onboarding material.

For the example pipeline, the rules could be:

• New lead: A potential opportunity exists, but qualification has not yet been completed.
• Qualified: The prospect has a relevant need and fits your basic customer criteria; a next sales conversation is scheduled or agreed.
• Discovery: A substantive conversation has clarified needs, stakeholders, timing, or buying process.
• Proposal: The buyer has received pricing, scope, or a recommended solution tied to the discovery.
• Negotiation: The buyer is actively discussing terms, approvals, or final changes required to buy.
• Won: The customer has made the commitment your business defines as a sale, such as a signed agreement or accepted order.

Names such as “Follow up,” “Waiting,” “Nurture,” and “In progress” make reporting unreliable because they describe rep activity or delay, not buyer progress. One rep might move every quiet deal to “Waiting,” while another leaves the same deals in Proposal. Your conversion rates would then reflect rep habits rather than sales progress.

Use other Pipedrive tools for these situations:

If a deal goes quiet, leave it in the last buyer-confirmed stage and create the next activity. If it no longer has a credible path to purchase, mark it Lost with a useful lost reason. This keeps pipeline aging and forecasts more honest.

Check that your pipeline works before your team starts using it

Test the pipeline with a sample deal before asking the team to use it. This helps you find unclear definitions, awkward stage order, and probabilities that do not produce the forecast view you expected.

1. Create a test deal in the new or edited pipeline.

2. Enter a realistic deal value, contact, organization, and expected close date.

3. Place the deal in the first active stage.

4. Move the deal through each stage only when its written entry rule has been met.

5. Check the deal value in the pipeline view and any weighted-value or forecast view available in your Pipedrive setup.

6. Confirm that the weighted amount changes as the deal enters stages with different probabilities.

7. Move the test deal to Won, then create a separate test deal and move it to Lost to confirm that outcome handling and lost reasons fit your process.

8. Delete or clearly label the test records so they do not distort live reporting.

The setup is working when the pipeline displays stages in the intended order, the sample deal can move through them without ambiguity, and weighted values change in line with the probabilities you entered. A $10,000 sample deal in a 25% stage should be treated as $2,500 in weighted pipeline value where that calculation is shown.

Before launch, give the team a one-page stage-definition guide. Include the stage name, evidence required to enter it, the usual next activity, and when to mark a deal Lost. Then walk through a few realistic examples together: an early opportunity, an active proposal, and a stalled deal. This often reveals definitions that sounded clear on paper but are unclear in use.

Review the first several weeks of usage. Look for deals sitting in one stage for unusually long periods, stages that almost nobody uses, and reps applying a stage differently from the rest of the team. Clarify definitions first; change the pipeline structure only when the sales process itself needs a different model.

When to add another pipeline, a custom field, or an activity instead of another stage

Add another pipeline only when a group of deals follows a genuinely different selling process. For example, a team selling both self-serve subscriptions and enterprise contracts may need separate pipelines if qualification, approval, and closing steps are materially different. Different labels for the same underlying process usually do not justify another pipeline.

Use a custom field when you need to sort, filter, or report on a deal attribute without changing its sales progress. Common examples include product line, customer segment, implementation complexity, procurement requirement, lead source, or a pause reason. A custom field answers, “What is true about this deal?” A stage answers, “How far has the buyer progressed?”

Use an activity for a specific piece of work: call a stakeholder, send a proposal, schedule a demo, or follow up after a set date. Activities keep reps focused on the next action without turning temporary work into pipeline structure.

Long implementation or onboarding work normally belongs after a deal is Won, not in sales stages, if the sale is already complete. If your business does not consider a deal won until implementation or another post-contract milestone is complete, define that policy carefully and make it explicit. Mixing delivery work with active selling can make sales forecasts hard to interpret.

For stalled deals, do not automatically add a “Stalled” stage. Keep the deal in the last confirmed buyer milestone, record the next action or pause reason, and set a rule for when the team should close it as Lost. Add a stalled-deal field or report if you need to monitor inactivity across the pipeline.

Keep the main pipeline simple enough that a rep can choose a stage quickly and explain the choice. If a proposed stage cannot be tied to a clear buyer milestone and a reporting decision, it is probably better handled with a field, activity, or saved filter.

Conclusion

Build the first version around the sales process your team can describe today, then use it with real deals. Set a date to review stage aging, conversion patterns, and rep feedback after the team has worked from the new definitions. Update probabilities from your own closed-deal results, and do not add stages simply to account for every exception.