Analyse first, build second
Most AI projects don't fail on the model. They fail on the step that gets skipped before it: understanding where the work actually gets stuck.
So we start by mapping how your knowledge work runs. Where the thinking sits, where the busywork sits, and what that busywork costs in hours and euros. Only once the problem is sharp does the choice of approach follow. Sometimes the outcome is that an existing tool will do, and sometimes that AI adds nothing here. That's an honest answer too.
The six protective layers
A trustworthy system is more than a clever model with an input box. It has six layers, and you can hold any supplier to every one of them. Where a layer is missing, there's a risk — and nearly every AI incident you've heard of traces back to a missing layer.
The sources.
Every answer points back to where it came from, and the system honestly says “I don't know” when the source isn't there.
The limits.
Sensitive actions — calculating, paying, publishing, deleting — sit outside the model, in fixed rules.
The sign-off.
A human approves the substance before anything goes out, and that stays real scrutiny rather than clicking it away.
The record.
For every answer it's logged which source was used, what was answered and who approved it, so all of it can be shown later.
The data.
Where the data lives, what happens to it, and that it isn't trained on: that belongs in the contract, not in a sales pitch.
The people.
The system takes over the routine work and leaves the judgement with the team, instead of slowly taking over the thinking.
These six questions are the yardstick for everything we make. And if you're judging a supplier yourself, take them with you: a system that can't answer one of them is out.
The human stays in control
The AI does the routine work: searching, sorting, preparing, drafting first versions. Anything that goes out, or that matters, passes a human first.
It's also a design choice with long-term consequences. A system can take over the routine work and keep judgement sharp, or quietly take over the thinking. We deliberately build for the first, so that in five years your team is more capable, not more dependent.
Measuring instead of believing
Whether AI helps isn't a matter of feeling. Research shows people feel AI to be faster than the clock says it is, and that the time then leaks away into checking and repairing.
So we measure before and after. Honestly timing a task for a week, with and without AI, says more than any impression can. That's how you know whether a project really delivers, and not just whether it feels that way.
METEN IN PLAATS VAN GELOVEN · GEVOEL ↔ GEMETEN
Buy, build, or neither
The honest order is always the same: first the analysis, then the choice. For routine work that looks the same everywhere, a good existing tool usually wins. Where source obligations, sector rules and confidential material meet, off-the-shelf tools fall short — and that's where we build the custom layer: the search across your own sources, the citation, the sign-off.
And sometimes the answer is neither: a simpler process, or nothing at all. Hearing after a thorough analysis that AI adds nothing is just as valuable an answer as having something built.
DE KEUZE · KOPEN, MAKEN, OF GEEN VAN BEIDE