After 5 EventsDecide the programme length first
Everything else follows from how long people sit or stand in one mode. A fifteen-minute welcome and toast requires no staging and no seated capacity. An hour of updates, a demo and three speakers requires chairs, sightlines, a confidence monitor and a plan for the moment attention breaks. The room that works for one will fight you in the other.
Software teams leave if the programme runs long. Build for thirty minutes of structure, then open it up. That may mean no programme at all — a seasonal gathering with music from the start — or it may mean one announcement and one toast at a marked moment. Both work. The seated programme with five speakers does not.
Make the remote half present, not spectated
A laptop on a table pointing at the room is worse than no link. Remote staff watch the back of someone's head, hear the person nearest the microphone and leave after ten minutes. If a third of the team is remote, the event is hybrid, and hybrid has requirements.
You need a camera operator, a dedicated screen, and a microphone discipline: if it is not said into a mic, remote staff do not hear it. The screen must be large enough and bright enough that a face on it registers as a face in the room, not as an icon. That determines minimum screen size before you choose anything else — and it determines whether the venue can deliver power and throw distance for that screen.
Sound is the variable that breaks. Echo, compression, microphone bleed. Test the link in the room with the PA running, not in the office the day before.
Choose the venue for what happens after the programme
Most company parties are two-thirds music and movement. The venue must function when fifty people are standing, talking and not facing forward. That means circulation space, bar access that does not require crossing a dance floor, and acoustics that let people converse when a DJ is playing.
A glass-walled hall looks clear on the site visit and becomes unusable the moment bass starts. A narrow room with the bar at one end creates a queue that blocks everything behind it. A terrace works until the wind makes speech unintelligible or the neighbour calls at ten.
Walk the venue as though you are holding a drink and trying to reach someone on the far side. If that movement is blocked or awkward, the evening will feel blocked.
The technical rider exists to protect the evening, not the supplier
Power capacity, rigging points, load-in access, noise curfew. These are not negotiable, and finding out on the day is too late. A venue may promise rigging and deliver a ceiling that cannot take the weight. It may offer power and mean two domestic sockets on one breaker.
The crew who quote should know the venue or visit it. Forwarding a brief to a subcontractor who has never seen the room produces a quote that omits the generator, the speaker delay, the dolly for the five-floor walk-up. Those omissions appear as surprises on the invoice or as missing capability on the night.
Sound and screen are judged professionally
Your colleagues design interfaces and debug code. They will hear compression, see pixel break-up, and notice when a microphone feeds back. The standard is not "good enough for a party." The standard is: would this be acceptable in a product demo?
That means a projector with brightness sufficient for a half-lit room, a screen surface that does not wash out, and a PA system with enough headroom that speech does not distort when someone leans into the mic. It means a technician present, not a system left on a preset.
The problem is not budget; it is return
Software companies allocate event budget generously relative to headcount, but the founder reads the invoice and will ask what the line is for. Spending must be legible: this cost produced this part of the evening.
The way to waste money is to hire an agency that plans and then subcontracts every element, earning a margin on the room, the caterer, the AV, the staff. You pay for coordination you do not see. The way to spend well is to work with the people who will be in the venue: the crew who quote are the crew who build the rig, and the technician at the desk is on the same payroll.
That structure is factual, not rhetorical. Some event companies are brokers. Others employ the people who do the work. After 5 Events is the latter.
What to settle before calling anyone
Programme length: none, short or structured. Remote participation: passive watch or active presence. Format after the programme: seated, standing, dancing. Venue shortlist: names, or constraints if you need recommendations. Headcount and the split between local and remote.
Those five points determine what the evening requires. Everything else can be solved, but it is solved from that frame.