Who is WireFlow for?
Production companies, AV techs, LED engineers, broadcast crews, integrators, and anyone who needs show documentation that survives load-in.
When to use this
Use this to decide whether WireFlow fits your shop, or to explain the product to stakeholders who ask "who is this for?"
Primary users
- Live production companies planning multi-camera shows, corporate events, and festivals
- AV technicians and freelancers who document signal path before every gig
- LED wall techs and video engineers sizing walls and processor paths
- Broadcast and streaming teams mapping encoders, routers, and IFB/comms
- Low-voltage and AV integrators documenting rack builds for handoff
- Event production teams coordinating video, audio, and lighting infrastructure
- Small AV companies and DJs who outgrew napkin sketches but do not need full CAD
Roles on a typical show
Different people touch different pieces of the same project. A TD might own the main diagram while a rack tech owns elevations and patch fields.
- Technical Director / Lead Engineer — overall signal flow and system architecture
- Video Engineer — switcher path, playback, LED processor routing
- A1 / Audio — console, wireless, Dante/AES paths (same diagram or zone)
- Rack Tech — rack elevation, PDUs, internal patching
- LED Tech — cabinet layout, data paths, power circuits
- Production Manager — share links and PDF exports for client approval
When WireFlow is the right tool
- You repeat similar rigs but every show changes I/O count or wall size
- Crew asks for "the diagram" and you keep rebuilding it in three places
- You need rack drawings installers can follow without opening your laptop
- You want cable labels pulled from actual port names, not retyped in Excel
When to use something else
- Architectural venue CAD, rigging plots, or power distro one-lines — WireFlow complements those, it does not replace dedicated CAD
- Real-time show control or switching — WireFlow documents the plan; it does not run the show
- Inventory/asset management at warehouse scale — gear lists help on a project; full asset ERP is outside scope