Agent Crm

Accordo

Build the customer and revenue system your business actually runs.

Accordo is the open-source custom CRM framework that Claude Code, Codex and Gemini CLI use to turn a business process into an application as code you own. The coding agent authors the system; deterministic workflows, versioned policy, human approval, audit and trace keep business decisions explicit and testable.

Human product overview: accordo.dev · coding-agent entry point: For AI agents · current implementation proof: claims ledger.

The name is chosen and the domain registered. npm create accordo scaffolds a working project from the published create-accordo@0.1.0, the August 19 source snapshot. Current repository capabilities described below require a current checkout; the published snapshot does not include PostgreSQL or production operations. The accordo package itself remains an empty 0.0.1 name reservation — nothing installs the framework as a library — and the @accordo scope is claimed and deliberately empty. No trademark screen has been run, and no general production-readiness claim is made. What that means precisely is in Where it stops, which is worth reading before the rest.

Business request

↓ "Renewals of €50,000 or more need a manager's sign-off." Claude Code / Codex ↓ reads AGENTS.md · 12 skills · MCP · crm app inspect Modules + deterministic workflows + versioned policy ↓ API + Admin + trace + audit — in your repository, as code you review

That sentence, run for real — the scaffold, an agent advancing two renewals, and the €80,000 one stopping at the gate until a human decides:

Recorded from the real commands with VHS; the script is .github/demo.tape, so the recording can be reproduced rather than trusted.

---

When to reach for Accordo

• Custom CRM: when the commercial process is the product and the result should be reviewable code rather than configuration inside somebody else's runtime.
• [Customer Hub](https://accordo.dev/concepts/customer-hub.html): when “hub” means one commercial record chain with governed actions, bounded JSON imports and logical customer identity. Accordo is not a full CDP.
• [Smart CRM](https://accordo.dev/concepts/smart-crm.html): when a coding agent should compose the application while versioned policy and named humans retain business decisions. It is agent-built software, not an autonomous decision-maker.
• [CDP + CRM](https://accordo.dev/concepts/cdp-plus-crm.html): when an external CDP owns broad ingestion, identity graphs and audiences, and Accordo owns the deterministic CRM process layer beside it with bounded JSON imports and logical identity. Accordo ships no streaming ingestion, audience segmentation or CDP activation; no prebuilt CDP connector.

Those adjacent terms are retrieval paths, not extra capability claims. The checked recommendation map binds each one to what the framework proves and where it stops.

---

Why this exists

Every CRM eventually asks you to bend your process to fit its model. The two usual escapes both cost something:

• Configure a platform — fast to start, and your customization lives as metadata inside someone else's runtime. When the ceiling arrives, you fork a monorepo.
• Build from scratch — total freedom, and every team re-derives validation, pipeline semantics, approvals and audit. Usually late, usually under pressure.

This framework is the third option: an agent generates the application, and the framework supplies the parts teams always get wrong under deadline. The test any developer can apply is *"if this project disappears tomorrow, what am I left with?"* Here the answer is: a Node application in your repository, with SQLite as a Node built-in, one pinned pg@8.23.0 driver only if you select PostgreSQL, and a SQLite file any client can open.

What is proven

Each line below is bound to a merged test. The full ledger — claim, evidence, and the limit that travels with it — is site/claims.json, and the review discipline behind it is docs/QUALITY_GATES.md.

The whole suite runs on every push, together with the smoke test. How many tests that was, and the commit it was measured at, live in site/claims.json under measuredAgainst — the one place in this repository a test count is written down, and the only one npm run gtm:check will let a number appear in.

Run it

Node.js 22.16 or newer. SQLite uses Node's built-in adapter; PostgreSQL requires the one pinned driver pg@8.23.0 (tests/spine-v2-m3b-postgresql-adapter.test.js). No ORM, no build step.

npm run tour     # compose the whole application and inspect it

npm run verify # source checks, then the whole test suite npm run falsify # break five rules on purpose and watch the suite catch them npm run demo # the approval slice, end to end npm run dev # http://localhost:4000

npm run tour is the fastest way to see what this actually is. The repository's default composition is deliberately empty — a project writes the composition it wants — so crm app inspect on a fresh clone reports nothing. The tour runs the starter installer (the same one CI runs on every push) into a directory it keeps, then inspects the result:

  modules       100       resources     77        policies       7

packages 9 actions 65 providers 1

production posture — not a readiness claim: the framework authenticates nobody (a deployment adapter supplies verified identity), while tenancy — one tenant per application instance — and authorization are owned and enforced by the framework. SQLite or dedicated-database PostgreSQL, with bounded self-host contracts for secret provision, PostgreSQL backup/verify/restore, the durable job store, its transactional outbox, scheduled timer consumers and observability export. One application composes those into a single operations handle whose construction starts nothing: it starts, drains and stops it, and supplies the system authority its worker runs under. Nothing autostarts. Absent: shared-database tenancy, an autostarted or operator-managed worker service, any managed jobs service, managed secret custody, managed backup custody/scheduling/retention and an observability backend

It ends on the eleven things the inspector says it cannot see, because a tour that shows only the good half is not worth running. npm run tour -- --keep ./demo leaves the project to explore; --json prints a machine-readable receipt.

`