R&D Tax Credits for Silicon Valley AI & SaaS Startups

If you’re building an AI or SaaS company in the Bay Area, you are running one of the most R&D-intensive businesses in the economy. Your burn is mostly engineers. Your roadmap is a stack of hard, uncertain technical problems. And yet a federal program designed to put money back in the hands of companies doing exactly this work goes unclaimed by a striking number of Silicon Valley startups every year.

This is not a deduction you take someday when you’re profitable. For an early-stage, pre-revenue startup, the R&D tax credit can be cash against your payroll taxes - now, while you’re still burning runway. Here’s how it works, why AI and SaaS work qualifies so cleanly, and what’s changed in 2025 that makes it more valuable than ever.

The part most founders miss: it’s cash, not a someday-deduction

The objection we hear most from founders is “we’re pre-revenue, so a tax credit does nothing for us.” That was true decades ago. It isn’t now.

A qualified small business - broadly, one with under $5 million in gross receipts for the credit year and no gross receipts in any year before the five-year window ending with it - can elect under IRC §41(h) to apply the federal R&D credit against its employer payroll taxes, up to $500,000 per year for tax years beginning after December 31, 2022. You don’t need income, profit, or a tax bill. If you have a payroll - and you do - you can monetize the credit on your quarterly payroll tax filings.

For a seed or Series A startup spending the bulk of its capital on engineering salaries, that is a direct extension of runway. It is one of the few non-dilutive sources of cash a venture-backed founder can pull without talking to an investor. The mechanics - the election on Form 6765, the bridge through Form 8974, and the quarterly claim on Form 941 - are laid out step by step in how startups turn the R&D credit into payroll-tax cash and on our payroll tax offset page.

One caution worth internalizing early: the election has to be made on a timely filed original return (extensions included), and it is available for at most five taxable years in a company’s life. Both facts turn it into a planning decision rather than a filing formality.

Why AI and SaaS work qualifies so cleanly

The federal credit under IRC §41 uses a four-part test, applied per business component. An activity qualifies when it meets all four:

1. Permitted purpose - you’re developing or improving the functionality, performance, reliability, or quality of your product.
2. Technological in nature - the work relies on computer science, engineering, or the hard sciences.
3. Elimination of uncertainty - at the start, you didn’t know whether you could achieve the result, how, or what the right design was.
4. Process of experimentation - you evaluated alternatives through prototyping, benchmarking, modeling, or systematic trial and error.

The day-to-day reality of an AI or SaaS team clears this bar more often than founders assume. A few examples that frequently qualify:

• Model development and fine-tuning - selecting architectures, building training and evaluation pipelines, fine-tuning open-weight models, and the experimentation that comes with chasing a metric.
• Retrieval and RAG systems - designing chunking, embeddings, retrieval, and ranking where the right approach was genuinely uncertain and had to be tested.
• Inference performance and cost - quantization, batching, caching, GPU/accelerator scheduling, and the latency-versus-quality trade-offs you benchmarked your way through.
• Evaluation and reliability - building eval harnesses, guardrails, and hallucination mitigation for non-deterministic systems.
• Core platform engineering - re-architecting for scale, redesigning data models, multi-tenancy, and security engineering where the design wasn’t obvious.

The work qualifies even though it lives in pull requests, tickets, and design docs rather than a lab notebook. The activity is research; it just wasn’t labeled as research.

For a deeper walk-through of how everyday engineering maps to the test, see our SaaS & software industry guide, the four-part test in plain English, and what actually qualifies for SaaS.

2025 changed the math: §174A brings back full expensing

For a few painful years, companies had to capitalize and amortize their R&D costs rather than deduct them - a rule that hit cash-burning software startups especially hard, sometimes creating a tax bill on top of a net loss.

That’s been reversed. The One Big Beautiful Bill Act created IRC §174A, restoring immediate, full expensing of domestic research costs - software development explicitly included - for tax years beginning after December 31, 2024.

