CRM and sales decision
Zatten
A competent developer can reproduce a useful subset (CRM + WhatsApp + basic AI orchestration) using existing open-source CRM projects, but matching Zatten's end-to-end product polish, Meta template relationships, and operational integrations is non-trivial — keep paying if you need the full managed experience.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off136 h to build
$200/mo6 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Zatten alternatives, with the arithmetic →
What a replacement has to do
- Receive WhatsApp messages via Cloud API → AI agent processes message and may update CRM/pipeline → send reply or escalate to human → log actions and metrics → run campaigns/templates via Cloud API.
What it still won’t have
- Pre-approved Meta templates, established template approval workflows and operational relationship with Meta
- Mature, niche-validated conversation templates and industry-specific agent templates
- White-label polish and onboarding flows that reduce client setup to minutes
- Customer support, SLA, and product updates from a vendor operating at scale
What remains hard
- Execution quality
Setup em 5 min 5 minutos. Do zero à plataforma no ar.
First-year cost
No published price
Zatten does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted Zatten-like service using Node.js (NestJS) + Postgres + React (Vite) on Docker. Core features in scope: (1) WhatsApp Cloud API integration (webhooks, send templates, message status), (2) Postgres CRM with leads/contacts/tags and Kanban pipeline UI, (3) AI agent orchestration service that runs prompt templates, records action logs, and exposes actions to read/write CRM, (4) campaign/template management UI with per-contact delivery/read metrics, (5) white-label settings (custom logo, colors, custom domain), (6) RBAC with departments and notifications and human handoff that pauses AI. Out of scope: multitenant billing, built-in Meta template approval automation, advanced analytics dashboards. Include input validation, error handling, request retries for external APIs, basic unit and integration tests, Docker Compose manifests for local dev, and deployment instructions for a single VPS (Docker).
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productZatten — official product
- open sourceArnasDon/wacrm
- open sourcekrayin/laravel-crm
Integrity checks
What held up, and what did not.
