In a regulated environment, every step must be traceable
Oss has a strong life sciences and food industry. Something applies there that is optional elsewhere: what the system does must be demonstrable. That does not make AI impossible, but it does determine how we build it. We log every decision and put a person where things get signed off.
- Oss 35 km from our office
- Uden 13 km
- 's-Hertogenbosch 17 km
- Veghel 17 km
- Nijmegen 24 km
- Land van Cuijk 25 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 Oss — 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 Oss 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 35 kilometres. So we will also drop by when it is not on the schedule.
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 Oss
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:
Every decision traceable
What the system proposed, what the person did and when. Without that log, AI cannot be used here.
Changes that have to be proven
Every change requires demonstrable testing. That calls for an architecture that supports it.
Versions that matter
Specifications and procedures where the right version must be easy to find, with its source.
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.