Many enterprise AV decisions follow a familiar pattern. A brief arrives, usually scoped around meeting rooms. The procurement team evaluates devices, checks certifications, selects a vendor, and deploys.
The problem is that most organizations evaluate those decisions on the wrong criteria, at the wrong level, and with the wrong timeframe in mind. When the limitations eventually become visible, the hardware is already embedded in the building and costly to undo.
Vic Bhagat, Senior Director of Alliances at Q-SYS, sets out seven questions that are designed to be asked before that happens. They won’t tell you which product to buy. But they will tell you whether your current approach can genuinely scale, adapt, and serve the workplace you are building, not just the one you have today.
1. Is Your AV Strategy Built Around a Collaboration Application, or the Whole Workplace?
This is the question most IT leaders have never been asked directly. The meeting room brief is well understood. The broader workplace technology strategy, covering shared spaces, common areas, large format rooms, and the informal collaboration zones between them, rarely gets the same attention.
According to Vic Bhagat, Senior Director of Alliances at Q-SYS, most enterprises have answered the wrong question. They’ve built an AV strategy around the meeting and assumed that covers the workplace. It does not.
“The right question is not what is my AV strategy to support meetings. It is what is my AV strategy as a whole.”
If your answer only covers meeting rooms, that is worth knowing before you commit to your next deployment.
Watch:Vic Bhagat on why enterprises need a platform approach to AV
2. What Happens to a Space When its Requirements Change?
This question rarely comes up in procurement conversations, but it should. The goal of any AV investment should be to future-proof the estate, building infrastructure that adapts as requirements change rather than one that needs replacing every time they do. Most AV decisions get evaluated on what a space needs to do today. The more revealing question is what happens when that brief changes next year, or the year after.
In a device-by-device estate, change can be expensive. Every new requirement means either replacing hardware or adding an entirely separate system on top of what is already there. Bhagat explains what that means in practice:
“If you want a room to do more, you either have to rip-and-replace that device, or you have to add entire new systems.”
With a software-defined platform, many of those changes become a configuration update rather than a capital project. Ask your vendor what reconfiguring a space actually involves. The answer will reveal a great deal about how the next five years look.
3. How Many Different AV/IT Subsystems Are You Managing, and Does Anyone Have a Single View Across All of Them?
This is a straightforward question with a surprisingly complicated answer in most large enterprises. Meeting rooms on one system, common areas on another. Signage managed separately. Support contracts spread across multiple vendors and integrators in different markets.
The operational consequence is an IT team that spends its time reacting to reported problems rather than monitoring the estate proactively. There is no single dashboard, no early warning, and no way of knowing how the estate is performing until something goes wrong.
“The biggest change a platform brings is that teams move from reacting to issues to proactively managing the entire workplace. A software-defined platform provides visibility into how spaces are performing, but the real value comes from what is built on top of it. The more services and applications deployed on the platform, whether room booking, signage, environmental controls, or occupancy tracking, the richer and more proactive that visibility becomes, all surfaced through common tools your team already knows.”
If the honest answer here is that nobody has a single end‑to‑end view of the estate, that alone exposes the fragmentation problem. Q-SYS Reflect, bridged with the Microsoft Teams Rooms Pro Management portal, is designed to close exactly that gap: giving IT teams a unified view across the estate and the tools to act on it.
4. Is The Experience Consistent Across Every Space Type, Site, and Region?
For enterprises operating across multiple locations, consistency is both a user experience issue and an IT management issue. When different sites run different systems, which different integrators procured under different contracts, the estate drifts. Standards diverge, and end users get a different experience depending on which office they walk into.
A platform-based approach provides a unified foundation that different experiences and applications are built upon, making it easier to manage, support, and scale across every space type and region. The Microsoft EC1 deployment in Redmond demonstrates what this looks like at scale: more than 1,200 endpoints across every space type, all running on the Q-SYS Full Stack AV Platform: one standard, centrally managed, regardless of how the space is used.
If your current approach cannot deliver that consistency across regions and space types, it is worth asking what it will take to get there, and what it is currently costing you not to.
5. What Does Your AV Estate Actually Know About How Your Spaces are Being Used?
Device-by-device AV estates generate data, but only up to a point. What they produce is confined to the meeting room and siloed by system, falling well short of a holistic view across the workplace. The spaces in between, the informal collaboration zones, the common areas, the shared spaces people move through every day, produce no meaningful insight at all.
For enterprises making decisions about how their workplace is structured and resourced, that data gap has real consequences. Space planning, energy management, occupancy tracking, and workplace strategy all depend on understanding how spaces are actually used, not just whether the AV in them is functioning.
“The most important decision is whether organisations are going to unlock insights from their deployed spaces, or leave that value on the table.”
A connected platform turns the AV estate into a source of workplace intelligence. That distinction matters more as organisations look to make their real estate work harder. Q-SYS is built for exactly this, a workplace platform that extends beyond the meeting room, connecting the physical hardware of the built environment into a single, manageable, insight-generating infrastructure.
6. Is Your AV Infrastructure Ready to Work With AI, or Will it Need to Catch Up?
AI tools are becoming a standard part of the workplace technology stack. Microsoft Copilot, Microsoft Places, and a growing range of AI-driven applications all depend on data from the environments they operate in. The question is whether your AV infrastructure can independently supply that data in a meaningful way, drawing from across the entire workplace rather than being confined to or routed through individual room systems.
Most fixed-function, hardware-dependent AV estates cannot. They were not designed to be data sources. They were designed to make meeting spaces/rooms work. That was a reasonable design brief at the time, but it creates a compatibility problem as AI tooling matures.
“AV is really not just an output at this point. It becomes a source of insights and for AI. When you connect a platform to experiences across the workplace, AI just becomes richer.”
This question is worth asking now, before the next generation of workplace AI tools arrives and finds the infrastructure underneath them is not ready.
7. Are You Calculating the Cost of Your AV Estate at Room Level or Across the Full Estate?
Room-level cost comparisons are common in AV and facilities procurement. They are also incomplete. The unit price of a device tells you nothing about what it costs to manage, support, update, and eventually replace across a global estate over five or ten years.
Bhagat argues the financial case for a platform-based approach only becomes clear when you run the numbers at estate level and across the full lifecycle.
“Estate-level total cost of ownership is not just about what you spend today. It’s about how long that investment remains valuable. Platforms that can reuse the same application across different areas, and add new capabilities without ripping out hardware, help reduce duplication, simplify support, and create long-term savings.”
A capability deployed once on a software-defined platform, whether room booking, digital signage, or environmental controls, can extend to any space that needs it. In a device-by-device estate, each of those requires a separate procurement for each location. Run the numbers at estate level and the calculation often looks quite different.
What to Do With The Answers
These questions are not a product evaluation checklist. They are a way of stress-testing your current approach against the real demands of running an enterprise AV estate at scale.
If your current approach answers all seven comfortably, you are in good shape. If it struggles with more than one or two, those gaps are worth understanding before your next procurement decision locks you into the same approach for another cycle.
The shift from device-led to platform-led AV management does not happen overnight. But it starts with asking the right questions before the brief gets written.
