Atomic CRM Builder

Building a custom CRM from scratch demands both domain knowledge and technical expertise. Atomic CRM Builder lets non-developers design, build, and customize a CRM tailored to their domain using plain-English instructions.

It uses Atomic CRM as a starting template and orchestrates a team of AI agents specialized in CRM development, powered by Claude Code. Everything runs in a containerized environment to keep execution secure and isolated. The resulting CRM is built on Supabase, React, and Shadcn.

Quick start

Prerequisites

• Docker Desktop installed
• A valid Claude Code subscription or an Anthropic API key: console.anthropic.com

1. Build (once, ~5 min)

docker build -t atomic-crm-dev .

2. Launch the builder

make up

# First-time login:
# Run this from another shell — the stack pauses on first boot waiting for
# credentials, and resumes automatically once login completes.
make claude         # OAuth flow on first run — copy URL to browser, paste token back

3. Stop and Restart

make down        # Keep your code changes between sessions
# or
make wipe        # Full reset — deletes volumes (loses code changes)

Usage

Once started, open http://localhost:8080 to get the builder UI. The content frame displays the CRM, ready to test. The sidebar shows your build session history. To start customizing, click "New Session" to open a chat interface and prompt the assistant. It will ask follow-up questions if needed, then modify the CRM autonomously and test its changes. You can use the content frame at any time to try the modifications yourself.

The builder UI also lets you run multiple sessions in parallel, browse session history, switch between frontend-only and full-stack mode, and download the modified code.

Other useful urls:

• http://localhost:5173: The CRM
• http://localhost:54323: The Supabase Dashboard (full mode only)

For a direct, interactive Claude session in the builder, run from your host:

make claude         # opens `claude --dangerously-skip-permissions` in the container
                    # (also triggers OAuth on first run if ANTHROPIC_API_KEY is unset)

Container Isolation

The entire stack runs in a docker container:

• The CRM (database, server functions, and frontend)
• The builder UI (chat interface, stats, real-time notifications)
• The Claude Code session

This allows to run Claude with --dangerously-skip-permissions, and avoids asking technical confirmation to the end user (who is not technical).

Custom Harness

The builder runs on a custom harness: a team of agents specialized in CRM development (orchestrator, architect, developer, reviewer, documentarian, etc.), along with dedicated skills, rules, and hooks. You can explore the harness setup in .claudeConfig/.claude.

The harness will use a single agent for simple modifications, and spawn a team for more complex ones.

Note: The harness uses claude -p. This means the tokens are charged as API calls.

Recommended workflow

1. Start the app in demo mode (frontend-only, mocked backend)
      ↓
2. Chat with the assistant to add features
      ↓
3. Validate in the browser on test data
      ↓
4. Claude develops the backend, generates and applies the Database migrations
      ↓
5. Validate in the browser on real data

Here is an example:

Phase 1 — Fast dev in demo mode

You:
  "Add a 'priority' field (low/medium/high) on contacts
   with a coloured badge in the list"

Assistant:
  → Spawns a dev team in an isolated git worktree
  → Edits ContactList.tsx, ContactEdit.tsx, types.ts
  → Reviews, validates, merges to main
  → Vite hot-reloads the browser

Validate visually on localhost:5173.

Phase 2 — Promote to your real database

When a feature changes the data shape, the assistant writes the SQL into supabase/migrations-pending/ (invisible to Supabase CLI) and, once the dev wave is merged, asks for permission in plain language:

Assistant:
  "Some of these changes affect how your data is stored.
   Want me to apply them to your real database now?"

You: "yes"

Assistant:
  → Promotes the file from supabase/migrations-pending/
    to supabase/migrations/ (one commit on main)
  → Starts Supabase if needed and applies the migration

(if you are still in demo mode)
Assistant:
  "Your real database is up to date. Want to switch the app
   over to your real data now?"

You: "yes"

Assistant:
  → Switches the data provider to Supabase — Vite hot-reloads

You can also toggle modes yourself at any time: one click on the mode badge in the chat header, or switch-mode demo / switch-mode full from make claude.

What works in demo vs full mode

Feature	Demo mode	Full mode
UI components, forms	✅	✅
New fields, views	✅	✅
Filters, sorting, pagination	✅	✅
Response speed	✅ (instant, in-memory)	⚠️ (network round-trip, migrations)
Data persistence	❌ (reload = reset)	✅
Real authentication	❌	✅
File attachments	❌	✅
Security policies (RLS)	❌	✅

Roadmap

• Easier install
• Automated deployment to supabase.com and Cloudflare pages
• Automated UI tests

License

MIT