Event-sourced spine
Postgres with pgvector underneath. Every state change is an event, so the system can be replayed, audited and reasoned about rather than just queried.
So I learned to build. These are the systems that came out of twelve years of watching what actually breaks.
An AI operating system for running an experiential events company. Built solo in 28 days, from 15 June to 12 July 2026. In production usage since the day it shipped.
No client ROI figures yet. When there are, they will appear here with a source.
Built for an established UAE experiential events group operating across the GCC.
Postgres with pgvector underneath. Every state change is an event, so the system can be replayed, audited and reasoned about rather than just queried.
Specialist agents for the distinct jobs, with a director that routes work between them instead of one model trying to hold everything at once.
A working Next.js front end, not an API and a promise. Roughly 25k lines of Python and 14k of TypeScript behind it.
Runs from zero dollars a month up to roughly three hundred, depending on which models are enabled. The cheap mode is genuinely usable, which was the point.
The part I am most willing to be questioned on, because the numbers came out of a validation run rather than a pitch deck.
| Measure | Result |
|---|---|
| Real price points used | 1,136 |
| Baseline mean absolute error | 41,432 |
| Model mean absolute error | 13,927 |
| CatBoost promoted over baseline | +7.6% and +8.1% |
Twelve years of knowing what breaks is the actual moat. The code is the easy half.
A personal AI operating system. Domains, persistent memory, scheduled briefs and a runner that does not sleep. I use it every day, which is the only review that matters.
Kaggle Expert with six published notebooks. Breast cancer detection at 98%, churn prediction at 86%. Python, SQL, Power BI and Tableau.
One source of record behind every figure published under my name. If a number is not in it, it does not go on a page. That rule is why this site is short on superlatives.
That is usually the one worth automating first. Tell me what it is and I will tell you honestly whether it is worth building.