R&D Tax Credit for Software Startups: Cash Before Profit
You raised a seed round, you're paying a team of engineers to build something that doesn't fully exist yet, and you haven't turned a dollar of profit. So when someone mentions a tax credit, you tune out. Credits offset taxes, and you don't owe any.
Here's what that instinct misses. The R&D tax credit for software startups isn't only an income-tax break. For an unprofitable company, it can come back as actual cash, applied against the payroll taxes you're already paying every quarter. That single feature is why this is one of the most underused sources of non-dilutive funding available to early-stage software, AI, and SaaS companies.
Can a pre-profit software startup use the R&D tax credit?
Yes. Through the qualified small business payroll tax offset, an eligible startup can apply up to $500,000 of its federal R&D credit each year against employer payroll taxes, turning research spending into cash even with zero income tax liability. You claim it on Form 6765, then Form 8974.
What actually counts as "research" when you're building software
The biggest reason founders skip this is a wrong assumption: that "research" means lab coats, patents, or something nobody has ever done before. It doesn't. The work has to clear a four-part test under Section 41, and ordinary product engineering usually clears it. You need a permitted purpose (developing or improving a product, process, or software), the work has to be technological in nature, you have to be resolving genuine technical uncertainty, and you have to get there through a process of experimentation. Building a new inference layer, re-architecting for scale, integrating a model where the approach isn't obvious upfront: that's the kind of thing the credit was written for. The experiments don't even have to succeed to count.
Once an activity qualifies, three buckets of spending feed the credit. There's the wages you pay U.S. employees doing or directly supervising the qualified work, which for most software companies is the biggest number by far. There's supplies consumed in development, and for a modern software team that includes the cloud compute you burn training and testing. And there's 65% of what you pay U.S. contractors for qualified research. Foreign engineering doesn't make the cut, which matters more than it used to, and we'll come back to that.
Turning the credit into cash: how the payroll offset works
This is the part that changes the decision. Normally a credit only helps if you owe income tax. The payroll offset exists specifically so pre-profit companies aren't shut out.
To use it, you have to be a qualified small business, or QSB. The definition is narrower than it sounds and worth checking against your own numbers: your gross receipts have to be under $5 million in the credit year, and you can't have had any gross receipts more than five years before the credit year. A company that first booked revenue two years ago and did $600,000 last year qualifies. A company that's been selling since 2018 does not, no matter how small. Once you qualify, you can apply up to $500,000 of credit against payroll taxes per year, for up to five years, a $2.5 million lifetime ceiling. The credit hits the employer share of Social Security tax first, up to $250,000, then the employer share of Medicare for anything above that.
The mechanics are where timing bites. You make the election on Form 6765 with your income tax return, and it has to be your original, timely-filed return, extensions included. You cannot go back and add it to an amended return later. From there, Form 8974 rides along with your quarterly Form 941, and the credit starts reducing your payroll deposits in the first calendar quarter that begins after you file the return. File a quarter late, and you lose a quarter of benefit.
Here's what it looks like for a pre-revenue AI startup with a U.S. engineering team, using tax year 2025 numbers:
Qualified research expenses (2025)
U.S. engineering wages for qualified work: $900,000
Cloud compute and supplies used in development: $150,000
Contract research (65% of $100,000 paid to U.S. contractors): $65,000
Total QREs: $1,115,000
Credit and cash benefit (2025)
Method: alternative simplified credit, first year with no prior QREs (6% of current QREs)
Federal R&D credit: $66,900
Elected as a payroll offset (company is a QSB): $66,900 in cash against employer payroll taxes, starting the quarter after the 2025 return is filed
No income tax liability required. That $66,900 is money the company keeps instead of remitting, at exactly the stage when runway is the thing that matters most.
The 2025 rule change that made this bigger
For a few painful years, a separate rule quietly worked against software startups. The 2017 tax law forced companies to capitalize and amortize their software development costs over five years under Section 174, rather than deduct them right away. For a pre-profit company, that created phantom taxable income: you'd spend a million dollars building product and only get to deduct a fraction of it that year.
That reversed in 2025. The One Big Beautiful Bill Act, signed in July 2025, added Section 174A and restored immediate expensing of domestic research costs for tax years beginning after December 31, 2024. Software development explicitly counts. So your 2025 spending is fully deductible now, and because the credit is built on those same expenses, a cleaner Section 174 picture and a cleaner credit tend to move together. (Foreign research still has to be amortized over 15 years, which is one more reason where your engineers sit matters.) There was also a retroactive window letting small businesses amend 2022 through 2024, but that window closes July 6, 2026 under Rev. Proc. 2025-28, so for most companies the going-forward benefit is now the play.
California plays by its own rules
If you operate in California, and most of our clients do, run the state analysis separately, because it diverges from the federal one.
California has its own research credit, and the differences are noteworthy. The state offers a 15% credit on qualified expenses over a base amount (with a new 3% simplified method available for tax years beginning on or after January 1, 2025), and the research has to be physically performed in California to count. The big one for a startup: California has no payroll offset. None. The state credit only does you good once you actually owe California income or franchise tax, and it can't drop you below the $800 minimum franchise tax. The consolation is that unused California credits carry forward indefinitely, so they wait for you until you're profitable, rather than expiring. California also never adopted the federal amortization mess, so it has always let you expense research costs. For tax years 2024 through 2026 there's a $5 million cap on total business credits, though for a company at this stage that ceiling almost never binds.
The practical upshot: a California software startup can often claim a real federal cash benefit this year while its state credit sits parked as a carryforward for the year it starts owing tax. Two different timelines, one set of expenses.
Where founders get this wrong
When a founder brings me this, the first thing I check is whether the payroll election was actually made on the original return. More than once I've seen an otherwise valid credit sitting as an income-tax carryforward because it got claimed a few months late or tacked onto an amended return, which the payroll election doesn't allow. For a company that won't owe income tax for years, that timing slip can leave serious money on the table, and it's completely avoidable if it's on the calendar early.
The other recurring mistakes cluster around the same theme of doing it after the fact instead of alongside the work. Documentation is meant to be contemporaneous. Notes on what technical uncertainty you were chasing and how you experimented are worth far more written during the sprint than reconstructed the week before filing. You should be documenting your processes anyway. Founders also assume California mirrors the federal treatment and overestimate what the state credit will do for them this year. And they overlook that claiming the credit reduces the deduction for those same wages unless the reduced-credit election is made, so the two benefits don't fully stack on the same dollar.
What this means for your next return
If you're an early-stage software, AI, or SaaS company with U.S. engineers and no profit yet, the decision isn't whether the credit is worth something. It's whether you capture it correctly and on time this year, because the payroll offset only works if the election lands on your original return. Model your qualified spend, confirm you clear the QSB test, and get the election onto the return before it's filed, not after.
If you want a second set of eyes on whether your work qualifies and how much of it converts to cash, that's a conversation we're glad to have.
This is general information, not tax advice for your particular company. The rules here carry real conditions and deadlines, and the details of your situation change the answer. Talk with a CPA (ideally us) before you act on any of it.
