R&D Tax Credit for SaaS Companies: What a Credit Study Asks of Your Engineering Team
The R&D tax credit for SaaS companies rarely stalls on eligibility. It stalls on a worry that a study will pull engineers off the roadmap. Here is what a well-run study actually asks of each part of your team.

TL;DR
- The R&D tax credit for SaaS companies is usually within reach for teams building new features, architecture and integrations. The bigger hurdle is often bandwidth, not eligibility.
- A well-run study asks for a modest amount of time from engineering, finance and leadership. The specialist carries most of the work.
- What you get back is a documentation package built to support the claim. You hand it to your CPA to file with the return.
Why SaaS teams hesitate on the R&D tax credit
The R&D tax credit for SaaS companies is one of the more natural fits in the tax code, and yet many founders and CFOs put it off year after year. The reason is rarely “we don’t think we qualify.” More often it is “we can’t afford to pull our engineers off the roadmap for a tax project.”
That concern is reasonable. Engineering time is the scarcest resource in most software companies, and a project that eats a sprint or two can cost more in delayed releases than it is worth. The good news is that a well-run credit study should not look like that. This post walks through what a study actually asks of each part of your team, and what you get at the end.
What the R&D tax credit is, and why SaaS companies can qualify
The federal research credit under IRC Section 41 rewards businesses for qualified research. That means work aimed at new or improved functionality, performance, reliability or quality, where the team faced technical uncertainty and worked through it by evaluating alternatives. The Treasury regulations at 26 CFR 1.41-4 spell out how that test applies.
For many SaaS companies, that describes a good share of the engineering calendar: new product features, re-architecture for scale, performance work, data pipelines, and integrations that did not have an obvious answer at the outset. Routine bug fixes, cosmetic changes and simple configuration generally do not count, and software built mainly for internal back-office use faces a higher bar. A specialist’s job is to sort the qualifying work from the rest, which is why the study needs some input from the people who did it.
What the study asks of your engineering team
This is the part founders worry about most, so it is worth being direct: the ask of your engineers is small, and it comes early.
What they provide. Engineers and technical leads help the specialist understand what was built during the year, what was technically hard about it, and how the team worked through the hard parts. That means short, structured input about how their time was spent and a focused conversation with the people who led the work. Nobody is asked to write a report or rebuild a year of history from memory.
What they do not have to do. They do not need to learn tax rules, fill out IRS forms or reformat their tickets. The records software teams already keep, like design docs, pull requests, sprint boards and test results, often carry much of the supporting detail. The specialist does the translation.
How it fits around a release. Because the engineering input is brief, it can usually be scheduled around sprint boundaries rather than in the middle of a launch. If your team has a crunch coming, say so up front; a good provider can plan around it.
What the study asks of your finance team
Finance usually carries a little more of the early work than engineering, but it is mostly gathering information you already have.
Payroll and people. The credit is built largely on the wages of people who perform, directly supervise or directly support qualified research. The specialist will ask for payroll information and job roles for the years in scope.
Tax returns and expenses. Expect a request for tax returns for the study years and general information about vendor and contractor spending. For SaaS companies, this is where cloud computing costs and outside development contracts get evaluated, since some of those costs can count when they tie to qualifying work.
Contracts. If you build custom functionality for specific customers, the specialist may want to look at some sample agreements. Who bears the risk of the work and who keeps the rights to it can affect what is eligible.
Most finance teams find this is a matter of pulling reports, not creating new ones.
What the study asks of founders and leadership
Leadership’s role is mostly about context and decisions. You will be asked to:
- confirm which product lines and initiatives were in play;
- flag anything unusual, such as an acquisition, a new entity or a pivot;
- make a few calls along the way, such as which open years to consider.
A founder who was close to the technical work may also join the conversation with engineering. Beyond that, your involvement can be light.
How long the whole process takes
A typical study often wraps up in roughly four to eight weeks, depending on how quickly information comes in and the size of the engagement. Most of that time is the specialist’s analysis and write-up, not your team’s effort. How fast documents arrive drives the timeline more than anything else, so starting earlier simply gives your team more room to fit requests around releases and close.
It also starts small: Strata offers a $0 initial assessment to size the opportunity before anyone commits to a full study.
What you get at the end
The deliverable is a documentation package built to support the claim. It includes the credit calculation, the forms ready to file, and documentation that ties your qualifying activities to the costs claimed. Strata delivers it to you, and you hand it to your CPA, who files it with your return.
That documentation matters more than it used to. Under the current Form 6765 instructions, many taxpayers are expected to report information about each business component (product, feature or process) for tax years beginning after 2025. There are some exceptions for smaller claims and qualified small businesses. A study that records detail for each project as it goes can make that reporting much easier.
For a sense of scale, Graphite Connect, a SaaS company, identified more than $1.1 million in R&D credits through a structured study. Individual results vary, depending on the specific activities, documentation and facts.
How the R&D tax credit can help a SaaS company that is not yet profitable
A common question from early-stage founders is “We don’t owe income tax yet, so why bother?” Qualified small businesses may be able to apply part of the credit against payroll taxes instead, and unused credits can generally carry forward. Whether that applies depends on your gross receipts and history, which an initial assessment can sort out quickly.
Choosing a lighter or fuller level of support
Not every SaaS team wants the same amount of help. Teams that know their numbers well and want a streamlined path may prefer a lighter-touch option. Teams that want a dedicated specialist building and documenting the claim may prefer a fuller engagement. Strata offers Self-Serve, Full-Service and Enterprise options, and a short conversation is usually enough to tell which fits.
Frequently asked questions
How much engineering time does an R&D tax credit study take for a SaaS company?
Usually a modest amount, early in the engagement: brief structured input about how time was spent and a focused conversation with technical leads. Most of the work sits with the specialist.
Do we need detailed timesheets to claim the software development tax credit?
Not necessarily. Records made at the time the work happened are stronger, but many SaaS teams can support a claim with payroll data plus the engineering records they already keep, like tickets, pull requests and design docs.
Does bug fixing count toward the R&D tax credit?
Routine bug fixes and maintenance generally do not. Work that resolves real technical uncertainty, such as re-architecting for performance or building a new capability, can.
Can we claim the R&D tax credit for prior years?
Often, yes, through amended returns for open years, subject to the IRS refund-claim rules. An initial assessment can help you see which years are worth reviewing.
Who files the claim?
Your CPA files it with your return. Strata prepares the calculation, forms and supporting documentation and delivers them to you to pass along.
Bring your R&D tax credit questions to us first
If the worry holding you back is that a study will derail your roadmap, start with a conversation. Strata’s 15-minute review and $0 initial assessment will show you whether the R&D tax credit fits your company and what it would take from your team. Schedule yours at stratataxgroup.com/contact.
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



