A business component is the product, process, computer software, technique, or formula your team develops, and the credit is calculated component by component. For U.S.-based AI, SaaS, and technology companies that build the software they own, the federal R&D credit is often the single most valuable incentive available. Below are the 25 business components that qualify most often, plus the exclusions that quietly disqualify the rest.
A qualified claim isn’t a pile of activities, it’s a chain of evidence linking people to a component, through uncertainty, to documented experimentation.
Establish this chain end to end, and you’re in a strong position to substantiate the credit in an examination.
Example components, the technical uncertainties they resolve, the roles behind them, and the evidence that defends them.
Each qualifying activity attaches to a business component the credit is calculated on. Expand any item to see the component it maps to.
The bands show the low-to-high range of time that commonly counts as qualified research, by role. Engineering and data roles cluster high; support and design roles are partial and fact-dependent.
Illustrative ranges across MainStreet engagements. Actual percentages depend on facts and circumstances and should be supported by interviews, documentation, and a defensible time-allocation method (see Treas. Reg. §1.41-2(d) substantially-all rule). Support roles qualify only for development-linked troubleshooting, not routine customer support.
Even technical-looking work is carved out by §41(d)(4). Screening components against these exclusions before a study is one of the most effective ways to reduce audit exposure.
Routine bug fixes, maintenance, and ongoing debugging once a component is release-ready.
Adapting existing software to a particular customer or environment. Hits enhancement and integration activities.
Work paid for by a customer or grant with no retained rights and no financial risk. A trap for client work.
Reproducing an existing component from inspection or another party’s plans or documentation.
Purely aesthetic UI/UX work — only the technical implementation qualifies, not appearance decisions alone.
Market research, routine data collection, QC testing, non-U.S. research, and the social sciences and arts.
Components built primarily for internal use (automation engines, DevOps platforms, internal AI tools) must pass all three prongs of the high-threshold-of-innovation test under Treas. Reg. §1.41-4(c)(6). It is a frequent audit focus.
Would result in a meaningful reduction in cost, improvement in speed, or other measurable economic improvement compared to available alternatives.
Substantial resources committed, with substantial uncertainty that they would be recovered in a reasonable period given the technical challenges involved.
Cannot be bought, leased, or licensed and used without modifications that would themselves meet the high-threshold test.
Dual-function software — serving both internal users and third parties — is governed by separate presumption and safe-harbor rules. Document the three-part test for every internal-use component.
The artifacts your team already produces are the same ones that win an examination — if they are connected to the right components.
Employee → Activity → Component → Uncertainty → Experimentation → Documentation
Most software companies meet all four on their core product work every year, usually without realizing it counts.
The employees performing the development work are located in the United States.
The company keeps substantial rights and IP ownership in the work it funds and builds.
The work is not funded or paid for by a customer or grant that bears the financial risk.
Activities involve real technical uncertainty resolved through a process of experimentation.
The components above cover the vast majority of qualifying R&D in modern software companies. Claiming it well comes down to four moves.
Map qualifying work up to a named product, process, or software component for Form 6765 Section G.
Screen for adaptation, funded research, and post-production work before the study, not after.
Internal software and AI agents need the three-part high-threshold-of-innovation test documented.
Tie employees and time to components through repos, tickets, and design records.