Strata R&D Tax Group
Blog postAugust 20, 2026

One Credit May Be Hiding Another: A State R&D Credit Decision Framework for SaaS Companies

Most states offer their own R&D credit, and for SaaS companies with distributed teams, the federal claim is often only part of the picture. Here is how to think through whether state credits are worth pursuing.

One Credit May Be Hiding Another: A State R&D Credit Decision Framework for SaaS Companies

TL;DR

  • Most states offer their own R&D tax credit on top of the federal credit, and many conform closely to the federal definition of qualified research, so the work behind a federal claim can often support a state claim too.
  • For SaaS companies, what matters is where the research is performed, not where your customers are. A distributed engineering team can mean credit opportunities in more than one state.
  • The decision comes down to five questions: where the work happens, whether that state has a credit, whether you can actually use it, what claiming adds to the effort, and whether the numbers justify it.

If your SaaS company claims the federal R&D tax credit, there is a reasonable chance you are answering only half the question. The federal credit under IRC Section 41 gets most of the attention, but a majority of states run their own R&D credit programs, and state activity has picked up. Texas, for example, moved its R&D incentive to a new franchise tax credit structure effective for reports due on or after January 1, 2026, and California added an alternative simplified calculation method for taxable years beginning on or after January 1, 2025.

None of that matters, though, unless a state credit actually makes sense for your company. Here is a framework for thinking it through.

Question 1: Where is your qualified research actually performed?

State R&D credits generally follow the location of the work. For a SaaS company, that means the states where your engineers, product developers, and technical staff sit while they do the qualifying work, not the states where your customers or servers are.

This is where distributed teams change the math. A company headquartered in one state with engineers working remotely in two or three others may have qualified research expenses attributable to each of them. A quick way to check is your payroll by state: if a meaningful share of your engineering salaries goes to employees based in a particular state, that state is worth a look.

Question 2: Does that state offer a credit, and how closely does it track the federal rules?

Most states with an R&D credit conform, at least in large part, to the federal definition of qualified research under IRC Section 41 and Treasury Regulation 1.41-4. That conformity is the practical good news: the analysis that supports a federal claim, identifying qualifying projects and the expenses tied to them, can often carry over to the state claim with adjustments rather than starting from zero.

Two examples show the range. California's research credit is generally 15 percent of qualified research expenses above a base amount, for research conducted within California, using the federal definition of QREs. Texas's new Subchapter T credit is calculated from the qualified research expenses a company reports on federal Form 6765 that are attributable to research conducted in Texas. Each state sets its own rate, base calculation, and mechanics, so conformity is a starting point, not a guarantee that everything maps one to one.

Question 3: Can you actually use the credit?

This is the question that separates a credit on paper from cash in the business. State credits differ on three points that matter:

  • Refundability. Many state credits, including California's, are nonrefundable: they offset state tax liability but do not generate a refund beyond it. Some states offer limited refundability in specific situations. Texas, for instance, allows a refundable credit for certain entities that owe no franchise tax.
  • Carryforwards. Nonrefundable does not mean useless. Many states allow unused credits to carry forward, which can matter for a SaaS company that is pre-profit today but expects state tax liability later.
  • Your own tax posture in that state. A credit against a tax you do not owe, in a state where you have no filing obligation, may not be worth pursuing. Your state tax footprint has to line up with where the credit lives.

Question 4: What does claiming actually add to the effort?

Less than most owners expect, in many cases. Because the qualification analysis often carries over from the federal work, the incremental effort for a state claim is typically about allocation: establishing which qualified expenses are attributable to research performed in that state, and preparing the state form. It is generally an extension of the same body of work, not a second study. A provider that handles both at once can keep the incremental lift on your team modest, though the specifics depend on the states involved and the quality of your location records.

Question 5: Do the numbers justify it?

There is no universal threshold, but the inputs are knowable: your engineering payroll in the state, the state's credit rate and base calculation, and your ability to use the credit now or through carryforwards. A state claim built on a small sliver of payroll in a state with a modest, nonrefundable credit may not be worth the effort. A meaningful engineering presence in a state with a strong program often is. This is a case where an estimate up front beats a guess. Strata's initial assessment is free, and it can size the state opportunity alongside the federal one before you commit to anything.

What this looks like for a SaaS company

Consider a hypothetical: a 40-person SaaS company with engineers in California and Texas claims the federal credit each year. Under this framework, both states deserve a look. The California work may support a state credit at a higher rate than the federal one, subject to California's base calculation and its non-refundability. The Texas payroll may now feed the new franchise tax credit. Whether either claim makes sense depends on the company's specific activities, documentation, and tax posture in each state, but the point stands: stopping at the federal claim was never a deliberate decision. It was just the default.

The results can be meaningful. One SaaS client, Graphite Connect, identified over $1.1M in R&D credits. Individual results vary, and your outcome depends on your specific facts, activities, and documentation.

Next steps

If your company claims the federal credit and has technical staff in a state with its own program, or if you have never claimed at all, the state question is worth asking deliberately. Strata works alongside your CPA, handles the analysis, and starts with a $0 initial assessment. Get in touch to find out what your federal and state picture may look like.

This post is for informational purposes only and does not constitute tax or legal advice. Consult a qualified tax professional regarding your specific circumstances.

Author

Strata R&D Tax Group

← All insights