Balances you capitalized in 2022 through 2024 are not stranded: the remaining unamortized amount can be deducted in the first tax year beginning after December 31, 2024, or split across 2025 and 2026. (Updated August 13, 2026: the separate window for eligible small businesses to amend 2022-2024 returns retroactively generally closed July 6, 2026. Only narrow, fact-specific situations tied to a still-open refund statute could remain - confirm with a qualified professional rather than assuming.) The procedural roadmap is Rev. Proc. 2025-28, implemented through Form 3115.

The credit and the deduction work together: you take the deduction for the spend and the credit for the qualified portion. Our §174A explainer covers the mechanics.

Don’t forget California (and wherever else you operate)

Federal is only half the picture. California has its own R&D credit, and most startups that claim the federal credit never capture the state one - even though the qualifying work is the same. Because every state defines its base, rate, caps, carryforward, and refundability differently, the state benefit gets skipped by tools that optimize the federal number and stop.

Ricerca computes the federal and state credit from the same qualified-research base, so your California benefit (and any other state where you have nexus) is captured in the same study. More on that on our state R&D credits page.

The catch: the IRS now wants the receipts

Here’s the part the “instant credit” tools gloss over: the IRS has moved substantiation onto the return itself and onto the front end of refund claims.

On an amended return, a research credit is a refund claim, and - as the IRS has set out the requirements - a valid claim must identify all the business components the claim relates to, identify all research activities performed for each component, and provide the total qualified wage, supply, and contract-research expenses for the year. Two items the IRS previously required, naming the individuals who performed each activity and describing the information each sought to discover, were waived for claims filed on or after June 18, 2024 - though the IRS notes that information can still be requested in an examination. As of this writing that waiver stands, and the transition period allowing 45 days to perfect a deficient claim ran, as published, through January 10, 2027. This guidance has been revised repeatedly; check current IRS guidance before filing.

On an original return, the revised Form 6765 adds Section G, which asks for business-component-level detail. Per the current Instructions for Form 6765, Section G is optional for tax years beginning before 2026 and applicable for tax years beginning after 2025, with exceptions for qualified small businesses electing the payroll credit and for smaller filers on originally filed returns - confirm the thresholds against the current-year instructions, because the phase-in has already moved more than once.

In other words: an aggressive, thinly-documented credit is a liability, not a windfall. The number is only worth what you can defend - see what examiners actually ask for.

This is exactly where an automation-only tool falls short and where a study should be defensible by construction. Ricerca enforces the §41 statutory tests in software - the four-part test, the §41(d)(4) exclusions, funded-research and rights-and-risk contract analysis, the alternatives evaluated and rejected for each component, and §41(f) controlled-group rules - and then has experienced R&D specialists review and finalize every study before it’s issued. You get the speed of AI on intake and narratives, with substantiation built the way an examiner actually reads it. See why founders choose Ricerca.

What to do before you file

A few concrete steps for a Bay Area founder:

• Don’t wait for profitability. If you’re a qualified small business, the payroll-tax election can put cash to work this year - but it has to be made on a timely filed original return.
• Check your gross-receipts history first. Receipts in any year before the five-year window disqualify the election outright, and that is a fact about your past that no planning fixes.
• Capture engineering evidence as you go. Your tickets, PRs, commits, benchmarks, and design docs are your contemporaneous record - and the rejected approaches are the best proof of experimentation you have.
• Screen your contracts. Customer-funded development and grant-funded work can be excluded as funded research under §41(d)(4)(H) no matter how strong the engineering was.
• Claim the state credit too. California and other states stack on top of the federal credit - see state R&D credits.
• Look back at open years. Prior-year claims are still possible within the general refund statute, with the extra specificity requirements described above.

Curious what your credit could be? Try our R&D credit estimator - it runs entirely in your browser - or start with the R&D tax credit guide.

Sources

• IRC §41 - Credit for increasing research activities and IRC §174A - Domestic research or experimental expenditures (U.S. House, Office of the Law Revision Counsel)
• IRS - About Form 6765 and the Instructions for Form 6765
• IRS - About Form 8974
• IRS - Required information for a valid research credit claim for refund
• IRS - Rev. Proc. 2025-28 (PDF)