In Brainport, the systems have grown along with the business
Machine builders, suppliers and technical wholesalers around Eindhoven rarely run on standard software. There is an ERP with twenty years of customisations in it, a configurator someone once built themselves, and a mountain of documentation nobody searches. Putting AI on top of that only works once that foundation is right. We do both, and our office is just around the corner.
What is running at our clients
Three projects from the southern Netherlands. Not all of them from Eindhoven — we would rather say so than pretend otherwise. We may name the sector, location and size; not always the name.
14
hours of retyping saved per week
Packing slips that book themselves
Technical wholesaler, 140 employees — PDFs from the mailbox are read, checked and created as orders in the ERP.
Laravel · RAG · ERP integration
6
weeks until the first integration went live
A core system from 2012, opened up again
Manufacturer in the Brainport region, 320 employees — an API layer next to the existing system, without production downtime.
Laravel · API · migration path
38.000
documents searchable with their source
The archive gives answers
Engineering firm, 85 employees — staff ask a question and get the answer with its source.
Laravel · embeddings · SSO
When proximity really matters
The honest answer: for most of the work, distance makes no difference. We write code, build integrations and handle maintenance from Eindhoven, and whether you are in Eindhoven or in Groningen, you will not notice.
There are two moments when it does matter. The first is the use case: we want to see how the work is done now, at the desks of the people who do it. That is a morning on site, not a video call. The second is the rollout, when the first department starts working with it and one of us needs to be there.
Eindhoven is where we are based ourselves, on the Daalakkersweg. That is not an argument in itself — but it does mean those two moments are never a scheduling problem.
Use case and rollout
The first session in which we see the work, and the days when the first department switches over.
Building and maintenance
Development, integrations, updates and monitoring. Nobody needs to get in the car for that.
What we come across in Eindhoven
Every region has its own kind of business, and with it its own kind of system problem. This is what we see most often here:
Twenty years of customisation
A software package that grew along with the business until nobody dared to upgrade it any more. We put an API layer next to it instead of replacing it.
Drawings, specs and certificates
Supplying runs on documents that arrive by email and are retyped by hand. Exactly the kind of work AI is good at.
The man who knows
At technical companies, the knowledge sits with a handful of people. When they retire, the archive has to be able to answer.
Three things, one foundation
AI in your own software
Reading documents, searching archives, routing requests — in the system you already use.
Taking out the manual work
Steps that now involve cutting and pasting become a chain that runs by itself, with a person in the right place.
Opening up the old system again
An interface next to the existing system, so something can be built on top of it without production coming to a standstill.
Half an hour costs you nothing
Tell us which process takes the most manual work. We will tell you honestly whether AI is the right answer — and sometimes the answer is: fix your integration first. Then you have that too, without an invoice.