The date decides the venue
A product launch date is set by engineering, supply chains, and board calendars. You inherit it. The venue has to fit that date, which means you lose your leverage in negotiation and sometimes lose the venue you wanted.
Book the room as soon as the date is firm. If the product slips, renegotiate. Most venues allow one move without penalty if you tell them early. Waiting to book until the product is certain leaves you with whatever is still available.
The guests come for the product, not the evening
Your audience is customers evaluating a purchase, press deciding whether to cover it, and partners deciding whether to recommend it. They tolerate the event format because they want the information. The whole structure serves one moment: the product working in front of them.
That shapes everything else. The presentation is the content. The demo is the reason they stayed. If the founder speaks for twenty minutes before showing the product, half the room is checking their phone.
Reveal it early. Explain it after. Let them see it working before you tell them how it works.
Build for cameras before you build for the room
A product launch is documented. Photographer, video, often a livestream. The coverage outlives the event, and the coverage is what the people who were not there will judge you on.
The technical build follows the camera, not the guest. The product needs to be lit so it reads on screen. The speaker needs a microphone that does not fight the acoustics. The demo needs to be visible from the camera position, not just from the front row.
If you are streaming, the internet connection is the first thing to test and the last thing to assume. A venue promises WiFi; you bring a cabled backup. The stream going dark during the demo is the failure everyone remembers.
The demo is a technical event, not a presentation
If the product is software, you need a screen large enough to show interface details from the back of the room, HDMI routing that does not add lag, and a laptop that will not restart for updates while the CEO is speaking.
If the product is hardware, you need a stage or a plinth that positions it at the right height for the camera, lighting that does not create glare on the surface, and a backdrop that does not compete with it visually.
Rehearsal is not optional. The product will fail in some small way during setup — a cable, a login, a screen timeout — and you find that in rehearsal, not in front of customers.
Two kinds of event company run product launches
One kind plans the event, writes the brief, then sends it to subcontractors: an AV company for sound and screens, a caterer for food, an agency for video, a florist for staging. The planner has never worked with most of them and earns a margin on every line. When the demo laptop will not talk to the projector, the planner calls the AV company, who send someone.
The other kind quotes, builds, and runs the event with the same crew. The person rigging the screen is the person who will troubleshoot it, and the technical lead in the rehearsal is the same one standing in the wings during the presentation. Nothing is forwarded.
The difference becomes visible when something breaks. It always does.
What a guest sees
They arrive at a venue that is easy to find and has somewhere to leave a coat. Registration is fast. There is coffee, and if the event is evening, something to eat that does not require a plate and a fork at the same time.
The room they are led into has seating that faces the product. The screen is large and readable. The sound is clear and not loud. The product is lit. When the presentation starts, it starts on time.
The product is revealed in the first five minutes. The demo works. The founder or the product lead speaks briefly and shows the product working longer. Questions are invited and answered. If there is food afterward, it happens in a different space so the people who need to leave can leave.
They collect a press pack or a product sheet on the way out. A photographer has taken a picture of them with the product, which arrives in their inbox the next morning. They leave knowing what the product does.
Decide the format, then the venue
A product launch can be thirty people in a meeting room with a screen and coffee, or two hundred in a gallery with a bar and a band. The format depends on who you are launching to and whether the product benefits from ceremony.
Software for enterprise customers: small, focused, demo-heavy. Consumer hardware: larger, with more theatre and post-event social time. A component for industrial use: midsize, technical presentation, no livestream.
The venue follows from that. A meeting room for thirty. A gallery or an event space for two hundred. A factory floor for a machine that cannot be moved.
What to settle before you call anyone
The date, fixed. The format: presentation only, or presentation and reception. The guest list, at least approximately. Whether you are streaming. Whether the product will be demonstrated live or shown in video. And the one question that determines the technical build: does the product need to be in the room, or can it be represented?
After 5 Events is the production company writing this guide. The crew that quotes is the crew that builds the room and runs the evening. Decide those things, then talk.
After 5 Events