The data is there, but it doesn’t answer.
ERP, document archive and worksheets on different servers, each with its own language. Anyone who doesn’t know the internal codes gets nothing.
02 · Metis
The processes that cost you days today, carried out automatically.
Digital co-workers connected to your ERP, which prepare the work ready for your approval. Inside your infrastructure, on your data.
Book the qualification call (30 min) →
We quantify the scope and the investment in the Kleis session report.
Your systems already contain the answer. The problem is that they only answer those who know the exact code, the right folder, the precise format.
So people search by hand, rework things in a spreadsheet, send emails to ask for things the company already knows.
They work around the systems, instead of with the systems.
Where it jams
Three reasons why the data you have doesn’t work for you.
Repetitive tasks absorb the best hours.
Loading delivery notes, searching for orders, filling in reports, sorting emails. People capable of doing other things.
Generic AI doesn’t solve an industrial problem.
It doesn’t know your price lists, your item codes, your procedures.
The mechanism
How a Metis agent works.
-
It receives the input
A request for a quote by email, a customer order, a supplier delivery note.
-
It searches on its own
It goes and gets the information in the ERP: price lists, stock, history.
-
It calculates and applies
It runs the calculations and applies your business rules, not generic rules.
-
It delivers the work ready
The work arrives ready for final approval. Whoever approves decides, they don’t fill in forms.
Approval stays with a person. Always.
Two processes, in full
The same six systems. Just one that queries them.
The sales quote
Today the salesperson opens the ERP, looks up the price list, checks the costs, verifies the customer’s history, calls production for lead times, recalculates the margin in a spreadsheet and writes the quote. Every step is one person waiting for another person.
In
The request
Email with specifications and technical attachments.
The six systems, queried by the system
The ERP
Price lists, discounts and customer history
Accounting
Credit limit, unpaid invoices and agreed terms
Drawing archive
Dimensions, tolerances and current revision
Sheets on the server
Hourly costs and mark-ups
Workshop
Machine capacity and cycle times
Document and CRM
The text of the quote and the follow-up
Instead of the person in the middle
The Metis agent
It retrieves price lists, costs, availability and history, runs the calculations, applies your margin rules and prepares the draft.
Out
The salesperson checks and signs
The time it takes is the time to read, not to gather.
The customer order
Today
You check the customer record, check the agreed terms, look at stock, ask production for lead times, reply to the customer. Every time.
With Metis
The system checks everything and flags only the lines that don’t add up. The order confirmation is already written. Whoever signs it decides, they don’t fill in forms.
The build
How you get to production.
-
Discovery.
We map the highly repeatable processes and establish where the return is real. You come out with an order of priorities, not a catalogue of technologies.
-
Building in sprints.
Every sprint delivers something that works. Your team validates and corrects before moving on.
-
Go-live and oversight.
Operational training, monitoring, continuity fee. At the end your team knows how to run the system.
The go-live is switched on one switch at a time.
Each phase switches on a single capability. None starts before the previous one has been verified and signed off, and you can roll back from each one.
| Phase | What is switched on | Minimum duration |
|---|---|---|
| Read-only | Operators use the console on real cases. No action leaves the system. | 2-3 days |
| Dry run | Each case performs every action except the last. The result is compared with the work done by hand. | 3-5 days |
| Supervised actions | The actions are real, the operator is present and checks case by case. Confirmations to the customer don’t go out yet. | 5-10 days |
| Sending confirmations | First an internal mailbox, then the first real customer, under supervision. | 2-3 days |
| Production | Normal operation, after seven days of close monitoring. | ongoing |
Each step opens with the signature on the report of the previous phase. The rollback lever is tested before the go-live, not after.
Sovereignty
Where the systems run.
Inside your infrastructure: on your existing cloud subscription, or on-premise on your server.
No sensitive data passes through third-party servers, no data trains public models.
It isn’t an option: it’s the foundation.
On delivery
What stays with you.
Project-based investment, proportionate to the annual saving generated, plus a monthly continuity and support fee. We quantify it in the report of the Kleis session.
What we leave you
- The agents.
- The orchestration between them.
- The operating procedures, written and validated.
- The connectors to the systems you already use.
- A dashboard with the KPIs before and after.
- A test suite, to check that the system keeps responding well.
Three questions
The ones we are always asked.
What if the system makes a mistake, or blocks the ERP?
In Kleis we only read: the ERP is not modified. In production every action that writes is switched on one at a time, with the operator checking case by case and the lever to roll back always connected. Approval stays with a person.
Does our data leave the company?
No. Processing takes place locally on your servers, or on a private cloud inside the European Union with no data retention. We don’t train public models on what we read. Where personal data is needed, we anonymise it before it leaves your network.
We already have an IT department. Do we still need this?
Your IT builds and maintains the systems. We open up the data that is closed today and put the process back in the hands of those who run it. We work with IT, not in its place, and the code stays yours.
The qualification call
Book the technical qualification call (30 min)
Thirty minutes in which we look together at which ERP you use, which process costs you the most hours and whether the data an agent needs can be read. If it can’t, we tell you straight away.
- Thirty minutes, no commitment. Michele Balsamo runs it.
- We look at your ERP and at the process that costs you the most.
- If there is no net return, we are the ones who tell you not to go ahead.