Pipedrive Feature Research (official documentation)
Findings from Pipedrive’s official knowledge base (support.pipedrive.com) and feature/newsroom pages (pipedrive.com), researched 2026-07-07, to ground the Pipedrive-parity features in
project-prd.md(F20–F35, §Reference-System Classification P-04/P-12–P-33). Preserved here so the parity requirements trace to source and the detail survives (the PRD only carries the distillation).Plan-name caveat: Pipedrive is mid-migration between plan schemes — old Essential / Advanced / Professional / Power / Enterprise vs new Lite / Growth / Premium / Ultimate. Some KB articles still use old names. Verify exact gating against the live pricing page before quoting a client.
Parity vs add-on (load-bearing for “nothing lost on transition”): email/calendar/contact sync, leads+import, activities+calendar, deals, pipelines, products, in-CRM email, sequences are base CRM (real parity). Chatbot/Live Chat (LeadBooster), Campaigns, Data Enrichment, LinkedIn are paid add-ons or third-party — Empire is only “missing” them if they pay for them today (→ OQ-23 Pipedrive audit).
A. Email & communication
Email sync (two-way) — → PRD F20, P-12
Centralises email in a Sales Inbox; auto-links conversations to deals/leads/projects; view/send/reply in-CRM. Two mechanisms: Full email sync (automatic both directions) and Smart Email BCC (manual — unique Bcc address drops a copy in; each deal + each lead also has its own Bcc address). Setup per-user (Personal preferences → Email sync); Personal vs Team (shared) account. Providers: Gmail, Office 365/Outlook, Exchange (EWS), any IMAP. Limits: ~40 email actions/min/company; attachment size provider-dependent (Smart Bcc <20 MB); Smart Bcc needs DKIM or SPF. Plan-gated mid-tier+ (“Growth”/“Advanced”+). Confirmed constraint: automated emails send from the individual user’s synced account, not a shared/system address (“Email sync must be enabled to send automated emails”; From = a synced mailbox). If a rep leaves, their automations stop. → Our custom build can send system/automation mail from a shared authenticated sender (an improvement).
In-CRM email + templates — → PRD F20, P-13
Compose/send from a deal/contact or the Sales Inbox. Templates (custom + shareable, plus out-of-box) with merge fields (Fields menu — deal/person/org incl. custom fields, pre-populated per recipient). Group email ≤100 recipients w/ ~30s spacing. Open + link tracking (real-time notifications). Scheduled send. AI “Write my email” present in composer (not in group email).
Open and link tracking — how it works and its limits (added 2026-11-16, F20-g) — → PRD F20, F20-g
Read on 2026-11-16 from Pipedrive’s help pages Email tracking and Email tracking reports with Gmail and Apple (both last updated 2026-09-03). A dated observation: re-read the pages before relying on a detail.
- Opens: Pipedrive adds a small, invisible tracking image to the email, and counts an open when the recipient’s mail program loads it. F20-g works the same way.
- Clicks: the pages say link tracking does not rely on images, so it still works when images are blocked. They do not say how links are rewritten or which domain they pass through; from the mechanism, a click must reach Pipedrive’s server before the real page, as in F20-g. Not confirmed from a Pipedrive-sent email.
- Turning it on: a per-user default in Personal preferences › Email sync (separate options for opens, for link clicks, and for alerts), and two per-email icons in the composer (an eye for opens, a cursor for links) that change it for one email. The pages do not state the default. Tracking applies only to emails sent from Pipedrive, chosen before sending.
- Where it shows: the eye and cursor icons turn solid in the Sales Inbox, with the time on hover; a notification per open or click when alerts are on; stats on the linked deal, lead, person and organization; open data in the Insights email reports.
- Limits Pipedrive admits: an open is not counted when the recipient’s mail program blocks images; Apple Mail Privacy Protection (iOS 15, macOS Monterey and later) means Pipedrive “can’t provide any tracking information” for those emails; Gmail caches images on its own servers, and opens are not counted when automatic image loading is off; viewing the email in your own Sent folder in an outside mail program can count a false open; with several recipients it cannot tell which one acted; forwards are not tracked. Link tracking is described as unaffected by these policies.
- Consent: Pipedrive says it is the data processor and its customer the data controller, who decides whether consent is needed and collects it. The page notes that EU data-protection authorities have said email tracking needs the recipient’s opt-in, citing the French (CNIL) and Italian (Garante) regulators, and advises legal advice. No consent feature for one-to-one emails is described.
- Compared with F20-g: the same image for opens, click tracking through the server, and the same limits (F20-g spec decision 10, “Opens and clicks are estimates”, which the CRM states in the label’s hover text). F20-g differs in having one Track Opens and Clicks box for both, ticked on every email, with no per-user default and no alert on an open or click.
Email sequences — → PRD F25, P-14
A sequence = repeatable multi-step cadence for deals/leads mixing email steps + activity/task steps. Max 10 steps; ≤250 items enrolled; a sequence locks to deals-only or leads-only once first used; automated email steps can’t be edited after set. Uses templates in steps. Enrollment manual, via detail views, bulk list, or auto-enroll via Automations. AI email composer available for step emails. Plan-gated mid-tier+.
Email campaigns (Campaigns by Pipedrive) — → PRD F28 (Deferred, add-on)
Dedicated email-marketing/newsletter product (paid add-on). Drag-drop editor, import HTML, free templates. Subscriber management (contacts need “subscribed” marketing status; consent via web forms; double opt-in). Segmentation by campaign data/interactions/status. Analytics (open/click/CTR, bounces, per-recipient; Premium adds campaign-type + comparative insights). Volume-based pricing (1k–50k subscribers, slider; ~$13–39/company/mo range). Two add-on tiers (Standard/Premium). No documented in-editor AI writer.
AI email (writer / summarization / agentic) — → replaced by Claude (PRD P-21)
- AI email creation (“Write my email”): keywords + tone (Professional/Formal/Friendly) + length (Short/Standard/Long); Professional+; not in group email.
- AI email summarization: thread → summary + sentiment + “readiness to buy” (1–10) + action items; beta, Professional+; caps 50/day, 10/30-min; admin-enabled; accept AI Beta ToS.
- Agentic email (2026 newsroom): pilot/beta agent that drafts personalized mail, summarizes threads, explains wording, flags urgent mail. Built on OpenAI + proprietary engines. Beta/limited.
Empire twist: our AI is Claude, tea-domain, HITL, pricing-omitted — replaces all of the above with domain context Pipedrive’s generic AI lacks.
B. Sync & data
Calendar sync (two-way) — → PRD F21, P-15
Connect Google / Microsoft 365 / Exchange-Outlook calendar; one-way or two-way (edits sync both directions). Per-user (Personal preferences → Calendar sync → OAuth). Choose which activity types sync + visibility of external events. Limits: only future events sync (no backfill); recurring activities can’t be edited in Pipedrive; calendar view shows ≤500 activities; syncs only the user’s own activities. IMAP/POP not supported. Native; not gated like email sync (marketed “free”).
Contact sync (auto-pull) — → PRD F22, P-16
Auto-sync external contacts from Google/Outlook.com/Microsoft 365 into People (no one-by-one add/import); one- or two-way; choose contact group. Requires “add people/organizations” permission. De-dup caveat: the same contact held by two users creates two records (no cross-user merge). Visibility granularity plan-gated (finer options Premium+). Native.
Spreadsheet import (CSV/Excel) — → PRD F23, P-17 (+ migration F4)
Import People/Orgs/Leads/Deals/Projects/Activities/Notes/Products. Flow: file info → upload → map fields (auto-match by header; create custom fields during mapping) → preview → finish (merge duplicates or create new). Each row links all data it contains (person + org + deal in one row → all created/linked). Missing deal/lead titles auto-generated. File types XLS/XLSX/CSV (+ Google Sheets, CRM migration); ≤50,000 rows, <50 MB. Native, ungated.
Data enrichment — → PRD F29 (Deferred, add-on + 3rd-party)
One-click fill of empty Org/Person fields (org: address, industry, employees, revenue, website, LinkedIn URL; person: phone, email) from public web data. Manual trigger (single or bulk ≤100); only empty fields filled. Credit-based (org 1 / email 2 / phone 5 per record). Premium = org only; Ultimate = org + person. Underlying data is third-party — Pipedrive’s own pages disagree on provider (Surfe/Growster SAS per KB vs RightBound per marketing) — flag to verify.
Empire twist: an AI/tea-aware enrichment (infer likely market + required certs from a buyer) beats generic firmographics.
LinkedIn — → PRD F30 (Deferred, NOT native)
Pipedrive has no native LinkedIn connection. All LinkedIn functionality is third-party marketplace apps: Surfe (add LinkedIn contacts one-click, sync LinkedIn messages, export Sales Navigator lists; Chrome extension), Outfunnel LinkedIn Lead Gen Forms Sync (form submissions → contacts/leads/activities), plus LeadCRM/LinkMatch/ReachOut. Not a parity requirement — net-new enhancement only if Empire uses a LinkedIn tool today.
C. Core CRM objects & engagement
Leads / Leads Inbox — → PRD F11, P-05
A Lead = unverified/prequalified opportunity in the Leads Inbox, kept out of the pipeline (does not contribute to forecast) until converted. Add via green “+ Lead” (must link a Person/Org; other fields optional); also from Web Forms/Chatbot/Prospector/import/API. Convert to deal from the lead’s contextual view (or bulk); deals can convert back to leads. Core on all plans.
Activities + calendar side-view — → PRD F3 + F21
Activity = “any scheduled action to close a deal”. Default types Call, Meeting, Task, Deadline, Email, Lunch + custom types. Schedule on a deal/lead (auto-links the deal’s person+org). Activity Calendar: day/week/list views; left rail of activity-type filters; drag-to-reschedule; synced external events show alongside; Scheduler meeting-booking (Zoom/Teams/Meet). Core (calendar sync/Scheduler richer on higher tiers).
Creating pipelines — name + probability + rotting — → PRD F24, P-04/P-18
Deal-admin creates pipelines: “+ New pipeline” → name + stages (pencil editor; “+” between stages to insert). Per-stage config:
- Stage probability = likelihood a deal in that stage is WON (0–100; default 100). Produces the weighted forecast (a $10k deal in a 40% stage = $4k expected). Best practice: rising probability per stage.
- Rotting = idle-deal flag: a deal untouched longer than the stage’s “Rotting in (days)” turns red; clock resets on: mark activity done, add note/file, email action, or edit deal details. Per-stage thresholds. Limitation: rotting ignores future scheduled activities. Unlimited pipelines on every plan. Pipelines are stored/managed separately (can’t merge into one board).
Decision (2026-07-07): our build is admin-configurable (stages/probability/rotting) seeded with the two tea pipelines as editable defaults. Risk R-14: keep a stable stage-type mapping under the display name so AI/automations don’t break on renames.
Adding a deal — → PRD F2, P-03
Deal fields: Title (required), Value + Currency, Owner, Person and/or Organization, Pipeline + Stage, Expected close date, Label(s), + custom fields. Add via “+ Deal” (pipeline/forecast/list), “+” in a Person/Org, or import (deal-title column). Assign to a pipeline+stage; drag between stages/pipelines (movement resets rotting).
Products — → PRD F26, P-19/P-20
Products catalog (all plans): “+ Product” (name required); fields — unit price (per currency; multiple price variations), product code, unit, tax %, cost per unit (notational), category, description, owner, active, + custom fields. Attach to a deal via “+ Products” with quantity + discount (amount/%); per-deal price override doesn’t change the catalog; ≤1,000 products/deal; line items roll up into deal value. Smart Docs (quotes from product data) = Professional+/add-on.
Empire extension (gated on OQ-20 for brand): grade, origin, held certifications → feeds F9 cert-mismatch + F7 quote line items.
Chatbot & Live Chat (LeadBooster) — → PRD F27 (Deferred, add-on)
Part of the LeadBooster paid add-on (bundles Chatbot, Live Chat, Prospector, Web Forms + Scheduler; addable to any tier; Web Visitors separate). Chatbot = website widget running a scripted playbook (templates: Get more leads / Book meetings / Qualify & route / Chat with leads); embed via code snippet; qualified leads land in Leads Inbox. Explicitly NOT AI — “relies on customizable conversation flows the user creates”, not ML/NLP. Live Chat = human handoff (unassigned → assign-to-me; online/offline; inbox folders).
Empire twist / differentiator: build a Claude-powered chatbot that understands tea inquiries (grade/volume/certs/market) → structured lead into F11, with live-chat handoff — something Pipedrive’s own bot can’t do. Empire has a website not currently using chat capture.
Sales goals — → PRD F35 (Deferred, audit-dependent OQ-29)
Pipedrive Goals track rep/team targets vs actuals (revenue, deals won, activities), period-based. Promote to V1 only if the audit shows Empire uses Goals today.
D. Parity items added to the PRD from this research
F20 email-in-CRM (P0), F21 calendar+sync, F22 contact sync, F23 import/export, F24 configurable pipelines (probability+rotting), F25 sequences, F26 products catalog, F31 global search, F32 list views/filters/bulk actions, F33 file attachments, F34 admin custom fields; Deferred (audit-dependent): F27 chatbot/live chat, F28 campaigns, F29 enrichment, F30 LinkedIn, F35 sales goals.
E. Two Pipedrive limits our custom build removes
- Automated/sequence email can only send from an individual rep’s mailbox → our build supports a shared authenticated sender.
- Pipedrive’s chatbot is rules-only (not AI) → our F27 would be Claude-powered.
F. To verify with Pipedrive directly (thin in docs)
Exact plan-tier gating per feature (naming inconsistent across KB); enrichment data-provider (Surfe vs RightBound); exact enrichment credit allotments per plan; LeadBooster/Campaigns current pricing.