Selling through five channels means updating five times
Around Roermond, retail, logistics and manufacturing sit close together, with a lot of trade across the German border. If you sell through multiple channels, you keep track of stock, prices and statuses in multiple places. That is work an integration should be doing.
- Roermond 45 km from our office
- Weert 21 km
- Sittard-Geleen 23 km
- Venlo 23 km
- Heerlen 34 km
- Helmond 39 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 Roermond — 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 Roermond 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 45 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 Roermond
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:
Web shop, marketplace and the counter
Stock that is correct in five places is an integration issue, not a discipline issue.
Two countries, two regimes
VAT, returns and transport documents that differ per country.
The same question, all day long
Where is my order, what does it cost, is it in stock. The system can answer that itself.
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.