Method

No event runs as planned. And that’s fine.

RMIX 10-minute read On planning and execution

There’s a truth every seasoned producer knows and no sales brochure admits: there is no event that runs exactly as planned. None. In twenty-five years and over fifteen hundred productions, we haven’t seen a single one.

And we’re not talking about catastrophes. We’re talking about the everyday. The truck carrying the structure is delayed at the border. The generator that ran perfectly in testing sputters at six in the evening. The keynote speaker moves his arrival three hours. It rains when the forecast said it wouldn’t. The room measured on the plans has, in reality, a column the plans didn’t show.

Each of those imponderables is minor on its own. Together, and at the last minute, they’re the difference between an event that happens and one that falls apart. The real work of a production company isn’t to prevent them from appearing —that’s impossible— but to be ready for when they do. All of them. At once. With the clock running.

A plan isn’t a document you follow. It’s the base from which you improvise with judgment.

The plan isn’t the deliverable. The ability to adjust it is.

When a client hires a production company, they think they’re buying a plan: a schedule, a technical rider, a supplier list. That’s what they see, and that’s what they compare across quotes. But it’s not what they really need.

What they need —even if they don’t know it yet— is the assurance that, when the plan meets reality, someone has already thought about what to do. A good plan accounts for its own breakdown. For every critical decision there’s a ready alternative, and behind that alternative, another. Not because we’re pessimists, but because we know the craft.

Plan A — what’s presented

The production as designed and approved. It’s the one the client knows, the one in the contract and the one that, with luck, runs almost entirely.

Plan B — what’s almost never seen

The alternative prepared for every point that can fail. A second generator already connected. A backup supplier with the order ready. Rain coverage that requires no decision under pressure.

Plan C — what we hope to never use

The fallback. What to do if the unthinkable happens anyway. Having it written isn’t distrust: it’s the only way to stay calm when everything else has shifted.

The cost of preparing three plans when one almost always suffices is real. It’s time, foresight, money the client sees reflected in nothing tangible. That’s why it’s so easy to cut, and why so many production companies cut it. The difference shows just once: exactly the day it’s needed.

Getting ahead is cheaper than correcting.

One rule governs all production: the later a problem appears, the more expensive it is to solve. A change in the design stage is fixed with a conversation. The same change during setup is fixed by dismantling what’s done, paying twice and negotiating with the clock.

That’s why the real work begins long before the first light comes on. It’s anticipating. Walking the site before being asked. Asking about the river’s flood level at that time of year. Confirming the power supplier has the backup it claims. Every uncomfortable question we ask in the planning stage is a problem we won’t have to solve, against the clock, the night of the event.

And there’s a part the client shouldn’t see.

Here, for us, is the heart of the craft. When an imponderable appears —and it does— there are two ways to handle it.

The first is to pass it to the client. “We have a problem with the generator, what do you want us to do?” It’s comfortable for the production company: it shares responsibility, covers your back. And it’s exactly what a client doesn’t need on the day of their event, when they already carry all the pressure of their convention, launch or celebration going well.

The second is to solve it. Silently. The backup generator kicks in before anyone notices the first one failed. The late speaker finds his place without the program visibly changing. The rain has its plan and that plan executes while the audience keeps talking, oblivious to it all.

We deliver solutions. We don’t hand over problems.

This doesn’t mean hiding important information or making decisions that belong to the client. It means understanding the difference between what the client must decide and what we must solve. The budget, the identity, the message: that’s theirs, and it’s discussed. That the backup cable is laid just in case: that’s ours, and it’s not up for discussion. It’s simply our job.

To the client and the partner we give something more valuable than a problem-free event: we give them the peace of not having to find out about the ones there were. That peace —knowing that, whatever happens, someone has already thought it through— is what’s really hired when hiring well.

That’s why excellence is measured by what was never seen.

Do you have an event where there can be no surprises in sight?

Start the conversation

Method

Call the producer before you have the problem.

RMIX8-minute readOn when production comes in

Most agencies call us once the idea is already sold, the budget closed and the date looming. They call us, in short, when they already have a problem. And we do what we can. But we could do much more if they'd called earlier.

It's not a complaint. It's an observation of the craft. There's a pattern that repeats over twenty-five years: the event turns out better, and costs less, when technical production comes in early. Not at the end, to execute what's already decided, but at the start, when there's still room to decide.

An idea changes with a conversation. The same idea, already built, changes by dismantling, paying again and fighting the clock. That's the whole difference, and it happens because of one simple rule that governs any production.

The later a problem appears, the more expensive it is to solve. Always.

What an agency sees. What we see.

When an agency conceives an idea, it thinks from what it wants the audience to feel. That's right: it's their craft and what they do best. But that idea, to happen, has to pass through physics: weights, power loads, load-in times, flood levels, permits, distances. We see that from the first minute. Not to stop the idea, but so it's born viable.

