What is a CRM framework?

The definition, and the line it draws

A CRM framework is a body of source code that a development team builds a customer relationship management application on top of. It provides the mechanics every CRM needs — a way to declare records, persist them, mutate them through services, run multi-step workflows, apply business policy and expose an API — and it deliberately does not provide the finished CRM. The domain (what a lead is, when a discount needs approval, what happens after a deal is won) is the application author's to write.

The line this draws is between configuring and programming. A CRM product — hosted or self-hosted — is configured: custom fields, automation rules, permission sets, all expressed inside the vendor's runtime and only meaningful there. A CRM framework is programmed: the output is an application in the team's own repository, reviewable in a diff and owned outright. 'CRM for developers' can mean either a product with a good API or a framework; the two are different categories, and the test is what you are left with if the vendor disappears — an account export, or a codebase.

'Open source CRM framework' adds a licence to that, not a capability. It says the framework's source may be read, changed and kept under the stated terms. It does not say the result is deployable, secure or complete, and a licence page is not an architecture page.

How Accordo implements the term

Accordo's unit of composition is a module manifest: the author declares a record's fields once, and the framework turns the declaration into a migration, a service, a REST resource, an SDK method and Admin screens, with no page code written by hand (C-01). Business behaviour is not generated — services, workflows and policies stay explicit, reviewable source, which is the property that makes the framework usable by a coding agent under human review.

Domains larger than one record live in packages. A customer-authored domain package attaches with one static import and detaches with the kernel's fingerprint unchanged, reaching other packages only through capabilities it declares (C-13) — so extending the CRM means adding a package, not forking a platform. Every mutation in the composed application goes through a module service or a named workflow and leaves an audit event and a step-level trace behind it (C-16).

The dependency posture is part of the definition here: Node 22, its built-in SQLite adapter, its built-in HTTP server and test runner, and one pinned pg@8.23.0 driver if you select PostgreSQL — no ORM (C-17). That is a property of the framework, not of your application; the next library you add is yours to carry.

Open source, with the distribution mechanics stated

The licence is MIT, confirmed by an ADR rather than assumed, and it covers this framework only — it decides nothing about the licence of the applications generated with it, which belong to their authors. That is the 'open source CRM framework' reading in full: source you may keep, read and change.

Distribution is narrower than the phrase usually implies, and this site states it rather than letting a reader discover it: what installs from npm is a scaffolder, not the framework. `npm create accordo` — the published `create-accordo@0.1.0` — scaffolds a working project by copying the framework source into it, and the same bootstrap runs from a checkout of this repository. Either way the framework is vendored into the project — so upgrading means merging changes into a copy, not bumping a version (L-08).

What the term does not buy

Being a framework does not make the output deployable, and this one is explicit about it. No authentication ships, so a deployment must supply the verifier (L-01); persistence supports SQLite and dedicated-database PostgreSQL (L-02); the managed Cloud hosts only Blueprint-configured workspaces — the framework's output is an application in your repository that you run (L-07).

Being a framework also does not make it measurably better than the alternatives. No benchmark has compared building on Accordo with building from scratch or with adopting a product: the build benchmark protocol is published and has not been run, so any number quoted for this project is not ours (L-03).