Your Developers Are Already Doing R&D. There's a Tax Credit Built Around That.

TL;DR

• Software development regularly qualifies for the federal R&D tax credit under IRC Section 41 — labs and white coats not required
• The IRS four-part test rewards technical uncertainty and experimentation, which describes most serious engineering work
• Wages, contractor costs, and cloud computing expenses all count toward the credit calculation
• A three-year lookback allows companies to recover credits from prior years never assessed — average lookback value across Strata's active engagements is $245,000
• Graphite Connect, a SaaS company, secured over $1.1M through a documented Strata engagement

Most software founders don't think of their work as research and development. R&D sounds like a pharmaceutical lab or an aerospace program — white coats and wind tunnels. Not sprint planning and GitHub commits.

But the R&D tax credit doesn't care about optics. It's built around a specific legal definition, and a lot of what software companies do every day fits that definition exactly. Graphite Connect, a SaaS company, discovered this firsthand — and walked away with over $1.1 million in R&D credits.

That's a documented result from a Strata engagement — and one that reflects Graphite Connect's specific qualifying activities. Individual results will vary.

Here's what actually happened, and more importantly, why it happened.

What the IRS Is Looking For

The R&D tax credit runs on a four-part test called the Qualified Research Activities test. Every activity that generates a credit has to meet all four criteria. They're not complicated, but they're specific.

1. Technological in nature. The work has to rely on a hard science — engineering, physics, computer science, or a biological science. Software development often satisfies this criterion, though it's always evaluated against the specifics of what your team actually builds.

2. Permitted purpose. The work has to be aimed at creating a new or improved product, process, or software. Not marketing. Not administration. The thing you're actually building.

3. Elimination of uncertainty. At the start of the project, there was a genuine question: Can we build this? Will this approach work? Will this architecture hold under load? If you knew the answer before you started, it doesn't count. If you had to figure it out, it probably does.

4. Process of experimentation. You evaluated alternatives. You tested approaches. You iterated. Sound familiar? That's the core of how software gets built.

If your engineers are solving problems they haven't solved before — debugging unexpected behavior, building integrations with no existing template, designing systems that have to perform at a new scale — they're likely doing qualified research. The credit follows the work.

Where Software Companies Leave Money on the Table

The most common mistake is scope. Companies claim the credit only for what they think of as "R&D" — a new feature, a skunkworks project, a technology pivot. But the credit applies to qualified activities across the entire development process: architecture decisions, algorithm development, API design, performance optimization, security engineering.

It also applies to wages, contractor costs, and cloud computing expenses tied to that work — not just salaries.

The second mistake is time. The R&D tax credit allows a three-year lookback, meaning you can file amended returns and recover credits from prior years you never claimed. Across 86 completed engagements, the average three-year lookback value is $245,000. Your result may be higher or lower depending on your company's specific qualifying activities and expenses.

What This Looks Like in Practice

When Graphite Connect came to Strata, they weren't sure they qualified. They had engineers building a supplier network platform with a complex integration layer — custom APIs, proprietary matching logic, security architecture that had to meet enterprise standards their team had never navigated before. They had uncertainty. They had experimentation. They had engineers solving hard problems.

Strata documented that work against IRS criteria, quantified the qualifying expenses, and submitted. The result was over $1.1 million in credits.

That kind of documentation is what separates a defensible R&D claim from one that creates audit risk. The credit exists to reward innovation — but the IRS expects you to be able to show your work.

The Cost of Waiting

R&D credits don't accumulate indefinitely. Each year you don't claim is a year that closes. The lookback window is three years, and it moves. If your company has been building software for the last three years and has never assessed your qualifying activities, there's a real number sitting uncaptured.

The average credit per engagement at Strata is $24,271 annually. Across a three-year lookback, that average climbs to $245,000. Neither of those figures is a promise or a projection — they're historical results from 86 active engagements.

Your number may be higher. It may be lower. The point is: you don't know what it is until someone looks.

What a Conversation With Strata Looks Like

There's no cost to find out. Strata doesn't charge for an initial assessment. You describe what your team builds, how they build it, what's been novel or uncertain in the last few years. Strata evaluates it against the four-part test. If there's something there, you'll know — and you'll have a clear picture of what the engagement involves before committing to anything.

The turnaround from assessment to filed claim typically runs four to eight weeks.

If you're running a software company and you haven't had this conversation, it's worth having.

Book a free consultation →

Frequently Asked Questions

Does software development qualify for the R&D tax credit?

It often does. Software development qualifies when it involves genuine technical uncertainty, a process of experimentation, and a permitted purpose under the IRS four-part test. Building new functionality, solving architectural problems, and developing integrations with unknown compatibility outcomes are examples of activities that frequently meet the criteria. Routine maintenance, bug fixes following known procedures, and administrative development typically do not.

What kinds of software activities qualify as R&D under IRS rules?

Activities that tend to qualify include: developing new algorithms or proprietary logic, designing and testing system architectures under performance uncertainty, building integrations where compatibility is unknown at the outset, optimizing systems for scale that hasn't been achieved before, and resolving technical problems that require iterating through multiple approaches. The key factor is whether your team was working through genuine uncertainty — not executing a known process.

Can early-stage or startup software companies claim the R&D tax credit?

Yes. Qualified small businesses — generally those with less than $5 million in gross receipts and fewer than five years of revenue — can apply the R&D credit against payroll taxes rather than income tax, which makes the credit immediately usable even without a tax liability. This provision was expanded by the Inflation Reduction Act and is particularly valuable for pre-profit SaaS companies with active development teams.

What documentation does a software company need to support an R&D credit claim?

Documentation should demonstrate that the activities met the four-part test: technical in nature, aimed at improvement, involving genuine uncertainty, and pursued through experimentation. Useful records include project documentation, sprint notes, architecture decision logs, GitHub commit histories, employee time allocations, contractor invoices, and any records showing iteration or testing. Perfect records are not required — reasonable, organized evidence is the standard. A proper R&D study structures existing documentation into a format that meets IRS expectations.

How much is the R&D tax credit worth for a software company?

It depends on the volume of qualifying activity and the wages associated with it. Strata's active engagements average $24,271 in annual credit value, with a three-year lookback average of $245,000. Software companies with larger engineering teams and higher proportions of novel development work typically see higher results. There is no cost to find out what your company's number might be.

Strata R&D Tax Group specializes in R&D tax credit documentation and filing for companies in technology, manufacturing, and professional services. This post is for informational purposes only and does not constitute tax or legal advice. Consult a qualified tax professional regarding your specific circumstances.