Case Study · Corporate Live Event
Monday.com: one accountable network behind a revenue-critical brand moment
A corporate live event where registration, payments, live demos, and production all rode the same network — and no single party owned what happened when it strained. LGL Networks ran it as one accountable operator, setup to teardown.
Context
Monday.com staged a corporate live event where, as with most corporate live events, the network was assembled from the venue circuit, an AV/production vendor’s gear, a registration platform, and onsite payments — each owned by a different party, none accountable for the whole.
LGL Networks was engaged to operate the event’s mission-critical network end to end as a segmented Critical Operations Network overlay, behind the venue circuit. We supplemented the venue circuit where permitted and never bypassed venue exclusivity.
Challenge
The exposure was familiar and high-stakes:
- Revenue-critical systems with no single owner. Registration check-in, any onsite payments, and live product demos all depended on connectivity — but responsibility was split across venue, AV, registration, and carrier vendors. When something slows mid-event, that gap becomes finger-pointing, not resolution.
- Brand risk on a public stage. A failed live demo or a stalled check-in line is visible to every attendee, customer, and sponsor in the room.
- Mixed traffic on one fabric. Payment, production, staff, and attendee traffic sharing an unsegmented network is both a reliability risk and a compliance-scope problem.
- No proof before go-live. Without a documented acceptance test, “it worked when we set it up” is the only assurance anyone has when the room fills.
Approach
We applied the standard LGL motion — Risk Assessment, then written venue authorization, then the Critical Operations Overlay, monitored through teardown.
Segmented overlay, wired-first
We deployed a segmented LAN with wired drops for the revenue- and event-critical systems — registration, any payments, production, and staff operations — wired first for the paths that cannot tolerate RF contention. Our documented segmentation standard isolated payment, production, registration, attendee, contractor, and management traffic into distinct zones.
Connectivity resilience
Where venue policy permitted, we ran dual-WAN with defined failover; where a single underlay was required, we used an approved configuration with a documented failover plan and target window. LGL procures dedicated, redundant upstream circuits rather than reselling commodity bandwidth.
Pre-opening acceptance + failover testing
Before go-live, we ran the documented pre-opening acceptance test: verifying that segmentation held, that WAN failover landed inside its target window, that critical-system redundancy was live, and that monitoring was reporting.
Onsite engineering + NOC monitoring
An onsite network lead owned incident response on the floor, backed by remote NOC monitoring from setup through teardown — one accountable operator, not a help-desk ticket.
Outcome
Each engagement closes with a post-event report documenting acceptance-test results, any incidents and time-to-failover, and segmentation integrity. The measured results for this event — acceptance-test outcome, incident count, failover times, and network availability — are documented in the client’s post-event report.