I help companies build with AI, and make the kind of product that’s hard to copy.

Where I can help

1. You want agents in the product

   Agents that do the work.

   I build agents that plan, use your app’s tools and check each other’s work, with evals so you can see how often they get it right.

2. You need someone senior who still writes code

   I do the building.

   I co-founded an enterprise SaaS and hand-wrote over half its code as CTO. I join your team and build the system, platform or API you need next.

3. You’d like a second opinion before you commit

   Talk it through first.

   I’ve been the CTO making these calls, and I’ve worked with Ericsson, Accenture, Hetzner, USAID and Groove. Send me what you’re weighing up and I’ll tell you what I’d do.

How I work

Code is cheap. Engineering isn’t. I’ve been the one paged when it broke, so what I ship comes with the tests, permissions and deploy path it needs, and your team can change it after I leave. I take one main client at a time, and work in your repo on your tools.

• Shipped means in production: What we build goes live for your customers, not into a demo or a branch that sits.
• Tests and security in the same PR: Every change ships with its tests and a security review, not as a follow-up ticket.
• Your team keeps it: Plain code, written docs, and I explain the decisions as we go, so nothing depends on me.

Recent writing

I write up what I learn, mostly building with AI, Elixir, Phoenix and AWS.

Render PDFs in Elixir with the Typst NIF→

9 November 2026 · 6 mins

A Phoenix app renders its report PDFs inside the BEAM with the typst package's NIF. Why not headless Chrome or the Typst CLI, the checks a NIF has to pass, and a benchmark against the CLI.

A time on the Phoenix scope goes stale in a LiveView→

7 November 2026 · TIL

Phoenix filter_parameters doesn't redact tokens in the URL path→

5 November 2026 · TIL