What I build
For anyone wondering whether I do the building myself, or farm it out.
Most of this site is about making your existing work smaller: mapping a workflow, cutting the manual steps, keeping it running. That raises a fair question, which is whether I can actually build something when a build is what the answer turns out to be. Yes. Here are two.
Velagain
A booking platform I built and that runs. Several businesses on one system, each with their own environment.
- Booking by chat. Customers make an appointment over LINE or WhatsApp, in an ordinary conversation. The chatbot schedules, reschedules and cancels, start to finish, with nobody watching over it.
- Payments are inside the system, not bolted on beside it.
- Three portals: one for staff, one for the customer, and one inside the chat app itself.
- Under the hood: a Python backend, three web apps in Next.js, and a PostgreSQL database. Built and maintained by me, with a fleet of Claude Code agents doing the routine work under my direction.
Kengly Signal
The other one is quieter and closer to what the audit is really about: taking work a person would otherwise do by hand, every day, and having a system do it instead, with a check on whether it can be trusted.
- It reads a firehose. News and social posts come in as a messy stream. The pipeline sorts them, tags them, and turns them into structured observations, without anyone reading each one.
- It grades its own sources by what turned out true. Every source keeps a ledger: when it made a claim, the system later checks whether that claim actually held, and the source's reputation goes up or down accordingly. A source that is usually wrong quietly loses its weight.
- It ends in a decision, not a dashboard. The whole thing runs to a conclusion on its own, and its own test suite, over four hundred checks, has to pass before any of it is trusted to run.
Strip out the subject matter and that is the same muscle the audit sells: do the repetitive work automatically, and measure whether the output can be believed. I built this one for myself, which is exactly why I trust it as an example.
Where the AI actually comes from
Elsewhere on this site I say the answer is often not AI. I mean it. But that is a judgement, and a judgement is only worth something if you know what you are talking about. So, in order:
- 2023. From the moment ChatGPT existed I started working with it. Not as a hobby: at Enexis, the grid operator, where I was employed at the time.
- Then open-source models. Run on my own hardware, to understand what happens under the bonnet and what it really costs.
- This past while: agentic AI. Working out, full time, how you get AI agents to actually do work instead of talk about it, with Claude Code as the tool I settled on.
- And then built. Velagain and Kengly Signal above are the result. Not a presentation about agents, but systems that run, built with the tooling.
Three years, then. Long enough to know what it can do, and above all long enough to know when it is not the answer. That second part is what you are hiring.
Why this is here and not on the front page
Because you probably have no use for it. Most companies that call me do not need a booking platform, and certainly not AI agents. They need two hours a week of re-typing to stop happening.
I put it here in case you wondered whether I can do more than tidy up. I can. But I am not going to talk you into it, because that is exactly the pattern this whole site is against.
Working outside the Netherlands?
I do this kind of work for businesses elsewhere in Europe too. I work remotely regardless, so whether you are in Eindhoven or Lisbon makes little difference to how it runs. Mail or message me and we will see if it fits.