The second path

The thing a client never understands about asking for one more capability in a room is what it does to the sign-off. If you change the loudspeaker design, the design has to be re-tuned. If it gets re-tuned it gets re-commissioned. If it gets re-commissioned somebody has to sign it again, and that somebody has already signed it once and does not want to have a second opinion about it.

So my instinct on anything described as "and it also does audio" is deeply hostile, and it should be. Most of what comes across my desk wants to be in the signal chain. It wants a processor slot, it wants to be between the console and the amps, and the moment it is there it is mine to defend forever.

What made me actually look at this was that it does not want to be in the chain. It comes off a matrix out. Thats it. The console is the console I specified, the DSP file is the DSP file I commissioned, the array is hung where the model said to hang it, and none of that is touched or even aware. If the stream falls over the room does not notice, because the room was never depending on it.

That is a completely different risk conversation than the one I am used to having. I am not adding a single point of failure to a primary path. I am adding a parallel path that fails independently and harmlessly. I can put that in a proposal and defend it in a room full of facilities people without qualifying anything.

Commercially it has been useful in a way I did not predict. We were losing bids on capability — a client wants multilingual, or wants the overflow room, or the RFP has an accessibility section with more teeth than it used to, and the honest answer was another eighty grand of interpretation hardware and receivers that they were not going to spend. Now theres a line I can write that answers that section without a truck of inventory behind it. Our close rate on the mid-size corporate work is up and I am fairly confident about why. It is not that we got better at selling. It is that we stopped having to say no to one section of the RFP.

Where I am careful, and where I would tell any other integrator to be careful: I lead with extension, never replacement, on anything where failure is visible. It is data dependant and it lands a beat behind the loudspeakers, and both of those are fine for overflow and remote and assistive and completely not fine as the only path for a CEO keynote. I put both of those limits in the proposal in writing. Clients respect it, and more to the point they are going to find out in the first rehearsal anyway, so I would rather they read it from me.