Pipedrive CRM Research Notes
Date: 2026-06-17
Context: Empire Teas currently uses Pipedrive. We need to decide whether to optimize, extend, integrate, or eventually replace it.
Summary
Pipedrive is a sales-first CRM centered on visual pipelines and activity-based selling. It appears suitable as the CRM foundation for Empire Teas if configured around their export/private-label workflow rather than used as a generic deal board.
Relevant capabilities
- Leads, deals, people, organizations, activities, projects.
- Custom sales pipelines and stages.
- Custom fields for customer/product/compliance attributes.
- Email sync and centralized communication history.
- Workflow automations using if/then logic.
- Event triggers: create/update/delete for deal, person, organization, activity, lead, project.
- Date triggers for follow-ups, renewals, deadlines, etc.
- Actions: create/update entities, send emails, add notes, use webhooks, integrations.
- Conditions, if/else branches, and wait conditions in automation.
- Webhooks and REST API access.
- OAuth 2.0 / API token access depending on integration model.
- Marketplace with 500+ integrations.
- Common integrations: Zapier, Slack, Microsoft Teams, Trello, Asana, Mailchimp, PandaDoc, Zoom, QuickBooks.
- AI features: AI sales assistant, email writer/summarizer, AI reporting.
Why it matters for Empire Teas
Pipedrive can likely support:
- Export sales pipeline.
- Private-label inquiry tracking.
- Sample request follow-up.
- Quote stage tracking.
- Customer/account history.
- Trade fair lead capture.
- Activity reminders.
- Basic owner-level sales dashboards.
- Integration with ERP when a deal becomes an order.
- AI-assisted email/brief generation through custom extensions.
Possible gaps
Validate with the client:
- Does Pipedrive model sample requests well enough?
- Can it represent private-label product development without becoming messy?
- Are quote details/pricing handled in CRM, ERP, Excel, or elsewhere?
- Are teams actually using activities and email sync consistently?
- Are custom fields standardized or ad hoc?
- Does management trust CRM reports?
- How will new ERP integrate with CRM?
- Are native Pipedrive AI features enough, or do they need domain-specific AI?
Recommended stance
Do not recommend replacing Pipedrive yet. First perform a Pipedrive audit and classify issues:
- Configuration problem.
- Process/adoption problem.
- Integration problem.
- Genuine product limitation.
- Data quality problem.
Only consider replacement after this classification.
Integration opportunity
Pipedrive’s API/webhooks make it a good anchor for an automation layer:
Pipedrive event
→ webhook/API middleware
→ AI extraction/summarization/workflow logic
→ human review
→ update Pipedrive / notify team / hand off to ERP
Initial automation candidates
- New email/inquiry → structured lead/deal + draft reply.
- Deal enters “sample requested” → create sample checklist and owner activities.
- Quote submitted → follow-up reminder and quote aging dashboard.
- Deal won → ERP handoff checklist.
- Dormant customer → reactivation task.
- Trade fair lead upload → lead enrichment and prioritization.