Pipedrive webinar: setting up Pipedrive right
A masterclass with Pipedrive and CloudTalk on the five patterns we see most often in an existing Pipedrive setup. The content is written out below.
- Five patterns written out
- Checklist on this page
- With Pipedrive and CloudTalk
There is no recording of this session online.
What we showed in the session
It was one hour, so we did not fix anyone's own setup. You did see where to start.
Five patterns
The five patterns we keep seeing after more than 150 CRM implementations, each with a check.
A checklist for your setup
A checklist to review your pipelines, stages and fields. We worked out the ten points below after the session.
Calling inside Pipedrive
A demo of CloudTalk with Pipedrive, where every call lands in the right deal.
Email me about a new edition
There is no new date yet. Sign up and we email you when we run this session again.
In short
This Pipedrive webinar covered five patterns we keep finding after more than 150 CRM implementations: deals that sit in one stage for months, activities nobody logs, stalled deals nobody archives, custom fields that stay empty and calls that happen outside the CRM. For each pattern you find the symptom below, how to check for it and what to do about it.
Why does a Pipedrive setup stop working after a while?
Because the setup does not grow with the team. One pipeline for three people does not hold up for twelve reps with two products and their own way of working. Nobody decides to let it slide. It creeps in: an extra field here, a stage nobody uses there.
You notice the effect later. The forecast is off, managers steer on gut feeling and reps spend time updating the system instead of talking to customers. That is why we look around first in every account we take over, before we change anything. We find these five patterns almost every time.
Pattern 1: deals that sit in one stage for months
- Symptom. The pipeline looks full, but a large share of the deals has not moved in weeks. The total value in your forecast is far higher than what will actually close.
- Check. Filter open deals whose last stage change is more than twice your average cycle time ago. Count deals per stage. If more than a quarter of your deals sit in one stage, that stage has stopped meaning anything.
- Fix. Write one sentence per stage that says what must be true before a deal moves on, and make sure the whole team knows it. Turn on rotting, the setting that turns a deal red when it sits still too long, with a limit per stage. Go through the red deals every week.
Pattern 2: activities nobody logs
- Symptom. Deals without a planned next step. The rep knows what is going on. The CRM has none of it. When someone is out, a colleague starts from zero.
- Check. Count open deals without a scheduled activity. In a healthy account that number is close to zero, because every open deal has a next step with a date.
- Fix. Make a scheduled activity the rule for every open deal, and let Pipedrive ask for the next one as soon as an activity is marked done. Keep the number of activity types small, five to seven is enough. Too many types turn logging into a menu.
Pattern 3: stalled deals nobody archives
- Symptom. Deals from last year are still open. Nobody wants to mark them lost, because it feels like failing or it hurts a rep's numbers.
- Check. Sort open deals by creation date. Anything older than twice your normal sales cycle without activity is, in practice, already lost.
- Fix. Mark those deals lost with a fixed list of lost reasons, not a free text field. Agree up front what the lost reasons are for: they tell you where deals get stuck. Schedule a quarterly round to do it again.
Pattern 4: custom fields nobody fills in
- Symptom. Dozens of extra fields, created with good intentions. A few get filled, the rest stay empty. Reports on those fields mean nothing.
- Check. Export your deals and organizations and work out per field how often it is filled. A field that is set on fewer than half of the records is a field nobody uses.
- Fix. Keep only fields that drive a decision or a report. Use dropdowns instead of free text. Make the few fields that matter required in the stage where you need them; depending on your plan, Pipedrive lets you do that per stage. Delete the rest, after an export.
Pattern 5: calls that happen outside the CRM
- Symptom. A rep has good conversations on their own phone. Afterwards Pipedrive shows an empty activity, or nothing. Three weeks later nobody remembers what was agreed.
- Check. Compare the number of calls your team makes in a day with the number of call activities in Pipedrive that day. A big gap means the conversation is lost.
- Fix. Connect your phone system to Pipedrive so every call logs itself in the right deal. In the session we showed this with CloudTalk. The full setup is on the page of the masterclass on logging every call.
Checklist: review your Pipedrive setup in ten points
We worked out this checklist after the session, in the order we use when we review an account. Each point builds on the one before.
- Each pipeline matches one way of selling. Merge two pipelines that do almost the same thing.
- Each stage has a one sentence definition of what must be true for a deal to be there.
- A pipeline has no more than six to eight stages.
- Rotting is on, with a limit per stage.
- Every open deal has an owner, a value, an expected close date and a scheduled activity.
- There are five to seven activity types, no more.
- Lost deals have a reason from a fixed list.
- Every custom field has an owner and is used in a report or decision.
- Organizations and people are deduplicated, and there is an agreement on who creates new records.
- Calls, emails and meetings land in the deal automatically. Nobody retypes them.
If you want a second opinion on your own answers, our free Pipedrive setup tool gives you a setup proposal in three minutes.
When can you fix this yourself, and when not?
You can fix most of the checklist yourself, with an afternoon and someone willing to cut. That goes for rotting, activity types, lost reasons and cleaning up fields.
It becomes a project when the pipeline itself does not match how you sell, when several teams or countries share one account, or when data has to come over from another system. Then a rebuild is faster than patching. In a Pipedrive implementation we rebuild the pipeline, fields and automations in two to four weeks. For more on setup and admin, see the Pipedrive knowledge hub.
To be fair: a rebuild does not fix behaviour. If the team never agrees on what a stage means, the same pattern is back within six months.
Further reading
- Pipedrive implementationHow we set up or rebuild an account, with pipeline, fields and automations.
- Free setup toolAnswer a few questions and get a setup proposal in three minutes.
- Pipedrive knowledge hubArticles on setting up, running, integrating and pricing Pipedrive.
- Masterclass: every call loggedThe CloudTalk and Pipedrive setup, written out step by step.
Want your own account reviewed?
In the free growth scan (Quick Scan) we look at your CRM, data and workflows. Within 48 hours you know what to fix first.
What it covers
As a Pipedrive Platinum Partner, and since July 2026 one of the top 8 Pipedrive partners worldwide, we get inside a lot of companies. The first thing we do is look around. Usually the setup never grew with the company.
In the session, Sales Surge, Pipedrive and CloudTalk walked through the five patterns and what each one costs if you leave it.
Who it is for
B2B Sales & RevOps
Sales managers, founders and RevOps leads who use Pipedrive and know there is more in it. If you just started, you spot the patterns before they grow. If you have used it for years, the checklist tells you what to clean up first.
Questions about this Pipedrive webinar
Is there a recording of this Pipedrive webinar?
No. This session has no recording online, which is why the content is written out on this page: the five patterns, the symptom of each, how to check for it and what to do, plus the checklist. If you want to know when we run it again, sign up and you get one email as soon as there is a date.
Is this for me if I only just started with Pipedrive?
Yes. These patterns already show up in the first months. Stages that don't match how you sell and fields nobody fills in are visible within a few weeks. Spot them early and you rebuild less later. If you are still choosing how to set up, read on the Pipedrive implementation page how that runs in phases.
How long does it take to fix these five patterns?
It depends on the size of your account. The checklist itself takes an afternoon. Cleaning up stalled deals and empty fields is often a week of work next to your normal job. If the pipeline itself needs a rebuild, that is a project. A CRM implementation with us takes two to four weeks.
Do I need CloudTalk for calling inside Pipedrive?
No. The point is that every call lands as an activity in the right deal, with who called, for how long and what the next step is. CloudTalk is the phone system we connect most often and we are a CloudTalk Elite Partner. Other phone systems with a good Pipedrive integration can do the same. If your team rarely calls, this pattern matters less.
Can Sales Surge review my Pipedrive account?
Yes. The first step is the free growth scan, the Quick Scan. You leave your name, email and CRM, and within 48 hours you know what to fix first. If more is needed, an audit or a rebuild follows. We never take over an account without first looking at what is in it.
Email me about a new edition
There is no new date yet. Sign up and we email you when we run this session again.

