Learn
Most technical founders leave tens of thousands of dollars unclaimed every year because they don't know their development work qualifies. This guide explains exactly what the credit is, who's eligible, and what documentation the IRS expects.
<30%
of eligible SMBs claim the credit
$5K–$30K+
cost of traditional R&D credit studies
3 years
you can look back with amended returns
6–8%
typical credit rate on qualifying wages
Understanding the credit
The federal R&D tax credit under IRC Section 41 allows businesses to offset income tax liability based on qualified research expenditures. Enacted in 1981 and made permanent in 2015, it is one of the most valuable, and most underutilized, incentives available to small businesses.
The credit is calculated as a percentage of qualified research expenses (QREs), primarily the wages paid to employees performing, supervising, or directly supporting qualified research. For startups and small businesses, the Alternative Simplified Credit (ASC) method typically yields a credit of 6–8% of qualifying wages.
A solo founder paying themselves $120K and spending 70% of their time on qualifying R&D could generate approximately $5,040 in annual federal tax credits (enough to offset payroll taxes dollar-for-dollar under the startup election).
Every activity must pass all four criteria defined in Form 6765 instructions to qualify:
The activity must intend to create or improve a product, process, or software in terms of function, performance, reliability, or quality.
There must be uncertainty about the capability, method, or design that could not be resolved by existing knowledge or standard practice.
The work must involve evaluating alternatives: through modeling, simulation, systematic trial and error, or other methods.
The activity must rely fundamentally on principles of engineering, computer science, or physical or biological sciences.
Eligibility
Any U.S. business that pays wages to employees performing qualified research can claim the credit. There is no minimum revenue requirement, no industry restriction, and no company size threshold. The IRS explicitly includes software development as eligible R&D.
If you pay yourself a W-2 salary (or plan to) and spend time building software that involves experimentation, you likely qualify.
Each team member performing, supervising, or directly supporting R&D adds to your qualified research expenses.
Using Claude, ChatGPT, Cursor, or Codex to brainstorm, prototype, and experiment? Those sessions involve qualified research activity.
Under the startup election, companies with less than $5M in gross receipts can apply the credit against payroll taxes instead of income tax.
The IRS recognizes three categories of qualifying employees: those directly performing qualified research, direct supervisors of qualified research, and direct support personnel. Marketing, sales, and general administration do not qualify.
Qualifying activities
The IRS software experimentation audit guidelines provides specific guidance on how software development qualifies. The key distinction: routine development does not qualify; experimentation does.
Building a new feature with unknown technical approach
Prototyping three different data pipeline architectures to find one that handles real-time classification at scale.
Evaluating AI model integration patterns
Testing multiple approaches for integrating LLM APIs: prompt engineering, fine-tuning, RAG, each evaluated for acceptable accuracy.
Resolving performance uncertainty
Systematic experimentation with caching strategies, database indexing, and query optimization to meet latency requirements.
Designing novel algorithms or data structures
Developing a custom deduplication engine to prevent double-counting across multiple data sources with overlapping timestamps.
Architectural experimentation
Evaluating serverless vs. container architectures, testing edge computing patterns, prototyping distributed system designs.
Routine bug fixes with known solutions
Fixing a typo in a CSS file. Updating a dependency version. Correcting a null pointer exception.
Deployment and DevOps execution
Running CI/CD pipelines, configuring DNS, deploying to production using established procedures.
Cosmetic UI changes
Changing colors, adjusting padding, swapping fonts. No technological uncertainty involved.
The “vibe coder” workflow qualifies more than you think. Using AI coding tools to brainstorm architectures, prototype solutions, and evaluate alternatives is process of experimentation, a core element of the four-part test. The IRS cares about the nature of the uncertainty, not whether a human or AI wrote the first draft.
Documentation
The IRS requires taxpayers to “retain records in a sufficiently usable form and detail to substantiate that the expenditures claimed are eligible for the credit.” In practice, this means you need contemporaneous records: documentation created at or near the time the work was performed, not reconstructed months later.
Records showing when R&D was performed, by whom, and on which project. Git commit histories, IDE heartbeat logs, and session timestamps all serve this purpose.
Project-level descriptions of the technological uncertainty addressed and the experimentation performed. Must reference the four-part test without revealing proprietary details.
Per-employee breakdowns showing how much time was spent on qualifying vs. non-qualifying work. The IRS accepts reasonable estimates supported by factual evidence.
Wages and other expenses tied to qualifying projects and activities. For wage-based credits, this means connecting employee time to specific R&D projects.
Git commits provide timestamped, author-attributed records of exactly when development occurred and on which projects: the definition of contemporaneous documentation.
Branch naming patterns and commit messages reveal experimentation: feature branches, prototype iterations, and A/B testing are visible in the commit graph.
IDE and AI coding tool plugins capture real-time R&D sessions (including time spent on architecture planning, uncertainty resolution, and alternative evaluation) that produce no commit artifacts.
Combined, these sources create a documentation trail that is generated automatically as you work, not reconstructed from memory months later.
Debunked
These misconceptions stop more founders from claiming the credit than actual eligibility issues.
“You need to be doing lab science or hardware R&D.”
The IRS explicitly includes software development. If you're building software that involves technological uncertainty and experimentation, you qualify. The credit was expanded to cover internal-use software under specific criteria.
“Pre-revenue companies can't claim R&D credits.”
Under the startup election, qualified small businesses with less than $5M in gross receipts can apply up to $500,000 annually against payroll taxes, even with no income tax liability.
“It's not worth it unless you have a large engineering team.”
A single developer earning $100K and spending 60% of their time on qualifying R&D generates approximately $3,600 in annual credits. Over 3 years of lookback, that's $10,800+ recovered.
“The audit risk is too high for small companies.”
The IRS audits the quality of documentation, not the size of the claim. Companies with strong contemporaneous records (timestamped logs, technical narratives, time allocations) are better positioned than large companies with year-end reconstructions.
“You need to hire an expensive consultant ($10K–$30K).”
Traditional R&D credit studies are expensive because they reconstruct your year after it's over: interviewing engineers, reviewing project documents, writing narratives from memory. Continuous tracking eliminates most of that manual work.
A better approach
Traditional R&D credit studies are point-in-time reconstructions. A consultant interviews your engineers after the year is over, asks them to recall what they worked on, and writes narratives from memory. This approach is expensive, inaccurate, and produces weaker documentation.
Traditional approach
Continuous tracking
The IRS explicitly prefers contemporaneous records over reconstructions. Documentation created at the time of the research is harder to challenge in an audit because it does not depend on anyone's memory.
Go deeper
The federal R&D tax credit (IRC Section 41) lets businesses offset income tax with qualifying research expenses. Learn who qualifies and how it works.
The IRS uses a four-part test to determine if business activities qualify for the R&D tax credit. Learn each criterion and how software development applies.
IRS Form 6765 is used to calculate and claim the R&D tax credit. Learn how to fill it out, which sections matter, and what documentation to keep.
Compare the Alternative Simplified Credit (ASC) and Regular Credit methods for calculating R&D tax credits. Learn which method produces a larger credit.
Software development is one of the most common qualifying activities for the R&D tax credit. Learn which activities qualify and which don't.
Startups can use the R&D tax credit to offset payroll taxes even before they're profitable. Learn how the payroll tax offset works and how to claim it.
The IRS requires contemporaneous documentation for R&D tax credit claims. Learn what records you need and why real-time tracking matters for audit defense.
Research and experimental expenses are the cost base behind R&D tax planning. Learn how R&E expenses differ from Section 41 credit expenses and what records to keep.
Qualified Research Expenses are the basis for calculating R&D tax credits. Learn what counts as a QRE — wages, supplies, and contract research.
Connect your code repository and QuarryFi scans your commit history, classifies R&D activity, and shows your estimated credit value. Free forever for the current tax year.
See if you qualify, free for current year→No credit card required · Metadata only · Never source code
This content is for informational purposes only and does not constitute tax, legal, or accounting advice. QuarryFi is documentation preparation software, not a tax advisor. Consult a qualified CPA or tax attorney before claiming R&D tax credits. IRS guidance and regulations may change.