Implementation
AI where your data already sits.
The most expensive part of an AI project is rarely the model. It is the connection to what is already there: ERP, inventory management, mailbox, file store, customer portal. That is exactly where we work.
from €6,900 · your existing systems stay as they are
Why the connection is the actual work
In a business that grew over time, the data is rarely where the org chart suggests. Part in the ERP, part in a spreadsheet on the network drive, part in a mailbox, and a not inconsiderable part in a colleague's head. A model can process all of it - what it cannot do is ask for it.
The work therefore does not consist of teaching the system to think, but of getting it access. In our projects roughly half the effort goes there: clearing access, understanding formats, reproducing permissions, catching failures.
Your systems stay as they are while we do it. We do not replace an ERP and we do not introduce a platform - we connect to what runs.
What we usually connect to
- ERP and inventory management
- SAP, Microsoft Dynamics, abas, proALPHA, Sage, Streit V.1, pds and others.
- Accounting
- DATEV and the usual handover formats - in the shape your accountants expect.
- Mailbox and calendar
- Microsoft 365, Google Workspace, in-house mail servers.
- Archives
- Network drives, document management, PDM/PLM, mail archive - without you having to tidy up first.
- Portals and EDI
- Customer and supplier portals, tender platforms, EDI and VDA formats.
- No interface
- Where a legacy system has no way out, we build one. Impossible is rare - laborious sometimes.
If yours is not listed, that is not an exclusion. The list names what we meet most often, not what we require.
The hard question
Can we reach the data at all?
That is the question projects tip over on, and it cannot be answered from a desk. The interface the vendor lists in the data sheet sometimes does not exist yet in your version. The export runs, but delivers prices without the tiers. The drawings exist as scans, and specifically as scans of a fax.
Which is why the access check sits in the audit and not in the quotation: we pull a real export, open a real file, call a real interface. Only then do we name a fixed price - before that it would be a risk premium or an arithmetic error.
What the connection brings with it
- Permissions stay as they are
- A system adopts your permissions, it does not work around them. What someone may not open today, they will not see through the new route either.
- Logging
- Every run is traceable, every output names its source. An error surfaces before the customer reports it.
- Safe aborts
- An abort mid-transfer leaves no half-written record behind.
- An off switch
- Every routine can be halted without the business stopping - it falls back to the way it worked before.
In practice
What a connection looks like day to day
The system integration use case shows the routine step by step - today and with us, with acceptance criteria and the limit at which it is not worth it.
To the use casesFrequently asked
Do we have to replace our ERP?
No. We connect to what runs and replace no existing systems. A system migration is a project of its own with its own risks - it does not belong inside an AI rollout.
What if our system has no interface?
Then we build one. That is almost always possible - via exports, database access, file routes or, in the worst case, through the user interface. It is laborious sometimes, and then we say so before the quotation, because it can eat up the benefit.
Does the system get access to everything?
No. It gets exactly the rights the routine needs, and it adopts your existing permissions. The scope of action is in the specification, not in the conversation.
Does our data leave the building?
You decide, and it is settled per project. Where processing within the EU is required, we build on services in the EU or on models we operate ourselves. The basis in every case is a data processing agreement under Art. 28 GDPR.
What does a connection cost?
It is part of the process, not billed separately: from €6,900 for the first, from €4,900 for each further one in the same project. The reason for the difference is exactly this connection - with the first process it gets built, after that it stands.
Tell us where your time goes.
In the audit we record the process, work out what is worth automating, and you get a plan with fixed prices - credited against the build if you go ahead.