Case study · Flagship build

Auto Pilot Events OS

An AI operating system for an established UAE experiential events group operating across the GCC. An institutional brain that ingests everything the business produces, learns its economics, and runs the deal lifecycle from RFP to production under human supervision. Architected, built and shipped in 28 days by directing a fleet of AI coding agents.

28 days
Concept → live
95
Registered AI tools
7+1
Agents + director
753
Automated tests, green
$0/mo
Running-cost floor
01

The problem: every events company runs on tribal knowledge

I have spent twelve years inside large-scale live events in the UAE: GITEX, COP28, Dubai World Cup, government galas. The pattern is the same everywhere: the company's real intelligence lives in a handful of heads and a graveyard of old Excel sheets.

An RFP lands. Someone digs through past quotations to remember what a 6-metre stand, an LED wall or a custom counter actually costs. Pricing is inconsistent between estimators. Supplier knowledge is personal, not institutional. When a senior estimator leaves, years of pricing instinct walk out the door with them.

Nothing the company learns on one deal makes the next deal any smarter.

That is the actual transformation problem, and it is not "add a chatbot." The fix is structural: a system of record that turns every document, every quote and every correction into compounding institutional memory.

02

The design bet: five principles before a line of code

I wrote a full 360° blueprint before building, anchored on principles chosen to survive to 2040, not to demo well next quarter:

Agent-native, not agent-added

The default operator is an AI agent; humans supervise through approval gates. The UI is a window into what agents are doing, not a pile of forms.

Every capability is a tool

Pricing, 3D-file parsing, BOQ splitting, supplier discovery. Each is one typed, documented tool. A human clicks a button; an agent calls the same tool. No human-only capabilities.

Event-sourced memory

An append-only log of every business event is simultaneously the audit trail, the agents' working memory, and the ML training data. One design, three payoffs.

Degrade, never disappear

If a paid AI engine is unavailable, every feature still runs on a cheaper or local one. Nothing crashes, nothing blocks. This is what makes the $0 mode real.

ML is earned, not flipped on

A model ships only when it beats the working heuristic on cross-validated evidence. No model zoo you cannot feed. That is theater.

03

What was built

FRONT DOORS document drop zone · RFPs · SketchUp / 3D files · renders · pricing sheets · chat THE BRAIN Typed API · auth & role-based access · 95-tool registry THE SPINE Append-only event log: audit trail · agent memory · training data Agent runtime 7 specialists + a director, 24/7 Learning loop every correction → training signal Control room 23-page web app + chat assistant Model gateway routes every AI call: free local models ↔ free cloud ↔ paid frontier. Swappable, never load-bearing
04

The pricing brain: measured, not promised

The heart of the system learns what things cost from the company's own history. All results below were measured on real historical pricing data, cross-validated, and verified live against the running system, not projected.

Pricing error, median absolute error
Baseline model66% lowerlive-verified
A ⅔ reduction in pricing error, achieved by teaching the system to tell real line items from lump-sum totals and allowance buckets: 57% of the raw training frame turned out to be noise, detected and excluded by deterministic rules, with no guesswork.
Learned model vs. working heuristic, cross-validated
+7.6% / +8.1%live-verified
The gradient-boosted pricing model was only allowed to take over after clearing three statistical bars on cross-validation: beat the median baseline by ≥5%, beat the simpler regression by ≥5% (it cleared +14.9% and +15.8%), and produce a full explanation of its own pricing logic.
The model's learned pricing logic, explainable
learned, and explainable
The model does not just output a number, it outputs the reasoning: which materials, which heights and which build characteristics pushed the price, ranked by how much each one contributed. Those learned adders read like an estimator's own mental model. When a model can explain itself in the language of the trade, operators trust it, and correct it, which trains it further. The adders themselves are the client's commercial pricing structure and are not published here.

The part most AI projects skip: the first trained model looked 31% better than the regression, but only 1% better than a simple median. The system's promotion gate rejected it as theater. It also demotes a previously live model whose retrain no longer clears the bar, and when asked to break down a cost section it has too little history for, it refuses and says so rather than inventing a split. Honesty is enforced by machinery, not by intention.

05

Governance: autonomy is earned one capability at a time

Directors don't get asked "can you build AI?" They get asked "can you control it?" Every agent action passes through safety tiers, and each capability climbs this ramp only as evidence accumulates:

STAGE 1
Assistant

Drafts only. A human executes everything.

STAGE 2
Co-pilot

Acts, but a human approves each action.

STAGE 3
Supervised autopilot

Self-approves low-risk actions within rules; asks on high-risk.

STAGE 4
Autopilot

Runs routine deals end-to-end; escalates exceptions only.

06

Cost engineering: four modes, zero breakage

One environment variable moves the entire system between four cost postures: same containers, same database schema, same features everywhere. Capabilities degrade gracefully; nothing disappears. An events company can start at literally zero and pay only when volume justifies it.

ModeRuns onAI enginesCost / month
Local freeOne laptop + DockerFree cloud + local models$0
Cloud freeFree-tier cloud serverFree cloud models~$1
BoostedSame server+ paid frontier models~$15–40
All-inScaled cloud+ paid frontier models~$100–300
07

How one person shipped this in 28 days

I built this the way I'd run an AI-transformed company: as the director of a fleet of AI coding agents, not as a lone typist. Frontier models drew the architecture and reviewed the hard decisions; workhorse models implemented scoped, pre-specified batches; every batch shipped with tests and was verified live against the real system before the next began.

That workflow, blueprint first, typed tool seams, statistical promotion gates, human approval tiers, test-gated AI batches, is the same operating discipline I bring to transforming a business. The codebase is the proof it works.

08

What I will not claim

Read this before you believe the rest
  • It is not finished learning, and that is the design. The hard work is done: the corpus is built, the pipeline runs, the promotion gate works. Accuracy now improves with volume, so the more history a company feeds it, the sharper it gets. Any vendor telling you their pricing model is finished on day one is selling you something.
  • No revenue-ROI figures yet. The system entered production use on July 12, 2026. Client-facing ROI numbers (hours saved per quote, win-rate movement) will be published once real usage produces them, measured like everything above.
  • The accuracy numbers are technical, not commercial. They are cross-validated error reductions on real historical data. Strong evidence the learning works, not a promise about your P&L.
  • Some capabilities are deliberately dormant. Deal-outcome prediction, for example, activates itself only after ~100 closed deals of data exist. It would be theater to switch it on sooner, so it's off.

If a consultant shows you an AI case study with no section like this one, ask why.