In short
Source: Sales Surge price list and more than 150 CRM implementationsAs of: 16 November 2026
In this article
- What is Pipedrive, and who is it built for?
- How do you design your pipeline and stages?
- Which custom fields do you really need?
- Pipedrive automation examples: which ten to build first?
- Which Pipedrive plan do you need?
- Which reports and dashboards do you build in Insights?
- Which integrations does a B2B setup need?
- Set up Pipedrive yourself or hire a partner?
- What does it cost to have Pipedrive set up?
- Pipedrive partner tiers, in short
- Frequently asked questions

What is Pipedrive, and who is it built for?
Pipedrive is a CRM built around the sales pipeline. Every deal sits in a stage, every stage has a next activity, and the whole screen is designed to make a salesperson ask one question: what do I do next on this deal? That focus is why sales teams adopt it faster than broader suites.
It fits B2B teams of roughly 3 to 200 reps that sell through a defined process: services firms, SaaS, wholesale, agencies, recruitment and consulting. It fits less well when marketing automation is the centre of your revenue engine, when you need dozens of custom objects, or when a group of entities needs one shared data model with heavy permissions. In those cases look at the Pipedrive vs HubSpot and Pipedrive vs Salesforce comparisons first.
Out of the box Pipedrive gives you a default pipeline, standard fields and a trial. That gets you started, but it is not a setup. The rest of this guide is about the decisions that turn the trial into the system your team works in every day.
How do you design your pipeline and stages?
Design stages around what the buyer has committed to, not around what your team does internally. A stage is only real when you can check it: a meeting took place, a budget was named, a proposal was requested. Internal steps such as preparing a quote or checking stock belong in activities, not in stages.
Five to seven stages is enough for almost every B2B process. Fewer and the pipeline hides where deals stall. More and reps start skipping stages, which breaks your conversion reporting. Give every stage an exit criterion in one sentence, and train the team on those sentences, not on the screen.
Below are two worked examples we use as a starting point in discovery. They are a starting point, not a template to copy.
| Stage | SaaS: exit criterion | Services: exit criterion |
|---|---|---|
| 1. Qualified | Fits the ICP and has a named problem | Fits the ICP and asked for a conversation |
| 2. Discovery done | Pains, users and current tools are documented | Scope and decision makers are known |
| 3. Demo or solution shown | Champion saw the product on their own use case | Approach and phasing were presented |
| 4. Proposal sent | Pricing and seats are agreed in principle | Written proposal with a fixed price was sent |
| 5. Negotiation | Procurement or legal is involved | Buyer asked for changes or a start date |
| 6. Verbal yes | Decision maker confirmed, contract pending | Signature date agreed |
When do you need a second pipeline? When the process is genuinely different: a different buyer, different stages or a different sales cycle. New business and renewals are a common split. Two product lines sold through the same steps are not, and they belong in one pipeline with a field to tell them apart.
Pipedrive also separates leads from deals. Leads live in the Leads Inbox until someone qualifies them. Only then do they become a deal in the pipeline. Use that split. A pipeline full of unqualified names makes every forecast wrong.
Which custom fields do you really need?
Keep it short: start with no more than ten to fifteen custom fields per object, and only add a field when someone can name the report or the automation that uses it. Every field you add is a field a rep has to fill. Fields nobody fills are worse than no field, because they make filters and reports look broken.
Name fields so anyone understands them without training, and use the same pattern everywhere. Prefer single option and multiple option fields over free text, because only structured values can drive automations and reports. A free text field called Notes 2 helps nobody.
- On the deal: lead source, product or service line, expected start date, the lost reason and one field for the next commitment.
- On the organization: segment, size band, region and the current tool you are replacing.
- On the person: role in the decision (decision maker, champion, user) and preferred language.
Clean up once a quarter. Export the field list, check per field how often it is filled and which reports use it, and archive what nobody uses. The illustration at the top of this guide is exactly that exercise. Moving from another CRM? Then field mapping is the moment to cut, not to copy. The HubSpot to Pipedrive checklist walks through it.
Pipedrive automation examples: which ten to build first?
Start with the automations that remove forgotten follow-up, because that is where deals are lost without anyone noticing. Each example below is one trigger, one condition and one action, and each one can be built with Pipedrive's own workflow automation.
| Trigger | Condition | Action |
|---|---|---|
| Deal moves to Proposal sent | Deal has no planned activity | Create a follow-up call for the owner in three working days |
| New lead from the website form | Lead source is website | Assign an owner and create a call activity for today |
| Deal is won | Pipeline is new business | Create a deal in the onboarding pipeline and notify delivery |
| Deal is lost | Lost reason is timing | Create a check-in activity a few months later |
| Meeting activity is marked done | Deal is in Discovery | Create the next activity so the deal never sits without one |
| Deal value is updated | Value is above your large deal threshold | Add the sales manager as follower |
| Person is created | Person has no organization | Create a task to complete the record |
| Deal enters Negotiation | Expected close date is empty | Send the owner a reminder to set it |
| Deal owner changes | Deal is open | Email the new owner a summary and the next step |
| Organization field segment changes | New value is enterprise | Notify the account manager in Slack or by email |
Know the limits. Workflow automation is not included in every Pipedrive plan, and the number of active automations differs per plan. Pipedrive changes these limits, so check the current numbers in your own account or on Pipedrive's pricing page before you design around them.
Native automation also stops at the edge of Pipedrive. As soon as a workflow has to create a project in Asana, write to your accounting package or enrich a record from Apollo, you need a layer in between. We use Make for that, and the Make and Pipedrive guide shows how we build those scenarios. Our rule of thumb: native first, Make when the workflow leaves Pipedrive.
Which Pipedrive plan do you need?
Pick the plan on the features your process needs, not on the price per seat. At the time of writing Pipedrive sells four plans: Lite, Growth, Premium and Ultimate. The lightest plan covers the pipeline and activities. Automations, more reporting and more control over permissions come with the higher plans.
Three questions usually settle it. Do you need workflow automation? Do you need more than basic reporting in Insights? Do you need visibility rules per team? Answer those before the trial ends. Prices and plan contents change, so we keep them in one place: the Pipedrive pricing guide.
Which reports and dashboards do you build in Insights?
Build five dashboards and nothing more until the team actually uses them. Each one answers a question leadership asks every week.
Pipeline health.
Open deal value per stage, weighted value and deals without a next activity.Conversion per stage.
How many deals move from each stage to the next, so you see where deals stall.Speed.
Time from lead to first contact, response time on new leads and the cycle time from lead to deal.Activity per rep.
Calls, meetings and emails per person against the plan, used for coaching, not for policing.Forecast and results.
Won deals per month, expected revenue by close date and the lost reasons.
One honest limit: Insights reports well inside one object, but struggles with questions that cross deals, activities and products at once. For that kind of reporting we built our own tool, Surge Reports. For most teams the five dashboards above are enough for the first year.
Which integrations does a B2B setup need?
Connect the tools your team already uses every day before adding anything new. In order of impact that is usually this:
- Email and calendar sync, so every conversation and meeting lands on the right deal without copying.
- Website forms, so a request from your site becomes a lead with source and owner.
- Prospecting and outbound tools such as Apollo and Instantly, so replies land on the deal and nobody gets emailed twice. See the Apollo and Pipedrive guide.
- Telephony such as CloudTalk, so calls and recordings are logged on the deal.
- Accounting or ERP, so a won deal can become an invoice or an order without retyping.
Every integration is something that can break. Document what each one syncs, in which direction, and who gets notified when it fails.
Set up Pipedrive yourself or hire a partner?
Do it yourself when you have up to five users, one pipeline and no integrations beyond mail and calendar. Pipedrive works out of the box, and this guide covers most of what you need.
Hire a partner when you migrate data from another CRM, when you need automations across tools, or when several teams share the system. That is where self-built setups usually break, and the pattern is always the same. The stages were copied from a template. Follow-up depends on memory. Leadership does not trust the reports, so the weekly numbers still live in a spreadsheet. Whether you look for a Pipedrive specialist or an automation agency, pick one that designs the sales process before touching the settings.
Two examples from our own work. For BOOH Media, which sells out-of-home media, a seven-stage pipeline with digital signing was live in 5 days, where 4 weeks were planned. For Evans & Watson, a premium tea brand, response to leads went up 30% and automation gave 20%+ more margin, with a B2B funnel next to the B2C sales. In both cases the work started with the pipeline design described above.
Comparing partners? The guide on how to choose a Pipedrive implementation partner has the seven questions to ask and a twelve point checklist.
What does it cost to have Pipedrive set up?
We work with fixed-price packages, so you know the number before you sign. A CRM implementation starts from €2,950 and takes two to four weeks for a small team. Larger teams and migrations take longer, and that timeline goes in the proposal.
Starter
from €2,950
Growth
from €5,500
Scale
from €8,900
Enterprise
from €13,500
Retainer
Priced in the quote
Each phase is invoiced up front, so you only pay for a phase once it is agreed. Every package, add-on and integration price is on the pricing page. Working in Pipedrive already, but it keeps getting stuck? Then an audit is often the first step: for €2,200 you get the findings and a roadmap within seven to ten days.
Pipedrive partner tiers, in short
Pipedrive certifies implementation partners in three tiers at the time of writing: Authorized, Gold and Platinum. Each tier asks for more certified people across sales, support, marketing and customer success. Pipedrive also asks for a growth plan. Sales Surge is a Pipedrive Platinum Partner, was named a top 8 Pipedrive partner worldwide in July 2026 and won the Pipedrive 2026 Top New ARR Partner Award.
A tier tells you a partner knows the product. It does not tell you whether they understand your sales process. What each tier requires, and how to test a partner before you sign, is in the partner guide.
Frequently asked questions
Do you need a partner to set up Pipedrive?
Not always. With up to five users, one pipeline and no integrations beyond mail and calendar you can set Pipedrive up yourself with this guide. A partner pays off when you move data from another CRM, need automations across several tools, or have several teams sharing the system. What to look for when you pick one is in our guide on choosing a Pipedrive partner, linked higher up on this page.
How long does it take to set up Pipedrive?
For a team of up to about fifteen users a CRM implementation takes two to four weeks: intake and blueprint, the build, a test with real deals, then training on your own data. A migration from another CRM, several pipelines or integrations with accounting add time. We put the timeline in the proposal and invoice per phase, so you see the design decisions before anything goes live.
How many pipelines do you need in Pipedrive?
Usually one or two. Add a pipeline only when the process is genuinely different: another buyer, other stages or a different sales cycle. New business and renewals often get their own pipeline, and so does onboarding after a deal is won. Two product lines sold through the same steps belong in one pipeline with a field to separate them, otherwise your reporting splits into pieces nobody adds up.
How many automations can Pipedrive handle?
It depends on your plan. Workflow automation is not in every Pipedrive plan, and the number of active automations differs per plan and changes over time, so check the current limit in your account. For most B2B teams ten to twenty well chosen automations cover the follow-up. When a workflow has to reach other tools, we build it in Make instead, which also keeps your native limit free for what matters inside Pipedrive.
What is the difference between leads and deals in Pipedrive?
A lead is a contact or opportunity you have not qualified yet. It sits in the Leads Inbox, outside the pipeline. A deal is an opportunity you are actively working, with a value, an owner and a stage. Convert a lead to a deal only when it meets your qualification criteria. Keeping that line strict is what makes pipeline value and forecasts worth reading.
Can I move from HubSpot to Pipedrive without losing data?
Yes, if the migration is planned. Contacts, companies, deals, notes, activities and email history can all move, and HubSpot workflows are rebuilt as Pipedrive automations or Make scenarios. Some HubSpot objects have no direct counterpart and end up as fields or labels. The checklist on our site lists every step, and our migration service has a fixed scope and price.
Does Sales Surge offer support after the implementation?
Yes. Every implementation ends with a handover on your own data and written documentation, plus a period of aftercare that depends on the package. After that you can move to a retainer for new automations, report changes and onboarding new hires. Running it yourself also works, as long as someone in the team owns the system and looks at it every week.
