Odoo's CRM app, or one custom process as code you own?

Where Odoo wins

It is a suite, and CRM is one app inside it: the CRM arrives attached to the rest of the business system rather than as something you integrate later. The research file records a community edition under LGPL, deployment on Odoo.sh or self-hosted, a monorepo at roughly 53.5k GitHub stars as of August 4, 2026, and a target buyer running from SMB to mid-market — a buyer with a purchase order, not a repository. Its summary of the position is blunt and worth repeating rather than softening: Odoo owns the self-host SMB buyer, not the developer builder, and this project does not compete for that buyer directly.

Against this framework's own ledger the asymmetry is not subtle. No authentication, tenancy or RBAC (L-01). No email, calendar or marketing integration — a notification provider contract exists and no adapter sends anything to anyone (L-05). No import, export, dedupe, merge, bulk edit, saved views or global search (L-06). No hosted product to sign up for; the output is an application in your repository (L-07). And you cannot put real customer data in this yet: with no export and no erasure path, a data-subject access or deletion request cannot be serviced at all (L-09). If a sales team is meant to log in on Monday, that list is the whole answer.

Pipeline reporting is the same story in miniature. Reporting pipeline is recorded here as partially supported, not as a feature: there are no saved views, no dashboards and no report builder to hand to a sales manager.

Where this is different

Licensing shape. The research file records Odoo as the canonical open-core case — LGPL community alongside a proprietary Enterprise edition, with Studio, mobile and AI gated, and it notes from a secondary source that all AI features are Enterprise-only as of v19. That hedge travels with the claim: it is secondary-sourced there and it stays secondary-sourced here. This repository is MIT, one edition, nothing gated (ADR-023). The counterweight is the same one as everywhere else on this site: nothing is gated partly because there is not very much to gate, and none of the absences above carries a delivery date.

Customization model. The file describes Odoo customization as Python modules written in their framework idiom, and calls it upgrade-fragile, with no agent substrate for building — AI there is an Enterprise UI feature rather than a way to author the system. Here customization is the deliverable rather than a tolerated extension: a customer-authored package attaches and detaches with the kernel's fingerprint unchanged and reaches other packages only through declared capabilities (C-13), and generated modules evolve through explicit revisions and append-only named migrations rather than rewritten history (C-19).

What the process holds while it runs. Commercial policy is deterministic code rather than a model's judgement, and a renewal at or above the threshold stops and waits for a named human (C-03). The same refusal holds where the money is: an agent actor asking to approve a discounted quote is rejected with a 403 and code HUMAN_APPROVAL_REQUIRED, and only a human user actor can decide (C-21). That refusal is asserted by a test rather than promised in a README (C-04), and every mutation leaves an audit event and a step-level trace behind it (C-16). This is not a longer feature list than a suite's. It is a much shorter one that can be accounted for line by line.

How to choose

Choose Odoo if you are buying a CRM rather than building one — especially if you also need the rest of the suite around it, if it has to be running this quarter, if configuration by an admin or an implementation partner is how customization is meant to happen at your company, and if the Enterprise gating fits your budget.

Choose this framework in the narrow case: one commercial process specific enough that no suite app fits it, which must live as reviewable code in your repository, where a coding agent does most of the writing, and where you can supply authentication, hosting and data governance yourself — because this supplies none of them.

If both are true — you already run a suite and one process does not fit it — these are not mutually exclusive and this page does not argue that they are. It does have to say that no integration exists in this direction: there is no integration runtime, no adapter and no import, so connecting the two is engineering work you would own (L-05, L-06).

What this comparison does not cover

Nothing was installed or run. Every Odoo fact traces to docs/strategy/COMPETITOR_MAP.md, researched on August 4, 2026, and this environment has no network access to check any of it.

No feature comparison. That file does not enumerate Odoo's CRM features, so this page cannot and does not — no statement is made about its pipeline, its reporting, its mobile app or its AI features beyond the licensing note above.

No pricing. The file carries no Odoo price, so this page carries none either, and the Enterprise-only-AI point is repeated with the same secondary-source hedge it was recorded under.

Licence descriptions are factual summaries of published texts and third-party commentary, not legal advice. Open-core, LGPL and share-alike questions belong with counsel before anyone relies on them.

No migration path and no upgrade analysis. There is no import of any kind here (L-06), and nothing is claimed about Odoo's upgrade behaviour beyond the file's own word for it, upgrade-fragile. When that research is refreshed, this entry must be re-read against it.