Ask Radical Fanatics AI
← Back to all posts Custom development & AI

Turn your ERP implementation into an AI project

AI is only as good as the foundation underneath. An Odoo implementation lays that foundation: one database, clean data, clear processes. Get it right from the start and you go live with an ERP and a launchpad for AI. Here is how we do it.

Also in: Deutsch Nederlands

You are moving to Odoo. That means redesigning your processes, cleaning up your data and agreeing who does what. That exact work is what makes AI useful.

So bring the AI question into the implementation from day one. You go live with an ERP that works and a foundation AI can build on straight away. This article covers why Odoo suits that so well, what it gets you and how we approach it.

What you get

  • Less customisation
  • Faster integrations with other systems
  • No more double data entry
  • AI does the hard part, you decide
  • More insight without exporting first
  • Forecasting, including your cash flow

AI amplifies what is already there

AI makes good better and bad worse. A messy base with half-painted planks gets repeated by AI across the whole fence. A solid base gets carried through neatly everywhere.

AI learns from what it sees. Customers in your system twice? Stock levels that don’t add up? Everyone posting their own way? AI will repeat those mistakes. Faster, and at scale.

A forecast is only as good as the data under it. A cash flow forecast built on a messy receivables list gives you a nice chart with the wrong answer.

An ERP implementation forces you to clean this up. One customer list. One way of working per process. Clear agreements on who enters what. You are doing that work anyway. Put the AI question next to it and you set things up so AI can pick it up later without rework.

Why Odoo is a strong starting point for AI

At the bottom one database with sales, purchasing, inventory, manufacturing, timesheets and accounting. Above it Odoo, with open source code, public documentation and a fixed data structure that AI models already know. On top AI such as Claude, connected via MCP. AI works with your permissions, entries stay drafts and you decide.

Odoo is largely open source. Its code and documentation are public. That is why the major AI models already know Odoo well. They know how the data fits together, how an order moves through the system and where each field lives. There is little to explain.

Three more things help:

  • Everything in one database. Sales, purchasing, inventory, manufacturing, timesheets and accounting sit together. AI sees the whole picture instead of piecing it together from five separate systems.
  • An open connection. Through MCP a model such as Claude talks to Odoo directly. It asks questions of your data and prepares work for you.
  • Your permissions, your approval. Claude works with the user’s permissions, so it only sees what you are allowed to see. Entries stay drafts until someone on your team approves them.

This is practice. Our project at IDD Parts won this year’s Top Project Award for the best Odoo project in the Netherlands. AI was part of it too.

What it gets you

What you getHow it works
Less customisationA question that used to become a custom report, you now simply ask your data. You only build what you need every day.
Faster integrationsAI knows Odoo and its documentation. A link with a carrier, webshop or supplier is up and running sooner.
No double data entryAI reads delivery notes, order confirmations and invoices and prepares them in Odoo. Nobody retypes anything.
AI does the hard partThe digging, the puzzling, the first draft. Your people check and decide.
More insightAnalyses, reports and dashboards on live figures, without exporting to Excel first.
ForecastingDemand, stock and cash flow. AI works from the history already in Odoo.

Four examples you use the very next day

These are applications we make work on your own data after the implementation. Each one comes with a question you can put to Claude as is.

Forecast your cash flow

A weekly forecast from receivables, payables and open orders in Odoo. With scenarios.

Ask Claude: “Build a cash flow forecast for the next eight weeks. What happens if our three largest customers pay two weeks late?”

Prepare journal entries

Claude reads the payroll summary, for example, and prepares the journal entry as a draft. Your team checks and posts it.

Ask Claude: “Read the November payroll summary and prepare the journal entry as a draft.”

Analyse your own data

Margin per customer or product, stock turnover, purchasing trends. Combined with other sources where needed.

Ask Claude: “Which ten products have the lowest margin this year, and how has that changed compared to last year?”

Reports without exporting

A sales forecast or management report on live Odoo figures. No export, no Excel file that is out of date tomorrow.

Ask Claude: “Prepare the October management report: revenue, margin and outstanding items, compared to last year.”

How we approach it

How we approach it. ERP implementation: 1 fit-gap, 2 setup and data. AI track: 3 AI Kickstart, then go-live, 4 AI Implementation Day, 5 Innovation as a Service.
  1. Fit-gap. We map your processes and produce a project plan with hours per component. The AI opportunities go straight into it.
  2. Setup and data. Core processes, permissions and roles, key-user training and a clean data import. This is the foundation.
  3. AI Kickstart. A day on site, with up to eight participants. Beforehand everyone fills in a short baseline survey of about fifteen questions. Morning: what Claude can do, what it may do and how to use it safely. Afternoon: hands-on with your own work. You leave with working applications and a list of opportunities.
  4. AI Implementation Day. After go-live we pick the two or three opportunities that pay off most. We make them work, in Odoo and/or via MCP.
  5. Innovation as a Service. Half a day every month, at your office or ours. We show what is new and push through one improvement together. After three months we repeat the baseline survey. Cancel monthly.

That takes you from first meeting to working applications on your own data in two days.

Start with the foundation

Choosing Odoo? Ask about the AI opportunities in the very first conversation. We then set up your Odoo so AI can build on it from go-live. A solid base gets better with AI. A messy one just gets messy faster.

Book a conversation and bring a few processes where your team spends the most time today.

Further reading:

Frequently asked questions

Why is an ERP implementation a good moment to start with AI?

Because you are redesigning your processes and cleaning up your data anyway. That is exactly what AI needs. AI amplifies what is already there: with messy data it repeats the mistakes, with a solid base it pays off straight away. Bring the AI question into the implementation and you set up Odoo so AI can build on it from go-live.

Why is Odoo well suited for AI?

Odoo is largely open source. Its code and documentation are public, so the major AI models already know Odoo well. Everything also lives in one database, from sales to accounting. Through MCP a model such as Claude talks to Odoo directly, using the permissions of the user.

Can AI post entries in Odoo on its own?

AI prepares the entry as a draft. Someone on your team checks it and posts it. Claude works with the user's permissions, so it only sees what that user is allowed to see.

What does AI deliver in Odoo?

Less customisation, faster integrations and no more double data entry. On top of that, more insight: analyses, reports and forecasts on live Odoo figures, such as a weekly cash flow forecast with scenarios.

How quickly do you get working AI applications?

In two days. First the AI Kickstart: a day on site where your team learns what Claude can do and works hands-on with their own tasks. Then the AI Implementation Day, where we make the best two or three opportunities work on your own data.

Recognize this from your own setup?

A 30-min scan turns hunches into a concrete view, what stays standard Odoo, what becomes custom, what doesn’t need code at all.

Get in touch ← Back to blog