Can Close be vibe coded?
Track deals and manually log communication in a focused sales workspace
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Close, track deals and manually log communication in a focused sales workspace. The hard boundary is built-in email, calling, sms, power dialer, workflows, and sales reliability, plus integrations, data quality, and workflow lock-in.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
high editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Manage contacts and companies in a focused sales workspace, move deals through a pipeline, manually log communication, and surface the next action.
- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- built-in email, calling, SMS, power dialer, workflows, and sales reliability
- automatic email and calendar capture
- data enrichment
- large integration ecosystem
- Years of history, configuration, and habits make migration costly.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
Why people still pay
People still pay for Close because CRM value compounds as the system becomes the shared memory of every customer interaction and embeds itself in the rest of the stack. The recurring cost buys deduplication, permissions, imports, sync, enrichment, email capture, automations, backups, and audit history, not just the visible interface.
Years of history, configuration, and habits make migration costly.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
Reliability at the vendor's scale is an operations problem, not a prompt.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Close
Context
**Close** — Track deals and manually log communication in a focused sales workspace. It currently costs $59/mo.
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Close, track deals and manually log communication in a focused sales workspace. The hard boundary is built-in email, calling, sms, power dialer, workflows, and sales reliability, plus integrations, data quality, and workflow lock-in.
This brief describes a focused, single-operator replacement for the part of Close that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Manage contacts and companies in a focused sales workspace, move deals through a pipeline, manually log communication, and surface the next action.
Build a focused single-user workflow with real persistence, search, and export.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Docker.
PostgreSQL.
Self-hosted server.
Data and integrations
Optional email API credentials.
Each of these needs a real account, credential, or quota. Set them up before writing feature code.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build a closest honest personal substitute for Close in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose; do not offer alternative stacks.
The core loop is: manage contacts and companies in a focused sales workspace, move deals through a pipeline, manually log communication, and surface the next action.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Create contacts, companies, opportunities, notes, tasks, and configurable pipeline stages.
Add fast global search, duplicate detection, merge, CSV import, and CSV export.
Provide a chronological interaction timeline with manual email and meeting logging.
Implement saved views, filters, owner assignment, and a next-action dashboard.
Add role-based access, an immutable activity log, backups, and a recovery command.
Seed a realistic demo workspace and document field mapping for imports.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out automatic mailbox ingestion.
Deliberately leave out commercial enrichment databases.
Deliberately leave out enterprise forecasting, integrations, and compliance.
Finish by running the tests and listing the exact commands used.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Built-in email, calling, SMS, power dialer, workflows, and sales reliability.
Automatic email and calendar capture.
Data enrichment.
Large integration ecosystem.
Years of history, configuration, and habits make migration costly.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
What you still own after launch
Secure credentials, rotate secrets, and handle provider rate limits.
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Maintain every third-party integration as APIs and OAuth rules change.
Risk
**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.
Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[Twenty](https://github.com/twentyhq/twenty) — Active open-source modern CRM with extensible data models
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/close-crm
You still own the product
- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.
Open-source prior art
Before you start
Can Close be vibe coded?
Not faithfully. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Close, track deals and manually log communication in a focused sales workspace. The hard boundary is built-in email, calling, sms, power dialer, workflows, and sales reliability, plus integrations, data quality, and workflow lock-in.
What can an AI coding agent reproduce from Close?
Manage contacts and companies in a focused sales workspace, move deals through a pipeline, manually log communication, and surface the next action. Build a focused single-user workflow with real persistence, search, and export. A responsive interface with real empty, loading, success, and error states.
What will a DIY Close replacement still be missing?
built-in email, calling, SMS, power dialer, workflows, and sales reliability; automatic email and calendar capture; data enrichment; large integration ecosystem; Years of history, configuration, and habits make migration costly.; Connectors, OAuth flows, and vendor API changes require constant upkeep.
What do I still own after building a Close alternative?
Secure credentials, rotate secrets, and handle provider rate limits. Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss. Maintain every third-party integration as APIs and OAuth rules change.