Building and exiting CASA before I could vote

CASA didn't start as a company. It started on the door of somebody else's event, doing a job that wasn't mine, watching a room I hadn't built fail the crowd in the same small ways, night after night. The music was an afterthought. The door ran on vibes instead of a system. The whole thing was engineered to break even on effort, not to be good. I wasn't angry about it. I was taking notes.

What I noticed wasn't a gap in the market so much as a ceiling nobody had bothered to test. Teen events in Dubai ran to a standard that had simply never been challenged, because the people running them had no reason to challenge it — the tickets sold either way. I'd seen what good looked like, in other rooms, other cities, and I couldn't unsee the distance between that and what I was watching get sold as a night out. Somebody was going to close that gap eventually. I didn't see why it shouldn't be me, immediately, with no one's permission.

So I stopped promoting other people's mediocrity and started building the version I actually wanted to walk into.

That decision looked braver in hindsight than it felt at the time. What it actually meant, day to day, was a teenager asking venues, vendors, and parents to trust him with responsibility for a room full of other teenagers — and having to earn that trust from zero, every single time, because nothing about my age made the case for me. The pitch couldn't be a resume. It had to be the room itself, run properly, with nothing going wrong that a parent would hear about the next morning. Safety at scale for a teen crowd isn't a slogan; it's a logistics problem that has to be solved correctly before a single ticket is sold, and getting it wrong even once would have ended the whole thing before it started.

The first stretch of that was not glamorous. There was no outside capital — every event had to fund the next one, which meant the standard I was chasing had to be built on a budget that punished mistakes. Getting the door right, the sound right, the safety and the logistics right for a room full of teenagers, city after city, is a different job from promoting a night someone else is responsible for. Berlin and Hamburg weren't extensions of Dubai; they were each their own market, their own vendors, their own way of doing things, learned from zero every time. Scaling to three cities didn't mean repeating a formula. It meant re-earning the same lesson three times and getting faster at it each time.

It worked. Over the run, CASA put on 25+ events across Dubai, Berlin, and Hamburg, pulled a combined audience past 10,000, and peaked at over 1,000 guests in a single night — the kind of number that stops being an abstraction fast when you're the one responsible for every one of those people having a good and safe night. Lifetime revenue crossed six figures, off a standing start with nothing behind it but the conviction that the gap I'd noticed was real.

What that number actually taught me had less to do with events than with operating. At 1,000 guests, nothing scales by being repeated harder — the systems that worked at 100 people quietly break at 1,000, and you only find out which ones by being in the room when they do. Staffing, crowd flow, the margin for a single vendor running late: every part of the operation had to be rebuilt heavier as the numbers grew, and the version of me running the door on someone else's event a year earlier wouldn't have recognized how much of the job was now invisible — solved before the doors opened, not managed once they were.

The exit, when it came, wasn't a retreat. By the time I handed it over, CASA didn't need me in the room to run to standard — which was the actual finish line I'd been building toward the whole time, even if I hadn't said it that plainly at the start. The mission was never "run events forever." It was "prove the standard could be higher, then make that provable without me." Once that was true, holding on longer would have just been sentiment. A five-figure handover closed it out, to someone who'd keep it running the way it was meant to run.

I won't pretend letting go of something that worked was frictionless. It wasn't nostalgia that made it hard — it was the part every founder underrates until they're in it, which is that handing off something real means trusting somebody else with the standard you fought to set, and there's no version of that where you get to keep full control and still call it an exit. You build the thing so it doesn't need you, and then you have to actually believe that, past the point where believing it costs you something.

The lesson I keep re-using in every venture since isn't "start a business." It's more specific than that: start ugly, inside an industry you don't yet have standing in, until you've learned it well enough to see exactly where it's failing people. Then build the version that should have existed from day one — and be willing to let go of it the moment it can stand up without you. Compounding only works if you're willing to hand off the thing once it's built, and go build the next one.