Engineering for brands whose products carry regulated claims

Find what your business thinks is working — but isn’t.

Your storefront says one thing. Your email platform says another. I inspect the joins by hand, prove what is broken with a reproduction path you can run yourself, and fix what is worth fixing — with your people approving every change.

From one real inspection · 2026

The shop said 5,490 customers could be mailed. The email platform could reach about 150. Nothing anywhere said a word.

One of three findings published here, reproduced before reporting. No campaign has been sent to any of those records, and no customer outcome is claimed.

Send one page — read by hand, free

Prefer to describe a stuck workflow instead? One sentence by email is enough.

One named builder: David Bentley · Built in your accounts, not mine · Nothing changes state or sends without your named approver · A documented handover

Evidence you can reproduce

One inspection. Six verified failures, invisible from inside.

One private engagement with a small independent British supplement business, inspected in 2026. Six findings were reported privately, each reproduced before it was reported; five sat between two systems, in a join nobody owned. Three are published, with the path to check each one yourself. The business is not named and never will be: a client’s private weakness is not my marketing asset.

Observed · Reproduced · Not proven — stated on every finding. Read the findings and how they were checked

The method

How an engagement runs

Check. One page of your site, read by hand, free. A reply in two working days.
Inspect. Inside your own accounts, on a screen share, before any fee is agreed.
Build. 90 days, in three separately approved stages, only if your own numbers justify it.
Operate. Ongoing, documented, handed over. Your business keeps the system.

Every step is complete in itself and refusable, with a fixed price stated in writing before any work begins. If the inspection does not justify the work, I decline it. How the work runs, in detail

Selected work

Also built: three systems for a €3 million regulated training business

Sofema Aviation Services trains engineers under EASA regulation, where a wrong answer carries a regulatory cost. A training ROI calculator and a course finder are publicly reachable; a cited EASA answer system is in review and may never ship. All were built agent-assisted and human-directed.

I did not win this work in open competition: it shows what I can build inside a regulated operation, not that the market has chosen me. See the work

The model

Agents produce. One engineer answers. Your people decide.

A directed team of AI agents gives one senior engineer unusual capacity: they read, test, draft and propose inside agreed boundaries; I brief them, verify their work against each other and merge what survives. Judgement does not delegate. A named person in your business approves anything that changes state or reaches a customer, and the system, source and records stay in accounts you control.

Send one page. I will read it by hand.

You send one public page URL, your name and a work email.
I read the served page, its forms and links, and your domain’s public email authentication.
You receive either a specific problem I verified, with the steps to reproduce it yourself, or an honest account of what was clean and what I could not see from outside.

One page per organisation · a reply within two working days · free · no list, no sequence, no call unless you ask.

Would rather write first? Send one sentence about the workflow that keeps getting stuck. I reply within one working day; if it does not fit, I will say so and point you somewhere better if I can.