Ask the ERP the way you would ask a colleague.

An MCP server makes the ERP available to the AI assistant the company already uses. The question is written in plain language, and the answer comes from the real data, with the permissions of whoever asks.

For
companies with an ERP, from TeamSystem to SAP Business One
Used by
management, sales, operations
First prototype
2–3 weeks

The problem

All the data is in the ERP, but getting it out means knowing where to look. People who do not work in it all day ask those who do, wait for Monday's report or export to Excel and redo the sums by hand.

Meanwhile some people in the company already use an AI assistant to write and summarise, but that assistant knows nothing about the ERP. The most useful part is exactly what is left out.

How the data flows

  1. Where it comes from: Plain-language question (from Claude or ChatGPT).
  2. What happens, Assistant + MCP server: AI, Picks the tool (customer, order, stock…); Checks permissions (same authentication); Reads from the ERP (read-only); AI, Writes the answer (with the numbers found).
  3. Where it ends up: Answer with the data (to whoever asked); Log of every call (who, what, when).
Steps marked AI are the model's. The rest is ordinary automation or people.

How we solve it

04
01

The ERP becomes a tool

We expose the functions you need (find a customer, order status, stock level, revenue by period) through the Model Context Protocol, the standard assistants use to talk to external software.

02

The same permissions as always

The assistant sees what its user sees, because it goes through the same authentication. A salesperson who cannot see margins in the ERP cannot see them here either.

03

It starts read-only

Questions first, then, if needed, actions, such as a draft quote or a note on a customer. Every write asks for confirmation and stays in the logs.

04

One server, many assistants

The same server works with Claude, with ChatGPT and with the agents you build later. If the tool changes, the work does not need redoing.

What we measure

03

These are the numbers we set in discovery, before writing any code. The starting value is measured on your data, and the prototype is judged against it.

Questions asked each week

An assistant nobody uses is useless, however accurate it is. It is the first number to look at, per person and per department.

Requests for exports and reports

How many still reach whoever manages the ERP. It is the time that goes back to that person.

Verified answers

A sample checked against the ERP. One wrong answer on the numbers costs more than ten right ones.

When it is not worth it

If the ERP has no API and no readable database, that access has to be built first, and sometimes it is the longest part of the project. If instead the questions are always the same five, a dashboard is enough.

We have already built it

In Kleio, our own ERP, questions about the data were the AI feature users adopted first, and by a wide margin.

How we put the models in

Services involved

Other use cases

11 scenarios
08 · Fractional AI/CTO

AI roadmap for SMBs

Everyone is pitching something with AI and nobody in the company can evaluate it. A technical counterpart who lines up the use cases and decides with you what to buy and what to build.

01 · Process automation

Order requests

Orders arriving by email, as PDFs, on WhatsApp. An agent reads them, checks prices and availability in the ERP and prepares the order for confirmation.

Tell us the process. We will tell you if it makes sense.

A free 30-minute call, with no commercial follow-up unless you want it.

Request a call

Companies that have already worked with us

  • Velux
  • ISU
  • MovePay
  • AB Group
  • Archiva Group
  • Onda SpA
  • PDE
  • Bynary System
  • COOPI
  • Gimasi
  • Creactives SpA
  • Rev AI
  • Odditt Inc.
  • Si Sociale
  • Stones
  • Turboden
  • Schindler