The proof, case by case

Different ERPs. The same wall.

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.

The wall, case by case

No brand named. We describe the constraint, not who imposes it.

An ERP widespread in manufacturing

Made-to-order machine building

Thirty thousand codes in the system, of which a thousand actually move. The bills of materials are loaded with their levels but without quantities, and the availability column is empty on every row. To know what is in the warehouse you look at a sheet kept separately, and shortages are noted on paper forms.

To look up a component you need the exact code: one wrong capital letter or an extra space, and it finds nothing. The technical drawings sit on a separate server, and are opened by hand.

An ERP whose release has been frozen for three years

Contract machining

The vendor has put in writing that no standard APIs exist in the version in use. The system stores data in a 1990s database format. Read access requires an additional paid module, and the vendor normally doesn’t open everything: it builds boundary tables.

No scheduled data flow is provided. The production data lives in a third application, from yet another vendor.

A vertical sector package

Healthcare services

The documented interface exposes the data read-only: how to write from outside is not documented, and the request to the vendor has gone unanswered.

A proprietary ERP

Technical components for the automotive industry

It covered twenty per cent of the real needs, and the changes that came through had been designed for another customer: they slowed the work down instead of speeding it up.

What we did

In these cases, we read the data anyway.

Read-only, without writing anything inside the ERP, without migrations, without asking the vendor’s permission and without a single piece of data leaving the company. There are ten routes, and they change depending on the system.

  • Direct connection to the database
  • Legacy drivers
  • Reading the interface
  • Interception of internal calls
  • Desktop application automation
  • Scheduled exports
  • Reading printouts
  • Print spool
  • Application logs
  • Browser extension

Which one works on yours, we establish in the qualification call, before you spend a single euro.

The calculation

How much manual work costs, and how we calculate it.

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

  • 300–600 technical quotes a year
  • 3–4 hours of work each
  • 900–1,800 hours a year
  • × €40 an hour at full cost
  • = €36,000–72,000 a year

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.

The qualification call

Does your ERP say no in the same way?

Thirty minutes in which we look together at which system you use, where the wall is and which of the ten routes can work in your case. If none is viable, 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.

If you don’t know the exact name, “I don’t know” is fine too: we’ll find it together.

We reply with two or three time slots within one working day.

We don’t add you to any list and we don’t pass your data on to anyone.