In healthcare, privacy is not an afterthought but the starting point
Nijmegen has a strong healthcare and knowledge sector and a sizeable semiconductor industry. Both work with data that cannot simply be sent to an AI service. That is precisely why we build it in your own environment, with personal data removed beforehand and every decision logged.
- Nijmegen 50 km from our office
- Land van Cuijk 13 km
- Arnhem 16 km
- Oss 24 km
- Ede 25 km
- Uden 26 km
As the crow flies, rounded · Entire region →
What is running at our clients
Three projects from the south of the Netherlands. Not all of them from Nijmegen — we would rather say so than pretend otherwise. We can name the sector, location and size; not always the client.
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 Nijmegen 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 someone from our team needs to be there.
From Eindhoven, that is 50 kilometres. Far enough that we will not just pop in, close enough to simply be there at those two moments.
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 Nijmegen
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:
Data that must not leave
Personal data is filtered out before anything is done with it. That is a design choice, not a setting.
Hours of case-file work
Recording, summarising and passing on. Work that piles up and that AI is good at.
Systems that need to talk
Healthcare and research systems with their own standards that need to be tied together.
Three things, one foundation
AI in your own software
Reading documents, searching archives, routing requests — in the system you already use.
Manual work out
Steps that now take copying and pasting become a chain that handles itself, with a person in the right place.
The old system open again
An interface next to the existing system, so something can be built on top without production grinding to a halt.
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.