Pipedrive was designed by salespeople, and it shows. The pipeline view is the product. Reps drag deals across stages, schedule the next call, and see at a glance what’s stuck. A small sales team can be working in it within days.
The trouble starts a year or two later. More reps join, a second pipeline appears, marketing starts sending web form leads, someone adds twenty custom fields, and a few automations get built on a Friday afternoon. The board still looks tidy. It just stops telling the truth.
What does “stops telling the truth” look like?
Usually one of these, often several at once:
Stages should mark buyer commitments
The most useful change we make in many Pipedrive accounts is renaming and reducing stages. A stage should represent something the buyer has done or agreed to: a discovery call held, a proposal received, terms under review. That gives you a defensible definition for each one, and it makes the deal probability attached to each stage mean something in forecasts.
We also look at whether you need more than one pipeline. Separate pipelines make sense when the sales motions are genuinely different, such as new business versus renewals, or a fast self-serve trial versus a quoted project. They don’t make sense when they exist because two managers prefer different stage names. Every extra pipeline is another set of reports to reconcile.
Lost reasons get the same treatment. We turn them into a short required list rather than free text, because “why do we lose?” is one of the few questions a sales CRM should answer reliably.
Leads Inbox versus deals
Pipedrive separates leads from deals on purpose. The Leads Inbox holds people and organizations you’re interested in but haven’t qualified yet. A deal is a real sales opportunity with a value, a stage and an expected close date.
When teams skip that distinction, the pipeline fills with “deals” that are really just contacts, and conversion rates collapse. When teams overuse it, good leads wait in the inbox because no one is responsible for reviewing it.
We define what qualifies a lead for conversion (fit, need, an agreed next step), use lead labels to show where each one stands, and make sure someone owns the inbox every day. Leads from web forms, chat or prospecting tools get a source recorded at creation, so you can later see which channel produced deals that actually closed.
Assignment and Automations
Pipedrive has two tools that people often confuse.
Automatic assignment sets the owner when a lead or deal is added, or when a deal changes pipeline or stage. Rules run in priority order, and a rule can assign to a specific user, rotate across a team using round-robin, or hand the record to whoever already owns the linked organization or person. That last option matters more than most teams expect: a new inquiry from an existing customer should usually go to their account owner, not the next rep in the rotation. Automatic assignment is only available on higher-tier plans, so we check yours before designing around it.
Automations are trigger, condition and action workflows. A deal reaches “Proposal sent”, so create a follow-up activity in three days. A deal is marked won, so create a project or notify the delivery team. They are useful and easy to overbuild.
Here’s a pattern we see. One automation reassigns deals when they move into the enterprise pipeline. Another, built later, sets the owner based on country. A deal from a large German company moves pipelines and its owner changes twice in a minute, and the rep who did the discovery call loses it. Each rule made sense when it was written, but no one checked them against each other.
- Existing organization owner
- Pipeline
- Region
- Deal value
- Account owner
- Enterprise rep
- Regional team round-robin
- Inside sales
We list every automation and assignment rule, note which fields each one writes, remove overlaps, and leave you with a short document describing what fires when. Lead routing is a regular part of our lead routing automation work.
Not sure what your automations are doing?
We'll map every Pipedrive automation and assignment rule, show where they overlap, and recommend which to keep.
Activities are the heartbeat
Pipedrive’s whole method assumes every open deal has a scheduled next activity. We set activity types that match how your team sells (call, demo, proposal review, site visit), make the next activity part of stage changes where it makes sense, and use deal rotting thresholds per stage so a red deal means “this needs attention” rather than “this is normal for us.” A proposal stage might rot after ten days; an early discovery stage after three.
Connecting Pipedrive to marketing and the rest of the business
Pipedrive is a sales CRM first. Its Campaigns add-on covers straightforward email newsletters, and Sequences handle simple sales follow-up on supported plans. Many businesses run marketing in a separate tool such as Brevo, Mailchimp or ActiveCampaign, feed leads from web forms or LeadBooster, and connect billing or project tools through the Pipedrive Marketplace or a workflow tool like Zapier or Make.
The connections are rarely the hard part. Deciding which system owns each field is. If marketing marks someone as a customer in one tool while sales tracks won deals in Pipedrive, the two will drift. We set a source of truth for each important field and design the sync around it as part of CRM integration work.
Reporting in Insights
Insights can answer the questions sales leaders care about: conversion by stage, average time in stage, won and lost by reason, activity volume per rep, and revenue forecasts. It can only answer them if stages, lost reasons and close dates are used consistently. We fix the inputs first, then build a small set of reports and dashboards your team will actually open.
How a Pipedrive project usually runs
Most start with a CRM audit covering pipelines, fields, the Leads Inbox, assignment, automations and reporting. From there we either restructure the existing account or, for new teams and rebuilds, plan it properly as a CRM implementation. If you’re moving into Pipedrive from spreadsheets or another CRM, we handle the mapping and cleanup through CRM migration.
How many stages should a Pipedrive pipeline have?
Usually five to seven. Fewer than that hides where deals stall; more tends to include stages that describe internal tasks rather than buyer progress. The right number depends on how many distinct commitments your buyers make before signing.
Should we use leads or go straight to deals?
Use leads if you receive unqualified inquiries or prospect lists. Converting only qualified leads into deals keeps the pipeline honest and makes conversion reporting meaningful. Teams with very few, already qualified inquiries can sometimes skip leads.
Can Pipedrive route leads automatically?
Yes. Automatic assignment can assign new leads and deals by rules, including round-robin across a team and assignment to an existing organization or person owner. It’s available on higher-tier plans.
Is Pipedrive good for marketing automation?
For basic email campaigns and simple sequences, yes. For lifecycle nurturing, detailed segmentation and behavioral triggers, most teams pair Pipedrive with a dedicated marketing platform and sync the two.
Can you clean up duplicate contacts in Pipedrive?
Yes. Pipedrive has built-in tools for merging duplicate people and organizations. We also find out where duplicates come from, usually an integration or import, and fix that so they don’t return.