CRM
Pipedrive
EU origin, foreign-owned Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Pipedrive Inc. · www.pipedrive.com
Compare with HubSpot Sales Hub → Compare with CentralStationCRM → Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Pipedrive is a web-based sales CRM, and the bench's split is clean: strong ecosystem, weak pricing and sovereignty evidence. Integrations scored highest on a 500+ app marketplace naming Zapier, Zoom and Xero, plus MCP and an API — though the API appears in the evidence only as the single word "API". Contact & data model clustered at exactly 4 on custom fields with smart formulas and product-to-deal linking; pipeline & forecasting drew 4-5 for customizable kanban pipelines with forecasting, goal-setting, team monitoring and realtime reports. The floor scores came on pricing transparency — the captured pricing page yielded no tier, price, billing period or seat minimum, leaving the 14-day no-card trial as the only public pricing fact — and sovereignty, where data residency, a DPA and a subprocessor list are all unknown under US private-equity majority ownership (Vista Equity Partners, since 2020). Automation scored 2-3 on evidence limited to automated follow-ups and AI prompts. No spread in the table exceeds one point — the split is over severity, not direction — and flagged splits flag none above threshold. Persona-weighted totals span 2.8 to 4.3.
Speaks for it
- integrations score 5-6 on a 500+ app marketplace (Zapier, Zoom, Xero) with MCP support and an API
- Custom fields with smart formulas and product-to-deal linking give contact & data model a steady 4
- Customizable kanban pipelines with forecasting, goal-setting, team monitoring and realtime reports earn pipeline & forecasting 4-5
- Few-click import from spreadsheets and other pipeline software is confirmed
- A 14-day trial without a credit card is public
Held against it
- Pricing transparency scores 1-2: the captured pricing page confirms no tier, price, billing period, seat minimum or VAT treatment
- sovereignty scores 1-2 with data residency, DPA and subprocessor list all unknown under US private-equity majority ownership since 2020
- automation scores 2-3, evidenced only as automated follow-ups and AI prompts — no multi-step workflows, branching, routing or webhooks
- Full export of notes, activities and attachments is unevidenced; the only portability right on file belongs to data subjects, not the account (import, export & exit 3-4)
- No evidence of dedupe, merge tooling or field-level permissions on contact records
Best for
- You want breadth of connections — a 500+ app marketplace, an API and MCP support — to wire the CRM into an existing stack
- You run sales on customizable kanban pipelines with forecasting and goal reports and can enforce stage discipline outside the tool
- You are migrating from spreadsheets or another pipeline tool and value few-click import
- You want to evaluate with a 14-day no-credit-card trial before any pricing conversation
Avoid if
- You must compute an invoice from public pricing before committing — no tier price, billing period or seat minimum is confirmed
- Your compliance review requires a DPA, subprocessor list and confirmed data residency before signing
- You need multi-step workflows, branching, lead routing or webhooks native to the CRM
The scores
Contact & data model
Show reasoningHide reasoning
How this is scored
Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.
0 — A flat address book; no relations between people, companies and deals.
3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.
5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.
8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.
10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.
The Solo Seller
Custom fields with smart formulas are confirmed, which is more than cosmetic, but the evidence is silent on dedupe, merge, activity history and field validation — hygiene tooling is entirely unevidenced, so I can't reach the 5 anchor. 1
The Data Protection Officer
Custom fields with smart formulas and product-deal linking are real customization, not cosmetic. But the evidence is silent on dedupe, merge, validation and field-level permissions — and, my standing complaint, there is no evidenced consent field anywhere in the data model for the people whose records this is. 1
The Sales Ops Lead
Custom fields with smart formulas and product-to-deal linking are confirmed, which is more than cosmetic, but the evidence says nothing about dedupe, merge tooling, field validation, required fields, or permissioned field access. Duplicates accumulating unchecked is exactly the failure mode rubric level 3 describes, so I sit just above it. 1
The RevOps Integrator
Custom fields with smart formulas and product-to-deal linking clear the cosmetic bar, but the evidence is silent on dedupe, merge, required fields, validation and permissioned field access — the hygiene layer simply isn't evidenced. That lands between rubric level 3 and rubric level 5. 1
The Migrator
Custom fields with smart formulas and product-to-deal linking lift this above a flat address book, but the evidence says nothing about dedupe, merge tooling, required fields, or activity history on the record — duplicates accumulating unchecked is exactly the anchor-3 smell I look for when inheriting a dirty database. 1
The Skeptic
Custom fields with smart formulas and product-to-deal linking are confirmed, which beats cosmetic customization. But the evidence is dead silent on dedupe, merge tooling, activity history on records and field-level permissions, so per the anchors 'duplicates accumulate unchecked' is the documented state of the world. 1
Pipeline & forecasting
Show reasoningHide reasoning
How this is scored
Whether the pipeline enforces a process and produces reporting a finance department accepts.
0 — A kanban of deals with amounts; nothing is enforced, nothing rolls up.
3 — Multiple pipelines and stage probabilities exist, but no required fields per stage and only canned reports.
5 — Stage requirements, win/loss capture and standard forecast views; custom reporting is limited or an add-on.
8 — Enforceable process (required fields, stage gates, routing), custom report builder, forecast by team and period with quota tracking.
10 — Forecasting a CFO signs: weighted and commit-based views, historical snapshots, attainment tracking, and reporting composable enough to answer questions the vendor never anticipated.
The Solo Seller
Customizable kanban pipelines plus forecasting, goals, team monitoring and real-time reports are confirmed, but there's no evidence of stage requirements, gates or win/loss capture — nothing about the process is enforced. 1
The Data Protection Officer
Customizable kanban pipelines plus forecasting, goal-setting, team monitoring and real-time reports get you to standard forecast views. No evidence of required fields per stage, stage gates, win/loss capture or a custom report builder, so I cannot move it to the enforceable-process anchor. 1
The Sales Ops Lead
Customizable kanban pipelines with forecasting, goals and team monitoring are evidenced, which beats canned reports — but nothing confirms required fields per stage, stage gates, or routing, and 'goal setting' is not quota attainment tracking. No enforceable process means no forecast my CFO signs; I interpolate between 3 and 5. 1
The RevOps Integrator
Customizable kanban pipelines plus real-time reports, forecasting, goal-setting and team monitoring are confirmed, but nothing on stage gates, required fields per stage, win/loss capture or a custom report builder. It reads as a good kanban with a report suite, not a process engine a finance team signs off on. 1
The Migrator
Customizable pipelines plus forecasting, goals, team monitoring and real-time reports are evidenced, which is standard forecast views territory. But there is no evidence of stage gates, required fields per stage, quota tracking, or a custom report builder — nothing a finance department would sign off on. 1
The Skeptic
Customizable kanban pipelines plus forecasting, goal-setting, team monitoring and realtime reports clear the 3-bar. No stage gates, required fields per stage, win/loss capture or custom report builder appear anywhere — the entire pipeline story is one block of homepage copy. 1
Automation & workflows
Show reasoningHide reasoning
How this is scored
Triggers, sequences and routing that remove manual work without a consultant.
0 — No automation beyond email templates.
3 — Simple if-this-then-that on records; no multi-step sequences, no branching.
5 — Multi-step workflows with delays and branching, email sequences, basic lead routing — capped by tier or count.
8 — Full workflow builder across objects with webhooks as steps, round-robin routing, sequence analytics.
10 — Automation as infrastructure: versioned workflows, error handling, per-step logs, and limits generous enough that the feature is not its own upsell.
The Solo Seller
The automation flag is true but the only quote describes automated follow-up conversations and AI prompts; multi-step workflows, branching, sequences and routing are all unevidenced — simple-trigger territory at best. 1
The Data Protection Officer
What is confirmed is automated follow-ups, AI-driven prompts and smart-field formulas — if-this-then-that territory. No multi-step sequences, branching, delays, webhook steps or routing are evidenced; the MCP endpoint existing is a hook, not a workflow builder. 1
The Sales Ops Lead
Automation is confirmed only as follow-up automation and AI-powered prompts so leads aren't missed; there is zero evidence of multi-step workflows, branching, lead routing, or webhooks. That is rubric level 3 territory — simple if-this-then-that with a chatbot on top. 1
The RevOps Integrator
The only native automation evidenced is automated follow-ups with AI prompts plus formula-field calculations; no multi-step workflows, branching, routing or webhooks anywhere in the evidence, with sequencing apparently riding on Zapier via the marketplace. Offloading workflow to glue tools is exactly the fragility I reject. 3 1
The Migrator
The only automation evidenced is automated sales conversations, follow-up notifications and AI prompts — a nudge engine, not workflows. No multi-step sequences, branching, routing, or webhooks appear anywhere in the evidence. 1
The Skeptic
The only automation evidence is a sentence about never missing a follow-up thanks to automated conversations and AI prompts — reminder-and-template territory, not even a confirmed if-this-then-that rule builder. No multi-step, branching, delay, routing or webhook capability is on file. 1
Integrations & API
Show reasoningHide reasoning
How this is scored
Two-way email/calendar sync, native connections, and an API that treats external systems as first-class.
0 — No API, no sync; data enters by CSV and leaves never.
3 — One-way email logging (BCC), a handful of Zapier triggers, a read-mostly API.
5 — Two-way email and calendar sync for the major providers, a documented REST API with sane limits, a modest native directory.
8 — Deep native integrations for the revenue stack, webhooks, OAuth apps, API parity with the UI for core objects.
10 — An ecosystem: public API covering everything the UI does, event streams, a marketplace, and sync so reliable the CRM can be the system of record without being the only system.
The Solo Seller
An API, MCP, a 500+ app marketplace and confirmed Gmail email sync are a solid base, but calendar sync, webhooks, OAuth apps and any statement of API depth or limits are missing from the evidence. 3 1
The Data Protection Officer
An API, MCP, and a 500+ app marketplace with Gmail sync carrying a no-ads commitment is genuine breadth. But two-way calendar sync, webhooks and API parity are unevidenced, and from my chair 500+ third-party connections with zero documented subprocessor hygiene is an unmanaged personal-data surface, which caps it. 3 1
The Sales Ops Lead
A documented marketplace of 500+ apps, an API, MCP, and Google account email sync are confirmed, which meets the anchor-5 bar of email sync plus a native directory and documented API. But nothing confirms calendar sync, webhooks, OAuth apps, or API depth and limits, so it cannot go higher. 3 1
The RevOps Integrator
A public API, a 500+ app marketplace including Xero and Zoom, and MCP support is a genuine ecosystem, and Gmail email sync is confirmed through the privacy notice. But two-way directionality, calendar sync, webhooks and API parity are all unevidenced, so I cap it below where a revenue-stack backbone would sit. 3 1
The Migrator
A 500+ app marketplace including Zapier, a named API, MCP, and Google email sync are evidenced, which is real ecosystem surface. But the API is a bare word here — no documented limits, no webhooks, no parity evidence — and those are the details that decide whether exit via API is a weekend or a project, so I won't rate higher. 3 1
The Skeptic
A marketplace with 500+ integrations, named apps (Zapier, Zoom, Xero), MCP support and two-way Gmail sync via the Google scope is a genuinely solid directory. But the API is evidenced by the single word 'API' — no documented limits, webhooks, OAuth app framework or parity claims — so it rises above 5 on breadth alone, not depth. 3 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where other people's personal data actually lives and under whose law — entity, hosting, subprocessors, DPA.
0 — US entity, US-default hosting, no public DPA or subprocessor list.
3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad and undocumented.
5 — EU hosting selectable at signup, published DPA and subprocessor list; core processing still touches US entities.
8 — EU entity or EU-default hosting with published subprocessors, consent-friendly fields, retention and deletion controls; residual US exposure named and narrow.
10 — European entity, EU-only processing including subprocessors, deletion that provably deletes — sovereignty a DPO can sign off without a caveat file.
The Solo Seller
The vendor is Pipedrive Inc. with majority US private-equity ownership, and hosting location, a public DPA and a subprocessor list are all unevidenced — only GDPR-style rights language and backup isolation until deletion in the privacy policy keep this off zero. 3
The Data Protection Officer
Entity jurisdiction, data residency, DPA and subprocessor list are all unknown on the vendor's own pages, while the majority owner since 2020 is a US private-equity firm — and the privacy policy confirms ingestion from commercial data enrichment services, exactly the third-party scraping I reject. Credit for retention deletion/anonymization language and backups isolated until deletion, which is why this is not a flat zero, but a DPO cannot sign off on a vendor whose processing location and subprocessor chain are unverifiable. 3
The Sales Ops Lead
The evidence is silent on legal entity, hosting location, and subprocessors, and no DPA is evidenced, while the vendor sits under US private-equity majority ownership since 2020 — for a Tallinn founding story, nothing here proves where the data lives. The privacy policy offers GDPR/CCPA-style rights and backup isolation until deletion, but rights language is not residency, so this scores near the bottom. 3
The RevOps Integrator
Legal entity, data residency and subprocessor exposure are all marked unknown — 'not confirmed on the vendor's own pages as captured' — majority ownership sits with US private equity, and no DPA or subprocessor list is in evidence. GDPR-style rights and backup-isolation language in the privacy notice keep this off the floor, but a DPO has nothing to sign. 1 3
The Migrator
Everything that matters is unknown: no data residency, no DPA, no subprocessor list confirmed, and the provenance header shows a US private-equity majority owner. The privacy policy does speak GDPR rights and promises backup isolation until deletion is possible, which is the only thing keeping this off a hard zero. 3
The Skeptic
Every sovereignty attribute is unknown: no DPA, no subprocessor list, no data residency, with majority ownership at a US private-equity firm since 2020. The privacy policy reads CCPA-first (opt-out of sale, targeted-advertising rights), admits commercial data enrichment services, and reserves transfer of all personal data to any acquirer — residual US exposure isn't named and narrow, it's the whole picture. 3
Import, export & exit
Show reasoningHide reasoning
How this is scored
Getting in with history intact, and out with everything — the anti-lock-in criterion.
0 — Import is a support ticket; export is contacts-only CSV missing notes, activities and files.
3 — Self-serve CSV import with mapping; export covers main objects but drops activity history, attachments or relations.
5 — Guided migration from major competitors, full-object CSV export, API access sufficient to rebuild the database elsewhere with effort.
8 — Complete export (all objects, history, files) self-serve in open formats, import with dedupe and dry-run, no API metering that prices exit out of reach.
10 — Exit as a feature: documented full-fidelity export, migration tooling both directions, and contractual data-return terms — leaving is a weekend, which is exactly why you can stay.
The Solo Seller
Self-serve import from spreadsheets and other pipeline software is confirmed in a few clicks, but the only portability evidence is a legal right of data subjects, not a product export feature — full export with history and files is unevidenced, so I assume it drops. 3 1
The Data Protection Officer
Self-serve import from spreadsheets and other pipeline software, an API, and a policy-level portability right are the entry pieces. Export of the customer's actual database — notes, activities, attachments, relations — is entirely unevidenced, and a privacy-policy right owed to data subjects is not an exit feature for the account holder. 3 1
The Sales Ops Lead
Self-serve import from spreadsheets and other pipeline software in a few clicks, an API, and a statutory portability right are confirmed — decent on-ramp. But full-object export, activity history, and attachments are completely unevidenced, so exit fidelity is unknown and I hold this between 3 and 5. 3 1
The RevOps Integrator
Few-click import from spreadsheets and other pipeline software is confirmed, and a structured-format portability right is stated in the privacy notice. But there is no evidence of full-object export with activity history, attachments or relations, and the API's export depth is unverified — exit remains an open question, not a feature. 3 1
The Migrator
Import from spreadsheets or another pipeline tool in a few clicks plus a stated portability right clear the support-ticket bar. But the evidence is silent on export scope — notes, activities, attachments, relations — on import dedupe and dry-run, and on API metering; silence on export completeness is precisely the red flag I price in before any migration. 3 1
The Skeptic
Import from spreadsheets and other pipeline software in a few clicks is confirmed, which clears the support-ticket bar. But export is never mentioned as a feature — the only portability on file is a data-subject legal right in the privacy policy, not a bulk account exit, and that silence about leaving is exactly the smell a lock-in hunt looks for. 3 1
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — An entry price exists, but the tiers most buyers need are unpriced, or per-seat maths is obscured by bundles, minimums or mandatory onboarding fees.
5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability hides in an unpriced tier or usage-metered add-on.
8 — Every tier priced publicly including annual/monthly split; limits, seat minimums and overage rules stated; only genuine enterprise contracts are custom.
10 — Complete price computability: every tier, add-on, usage meter and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.
The Solo Seller
A pricing page exists in the registry yet not one price, tier limit, seat minimum or billing term was confirmable — the only public commercial fact is a 14-day no-card trial, so no invoice at any seat count is computable. 2 1
The Data Protection Officer
A pricing page was captured yet produced not a single confirmed price, tier, seat minimum, billing period or VAT treatment — the only public pricing fact in evidence is the 14-day no-credit-card trial. No invoice is computable from this sheet, and a pricing page that yields zero numbers is its own form of opacity. 2 1
The Sales Ops Lead
A pricing page was captured and the trial terms are public (14 days, no card), but not a single tier price, billing period, seat minimum, or limit was confirmed from it. I cannot compute an invoice from this sheet, which lands just above 'no public prices at all'. 2 1
The RevOps Integrator
A pricing page exists in the registry and a 14-day no-credit-card trial is public, yet not a single tier, price, seat minimum, billing split or VAT treatment was confirmed from it. From this evidence a buyer cannot compute any invoice, which fails the entire point of the criterion. 2 1
The Migrator
A pricing page sits in the registry and the 14-day no-card trial is public, yet not a single tier price, limit, billing period, or VAT fact was captured — I cannot compute even a three-seat invoice from this evidence. The 'dedicated account manager' for large teams suggests an unpriced upper tier on top of that. 2 1
The Skeptic
The registry contains the captured pricing page and it yielded not one tier, number, billing period, seat minimum or renewal rule — a pricing page that says nothing is a quote-gate with extra steps. The only pricing fact anywhere is a 14-day trial without a credit card, so no invoice at 3 or 30 seats is computable from public evidence. 2 1
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 21 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity, Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 45 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 22 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 11 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.pipedrive.com Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
- 2 Vendor pricing page www.pipedrive.com Checked 15 Sep 2026 Details →
- 3 Privacy policy www.pipedrive.com Checked 15 Sep 2026 +1 earlier capture: 21 Aug 2026 Details →
- 4 Legal notice www.pipedrive.com Checked 21 Sep 2026 Details →
- 5 Subprocessor list www.pipedrive.com Checked 30 Sep 2026 Details →
- 6 Contact & data model — found from sitemap support.pipedrive.com Checked 1 Oct 2026 Details →
- 7 Contact & data model — found from sitemap support.pipedrive.com Checked 1 Oct 2026 Details →
- 8 Pipeline & forecasting — found from sitemap www.pipedrive.com Checked 1 Oct 2026 Details →
- 9 Pipeline & forecasting — found from sitemap www.pipedrive.com Checked 1 Oct 2026 Details →
- 10 Automation & workflows — found from sitemap support.pipedrive.com Checked 1 Oct 2026 Details →
- 11 Automation & workflows — found from sitemap support.pipedrive.com Checked 1 Oct 2026 Details →
- 12 Integrations & API — found from sitemap www.pipedrive.com Checked 1 Oct 2026 Details →
- 13 Integrations & API — found from sitemap support.pipedrive.com Checked 1 Oct 2026 Details →
- 14 Import, export & exit — found from sitemap support.pipedrive.com Checked 1 Oct 2026 Details →
- 15 Import, export & exit — found from sitemap support.pipedrive.com Checked 1 Oct 2026 Details →