Companies that grew, with systems that grew along with them
Uden and Maashorst have many companies that grew from ten to a hundred people in twenty years. The software grew along with them through patchwork: a software package, a few Excel files and one person who knows how it all fits together. That works until it no longer does.
- Uden 25 km from our office
- Veghel 7 km
- Oss 13 km
- Land van Cuijk 20 km
- Helmond 20 km
- 's-Hertogenbosch 22 km
As the crow flies, rounded · Entire region →
What is running at our clients
Three projects from the southern Netherlands. Not all of them from Uden — 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 Uden 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.
From Eindhoven, that is 25 kilometres. So we will also drop by when it is not scheduled.
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 Uden
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:
The key to everything
There is usually one file the whole company depends on, maintained by one person.
Recalculating every time
Price quotes put together by hand from old quotations. There is a lot of time to be gained there.
Email as an archive
Agreements, drawings and changes sit in mailboxes instead of in the system.
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.