CRMCAN I VIBECODE
Pipedrive?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Pipedrive is a sales CRM centered on visual pipeline management, founded 2010 (Estonia) and now operated under Vista Equity Partners. Core workflow: reps drag deals through customizable kanban-style pipeline stages, logging value, win probability, and expected close date, then track next steps via activities, tasks, and reminders. Users manage contacts/organizations, sync up to five email accounts for two-way email, schedule calls with meeting links, and capture leads via web forms. Automation covers workflow templates, lead-routing rules, and email-interaction-triggered follow-up sequences. Reporting includes goal tracking, funnel conversion, dashboards, revenue forecasting, and an AI Sales Assistant that predicts win/loss likelihood. The platform offers 500+ marketplace integrations, REST API, mobile apps, AES-256 encryption, SOC 2 compliance, and GDPR posture; a 14-day free trial is a
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a focused replacement for the core Pipedrive workflow: a web-based sales pipeline CRM where reps manage deals on a kanban board. Do not copy Pipedrive's brand, logo, color palette, marketing copy, or pixel-level UI; create an original visual design that merely fulfills the same workflow.
Workflow to implement: a rep creates or imports a deal (title, value, win probability, expected close date, linked contact/organization, custom fields), drags it across user-defined pipeline stages as the sale progresses, and logs next-step activities (call, email, meeting) with due dates and reminders. A separate Contacts/Organizations directory holds entities with de-duplication/merge affordances. A simple rules engine triggers actions (move stage, reassign, create activity, send a webhook or templated email) on deal-field or stage changes. Dashboards show funnel conversion by stage and a revenue forecast chart (weighted sum of deal value × probability grouped by expected close month).
User-facing requirements: drag-and-drop board with optimistic updates, deal detail drawer with activity timeline and notes, activity scheduler with reminders and a basic calendar view, lead-capture web form hitting a public endpoint that creates deals, role-based access (admin/user), CSV import/export, and a demo account with seeded data.
Technical requirements: React front end with dnd-kit; Node/Express or Python FastAPI API; Postgres persistence; Redis-backed reminder queue; WebSockets for real-time board updates; JWT auth; webhook outbox for external integrations; Docker Compose for local setup; unit tests, especially for the rules engine and forecast math.
Deliberately out of scope: real IMAP email sync (provide a pluggable adapter interface with a mock), mobile apps, billing/quota system, marketplace of 500 integrations (ship 2–3 webhook examples instead), native calling, and any AI assistant beyond optional simple win/loss heuristics.
Include a README covering setup, environment variables, seed/demo credentials, architecture overview, and important limitations (e.g., no real email transport, reminder delivery is best-effort, forecast ignores seasonality).