A common question is whether software performance optimization can qualify as research and development for the federal R&D tax credit under Section 41. The short answer is that software performance optimization may constitute qualified research when it involves a technical uncertainty and a process of experimentation. Routine performance tuning using established methods 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 Performance Optimization May Warrant Review
Software performance optimization 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, be intended to eliminate uncertainty, and be conducted through a process of experimentation.
Common scenarios that may warrant review include:
- New performance target — evaluating alternative approaches to resolve uncertainty about whether software can achieve a new performance target.
- Bottleneck resolution — testing alternative approaches to resolve uncertainty about whether a performance bottleneck can be eliminated.
- New workload — evaluating alternative approaches to resolve uncertainty about whether software can handle a new workload at the required performance.
- Resource optimization — testing alternative approaches to resolve uncertainty about whether software can achieve the required performance within resource constraints.
Routine Tuning vs. Optimization as Research
A central distinction is between routine performance tuning and optimization as research:
- Routine tuning — adjusting known parameters (e.g., cache sizes, connection pools) using established methods. There is no technical uncertainty. This is tuning, not research.
- Optimization as research — developing new approaches where there is a technical uncertainty about whether the software can achieve the required performance, and evaluating alternatives to resolve that uncertainty. This may warrant review.
Hypothetical Example
Consider a company that is optimizing a system to handle a new class of high-volume transactions and is uncertain whether any available approach can achieve the required throughput and latency. The company evaluates alternative approaches, tests each, 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 adjusts standard cache settings on an existing system, that is routine tuning, 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 performance optimization claims include design records identifying the uncertainty and alternative approaches, performance test results, profiling data, and records of how results informed optimization decisions. For more, see our page on R&D tax credit documentation.
Key Takeaway
Software performance optimization may constitute qualified research when it involves a technical uncertainty and a process of experimentation. Routine performance tuning using established methods 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.