Asking the vendor doesn’t work.
It isn’t ill will: it’s the business model. Every change is a development job to be queued behind all the others. You are not the only customer, and your urgency is not theirs.
On-site working session for mid-sized industrial companies (50–350 employees)
We unlock the data stuck in your ERP and build on it the systems you need. Without changing ERP, without waiting on their timescales, without a single piece of data leaving the company.
Launch price for the first cases. The call is included and comes before any commitment.
You have been paying the support fee for your ERP for ten or fifteen years. The data inside that system is yours: your orders, your job orders, your customers and the daily work of your factory are all in there.
Yet every time you ask for a change the answer is the same. It isn’t planned in the release. It takes six months and twenty thousand euros of development. Or a ticket that never gets an answer.
The data is yours, but to use it you have to ask permission.
The problem, in numbers
A mid-sized industrial company produces between 300 and 600 technical quotes a year. At three or four hours each, that makes 900 to 1,800 hours: at full cost, between 36,000 and 72,000 euros a year of skilled hours spent bridging software that doesn’t talk to each other.
The calculation, in full
The upper bound keeps three hours even at the high volume: it is the prudent reading, not the worst one.
It is an estimate built on typical volumes for the sector. We work out the figure for your case together during the session, and leave it with you in writing.
Then there are the orders that never come, because you replied three days later. Nobody counts those.
The three roads already travelled
It isn’t ill will: it’s the business model. Every change is a development job to be queued behind all the others. You are not the only customer, and your urgency is not theirs.
Eighteen to twenty-four months of migration, hundreds of thousands of euros, staff who have to relearn everything. In the end you have the same problem with a different vendor.
A generic assistant doesn’t know your item codes, your price lists, your margin rules. Without access to your data it remains a proofreader.
The mechanism
There are ten non-invasive routes to do it, and at least one always works.
None of these routes writes inside the ERP. It is read, not touched.
Read-only. Your ERP is not modified.
Built on your process, not on a generic one.
Local processing or private cloud within the EU. Zero data retention.
The code is yours. No commission on third-party licences.
The day
| When | What we do | In practice |
|---|---|---|
| Hour 1 | Connection and data mapping | We connect locally to the database or the interface of your ERP and identify where the data we need is. |
| Hour 2 | Configuring the agent | We set your business rules on the chosen process: cross-checking price lists and margins for quotes, or monitoring batch progress. |
| Hour 3 | Live test | We launch the automation on your real data. In a few seconds it does what used to take hours. |
| Hour 4 | Economic report | Together we draw up the balance: hours saved per year, euros recovered, what it takes to put the process into stable production. |
We don’t publish savings figures measured at clients, because we don’t have them yet. We publish what we know how to do, and how we have already done it.
In all four cases we read the data anyway: read-only, without writing anything inside the ERP, without migrations and without asking the vendor’s permission.
Four systems, four different ways of saying no. No brand named: we describe the constraint, not who imposes it.
Thirty thousand codes in the system, a thousand actually moving, and quantities the ERP doesn’t expose. The warehouse is run separately.
No standard interface in the version in use, and access to the data only through a paid module. Put in writing by the vendor itself.
The data can be read; writing from outside is not documented. Request to the vendor still unanswered.
It covered twenty per cent of the real needs, and the changes that came through had been designed for another customer.
What stays the same
The data can be read anyway. Which route works on yours, we establish in the call.
The offer
€2,500 €1,500 + VAT, one-off
The standard price is €2,500: the first cases come in at €1,500 because we need them to build the measured figures. Four hours at your premises, in Northern Italy. A maximum of four sessions a month.
Code, data and report remain yours.
Who takes the risk
Before confirming the session we examine your ERP and the chosen process. If there is no net economic return, or if the systems are not compatible, we are the ones who tell you not to go ahead.
We take the risk of the test. You keep what we discovered about your system in any case.
Kleis is complete in itself. No obligation to buy anything else.
The filter
Why now
We run four sessions a month, no more: each one requires two people in the factory for half a day and the technical preparation beforehand.
If your process loses fifteen hours a month per person, every month of waiting has a cost you can calculate yourselves.
Thirty minutes in which we look together at which ERP you use, which process you want to unlock first and whether the extraction is technically feasible. If it isn’t, we tell you before you spend a single euro.