CRM

Pipedrive

EU origin, foreign-owned Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Solo Seller v1.2 · The Data Protection Officer v1.0 · The Sales Ops Lead v1.0 · The RevOps Integrator v1.0 · The Migrator v1.1 · The Skeptic v1.2 · rubric v1 · evaluated 16 Sep 2026

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 Sales Ops Lead

Weighted verdict

Owns the forecast a 40-seat team lives by. Optimizes for pipeline discipline: stage hygiene, required fields, routing, quota and forecast reporting the CFO will accept. Rejects freeform pipelines that cannot enforce a process and reporting that stops at a dashboard screenshot.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Sales Ops Lead

Contact & data model

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.

Report an error

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

Report an error

Pipeline & forecasting

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.

Report an error

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

Report an error

Automation & workflows

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.

Report an error

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

Report an error

Integrations & API

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.

Report an error

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

Report an error

European sovereignty

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.

Report an error

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

Report an error

Import, export & exit

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.

Report an error

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

Report an error

Pricing transparency

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.

Report an error

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

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built 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

Do you know more about Pipedrive? Tell us Report an error on this page

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 →