The typical scene is this: an agency presents a spectacular idea to the client, the client approves it enthusiastically, and only then does someone ask how much it costs and whether it's possible. Sometimes the answer is no. And then you have to go back to the client to explain that what they approved wasn't feasible. That's the worst moment to find out.

If we're in the brief, that moment never comes. The idea is adjusted before it's sold, not after. The client approves something we already know can be done, with a real number, not an optimistic estimate that later has to be corrected upward.

Coming in early isn't coming in to take over.

Here it's worth being clear, because it's every agency's reasonable doubt: bringing production in early doesn't mean giving up the creativity. Quite the opposite. The idea stays with the agency, entirely. We don't propose concepts or talk to the client. What we bring is one single thing, early: a viability judgment that turns an ambitious idea into an ambitious and executable idea.

It's the difference between a partner and a supplier. A supplier receives a plan and quotes. A partner sits down before, listens to what you want to achieve, and helps make sure the path there has no expensive surprises. The agency loses no control. It gains a safety net that starts working from day one.

In the brief it costs a conversation

Nothing is built yet. Changing the scope, the material or the scale is free: you just think about it differently.

In design it costs time

There are sketches, renders, a direction taken. Correcting is still possible, but it's already paid in redone hours of work.

In setup it costs double

Suppliers are hired, the structure is up. Every change is paid twice: what's canceled and what's redone. And the schedule no longer gives.

No agency chooses to come in late on purpose. It happens because production is perceived as the last link, the one that executes. Our proposal is simple: move us a spot toward the beginning. Not to weigh in on the idea, but so the idea reaches the day of the event intact.

Production isn't what happens after everything is decided. It's part of deciding well.

Getting ahead is cheaper than correcting. And it hurts less.

Got a big idea and want to know if it's possible before selling it?

Start the conversation

Craft

The audience sees the show. We see the structure.

RMIX9-minute readOn the roles you don't see

When an event goes well, the audience remembers a moment: the light that dimmed just right, the sound that came through clearly, the transition that flowed without anyone noticing. What they don't see —what they shouldn't see— is how many people it took for that moment to happen without a single stumble.

An event isn't held up by one talented person. It's held up by a structure of roles, each with a clear responsibility and none stepping on the other. When that structure is well built, it's invisible. When it's missing, you notice right away.

Loose talent isn't enough. What holds up an event is that every cable has someone responsible.

The mistake that costs dearly: the one-man band.

There's an understandable temptation, especially when the budget is tight: hire a single person to "handle everything". Sound, video, lights, coordination. It sounds efficient. It's a trap.

We've seen it many times. The single technician is wrestling with a microphone that's feeding back, and at that very moment the institutional video has to launch. They can't be in two places at once. So something drops: either the microphone keeps screeching, or the video doesn't come in when it was supposed to. It's not a lack of talent. It's a lack of hands. One person can't solve two simultaneous emergencies, and at an event the emergencies are always simultaneous.

Hiring professional production isn't hiring someone who can do everything. It's deploying specialists who each do one thing, and do it well, at the same time. Peace of mind has a cost, and that cost is exactly what keeps someone from improvising with your brand's image.

Who does what, when no one sees them.

The structure varies by event, but there are roles that are almost always there, even if the audience doesn't know they exist. They're worth naming, because each one is a way of keeping something from going wrong.

The head of production

The architect of the operation. Translates what the client wants to achieve into a technical plan that can be executed. Coordinates all the teams before the first light comes on.

The show caller

The voice of command live. Calls the entrances —the "cues"— of every video, every light, every change, following the running order to the second. Without them, synchronization is impossible.

The crew chief on the ground

The foreman of the setup. Coordinates the crew during load-in and assembly, guaranteeing timing and, above all, safety. The one who makes sure a rigged structure is never a risk.

The specialist technicians

Sound, lights, video, each with their chief and their team. They're not interchangeable. The one mixing audio for the room isn't the one adjusting the signal for the streaming. Each front, its specialist.

We could go on: the one who guards the frequencies so wireless mics don't interfere, the one who aligns the projectors so the image is geometrically perfect, the one who receives remote speakers and checks their signal before giving them the go. Each role is an anticipated answer to a question the audience never asks: what if this fails?

The structure is what buys peace of mind.

What sets a serious production apart isn't how many people it deploys, but how clear it is who answers for each thing. When every task has an unequivocal owner, no gaps are left. And the gaps —those spaces where "I thought the other person was doing it"— are exactly where the failures the audience does end up seeing are born.

Leaving the technical structure to chance, or in the hands of a single overloaded operator, is a risk a brand's reputation can't afford. The method exists precisely so that on the night of the event no one has to improvise.

If we did our job well, you won't know we were there.

Does your next event need a structure that won't fail?

Start the conversation