A common question is whether software architecture development can qualify as research and development for the federal R&D tax credit under Section 41. The short answer is that software architecture development may constitute qualified research when it involves a technical uncertainty and a process of experimentation. Routine architecture work using established patterns generally is not qualified research, and internal-use software rules may apply. This page explains the framework in general terms. It is educational and is not individualized advice. For the foundational framework, see our page on qualified research.
When Architecture Development May Warrant Review
Software architecture development may warrant review when the work involves a genuine technical uncertainty and a process of experimentation. Under the four-part test, the work must be for a permitted purpose, be technological in nature (relying on computer science), be intended to eliminate uncertainty, and be conducted through a process of experimentation.
Common scenarios that may warrant review include:
- Scalability uncertainty — evaluating alternative architectures to resolve uncertainty about whether a system can scale to the required level.
- Performance uncertainty — testing alternative architectures to resolve uncertainty about whether a system can achieve the required performance.
- Integration uncertainty — evaluating alternative approaches to resolve uncertainty about whether a new system can integrate with existing systems.
- New technology uncertainty — testing alternative approaches to resolve uncertainty about whether a new technology can be used to achieve the required performance.
Routine Architecture vs. Architecture Development
A central distinction is between routine architecture and architecture development:
- Routine architecture — selecting established architectural patterns for a known application type. There is no technical uncertainty about whether the architecture will work. This is routine design, not research.
- Architecture development — developing a new architecture where there is a technical uncertainty about whether the architecture can achieve the required performance, and evaluating alternatives to resolve that uncertainty. This may warrant review.
Internal-Use Software Considerations
Software developed primarily for the taxpayer's internal use may be subject to the internal-use software rules under Section 41(d)(4)(E) and Treasury Regulation §1.41-4(c)(6). Software developed for sale, lease, or licensing, or software that enables a non-software business component, may warrant review under the excepted-software rules. The analysis is fact-specific.
Hypothetical Example
Consider a company that is developing a new software architecture to handle a new class of high-volume real-time transactions and is uncertain whether any available architecture can achieve the required throughput and latency. The company evaluates alternative architectures, tests each through simulation and prototyping, and systematically varies the approach to resolve the uncertainty. This systematic evaluation of alternatives may warrant review as qualified research.
By contrast, if the same company selects a standard microservices architecture for a known web application, that is routine architecture, not research.
This example is illustrative only and does not state that the activity definitely qualifies.
Documentation That May Help
Records that can help support architecture development claims include architecture design records identifying the uncertainty and alternative approaches, performance test results, simulation records, and records of how results informed architecture decisions. For more, see our page on R&D tax credit documentation.
Key Takeaway
Software architecture development may constitute qualified research when it involves a technical uncertainty and a process of experimentation. Routine architecture work using established patterns generally is not qualified research, and internal-use software rules may apply. Because the distinction is fact-specific, professional review is appropriate before claiming the credit.