Ten Years of Cosmic Production: What a Decade of Events Taught Me About Systems

It’s 6 a.m. and we’re loading the truck in the dark. The venue won’t open its gates for another hour, the coffee is bad, and nobody at the event we’re building will ever see this part. By the time the first guest walks in tonight, the cables we’re coiling now will be taped down and invisible, the spare microphone will be sitting in a case nobody opens, and the whole morning will have vanished into a room that looks like it simply happened. That hour in the dark is the job. The night is just where it shows up.

Cosmic Production is our family business in Split, and I’ve spent the ten years since 2016 building sound, AV, and production for events across Croatia — weddings, brand activations, and hospitality work from Split out to Hvar, Brač, and Dubrovnik, plus permanent installs in hotels like the Radisson Blu and Le Méridien Lav. Somewhere past five hundred events and fifty fixed installations later, the pattern is finally obvious. For a long time I thought I was getting better at events. That’s the obvious story: more years, more shows, sharper instincts under pressure. It took me most of the decade to notice that wasn’t what was happening at all.

What was happening is that I was learning the event is the visible tip of a system. And the system gets built when no one is watching.

The show that went perfectly

Ask me about a night that went flawlessly and I’ll struggle to tell you a story, because nothing happened. The good nights are the boring ones. No scramble, no near-miss, no moment where the room held its breath. Just sound that was right, light that arrived on cue, and a client who got to feel like the evening ran itself.

Every one of those nights traces back to the same unglamorous thing: the prep was done. The site was walked in advance. The power was checked before it was needed, not after it failed. The cues were written down where someone other than me could read them. The boring work was finished before anyone arrived to be impressed.

The nights I’d rather forget were the opposite — not because the crew was worse or the gear was weaker, but because somewhere a step had been skipped and we were paying for it live, in front of people. You can be brilliant at improvising under pressure. I got good at it. But getting good at improvising is just getting good at surviving the absence of a system. It’s a skill you build because you keep needing it, and you keep needing it because the real work didn’t get done upstream.

That was the turning point. The heroics aren’t the achievement. The heroics are the bill for prep you didn’t do.

What the redundancy taught me

The clearest lesson came from the line item clients always question: the spare. The second microphone. The backup channel. The duplicate of the one thing that genuinely cannot fail at the one moment that genuinely cannot wait — the speech, the first dance, the announcement the whole evening is built around.

Redundancy is invisible right up until the second it saves you. Most nights the spare mic goes home in its case, untouched, looking like money wasted. Then one night a cable dies mid-sentence, you swap to the channel that was already live and ready, and the room never knows anything happened. Nobody applauds the backup. Nobody ever will. That’s the whole point of it.

I’ve come to think that’s true of every system worth building, far beyond a stage. The work that prevents the disaster is invisible precisely because it works. You don’t get credit for the fire that didn’t start. So the temptation — in events, in any business — is to cut the thing you can’t see the value of, because on every ordinary day it looks like overhead. Until the one day it’s the only thing standing between you and the story everyone tells on the drive home.

The client never sees the work

Here’s the part that took me longest to make peace with. The better the system, the less anyone notices it. A flawless event looks effortless, and “effortless” quietly erases the morning in the dark, the contingency plan, the third walk-through of the room. The client isn’t paying for what they see. They’re paying for the absence of everything that could have gone wrong — and absence is hard to point at on an invoice.

For years that bothered me. Now I think it’s the truest measure of whether the system is any good. If the work is showing, the system is failing. The goal was never to be seen doing the impossible. The goal was for the night to feel like nothing was ever at risk.

The same discipline runs everything

What I didn’t expect is how completely this transfers. The discipline that runs a festival stage — map it before you build it, make the critical thing redundant, write the process down so it doesn’t live only in your head, finish the boring part before it’s urgent — is the same discipline that runs a business. An event is just a system with a hard deadline and an audience, which makes every weakness in it visible faster than anywhere else. Run enough of them and you stop seeing events. You start seeing the structure underneath, and the structure is the same whether the deadline is doors at eight or a client who needs to stop losing leads.

That’s what I actually do now. The stage taught me to see the system; the work since has been building those systems for people who don’t have a 6 a.m. load-in to teach them the lesson the hard way.

So I didn’t spend ten years getting better at events. I spent them learning that the event was never the thing. It’s 6 a.m. and someone’s loading a truck in the dark, somewhere, right now, taping down cables no guest will ever see. By tonight it’ll all be invisible. That was always the work. The show is just where it finally shows up.