ERP / CRM support matrix
A one-page reference for sales and customer conversations. For the technical decision, see ADR-004. Last updated: 2026-07-09.
DuDuClaw lets AI employees read and write data in your ERP / CRM directly. The table below shows current coverage in three states: Supported (ready to go live today), Abstraction ready (the skeleton for plugging in new systems is finished, integrations scheduled), and Planned (on the backlog, not yet started).
| System | Version / type | Status | What it can do | Isolation & audit |
|---|---|---|---|---|
| Odoo | CE (Community) / EE (Enterprise) | ✅ Supported | CRM leads, quotations and sales orders, inventory lookups, invoice and payment status (15 tools in total) | Per-agent credentials, action / model allowlists, every operation audited |
| ERPNext | v14+ | 🔜 Planned | First validation implementation once the abstraction layer lands | Shares the same isolation mechanisms as Odoo |
| Twenty | Open-source CRM | 📋 Planned | CRM scenarios (leads / opportunities / contacts) | Same as above |
| Other REST/JSON-RPC ERPs | — | 📋 Under evaluation | Extensible via the ErpConnector contract |
Built into the contract; new implementations get it for free |
Talking points for sales
Section titled “Talking points for sales”When a prospect says “Odoo only fits small and mid-size companies — we’re bigger than that”:
Odoo is indeed most at home in companies of 15-50 people; that’s its sweet spot. But DuDuClaw’s approach to ERP is not tied to Odoo. Underneath sits an abstract contract called ErpConnector (see ADR-004), and Odoo is just the first implementation. Once the contract is settled, connecting ERPNext, Twenty, or a customer’s own REST/JSON-RPC system follows the same path, and a newly connected system automatically inherits per-agent credential isolation, action allowlists, and full operation auditing. These are part of the contract itself, not something rewritten for every new integration.
So the honest pitch to a large enterprise customer is: “Odoo runs today; for the system you use, we have a standardized integration layer that can extend to it, and ERPNext is the first scheduled validation case.” No overselling with “we support everything”, and no turning the customer away either.
What “abstraction ready” means
Section titled “What “abstraction ready” means”Once ADR-004 is finalized, the duduclaw-erp skeleton crate provides the trait, connection pool, scope checks, and auditing, and Odoo becomes an implementer. At that point, the work of connecting a new ERP drops from “copy the whole Odoo stack” to “implement one trait”. “Abstraction ready” in the matrix refers to exactly this state: the skeleton in place and the Odoo regression tests all green.
Related documents
Section titled “Related documents”- ADR-004: ERP connector abstraction — why a trait, and the trade-offs
- features/12-industry-templates.md — a deeper look at the Odoo ERP bridge