Your programs work together. Your data stays under control.

We build interfaces and local automations for existing business software. Emails, PDFs, CSV, XML and other files are recognised, converted into the required format, checked and handed over to ERP, CRM, accounting or specialist applications.

Many companies work with software that does its job but has no clean connection to the other systems. Staff export files, change columns, transfer order data or retype content from PDF documents. We build a suitable connection between these steps without the existing software having to be replaced completely.

Check your process and systems Describe your project

Where the manual work comes from

One program exports CSV or XML, but the target system expects a different format.
Orders, delivery notes or requests arrive by email or as PDF and are transferred by hand.
ERP, CRM, accounting and specialist software keep the same details in different ways.
AI could handle texts or documents, but sensitive customer and company data should stay local.

What we connect for you

Programs and data sources
We connect existing ERP, CRM, accounting, shop and specialist systems through available interfaces or controlled file handovers.
Automatic file conversion
New files in a watched folder are detected, checked and converted into a suitable target format, for example CSV, TSV, JSON or XML.
Documents and emails
The system takes the relevant details from emails, PDFs and structured files and prepares them for the next step.
Local processing
Confidential documents and mappings can be processed on the company's own computer or network.
Protected AI support
If an external AI service makes sense, identifying details can be replaced locally beforehand. Only the content the task needs is transmitted. The details are put back locally and under control.
Review before handover
Results stay visible as drafts. Your team checks conflicts and releases the handover to the target system deliberately.

How we build the right bridge

Map the processWe record inputs, outputs, the programs involved and today's manual steps.
Pick the smallest useful handoverWe choose a clearly defined process with a visible benefit.
Test with realistic examplesFile formats, mappings and error cases are checked with suitable sample data.
Install locally or connectLogging, error handling and human approval are set up to fit the use case.

Typical tasks

Turn PDF orders into an ERP order draft
Convert CSV files automatically into XML or JSON
Recognise and check email attachments and assign them to a specialist application
Reconcile CRM and ERP data
Prepare export files from older software for a new target system
Use local AI for documents or recurring text work
Pseudonymise sensitive content locally before optional AI processing

Local data processing when the process requires it

Not every business process belongs in a public cloud. That is why we plan the processing according to the actual need for protection. A workflow can run entirely locally. If an external AI service is used, we limit the content to the task and can replace identifying details locally beforehand. These safeguards are reviewed and documented for the specific process. Pseudonymisation is not a substitute for a data protection assessment.

Frequently asked questions

Do we have to replace our existing software?

In many cases, no. We first check which programs do their job and where only a connection, a conversion or a controlled handover is missing.

What if a program has no API?

Then we look at existing exports, import folders, databases or other permitted handover points. Only then can we say with confidence which route is stable and maintainable.

Which file formats can be processed?

Typical inputs are PDF, email, CSV, TSV, JSON, XML and text files. The target format depends on the software that is to take over the data. Binary Office files or scanned documents need a suitable parser or OCR step.

Can data stay entirely within the company?

Yes, a process can be designed to run entirely locally. Whether that makes sense for the workflow depends on the documents, target systems, hardware and quality requirements.

Can AI be used without transmitting real names?

Identifying details can be replaced locally before optional external processing and are only put back after the checked return. The specific process must also be reviewed for indirectly identifiable content and legal requirements.

How does a project like this start?

We choose a clearly defined handover with real sample files provided in a privacy compliant way and a clear goal. After a technical test you decide whether further systems or formats should be connected.

Which two systems should work together?

Describe today's process, the programs involved and a typical file format. We check whether an interface, a local converter or a protected document process is the most sensible first step.

Check the process

A few sentences and an example without confidential data are enough for a first assessment.