How I build

I opened the site on my phone and the product cards were broken. One clipped its own content; another rendered blank with a lone button floating in it. On my laptop everything looked fine. I handed the symptom to an agent, which reproduced the page in a headless browser and showed it wasn't a layout bug at all. The glass cards use a backdrop-filter, and on mobile GPUs that filter kept re-sampling the animated blur behind them, so the card never composited cleanly. The fix drops the blur on touch devices only and keeps the glass on desktop, applied once through a shared hook so it covers every card on the site in a single change. The thing that flagged it was a human on a real phone. The thing that root-caused a GPU repaint quirk in minutes was the agent.

The call-to-action buttons looked washed out and nearly vanished in dark mode. I asked for a styling fix. The agent went a layer deeper and found the real cause: this is a Tailwind v4 project that was missing its @theme mapping, so every semantic colour utility on the site was quietly emitting no CSS at all. The brand blue only survived where someone had hand-written it. That is a far bigger finding than a button, and switching it on would shift colour across every page at once, so I didn't let it ship on autopilot. I looked at it, approved it, and one block brought the AiPOX blue back everywhere. Before it went live it was checked against roughly forty before-and-after screenshots, every page in both languages, light and dark, with the contrast re-measured to stay at WCAG AA.

I wanted the site's SEO to be genuinely good, so I asked a specific question: should the structured data on the English pages be in Dutch or English? The answer came back as advice, not a silent edit. English on /en, because Dutch structured data there doesn't help discovery, with a prioritised list of what else was weak. I read it, agreed, and handed over the profile links. Only then did the work go in: per-locale language tags and JSON-LD, hreflang and canonicals, the verified profiles, a generated sitemap. Doing it carefully surfaced two latent bugs that had nothing to do with the request. A locale left undefined, so /en was silently falling back to Dutch and breaking its own language tags, and a type mismatch breaking the production build. Both fixed in the same pass. That is the rhythm I want on the record: the fleet advises, I decide, then it gets built.

Vincalis is a B2B supply-chain platform I'm building. In one afternoon its codebase took seventeen commits; across the same day sixteen pull requests were opened and fifteen were reviewed and merged. I hand-wrote almost none of it. The work was done by a small fleet, a product owner agent and three developers, and every commit and PR carries their co-author trailer, so the authorship sits in git rather than being something you have to take on faith. The PO agent wasn't only writing code: two of the commits are it running the fleet, lifting a sprint and re-pointing idle developer hosts at the next queue of work. One review pass ran eight separate angles, and three of them landed independently on the same defect: widening one shared type would have let an invalid value slip past validation and crash the database with a 500 instead of returning a clean 400. The agents found it, fixed it, added a regression test, and verified it against a live environment before it merged. The team moved fast. The one thing that waited was my approval.

Proceshuis is one of the products I build with the fleet. In a single morning it moved from its old address to its own brand domain, proceshuis.com, and gained a new feature at the same time — with me steering on direction, not on every step. The move ran in two tracks at once. A developer agent combed the whole codebase for every reference to the old domain, from metadata and SEO to login and mail, on a separate dev environment with typecheck and lint green. In parallel, my sysadmin agent ops-01 handled the DNS, the reverse proxy with a www-to-apex redirect, and the TLS certificate. What the AI did not do on its own was the production deploy and placing a live mail secret: those sit behind a human gate, and I approved them deliberately. That is the pattern I care about most — the fleet knows which steps are irreversible or sensitive and escalates them by itself, even when I say 'go ahead, I can't watch right now.' The same morning a real user question came in: can you filter the process tree by who is responsible for what? It took the same road. First a designer and PO agent mapping the data model and delivering a plan — it could be done entirely on the front end, with no new database query. Then a developer building it. And then the real work: shaping the UX in plain language. 'Takes up too much room' became a filter icon with a popover; 'can it do several at once' became a compact chips combobox. Each round: adjust, look at it live, and only after an independent code review did it reach production. One remark from that morning — 'this isn't a consumer app, it can feel a bit ERP-compact' — the team stored as a standing principle in its memory, so the designer now acts on it by default. The first application rolled out right away: a page header that shrank from 82 to 47 pixels.

Lately the fleet worked through the remaining backlog in a run of sprints, and it went well. The surprise was where the ceiling actually sat. It wasn't the models. It was the infrastructure. The CI pipeline kept getting in the way, and unblocking it turned into a genuine puzzle that no amount of cleverer prompting would solve. In the end it needed hardware: my sysadmin agent, ops-01, called for extra SSDs and different Proxmox settings. Once that landed, the pipeline finally ran clean, and the throughput jumped. The work came out in two separate weekly bursts, roughly one big push a week, each a stack of pull requests and issues closed in a short window. The part I like most is the restraint. The fleet paces itself against a weekly token budget, tracks its own usage, and when it runs ahead of pace it pauses itself rather than burn through the budget. You can watch that happen live in Townhall's token channel. Fast when the plumbing allows it, and disciplined enough to stop itself.