Energy and grid management run on files and standards
Arnhem has a distinct energy and network sector, surrounded by a lot of business services. That is work with a lot of technology, a lot of standards and a great many documents. Exactly the combination in which searching your own archive pays off straight away.
- Arnhem 66 km from our office
- Nijmegen 16 km
- Ede 17 km
- Veenendaal 24 km
- Land van Cuijk 29 km
- Oss 36 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 Arnhem — we would rather say so than pretend otherwise. We may mention 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 Arnhem 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 66 kilometres. Far enough not to just drop by, close enough to simply come over for 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 Arnhem
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 answer is in there
Thousands of pages of standards, inspections and reports that ought to be searchable, with sources.
Additional work and changes
Correspondence that later decides who is right, scattered across mailboxes.
Recurring manual work
Periodic reports that are compiled from scratch every time.
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 opened up 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.