How we work
Most software projects don't fail on technology but on ambiguity: about the price, about exactly what's coming, about who's responsible for what. This is how we prevent that.
REF EN-WERKWIJZE REV 2026-09-24 ENV EU-WEST
The process
In person or by video. What you want to achieve, what you have now, what above all must keep working. We ask the questions; you don't need to prepare anything.
A document of a few pages: what we build, in what order, when it's done, and what it costs — as a fixed price. Plus what we deliberately leave out, and why.
We work in weeks. Every week you see a working version and can steer. What you see on Friday is what exists — no demos of things that don't work yet.
We put it live, set up hosting and hand it over: explanation, documentation, access. Then we host, monitor and maintain it — with one number for everything.
Commitments
What we need from you
| At the start | Half an hour for the intro call, and someone who can make decisions. |
|---|---|
| During the build | An hour a week to look at the new version and respond. Nothing more. |
| Material | Logo, photos, existing copy or systems if there are any. If something's missing, we sort it out together. |
| Access | To your domain, existing hosting or systems we need to connect to — only what's needed, properly recorded. |
| After delivery | A contact person in case we need to ask something. Otherwise nothing: we keep it running. |
Frequently asked
It depends what needs to be in it. That's why we do an intro call and then a fixed-price quote — no hourly billing. You know exactly where you stand before anything starts.
A website usually two to four weeks. A web app or automation four to eight, depending on scope. The timeline is in the proposal and we keep to it.
No. Everything is in your name and built with standard technology. The maintenance plan is cancellable monthly. We want you to stay because it's good, not because you can't leave.
Yes. We first look at what's there and in what state, bring it up to standard, then take on the maintenance. We only replace when it's genuinely necessary — and then step by step.
On servers in the Netherlands, in a European data centre. Backups stay in the EU. For AI automation we record which data goes to which service, and keep it as limited as possible.
Anywhere English, Dutch, French or Arabic is spoken — from the Netherlands, Belgium and France to Morocco, Tunisia, Switzerland, Canada and the Gulf states. We work remotely; intro calls and collaboration happen over video, and that works just as well from Rotterdam as from Casablanca. Invoicing from the Netherlands, in euros.
Then half an hour is enough to know whether it clicks — and what it would cost.