Setting up a Pipedrive pipeline that people actually use
Most Pipedrive implementations fail in the same place: the pipeline has too many stages, too many required fields, and no reason for anyone to move a deal. This is a setup method built around one constraint — every stage must represent something the buyer does, not something you do. Get that right and the rest is configuration.
Before you configure anything
Write, on paper, the last five deals you closed and the last five you lost. For each, note the last three things that actually happened before the outcome. You will find the same two or three events repeating — a call, a document sent, a decision made. Those are your stages. Not your internal process, not your CRM vendor's template: the events that repeat in your own history.
How many stages
- Three to five for a consultative sale. Example: Qualified → Discovery done → Proposal sent → Verbal yes → Won.
- Five to seven for a transactional sale with procurement. Add "Terms agreed" and "Invoice raised" as separate stages only if they genuinely get stuck there.
- Never more than seven. Every stage you add is a decision someone has to make correctly, repeatedly. Three stages people update beat seven they avoid.
Name stages after buyer events, not seller activities. "Proposal sent" is a real state a deal is in. "Working" is not — it is where deals go to be forgotten.
The fields worth having
Pipedrive ships with sensible defaults (value, currency, expected close date, owner, organisation, person). Add only these, and only if you will maintain them:
- Source — where the deal came from. The single field most teams regret not having after six months, because it is the only way to learn which channel works.
- Next action date — if your workflow does not already carry this on the activity, add it. A deal without a next action is not a deal, it is a hope.
- Lost reason — a short dropdown. This is the field that pays for the CRM, because it is the only honest record of why you lose.
Everything else — industry, employee count, budget band — is a field you fill in for the first month and abandon in the second. If a field is not on a report you will read, do not create it.
The three settings that decide adoption
- Turn on email sync for every user before day one. A CRM that requires manual logging is a CRM that is out of date. Sync first, then train.
- Reduce notification volume immediately. Default settings in every CRM generate noise proportional to the number of events. Turn off everything except "deal assigned to me" and "activity due today," then add back only what someone asks for.
- Set the rotting threshold honestly. Pipedrive flags deals with no activity for N days. Set N to your shortest normal sales cycle, not a round number. If you usually hear back within ten days, twelve days of silence is a real signal.
Day one: import less than you think
Import only live deals — anything with activity in the last 90 days, plus anything you genuinely expect to close. Archive the rest in a spreadsheet. A pipeline seeded with dead records has two effects, both bad: the value total is meaningless, and the team learns that the pipeline contains things that will never happen.
Import in this order: organisations, then people, then deals, then notes. Getting the order wrong creates duplicates you will spend a weekend merging.
The weekly ritual that makes it stick
- Twenty minutes, same time, every week. Filter to deals with no activity in 14 days. Each one gets a decision: an action, a stage change, or a lost reason.
- Review stage age, not stage count. A deal in "Proposal sent" for three weeks is stuck, and the age visible on the board is the only thing that tells you.
- Update forecasts from the pipeline, never alongside it. The moment a separate spreadsheet forecast exists, the CRM becomes optional, and optional tools decay.
What this guide is, and is not
This is a method guide based on how pipeline implementations fail, not a report from a specific client engagement. Pipedrive's plan structure and pricing are verified from its pricing page (October 23, 2026): Lite €14, Growth €39, Premium €59, Ultimate €79 per seat per month on annual billing, with no free plan and a 14-day trial. Which tier you need depends on whether you want lead capture (LeadBooster €32.50) and email campaigns (€13.33) as add-ons. Our hands-on testing cycle is in progress and will add account screenshots and friction points per our How We Test process.