Notes from the floor and the terminal.
What I learned running events and building systems, written down while it was still fresh enough to be useful. The long-form guides live on the Freelancers page.
The long ones.
Three engagements written up properly, with the numbers and the parts that went wrong.
Auto Pilot Events OS
95 tools, 7 agents, 753 tests green, built solo in 28 days.
Protocol at scale
Delegations from 140+ countries, seven programmes, three contracting relationships.
I am not a landscaping expert
Producing a public festival in Al Ain, and what it taught me about scope.
Shorter pieces.
These went out on LinkedIn. The cards below are an index of what has been published, not links: the posts themselves live on LinkedIn, and the button under the grid goes straight there.
Everyone builds AI for lawyers. Nobody builds it for events.
Two thirds of the guesswork, gone.
60 chauffeurs. Every airport in Dubai.
Protocol under pressure.
A production office, in software.
What AI runs in events. And what it must not touch.
7 things that quietly kill an event.
6 signs you are busy, not productive.
Everyone quotes two numbers. Nobody reads the third.
It is not coming for your job. It is coming for your calendar.
Most people are learning the wrong 20%.
Where to start with AI. Free first, in order.
A tool purchase with a press release attached.
The bottleneck is not budget. It is translation.
Nothing in that category yet.
Try another filter.
What is the question you keep hitting?
Most of these started as something somebody asked me on a build week. If yours is not here, ask it.