Mantis Audiovisual How to choose an AV integrator.
Most AV proposals look alike on paper: the same brands, similar diagrams, comparable prices. What separates a room that still works in year three from one that quietly degrades is not on the spec sheet. It is who owns the outcome, and for how long. These are the questions that surface it.
Who designs it, builds it, and supports it, and are they the same people?
The most common failure in commercial AV is not a bad product. It is a hand-off. One firm designs, a subcontractor installs, a third party writes the control code, and the manufacturer takes the support calls. Every boundary is a place accountability leaks, and the room is what falls through. Ask each bidder, plainly, which of those four jobs they do in-house and which they pass on. The fewer hands, the fewer seams. The strongest answer is that the same engineer carries the room from the drawing to the day it is running, and is still the person who picks up when it needs attention.
Who owns the boundary with IT and the trades?
A modern room is also a network, and it shares walls, power, and ceilings with other trades. Ask who owns the demarcation with your IT team and the contractors, and whether it is written into the drawings. "We will coordinate" is not the same as "here is the boundary, documented, so nothing falls between us." The difference shows up the week before go-live, when a missing VLAN or a moved conduit becomes someone's problem. It should already be clear whose.
How will you prove it works before you leave?
Rushed commissioning does not make problems disappear. It moves them to your support desk. Ask whether handover includes a signed commissioning record, every line measured against the written design, or just a walk-through and a thumbs up. A room that was measured (intelligibility at every seat, even coverage front to back, picture and sound in sync, one-touch start, graceful behaviour when the network drops) and signed off is a room you can hold someone to. A demo that looked good on the day is not. How a room is proven walks through the standards a finished room is tested to.
What do we actually own when you are done?
Ask what the handover package contains. The answer should be full as-builts, the commissioning record, and guides written for the people who use the room, so your own team or any competent integrator can run and extend it from the documentation alone. If the answer is "call us," you do not own the room. You rent the memory of it, and that is a lock-in dressed as a relationship.
Who answers in year three?
The day after install, every integrator is responsive. The real question is what support looks like once the project is closed and the next one has their attention. Ask whether the room is monitored, whether firmware and updates land on a planned maintenance window rather than mid-meeting, and whether you reach the engineer who built it or a queue that has never seen the room. Equipment ages and settings drift; the only thing that keeps a room dependable for years is someone who notices before you do.
The pattern behind the questions
Every question above is really one question asked five ways: is there continuity of accountability, or a chain of hand-offs? A spec sheet cannot answer it. The structure of who does the work can. If that is the standard you hold bidders to, you will choose well, whoever you choose.
It is also the standard Mantis is built on: one name on the whole job, with the room proven before it changes hands. If you are scoping one, describe what you need.