The R&D tax credit for hardware startups
The short answer
Hardware prototyping, PCB iteration, and firmware development usually qualify for the R&D tax credit. The sticking point is drawing the line between development and production.
What qualifies, and what fights you
Hardware startups spend much of their early life in a loop of designing, building, and testing prototypes. A PCB respin to fix a signal integrity problem, a firmware rewrite to hit a real-time timing constraint, a new enclosure to solve a thermal issue: this is the process of experimentation the credit is built around.
The sticking point is timing. Once a design is finalized and a company moves into steady production, that manufacturing work generally stops qualifying, since the technical uncertainty has been resolved. The line is not always sharp. A production line that still requires process changes to fix a yield problem can still involve qualifying research, but routine repeat manufacturing does not.
Firmware and embedded software development is often the biggest source of qualifying expense in hardware companies, since it involves the same kind of technical uncertainty as any other software engineering, layered on top of physical constraints like power, timing, and memory.
The four-part test, applied to hardware startups
Qualified purpose is easy to show for hardware: the work improves a physical product or the process used to build it. Technological nature is met through electrical engineering, mechanical engineering, and embedded software.
Elimination of uncertainty shows up clearly in prototype iterations. A team does not know whether a given PCB layout will pass EMI testing or whether a heat sink design will keep a component within its thermal limits until they build and test it. Each respin or revision that follows is the process of experimentation, including the ones that fail.
New to the test itself? Read what software work qualifies as R&D first.
Work that usually qualifies
PCB respins for signal integrity
Redesigning trace routing and layer stackup to resolve EMI or signal integrity failures found during testing qualifies as a direct process of experimentation.
Real-time firmware development
Writing and tuning control loop firmware to meet timing constraints that were not known to be achievable at the outset qualifies as technical uncertainty resolved through testing.
Thermal management prototyping
Iterating on heat sink or airflow design and testing each version under real load conditions to keep components within spec is qualifying engineering work.
Mechanical enclosure iteration for manufacturability
Revising an enclosure design across several prototype runs to hit tolerance and manufacturability targets, tested with each build, qualifies.
Sensor calibration algorithm development
Building and testing an algorithm that compensates for sensor drift or noise across environmental conditions involves genuine technical uncertainty.
Work that usually does not
Production runs after the design is finalized
Manufacturing units of a finalized design, with no open technical questions, is production, not research, even at high volume.
Routine component substitution
Swapping a part for an equivalent one due to supply availability, with no design or performance change, does not involve technical uncertainty.
Which expenses count
Prototype materials and supplies consumed during development count. PCB fabrication runs, components used in test builds, and materials used in mechanical prototypes are qualifying supply expenses, as long as they are used up in development rather than sold or kept in service.
Wages for the electrical, mechanical, and firmware engineers doing or supervising the prototype work count, prorated to time spent on qualifying design and testing.
US-based contract engineers count at 65% of what you pay them. Work done by a contract manufacturer located outside the US does not count toward the federal credit, even during the prototype phase.
A worked example
Hypothetical example. A hardware startup has 6 engineers across electrical and firmware roles, earning a blended average of $145,000, spending about 55% of their time on qualifying prototype work.
At 6 to 10% of total QRE, the federal credit lands between about $37,100 and $61,900. Under $5 million in revenue, the company can apply up to $500,000 of that against payroll taxes each year.