Skip to content

About

An operator who ships his own tools.

I run companies and I build the software they depend on. Not prototypes and not internal demos — systems that carry real transactions, real clients and real money, with me on the hook when they break at nine on a Monday.

That constraint is the whole point. When you both build the thing and answer for it, you make different decisions: you refuse the clever architecture that nobody can operate, you put a hard cost ceiling on the AI feature before you ship it, and you find out quickly which abstractions were vanity. Most of what is on this site exists because a business I am responsible for needed it to exist.

The work spans a real-estate brokerage, a production studio, an education platform, an agentic tooling company, and a set of independent brands. The technology under them is deliberately boring where boring wins and deliberately unusual where it pays.

Where the work concentrates

  • Platforms & CRM06
  • AI systems & agents12
  • Growth & content engines05
  • Sites & brand craft08
  • Infrastructure & reliability02

How to read this site

Every project page covers the same five things: the problem that existed before it, what was actually built, the technical approach, the creative approach including what went wrong, and what it does now. Status is stated plainly — a prototype is labelled a prototype. Where a system holds client data it is described at architecture level and shown as a diagram rather than a screenshot.