How to run a 500-person keynote with a two-person crew

There is a moment in every keynote where the room goes quiet and the speaker looks at you as if to say "we are really doing this, aren't we." That moment happened to me at a fintech conference in Berlin last March, forty seconds before a 500-seat auditorium was about to hear a 48-minute product launch with exactly two people running the entire show. Me and a stage hand. Here is how we pulled it off, because it changed the way I think about live event tooling. The show had five segments. An opening video, the main keynote address, a live product demo, an audience Q&A session, and a closing bumper. In a traditional setup you would expect a show caller, a graphics operator, a timer operator, a camera director, maybe a producer feeding lines to the speaker, and someone managing the audience microphones. That is at least six people, and honestly I have seen bigger crews for shorter shows. What made this particular event possible with two people was a combination of pre-show preparation and the right software architecture. The entire rundown lived inside Timers Studio as an agenda with five cues. Each cue had a duration, a speaker name, a title, and a set of notes visible only on the moderator console. The agenda player was sent to two screens: one confidence monitor facing the stage, and one large display visible to the audience showing a countdown. The first thing we set up was the Gateway. This is the audience-facing surface that lets people submit questions through their phones. We printed the QR code on the event program and on the holding slide. By the time the keynote started, we already had a dozen questions queued up, which meant the Q&A segment practically ran itself. The moderator player was the command center. From a single tablet backstage, I could see every cue in the rundown, the live countdown for the current segment, all incoming audience questions, and the intercom chat with my stage hand. I never had to switch apps. I never had to look at a second screen. Every piece of information I needed was on one surface, updated in real time through Server-Sent Events. When the opening video started, I tapped "next cue" on the moderator console, which auto-started the 48-minute master countdown on the audience display and the confidence monitor simultaneously. The speaker could see her remaining time in large glowing digits on the confidence monitor, and I could see the same information plus notes on my tablet. When she hit the demo section, I tapped next cue again. The timer reset to the demo duration and a flash message appeared on her monitor saying "DEMO START." She never lost her flow. The demo itself had a tricky moment. The product needed a live API call to complete a transaction, and the response took between two and eight seconds depending on network conditions. We had pre-configured a "hold" message that appeared on the confidence monitor during the wait, telling the speaker that the system was processing and she should fill time with the rehearsed talking points. That single flash message, triggered by my stage hand watching the demo screen and pressing a Stream Deck button mapped to the Timers Studio API, saved us from what could have been an awkward silence. The Q&A segment is where the Gateway really proved its value. Instead of passing a microphone around the room, which eats time and creates audio feedback risks, the audience submitted questions through their phones. I could see every question on the moderator console, approve or dismiss them, and push the selected ones to the confidence monitor so the speaker could read them out loud. The audience saw their question appear on the big screen, which created a genuine moment of connection that a handed microphone simply cannot replicate at scale. Here is the part that surprised me the most. The entire show ran three minutes under its 48-minute slot. Not because we rushed, but because the tooling eliminated every dead-air moment that usually pads a keynote. No "can we get a microphone to row seven," no "let me check my notes," no fumbling with timers on a laptop. The transitions between segments were instant because the cue system handled them automatically. My stage hand, who had never used Timers Studio before that morning, told me after the show that it felt like being a co-pilot in a cockpit. Every status indicator was where you expected it. The intercom meant he never had to leave his position by the stage-left curtain. And the Stream Deck integration meant his physical button presses had immediate, visible feedback on every screen in the room. If you are planning a keynote and wondering whether you can cut your crew size, the honest answer is: it depends on your willingness to prepare. The show itself ran on software. The preparation ran on discipline. We spent four hours programming the cue list, testing every transition, rehearsing the flash messages, and verifying that the Gateway worked on the venue Wi-Fi. That four hours of prep replaced four additional crew members. The economics are straightforward. A six-person crew for a half-day event costs between three and five thousand euros when you factor in travel, day rates, and equipment. A two-person crew with a Timers Studio subscription costs a fraction of that. For a corporate client funding an annual conference cycle, the savings add up fast. I am not suggesting that every show can run with two people. A multi-camera broadcast with live switching and graphics overlays absolutely needs dedicated operators. But for the standard corporate keynote, the technology has caught up to the point where a well-prepared two-person team can deliver a production that feels like it had ten people behind it. That is the real story of Berlin. Not that we saved money, though we did. Not that we proved a point, though the client noticed. The real story is that the speaker said it was the smoothest keynote she had ever given, because every piece of information she needed was always exactly where she expected it. And that, at the end of the day, is what show control is supposed to deliver.