Your Odoo, installed with AI already inside it.

• Find anything, instantly — any customer, order, invoice, lead, product or stock item, just by describing it.
• Answers, not spreadsheets — "revenue this month", "sales by rep", "how many open orders": it does the totals and comparisons on the spot.
• No IDs, no codes — say "Acme" or "that invoice from March" and it works out which record you mean.
• It knows your setup — your custom fields included, so answers match your business, not a generic template.
• Real data, never invented — every figure comes from an actual record, and it says so when your data can't answer.
• The whole picture at once — customers, sales, invoices and stock in one question, without stitching reports together.

• Draft it for you — quotes, new customers, opportunities and updates, previewed before anything is saved.
• Move work forward — confirm a quotation, post an invoice: the routine steps that keep things moving, on your say-so.
• Nothing happens by accident — a dry-run preview on every change, and it can't delete unless you've specifically allowed it.
• Paperwork where it belongs — attach and retrieve contracts, POs and receipts on the right record.
• A double request can't create two records — write de-duplication is built in.

Because it's one agent rather than a bolt-on, an ERP task doesn't have to stop at the ERP:

• Messaging — WhatsApp, Slack and Telegram, so answers land where your team already talks.
• Email — turn an Odoo finding into an on-brand follow-up, sent only on your approval.
• Research & web — enrich a prospect or verify details before you create the lead.
• Data & documents — charts, summaries and shareable reports from Odoo data.
• Automations — six ready to switch on: overdue-invoice chase, month-end checklist, weekly pipeline digest, stale-quote nudge, low-stock reorder and timesheet reminder.

• Read-safe by construction — the read path physically cannot write.
• No arbitrary code — only whitelisted models and business methods are reachable.
• Scoped keys — grant read, write or admin per key, so different roles get different reach.
• Your Odoo permissions still apply — the agent can never exceed the connected user's own rights.
• Full audit trail — every action logged, with a dashboard you can read it back from.

Six inside Odoo: the AI core (providers, jobs, audit log, model catalogue, permission tiers), the AI Fill form engine, and bindings for sales, purchase, accounting and purchase approvals.

Nine for configuration: the configurator core plus module-scoped customisers for sales, purchase, inventory, manufacturing, maintenance and quality — and an engineering pack.

They install into your own Odoo. There is no second system for your team to learn.

Yes, with one honest condition. Text documents — PDF, Word, Excel, CSV, email text — are read directly. Scans and photographs need a vision-capable model configured, and the system detects when a PDF is really a scan and switches approach. If no vision model is configured, it says so upfront rather than returning an empty result.

In our own testing, an image-only scanned supplier quotation was read correctly through the document pipeline.

Yours. Ten provider types through one path — OpenAI, Anthropic, Google Gemini, OpenRouter, DeepSeek, Groq, Fireworks, any OpenAI-compatible endpoint, and fully local models via Ollama. Keys live in one place in Odoo, masked and admin-only — and using a model never requires seeing its key.

Where you decide. Run a local model and nothing leaves your machines. Either way, the audit stream that leaves the machine carries field names only — before and after values stay in your local store. There's also a deterministic offline mode, so the system can be demonstrated with no external AI call at all.

• Creating a draft is frictionless — approval there would be friction with no safety gain.
• Changing an existing record needs a second person — and the approver cannot be the requester, refused even through the API.
• Money, stock, or anything a customer sees — always gated.
• No approver configured? The change is refused, not waved through.

Yes — that's how the agent factory works. Agents are built from folders of skills and personas rather than separate codebases, so your marketing agent and your sales agent are the same trusted runtime with different capabilities, branding and knowledge.

Adding a function to an agent is a configuration change, not a development project. Each build is signed, and every release is immutable with a checksum you can verify.

A linked-device assistant: scan a QR, and your own WhatsApp becomes a channel to your agent — self-chat, for the account owner. Writes are confirmed by typing a literal YES. A public company number with tappable approval buttons is an Enterprise feature.

The enterprise control plane: company identity-provider sign-in, per-person Odoo identity, centrally-set models and spend caps, private document intelligence, the official WhatsApp Business API, and partner isolation. When you need those, Enterprise switches on over the same installation — no migration.

No "zero hallucinations" — the claim is that it refuses rather than guesses. Our extraction benchmark runs on a synthetic corpus — a regression gate, not a field accuracy claim. One vertical pack exists today (engineering & manufacturing, in certification). Every product page carries its own "what this does not do yet" block — ask us for the full list at any point.