R&D Tax Credit for Software Startups: Who Qualifies and How to Claim

Section 41 of the Internal Revenue Code asks whether an activity meets all four of these conditions:

• Permitted purpose: the work aims to create a new or improved product or process, in function, performance, reliability or quality.
• Technological in nature: it relies on principles of computer science, engineering or the physical sciences.
• Elimination of uncertainty: at the start, you did not know whether the capability could be achieved, or the method or design to achieve it.
• Process of experimentation: you evaluated alternatives through modeling, prototyping, testing or systematic trial and error.

The test applies to each business component, such as a product feature or a system, and not to the company as a whole. A team can be doing qualified research on Monday and routine maintenance on Tuesday, which is why time and project records matter more than job titles.

Activities that often qualify include developing a new algorithm or data model where the approach was uncertain, designing an architecture to meet demanding performance or security goals, prototyping and testing alternative methods, and building integrations where compatibility had to be worked out through experimentation.

Work that commonly does not qualify includes cosmetic user interface changes, routine bug fixes after release, adapting a product for a customer using known methods, data entry and configuration, market research, and copying or reproducing an existing component.

Software you build to sell, license or provide to customers is generally not treated as internal use. Software built mainly for your own back-office functions, such as accounting or HR systems, faces an extra "high threshold of innovation" standard. Software that serves both purposes has its own rules. Ask your CPA to classify each project before you compute anything, because the classification changes the answer.

Qualified research expenses, or QREs, fall into three main groups: wages of employees who perform, directly supervise or directly support qualified research, supplies used in the research, and a portion of amounts paid to outside contractors for qualified research. Some cost types, such as cloud computing used in development and testing, have specific rules, so confirm treatment with your CPA.

Because engineers are usually the largest cost, wages set the size of your claim. R&D spending is 22 percent of ARR at the median private B2B SaaS company¹, and software developers earn a median of $135,980 across US industries². But only the share of each person's time spent on qualifying activities counts.

Say one engineer earns $150,000 and spends 60% of the year on qualifying projects: $90,000 of that wage is a candidate QRE. The credit itself is a percentage of QREs, calculated under either the regular or alternative simplified method, and companies with no prior-year QREs generally use a lower rate under the simplified method. Have your CPA run both methods.

Most startups have no income tax liability, so a credit against income tax has nothing to reduce. The payroll offset addresses that. A qualified small business can elect to apply up to a capped annual amount of the credit against the employer's share of payroll taxes, and the cap has been raised by later legislation, so check the current limit.

To qualify, a company generally needs gross receipts below a stated ceiling in the credit year and no gross receipts before a five-year lookback window. In practical terms, this is aimed at young companies with modest revenue.

Mechanics to know:

• You make the election on the credit form filed with your timely income tax return for the year.
• The offset begins with the first payroll tax quarter after that return is filed, not during the year of the research.
• Your payroll provider or CPA files the quarterly form that applies the credit.

Ask your CPA how the credit interacts with the treatment of research costs under Section 174 and Section 174A, covered in a separate guide on how Section 174 changed research cost deductions. For more on the offset itself, see the guide on offsetting payroll taxes with R&D credits.

Documentation is what survives an audit. Build the habit during the year rather than in March:

1. List the projects, and for each note the technical uncertainty you faced and the alternatives you tested.
2. Track time by project, even roughly, using tickets, sprint records or a short monthly allocation confirmed by team leads.
3. Keep design documents, test results, benchmark comparisons and commit history that show the experimentation.
4. Separate qualifying tasks from maintenance and support in your project tracker.
5. Keep contractor agreements that show who bears the risk and who owns the results.
6. Save payroll registers so wages tie to your allocation.

The QRE documentation and audit guide goes deeper on what auditors ask for.