When an engagement calls for a model or an AI prototype, I build it rather than commission it. A product and a set of working prototypes, built on my own time, and the reason I can say what these systems do and do not do well.
AI product, launching September 2026
Strafi
A strategic finance intelligence product for owner-managed businesses (strafi.co). It connects to the systems a business already runs on, accounting, payments, pipeline, reads them together, and tells the owner what needs attention while there is still time to act.
Python and Flask on PostgreSQL, with an LLM reasoning layer on the Anthropic API. Live integrations with FreeAgent, Xero, Stripe, HubSpot and Companies House, with more being connected. Built with AI coding tools, which is possible now in a way it was not three years ago.
Working experiments
AI prototypes
Various tools in Python and Next.js, on the questions engagements keep raising: the economics of AI investment at scale, diagnostics for growth-stage businesses, and others.
These systems fail in a particular way. Given thin or inconsistent data, a model will still produce a fluent answer. Most of the work goes into deciding what the system is allowed to conclude, and showing the basis for every conclusion it reaches. That is the part I would want to see before trusting one of these in a business.