Five Things AV Integrators Get Wrong About the R&D Tax Credit

TL;DR

• The R&D credit rewards solving technical problems, not inventing products. AV integrators who design custom signal paths, control logic, and acoustic solutions often do exactly that.
• The rules do not require novelty to the world, and they do not require the project to succeed. Both are common reasons integrators wrongly rule themselves out.
• For manufacturers and distributors, this is a natural conversation to open with dealers. You do not need to give tax advice; you just need to point them to a $0 assessment.

The integrator who "just installs"

Ask an AV integrator whether they do research and development and you will usually get a laugh. They mount displays, run cable, program control systems, and tune rooms. In their minds, the manufacturers do the R&D. The integrator does the work.

That framing costs integrators money every year. The federal Research and Development Tax Credit under IRC Section 41 is not a reward for inventing products. It is a credit for the cost of resolving technical uncertainty through a process of experimentation, and a good deal of custom AV integration involves precisely that. This post walks through five assumptions we hear constantly from integrators in the $3M to $15M revenue range, and what the rules actually say about each.

If you are a manufacturer rep, distributor, or buying-group contact who works with these integrators, keep reading to the end. There is a section on why this is your conversation to start.

Myth 1: "We integrate other companies' products, so there is no R&D."

This is the big one, and it rests on a misunderstanding of what the credit measures.

The regulations at Treasury Regulation 1.41-4 define qualified research around a "business component," which can be a product, process, technique, formula, invention, or software. Critically, the credit looks at what the taxpayer had to figure out, not at who manufactured the parts. A conference room that needs a custom-designed audio DSP configuration, a control system with logic written from scratch, and a video distribution architecture that has to work across incompatible signal formats is a business component the integrator developed, even though every box in the rack has someone else's logo on it.

What tends to qualify in AV work: designing and testing signal routing and switching architectures for unusual room requirements; developing custom control-system programming and user-interface logic; solving acoustic, latency, sync, or interference problems that had no off-the-shelf answer; and engineering integration between systems that were not built to talk to each other. What generally does not: routine installation to a manufacturer's spec, cosmetic UI changes, and work where the outcome was known before you started.

The distinction is technical uncertainty. If your engineers did not know at the outset whether an approach would work, or how to make it work, and had to evaluate alternatives to find out, the work may be eligible depending on the specific activities, documentation, and facts.

Myth 2: "It has to be new to the world."

Integrators often assume the credit is reserved for patents and laboratory breakthroughs. The regulations say otherwise.

Treasury Regulation 1.41-4(a)(3)(ii) states that qualifying research does not require the taxpayer to obtain information that "exceeds, expands or refines the common knowledge of skilled professionals" in the field. The standard is whether the information was uncertain to you at the start of the project. A signal-processing solution that another integrator in another state may have solved differently can still qualify for your firm if your team had to experiment to resolve it.

This matters enormously in AV, where nearly every project is a variation on a familiar theme with one or two hard problems buried inside it. The familiar parts do not qualify. The hard problems may.

Myth 3: "The project failed, so it does not count."

The same regulation section addresses this directly: qualifying research does not require that the taxpayer "succeed in developing a new or improved business component."

Every integrator has a story about the job where the first two approaches did not work. A distributed audio system that produced unacceptable delay across zones. A control integration that fought the building management system for three weeks. A projection design that had to be re-engineered after the ambient light measurements came in wrong. The time spent on the approaches that failed is often exactly the kind of experimentation the credit is designed to recognize, because it is the clearest evidence that uncertainty existed.

Failed iterations are not a reason to skip the credit. They are frequently the strongest part of the claim.

Myth 4: "We are too small, and we do not owe enough tax for it to matter."

Two separate concerns hide inside this one, and both have answers in the Code.

On size: there is no minimum revenue to claim the credit. Strata's clients are typically businesses with $3M to $15M in annual revenue, and the credit is calculated on qualified wages, supplies, and contract research, not on company size. An integrator with a handful of engineers and programmers doing custom design work has a real basis for a claim.

On tax liability: the general business credit, which includes the research credit, can be carried back one year and forward up to 20 years under IRC Section 39. A credit you cannot fully use this year is not lost. And for very young companies, IRC Section 41(h) allows a "qualified small business" (generally under $5 million in gross receipts and no gross receipts more than five years back) to elect to apply up to $500,000 of the credit against the employer share of payroll taxes, using Form 6765 and Form 8974. That election has to be made on a timely filed original return, so it rewards planning ahead.

Neither of these is a guarantee of any particular outcome. But "we do not owe enough tax" is rarely the end of the analysis.

Myth 5: "A study would eat my engineering team's month."

This is the objection integrators raise once they accept the credit might apply. Project managers and lead programmers are the most overbooked people in the building, and the idea of pulling them into a tax exercise feels like a nonstarter.

In practice, a well-run study puts most of the effort on the provider. The client's role is to point the provider at the right projects and people and to make a modest amount of engineering time available for conversation. Strata starts with a $0 initial assessment to determine whether a study is worth pursuing at all, and the full engagement typically runs four to eight weeks depending on the facts. The deliverable is a documentation package built to support the claim, and Strata works directly with the client's CPA so the credit lands correctly on the return.

One validated example from this vertical: a Utah-based AV integration firm working with Strata identified more than $300,000 in R&D credits. Individual results vary depending on the specific activities, documentation, and facts, and no outcome can be promised in advance. But the scale of what an integrator can leave unclaimed is not trivial.

Why this is a supplier's conversation to start

If you are a manufacturer rep, distributor, or buying-group contact, your dealers trust you on things that go beyond product. You see their project mix. You know which of them are doing genuinely custom engineering versus box sales. And you talk to them far more often than any tax advisor does.

That makes you the natural person to raise the topic, with two guardrails. First, you are not giving tax advice, and you should say so. Your role is to point out that integrators doing custom design work are often eligible for a credit they have never claimed, and to introduce a specialist who can assess it. Second, do not oversell. "You should look into this" is the right register. "You are leaving six figures on the table" is not, because neither of you knows that yet.

A practical way in: the next time a dealer describes a job where something did not work the first time, that is your cue. "Did you know that kind of engineering time can qualify for the federal R&D credit? There is a firm that will assess it for free." From there, a warm introduction is all it takes. For partners who refer clients, Strata's referral fee comes from Strata, not from the dealer's pocket, and it never changes what the dealer pays.

Next steps

The credit has been part of the Code for decades, but the AV integration industry has claimed it at a fraction of the rate its engineering work would support. If any of the five assumptions above sounds like something you or your dealers have said, the fastest way to find out is a $0 initial assessment. Visit stratataxgroup.com/contact to start the conversation.

Primary sources referenced in this post: Treasury Regulation 1.41-4 (eCFR), IRC Section 39 on carryback and carryforward of unused credits (uscode.house.gov), IRS: Qualified small business payroll tax credit for increasing research activities, and IRS: About Form 8974.

This post is for informational purposes only and does not constitute tax or legal advice. Consult a qualified tax professional regarding your specific circumstances.