The floor
Delivering against a date that does not move. Run sheets that survive contact, vendors who are late for a reason, crowd flow, the handover, and what a show call sounds like when something has already gone wrong.
I have delivered seven programmes across GITEX, COP28, the Dubai World Cup and Gulfood, then built the AI system that runs the operations side of that work: 95 tools, 7 agents, 753 tests green, written solo in 28 days. Almost nobody teaches both halves, because almost nobody has done both. This is where I put down how each one is actually done. It is not open yet.
Not open yet
Dubai · GCC · OnlineTell me what to cover ↗
Nothing here is filmed yet. This is the shape, written down so you can tell me where it is wrong before I record a minute of it.
Delivering against a date that does not move. Run sheets that survive contact, vendors who are late for a reason, crowd flow, the handover, and what a show call sounds like when something has already gone wrong.
Turning that operation into software without a computer science degree. What an agent can actually close on its own, what it must never be handed, and how to tell the difference before it costs you a client.
Where the two meet. Most AI teaching is written by people who have never called a show, and most operations teaching is written by people who cannot ship. The join is the whole reason this exists.
There is no waiting list, no email capture and nothing to pay for. If you run events, or you are trying to put AI into an operation and it keeps falling over, send me the part you are stuck on. The ones that come up most get built first.
Until it opens, everything I have written down already sits on Resources, free and ungated. So: what is the part of your operation you would want covered first?