Pipedrive pipeline setup: stages, activities, and follow-up

Quick answer: A useful Pipedrive setup connects deal stages to observable sales events and activities. Each active deal should have an owner and a next action the team can explain.

Design stages around customer progress

Pipedrive emphasizes visual deal pipelines and sales activities. Begin by listing the events in your actual buying process, rather than accepting a default pipeline without review. A proposal sent is an event; warm prospect is a judgment that different people may interpret differently.

For a quote-led service business, a starting pipeline could cover qualified request, visit arranged, quote sent, and decision pending. Won and lost outcomes close the conversation. Keep stage definitions in a short reference that a new salesperson can understand.

Treat activities as the operating rhythm

A stage answers where the conversation stands. An activity answers what someone should do next. Specify whether the next step is a call, a visit, a proposal task, or a review. Avoid advancing deals merely because a reminder was created; the stage should reflect the customer’s progress.

During the pilot, review overdue activities and deals without a next step. Ask whether the due dates are realistic and whether people have enough context to act. Reporting should support a weekly decision, such as reallocating work or reviewing an overdue quote, rather than rewarding record entry alone.

Automate a small rule with clear boundaries

A proposed first rule might create a review task when a quote enters the decision-pending stage. Define the condition, responsible user, timing, and stop rule. An automatic customer email needs additional checks: the contact details, message context, and whether a response has already arrived.

Confirm automation availability and connected services in the selected plan. Test a deal that moves backwards, a duplicate event, and a changed owner. Keep the workflow understandable to the person who will maintain it, and agree where failures will be reviewed.

A practical checklist

• Name stages after observable events.
• Specify the next activity and responsible user.
• Review overdue and ownerless deals.
• Test changes and repeats before enabling automation.

How many pipeline stages should we have?

Use the fewest stages that preserve meaningful differences in your process. Combine stages that lead to the same action and separate stages only when ownership, timing, or required information changes. There is no universal number that produces better sales results.

Continue with a related guide

Read the related guide, explore the CRM and automation library, or use the CRM readiness checklist.

Sources and editorial notes

• Pipedrive: designing pipeline stages

Prepared on 11 October 2026. This guide combines linked product documentation with a proposed implementation approach. Examples are illustrative. Platform capabilities, editions, and charges change; confirm requirements with the provider before buying. No vendor sponsorship or affiliate links are used in this article.