When AV Budgets Get Squeezed, What Actually Gets Cut First — and How to Protect Performance Anyway

Every AV project built in the last year has run into the same headwind: hardware costs are up, and they went up fast. Tariffs on imported components have pushed prices higher across displays, DSPs, cameras, and networking gear industry-wide. AVIXA has been tracking this pressure for months, and the Pro AV market is still expected to grow from $332 billion in 2025 to $402 billion by 2030 — but that growth is happening alongside real cost strain on individual projects, not because of it.

This isn't a story about who's at fault. Manufacturers are absorbing what they can and passing along the rest. Integrators are quoting honestly against real supply costs. Owners are working with budgets that were set before the new numbers landed. Everyone in the chain is making reasonable decisions under pressure. The problem isn't any one party — it's what tends to happen next, quietly, when a budget doesn't move but the price list does.

What gets cut first

When a project needs to close a budget gap, the cuts rarely show up as a single dramatic decision. They show up as a series of small substitutions, each one defensible on its own: a DSP with fewer input/output channels than originally spec'd. A lower-category cable run in a building that was going to need more bandwidth in three years, not zero. A display with lower nits in a room that gets more window glare than the original site visit accounted for.

Individually, none of these look like a problem. A line item goes from spec A to spec B, the total comes down, and the project moves forward. What's missing in that moment is usually the question that mattered most at the start of the project: what was this system actually supposed to do, and does the substitution still let it do that?

That question gets lost because most specs are written as a list of parts, not a list of requirements. If the only record of intent is a SKU, then any other SKU that's cheaper and roughly similar looks like a safe swap. There's nothing in the document to check it against.

Why a use-case-anchored spec holds up better

The fix isn't refusing to substitute — budget pressure is real and substitutions are sometimes the right call. The fix is writing the original spec so the use case is visible, not just the part numbers. A spec that says "this DSP needs 12 mic inputs to support the room's three-camera, four-microphone conferencing configuration" gives everyone downstream something to check a substitution against. A spec that just says "DSP: Model X" doesn't.

This matters for the integrator as much as the owner. When the reasoning behind a spec is documented, an integrator proposing a substitution can show exactly why it still meets the requirement — or flag early that it doesn't. That's a faster conversation than a change order six weeks into install, and it's a better outcome for everyone bidding and building the project. Cleaner specs mean fewer surprises at close-out, and fewer surprises is good for the integrator's margin and schedule too.

This is where independent, vendor-neutral design work earns its keep. Twenty-plus years spent on both the design and manufacturing side means knowing which specs are padding and which ones are load-bearing — which channel counts, cable categories, and brightness levels are actually tied to how a room gets used, and which were just the most convenient number to write down at the time.

Three questions before approving a substitution

When a substitution comes up mid-project, three questions catch most of the risk before it becomes a callback:

1. What was the original spec protecting — a specific use case, a future need, or a safety margin? If nobody can answer this, that's worth flagging before answering whether the substitution is fine.

2. Does the new component still meet that requirement, or just the price target? A cheaper DSP with fewer channels might still cover today's room. It might not cover the room in eighteen months.

3. Who signs off, and is it documented? A substitution approved verbally on a job site is a substitution nobody can point to later when something doesn't perform as expected.

None of these questions require blocking a decision. They just make sure the decision is made with the same information the original spec was built on, instead of against a bare price list.

The Bigger Picture

Tariff-driven cost pressure isn't going away this year, and it shouldn't be treated as a one-time budget event. It's a reason to make specs that explain themselves — so that when the next cost shock hits, whoever is holding the budget can tell the difference between a substitution that's safe and one that quietly changes what the system was built to do.