Skip to content

Cases

Real projects, honestly labelled

What I build and maintain for clients, and the systems I build for my own businesses. Every case states what it is and which phase it is in. Figures only appear when they have been measured.

How to read a case

Three kinds, each with its own label

  • External client case

    Built for a client and under maintenance. The date says since when.

  • Own practice case, measured

    In my own business, with figures that have been measured. The date is the measurement date.

  • Own build or product

    My own system, with the phase alongside: in use, running in simulation or final test phase.

All cases

Client work first, then my own systems

Figures only appear when they have been measured.

  • External client case · maintained since September 2026

    Connecting a web shop to Exact Online without anyone losing sleep over it

    Starting point
    a web agency wanted a WooCommerce-Exact integration for its client that the client owns and that speaks up when something goes wrong.
    Approach
    own server, Cloudflare WAF and Zero Trust, self-hosted n8n, monitoring with plain-language alert e-mails.
    Next cycle
    integration under maintenance, every deviation reported; follow-up measurement January 2027.

    Mercabilis · web agency · WooCommerce ↔ Exact · maintenance

  • Own build · in use

    A custom backend that tracks everything from request to advice

    Starting point
    Requests, intake, evidence and advice were scattered; advice is only as good as the data beneath it.
    Approach
    Custom backend: priority queue, step-by-step intake, evidence, opportunities and business case, call mode and reports.
    Next cycle
    Connect the jobs API to Tasks & errors; fill opportunities per case from the report.

    AIAgentCycle · custom backend · Audit Desk

  • Own build · running in simulation

    BH28: an autonomous trading system that only trades when every check is green

    Starting point
    A system that trades on its own must above all be good at saying no.
    Approach
    Python core, 32 n8n workflows, PostgreSQL audit, a risk gate per order, ChatGPT and Claude without authority over orders.
    Next cycle
    Show in simulation that the chain holds; only then a separate decision on a funded account.

    BH28 · own build · running in simulation

  • Own product · final test phase

    Holos33: a €250,000 app, designed together and built by me

    Starting point
    An app that works with sleep, heart rate and journal entries has to earn trust before anyone installs it.
    Approach
    Architecture with a freelance architect, design in Figma, built by me in Flutter and NestJS (278 endpoints), security reviewed by an external specialist, data and AI in the EU.
    Next cycle
    Finish the final test phases, then measure usage; direct integrations with Garmin and Oura once those are available.

    Holos33 · own product · iOS, Android, admin and CMS

  • Own practice case, measured · 4 September 2026

    985 submissions on the wrong list. And nobody saw it.

    Starting point
    985 of 1,136 form submissions carried the wrong origin label; one form rejected every submission for 25 days without a single error.
    Approach
    Baseline first, two-sided gates, single-source origin, idempotent delivery into Zoho CRM, Bookings and Listmonk, dead-letter with alerting.
    Next cycle
    Activate Turnstile, keep the daily watchdogs negatively tested, bring the next integrations under the same gates.

    Holos33 · Good Nature Vibe B.V. · 4 audiences, 2 languages

  • Your process

    The next case?

    In the free assessment we look at whether automating pays off for you. If it becomes a project, I document it the way you see here: starting point, approach and what gets measured.

Structure

How every case is built up

The same four parts, so you can compare cases with each other.

  1. Starting pointThe business, its size and the bottleneck, as concretely as possible.
  2. ApproachWhich systems, which flows and which choices, with the reason alongside.
  3. ResultOnly what has been measured. An estimate is called an estimate.
  4. Next cycleWhat gets improved or measured after delivery.

What clients say

In their own words

  • We build the web shop, but an integration with Exact is not our line of work. Our client works with separate prices for resellers, and that is where you get stuck with standard modules.

    Stefan built the integration between WooCommerce and Exact: whoever logs in sees their own price, and Exact remains the only place where a price changes. He also maintains the server the integration runs on, with maintenance every month. If something goes wrong, I get an email I can simply read. With Cloudflare in front of it, the security is in good shape.

    I can make my client a promise with peace of mind.

    Robin Duin

    Owner, Mercabilis (web agency)

    Read the case about Mercabilis →
  • I want to understand how something fits together before I say yes. With Stefan, that conversation is possible. He knows what he is talking about, explains why he builds something the way he does and looks at how we work.

    And then he comes up with just the piece I had not thought of myself. When I send a question, I get an answer quickly.

    Mike van Ekelenburg

    Mike van Ekelenburg

    Director, Greven

  • When it comes to our systems, Stefan is my sparring partner. How it should fit together and what is really needed. He first looks at how we work and finds the solution to match.

    I keep control of my business myself and still have someone beside me who keeps the overview. A pleasant collaboration.

    Dani Steen

    Owner, Mooier Thuis

Start with one process

In the assessment we choose the process, the exceptions and the expected value. You always get a short advice report, even if we do not continue.

Prefer WhatsApp? WhatsApp +31 6 54 36 25 26 · info@aiagentcycle.com