Claude writes the code.
I decide, review and stand behind it.
It is how the development teams of large organisations work too: AI writes, the developer is responsible for the architecture, the review and what goes live. Version control, tests, staging and a changelog come with it. I am open about this, and proud of it. This is what you get from me, from the first conversation to years after delivery.
One person responsible,
a team of agents.
I work from Bladel, in the Kempen region near Eindhoven, in the south of the Netherlands. The agency is one person: me. For each task I start a team of agents that builds, tests and checks; I decide what needs to be made, check everything and am responsible for what goes live. Which agents those are and what they do, you can see on the agency page.
What that means for you: your idea becomes working software in weeks instead of months. Every change goes through tests before it goes live, runs on a staging environment first, and for every version you can trace what changed and why. You can check that yourself: the code is yours, including its history.
Where AI helps write, it says so. I also make the texts, images and videos on this site with AI; on the page about AI you can read exactly how, where the line is, and who is responsible. If you ask whether something was made with AI, you get an honest answer.
Listen first.
Then something that works.
Four steps, and at every step you know where you stand.
-
01
Discovery session
In Bladel or by video call. First I listen to what you want, without a solution yet. You send your request through the intake: type it, record a voice message or a video.
-
02
Starter product
Something small that already works, so you can see what is coming. That is also the argument for the price: you judge what you see, not a quote.
-
03
Proposal
The price is fixed only after the starter product, and it is one amount. The proposal has to work for both of us: what do you gain, what do I gain, and what happens if it goes wrong.
-
04
Running it
Maintenance is part of the agreement from the start: a fixed amount per month, with what is and is not included on paper beforehand.
And after that,
I keep it running.
Software that is finished is not done. There will be browser updates, security holes, an integration that changes and a wish you only get once you work with it. That is why running it is part of the deal from the start, not a separate conversation afterwards.
What that includes: I host it, keep it up to date and make sure it keeps working. For a fixed amount per month, with what is and is not included on paper beforehand. Larger extensions are a new piece of work, with their own proposal. Everything on this site runs that way: my own systems, those of my companies and those of my clients, on the same stack, by the same person.
The four answers
that are settled up front.
Four things you need to know before you hang your business on someone else's software. I would rather put them on the table myself.
Who owns the code?
The client does. What I build is your property — I manage it for as long as you want. If you switch or carry on yourself, everything goes with you: the code, the data and the environment it runs in.
What if something happens to you?
Delivery includes onboarding a second party, so there is always someone who can take over. On larger projects we bring Nixo Webbuilding on board from the start, so you do not depend on one person.
Where is my data?
Within the EU by default. What runs where exactly depends on the project and is stated in the proposal. For example: my own sites and those of Nimad run on dedicated servers in Nuremberg, with encrypted backups every night to two locations outside that server, both in the EU.
And security?
You can impose your own requirements and have your own party carry out an independent audit; I supply what is needed for it. I work with automated security scans (OWASP ZAP, Nuclei, Aikido, gitleaks), more than 1,900 tests that must pass on every change, permissions that are read fresh from the database on every request, rate limits on all login routes, and administration only through a private network.
On larger projects I bring Sepp Stokbroekx of Nixo Webbuilding on board from the start, so you do not depend on one person. Where he helped build, it says so.
What I don't do.
No online marketing and no email marketing as a service. No long on-site engagements: I work from Bladel, visit where it really adds value, and do the rest by video call. No hours, rates or lead times as a sales argument: you buy an outcome, and the starter product shows which one.
Every request gets a discovery session. If it is not a good fit for me, I will say so honestly and help you think about where it does fit.
What should your
agency do?
I will come and map it out: at my place in Bladel or by video call. Listen first, then a starter product, then a proposal that leaves us both better off.