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.
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.
I wrote a full 360° blueprint before building, anchored on principles chosen to survive to 2040, not to demo well next quarter:
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.
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.
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.
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.
A model ships only when it beats the working heuristic on cross-validated evidence. No model zoo you cannot feed. That is theater.
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.
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.
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:
Drafts only. A human executes everything.
Acts, but a human approves each action.
Self-approves low-risk actions within rules; asks on high-risk.
Runs routine deals end-to-end; escalates exceptions only.
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.
| Mode | Runs on | AI engines | Cost / month |
|---|---|---|---|
| Local free | One laptop + Docker | Free cloud + local models | $0 |
| Cloud free | Free-tier cloud server | Free cloud models | ~$1 |
| Boosted | Same server | + paid frontier models | ~$15–40 |
| All-in | Scaled cloud | + paid frontier models | ~$100–300 |
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.
If a consultant shows you an AI case study with no section like this one, ask why.