R&D Tax Credits  /  Software & SaaS
R&D Tax Credits · Industries

R&D tax credits for
software & SaaS.

Building a platform, designing architecture, solving performance and integration problems, most of what your engineers do to make software work is exactly what the credit rewards. Software is one of the largest R&D credit categories there is.

Request a Complimentary Assessment
The Opportunity

Your engineering roadmap is R&D.

Developing new software, or meaningfully improving existing software, almost always involves technical uncertainty: whether an architecture will scale, how to hit a performance target, whether an approach will even work. That is the heart of the credit. From platform builds to algorithms to infrastructure, a large share of engineering payroll typically qualifies.

What Qualifies

The work that counts.

Development & architecture

  • New software and platform development
  • System and application architecture
  • Algorithm design and optimization
  • Database and data-pipeline development
  • API and integration engineering

Performance & infrastructure

  • Scalability and performance engineering
  • Cloud infrastructure and DevOps innovation
  • Security engineering
  • AI and machine-learning model development and testing
  • New technical approaches and prototyping
Example Projects

What it looks like in practice.

Platform architecture

Designing a new system architecture to meet scale and reliability targets under real uncertainty.

Performance engineering

Re-architecting a service to hit latency or throughput goals off-the-shelf approaches couldn’t.

Complex integration

Building a novel integration where the technical path wasn’t clear at the outset.

Worth Knowing

Two software-specific lines to watch.

First, funded work: if you build software for a client who bears the risk and owns the result, it may be “funded research” and excluded, company-owned product work generally qualifies. Second, internal-use software, built to run your own business, faces a higher bar, the three-part “high threshold of innovation” test, on top of the usual four. Routine bug fixes, configuration, and maintenance don’t qualify at all.

We separate qualifying development from routine work and apply the internal-use-software rules where they’re triggered, so the claim is both complete and defensible.
The Test, Applied

How the four-part test lands here.

01

Permitted purpose

A new or improved software product, feature, or capability.

02

Technological in nature

Grounded in computer science and software engineering.

03

Elimination of uncertainty

It was uncertain whether, or how, the technical goal could be achieved.

04

Process of experimentation

Resolved through design, prototyping, testing, and iteration.

Common Questions

Questions we hear.

Do we qualify if we’re not a “tech company”?

Any company writing software to solve technical problems can qualify. Development inside a non-tech business often qualifies too.

Does building features for clients count?

It depends on the contract, if the client bears the risk and owns the IP, it may be funded research. We review the terms.

What about software we build for internal use?

Internal-use software can qualify but faces a higher innovation threshold. We apply that test where it’s needed.

See what your work qualifies for.

Request a Complimentary Assessment

This page is general information, not tax or legal advice. Whether specific activities and expenses qualify depends on the taxpayer’s facts and applicable law, and is determined through the appropriate R&D study. Novaric does not guarantee eligibility, credit amounts, or any IRS outcome.