I work on the decisions around AI-built systems.

Who this is for

For directors, consultants, founders, and operators accountable for systems they cannot inspect line by line. The people who approve the rollout, recommend the system, or own the workflow — and still have to explain what changed.

Answerable for the cost, the risk, and the real question: was it worth it?

Where this comes from

Most of what I know about technology I learned by keeping it running. Eight years managing systems, servers, and labs. The kind of work that only gets noticed when something breaks. You develop a different relationship with complexity when you are responsible for it at three in the morning.

After that I tried building my own things. Multiple times, different shapes. A consulting venture. A product I believed in. Others. None of them survived long enough to matter the way I wanted them to. The judgment of what to build was there. The ability to get from idea to working system was not. Not at a price I could pay alone.

I went back to consulting and spent years close to large technology decisions. Alongside that work, I kept building and testing my own systems, where I could examine the full chain from idea to consequence.

I am not a software engineer. AI did not turn me into one. It changed what I could test without waiting for a full team. I built this site, working tools, and infrastructure that I could inspect from idea through operation.

The harder constraint remained judgment. What to build. Whether it matters. Whether it changed anything. Those questions have not become cheaper. That is what I write about here.

What is here

The views and frameworks here are strictly my own and do not represent any employer, client, or affiliated organisation. This publication relies on public information, generalisable mechanisms, and anonymised patterns.