The platform
Every product works on its own. Together they share one identity, one approval contract and one audit trail — so whatever your team or your AI does, there is always exactly one answer to "what happened?"
Products, each
sellable alone
Correlation ID
across every layer
Reinstalls when
you add the next one
QA cases published
with evidence
The architecture
People and AI clients enter at the top. Policy is applied once. Work happens through four products. Your Odoo stays the system of record — and a single thread ties the whole path together.
Follow one request
A buyer pastes a supplier quotation and asks the agent to raise the order. Here is every layer that request crossed — and what a single query returns afterwards.
This is the part that cannot be retrofitted. Four products agreed on one contract before any of them was built. Bolt four tools together later and you get four logs that don't join up — which is exactly the moment an auditor asks who approved something.
What they share
The same person, recognised by every product — and in Enterprise, acting in Odoo as themselves rather than a shared login.
Drafts are frictionless; changing a record needs a second person who isn't the requester. Enforced in the write path, not the interface.
A single correlation ID joins the conversation, the document, the write and the configuration change — refusals included.
Product by product
Upload the documents you already have. Discovery, requirements, fit-gap, documentation and a governed build — evidence-backed and approved by you at every step.
How it connects: it never reaches into your Odoo directly. It hands an approved change bundle over, where your Odoo re-validates and stages it for its own approval — a deliberate double gate. The blueprint carries the same correlation IDs as everything else, so when the instance goes live the Agent arrives already governed.
Not yet: the build is a governed bootstrap — taxes, opening stock and BOMs are discovered but deployed with your team. Full details →
Fifteen AI modules working in the Odoo screens your team already uses. Header fields and every line item with per-cell confidence, and nothing saved until the right person approves.
How it connects: it is Odoo — addons inside your own instance, with Odoo's ACLs and record rules fully in force and no privilege escalation on any AI write path. Its extractions, approvals and refusals land in the same timeline the Agent and MCP write to.
Ask your business in plain language, get the records back — or an honest "the data isn't there". On desktop, in the browser and on WhatsApp, with 418 skills across 18 business functions.
How it connects: only ever through MCP. The Agent gets no private door — same read-only defaults, same risk tiers, same approvals as any other AI. Under Enterprise its traffic also flows through the Gateway, and each person's Odoo actions run as themselves.
Claude, ChatGPT and your own agents reach Odoo through one path. Seventeen tools, eight on by default and every one read-only; everything that changes anything is off until you turn it on.
How it connects: it is the chokepoint the platform depends on. Because every agentic read and write passes through it, the audit trail is complete by construction rather than best-effort — which is what makes the single timeline possible at all.
Who can use AI, when, how much, and what they're allowed to send it — enforced at the server. Plus every request priced and attributed.
How it connects: it governs beside the execution path, never in front of it. No Odoo request is routed through a Gateway process — AI traffic flows through it for model, budget and policy, while approvals, risk tiers and the write path stay exactly where they were. Governance is added, never substituted.
Your contracts, complaints and correspondence become intelligent context — entities, processes and figures, resolved and cited.
How it connects: it answers alongside the ERP rather than instead of it. The agent reads Odoo records through MCP as that person and the document estate in the same turn, so the user never chooses a system. The pipeline that feeds it is ours, which is why the two halves join at all.
Standard is products 01–04. Enterprise adds 05 and 06 over the same installation. With every enterprise setting unset, the platform is byte-for-byte the Standard edition — that's the acceptance criterion, and proving it is itself a test case.
Which is what makes adding a product a decision rather than a project: same identities, same contracts, and the audit trail joins up retroactively.
Every plan includes
No obligation, no card, no lock-in. And what comes with your plan isn't a discount — it's what it takes to make an ERP actually land.
Not months. Your implementation is underway in your first week.
A full year included with every plan — not a paid add-on.
We come to you and train your team in the room, on your data.
A hundred hours of our engineering, built into every plan.
◆ No card to start · ◆ No obligation · ◆ Cancel any time in the three months · ◆ Your data stays yours
Questions
Each piece stands alone and joins later without a reinstall — because everything was built against the same contract from the first day.
Thirty minutes, your paperwork, your questions. We will show you what it does — and, just as importantly, what it refuses to do.
