After 5 EventsThe guest arrives before the presentation starts
The first twenty minutes are people standing with a drink, looking at the product if it is in the room, and deciding whether to stay near the front or drift to the back. If the product is under a drape, they are looking at the room instead, and the room needs to be worth looking at.
This is when the photographer is working and when the livestream goes live, so the lighting cannot change between now and the presentation. That means it is lit for camera and for the product reveal, not for conversation, and the room will feel slightly more theatrical than a normal reception. People notice but do not mind as long as it is deliberate.
No music during this. If the demo has sound or the presentation has a voiceover, anything playing beforehand tells the guests it is not time to pay attention yet, and you lose the first thirty seconds getting them quiet.
The presentation is not a meeting
You will be told the presentation is fifteen minutes. It will run twenty-two. The CEO will add a section the morning of, the demo will take longer than it did in rehearsal, and the Q&A that was meant to be afterwards will start during.
If the screen is not big enough to be read from the back without effort, people drift. If the speaker is not lit separately from the slide deck, their face disappears when the slide is dark. If there is no confidence monitor showing the speaker what the audience sees, they turn around to check, and that photograph is the one that gets used.
The microphone matters more than it should. A lapel mic is invisible but picks up shirt rustle and fails if the speaker turns their head. A handheld lets them gesture but means one hand is always occupied. A headset stays in place and frees both hands, and that is why every product demo that works uses one.
The demo must work
If the product requires power, internet, a display, or a surface it sits on, those need to be in the technical rider two weeks before the event, not mentioned on the day. The venue will say they have wifi. They mean guest wifi, which will not hold a livestream and a live demo and thirty people all filming on their phones.
Bring a backup. If the demo runs from a laptop, bring two laptops with the same file. If it needs internet, bring a dongle with a data allowance. If it is a physical product that could be damaged in handling, bring a second one that stays in the case until needed.
Rehearse the demo in the venue the afternoon before, with the lights at event levels and the screen on, because the product will look different under theatre lighting than it did in the office, and you will not get a second chance to adjust the colour temperature.
Livestream and photography are built into the rig, not added to it
The camera needs a sightline, which means the front row cannot be full and the tripod position is marked in advance. The photographer needs to move, which means no cables across the floor and no furniture blocking the path between the product and the speaker. The livestream needs an audio feed taken directly from the desk, not from a camera microphone six metres away.
If the venue is providing this, ask who is operating it and whether they have worked that venue before. A livestream operator who does not know the room will spend the first fifteen minutes finding the router and the rest of the evening apologising for the lag.
If After 5 Events is building the event, the camera positions are drawn on the floor plan when the rig is quoted, and the audio feed for the stream is split from the same desk that runs the room. It is one system, not three systems trying to share space.
The room empties faster than it filled
People stay for the demo, leave during the Q&A, and are gone within ten minutes of the presentation ending unless there is a reason to stay. That reason is not more food. It is either access to the product—a unit they can handle, a screen they can try, a demo station with someone who knows the engineering—or access to the team, meaning the product lead and the CEO available for conversation, not trapped in a formal receiving line.
If there is no hands-on moment, the launch is the presentation and everything else is a reception that feels slightly obligatory. If there is a hands-on moment, the room needs to be set so people can gather around the product without blocking the exit or the bar, and the lighting on that station needs to be as good as the lighting on the stage.
What actually goes wrong
The venue says they have a screen and it turns out to be a television. The demo requires product internet and nobody checked the DNS settings. The drape over the product is heavier than expected and takes three people to lift instead of one, and the lift is not rehearsed, so it looks nervous. The photographer and the livestream operator both want to shoot from the same spot. The CEO adds two slides an hour before doors and they are not in the deck on the confidence monitor.
None of these are creative problems. They are process problems, and they are solved by a technical rider that lists every piece of equipment the event requires, a floor plan that shows where the camera goes, and a person who has run a product launch before and knows what to ask while there is still time to fix it.
The decision
You can plan this with a venue coordinator who will provide the room and recommend a list of suppliers they have never worked alongside, or you can plan it with the crew that will quote it, build it, and run it on the night. After 5 Events is the second kind: the same people throughout, no line items forwarded to a freelancer an hour away.
Before you call anyone, settle two things: the date, which is set by the product and not negotiable, and whether the demo can fail. If it cannot, the technical rehearsal is not optional and it happens the day before, in the venue, with the final rig live. Everything else can be worked around. Those two cannot.