Skip to main content
2,200+ contractors in the research universe benchmarked. Do you know your gross profit per labor hour? See where you stand →
Level
Tax Strategy

Your Service Business Built Custom AI Workflows. Some of That Spend May Qualify for the R&D Tax Credit.

Kenneth MayEnrolled Agent (EA) · 45+ years tax planning · Owner, B A Services Inc · Specialist in service-business tax strategy
Updated October 7, 2026·Originally published April 30, 2026·9 minute read
Share

Tax Strategy

If your service business paid to build custom AI workflows, dashboards, or integrations, some of that work may qualify for the federal R&D credit. In a first year with no prior QREs, the simplified credit is 6% of qualified spend, and only 65% of qualifying contractor invoices count. Back-office tools face extra internal-use software tests. The payroll tax offset is limited to businesses under $5M in gross receipts with no receipts before the five-year window. It does not require a lab. It does require evidence.

Kenneth May, EA, 45+ years tax planning

9 minute readTax Strategy

If this is you

Fictional scenario: you spent $80K in 2025 having an outside developer build custom integrations between your field service software, QuickBooks, and a Slack bot that flags overdue invoices. Maybe another $40K on AI workflows that draft customer follow-up emails. Your CPA filed your return. Nobody mentioned the R&D credit. Was anything missed? Only if the work passes the tests below. These are back-office tools, so they face the stricter internal-use software rules. The developer contracts must also leave you bearing the economic risk and holding substantial rights. If all $120K did qualify and you had no QREs in the prior three years, the federal credit would be about $120K x 65% x 6% = $4,680, before any Section 280C adjustment. If none of it qualifies, the answer is zero.

The Federal Research and Development Tax Credit (Section 41) is often overlooked by service businesses. One reason: the credit dates to 1981 and is associated with pharmaceutical labs and aerospace engineers. Owners and advisers may not think to apply it to software and process work.

But Section 41 is much broader than that. If you spend money trying to develop or improve a process, product, software, technique, or system that involves uncertainty and experimentation, you may qualify. The language is broad, but the tests are real. AI workflow development, custom software, system integrations, automated dashboards, and improved operational processes can qualify when they pass the four-part test. Back-office software must also pass the internal-use software tests described below.

Fictional example: a $4M service business has $150K of qualifying contractor spend in one tax year. QRE is $150K x 65% = $97,500. With no QREs in any of the prior three years, the simplified credit is 6% x $97,500 = $5,850. If the prior three years instead averaged $60,000 of QREs, the base is 50% x $60,000 = $30,000. The credit is then 14% x ($97,500 minus $30,000) = $9,450.

The payroll tax option has two conditions: gross receipts under $5M for the credit year, and no gross receipts before the five-tax-year period ending with that year. An established $4M business that has had receipts for longer than that does not qualify. It uses the credit against income tax, and general business credit carryover rules apply if it has no current liability.

Here is what qualifies, what doesn't, the four-part test, and how to file without painting a target on your back.

What the credit is actually worth

The R&D credit is calculated on Qualified Research Expenses (QREs), which are mostly:

  • W-2 wages of employees performing or directly supervising qualified research
  • Supplies used in qualifying research, with statutory exclusions
  • 65% of contract research expenses paid to outside developers, consultants, or agencies, but only where you bear the economic risk and retain substantial rights to the results

The credit is computed with either the Alternative Simplified Credit (ASC) or the regular method, which is 20% of QREs above a historical base. Many small businesses use the ASC, which has two cases:

  • If you had QREs in each of the prior three tax years: 14% of current QREs above 50% of the prior three-year average QRE.
  • If any of the prior three tax years had zero QREs: 6% of current QREs.

Source: current Form 6765, Section B, and instructions. The ASC examples assume no energy-consortium or basic-research additions and no controlled-group adjustment.

Fictional example: you paid $100K to an outside developer for custom workflow integrations, and both the work and the contract qualify:

  • $100K × 65% (contract research factor) = $65K of QRE
  • First year with QREs (none in the prior three years): $65K × 6% = $3,900 federal credit
  • If your prior three years instead averaged $40K of QREs: base = 50% × $40K = $20K, so the credit is 14% × ($65K minus $20K) = $6,300

Two adjustments your CPA has to work through:

  • Section 280C. The credit requires an adjustment, either through your research expense treatment or by electing a reduced credit. Under the reduced-credit election, the credit is generally multiplied by 79% (100% minus the 21% corporate rate), so $3,900 becomes about $3,081.
  • Section 174 and 174A. How research costs are deducted depends on the tax year. Domestic research costs in 2022-2024 tax years were generally capitalized and amortized under Section 174, and domestic costs in tax years beginning after December 31, 2024 can generally be deducted under Section 174A, with an optional capitalization election and transition choices for older capitalized costs. Foreign research has different treatment. Your CPA needs to work out the year-specific treatment and how it interacts with Section 280C.

Some states offer their own research credits, each with its own rate, base and eligibility rules, and some states offer none. We have not verified current state rates for this page. Confirm your state's rules for the specific tax year before counting any state amount.

A qualified small business can elect to apply up to $500K/year of the credit against the employer share of payroll taxes instead of income tax. It qualifies only if gross receipts for the credit year are under $5M AND it had no gross receipts in any tax year before the five-tax-year period ending with the credit year. Controlled-group aggregation applies. Under Form 8974 instructions, up to $250K can offset employer Social Security per quarter; the remaining elected credit can offset employer Medicare. Unused credit carries forward, subject to the payroll liability calculation. This is not an automatic $250K/$250K split. The offset reduces payroll tax deposits; it is not an immediate refund. It can help a young, eligible company without taxable income. It does not help an established business with an older receipts history.

The four-part test in plain English

For an expense to qualify as QRE, the underlying activity must satisfy all four of these tests:

1. Permitted Purpose

The activity must be intended to develop or improve a business component, meaning a product, process, software, technique, formula, or invention. Custom internal software can be a "business component." That matters for service businesses, but internal-use software also faces the extra tests described below.

2. Technological in Nature

The activity must rely on principles of physical, biological, computer, or engineering science. Using computers, APIs or AI is not sufficient by itself; identify the computer-science or engineering principles used to resolve the uncertainty. Process automation that uses scripts, APIs, or AI can also rely on computer science. Passing this test does not settle the other three tests or the internal-use software rules.

3. Elimination of Uncertainty

At the start of the project, you must be uncertain about either the capability of developing the result, the appropriate method to develop it, or the appropriate design. If you knew exactly how to build it before you started, it doesn't qualify. If the capability, method or design was genuinely uncertain and you evaluated different approaches, libraries, models, prompts, or architectures to resolve it, this test may be met. Trying prompts until the output looks acceptable, without a technical question you were resolving, is a weak fact pattern.

4. Process of Experimentation

The activity must involve evaluation of one or more alternatives: testing, modeling, prototyping, iteration. Iterative development (write code, test, refactor, test again) can be a process of experimentation when you are evaluating alternatives to resolve the technical uncertainty and can show it. Routine debugging, configuring a known solution, and cosmetic changes generally are not. This test does not require a lab. It does require records.

Free benchmark review

See how your tax and cash plan benchmarks.

Start with a free conversation about your priorities. With agreed access to the relevant records, we compare your numbers with applicable benchmarks and identify what to review first.

Internal-use software faces extra tests

Some software is developed primarily for your own general and administrative functions, such as accounting, invoicing, HR, internal reporting and back-office workflow automation. That is internal-use software. Beyond the four-part test, it generally must also clear a high threshold of innovation under Treasury Regulation 1.41-4(c)(6):

  1. Innovative: success would produce a substantial and economically significant improvement, such as reduced cost or increased speed.
  2. Significant economic risk: you committed substantial resources with substantial uncertainty, because of technical risk, about recovering them within a reasonable period.
  3. Not commercially available: you could not buy software that does the job without modifications that would themselves meet these tests.

Classify by purpose, not tool brand. Software primarily serving accounting or internal administration generally faces the stricter standard. Software enabling customer interaction can have a non-internal or dual-function analysis; do not classify every Slack bot or dashboard solely from its name.

Contractor spend has its own conditions. The 65% contract research amount counts only where you bear the economic risk of the research and retain substantial rights to the results. If payment depends on the deliverable working, that portion can be payment for a result rather than for research. Your rights need not be exclusive; the developer can also retain rights to use the results. Have your preparer review the agreement for your right to the research results and the other contract-research conditions. Read the contract before you count the invoice. See Treasury Regulation 1.41-2(e) for the contract-research conditions.

Activity types to screen for service-business R&D

These activity types can qualify for service-business R&D credits when the tests above are met. None qualifies automatically:

Custom software development (back-office tools also face the internal-use software tests above):

  • Internal dashboards built in Retool, Airtable, custom React apps, or in-house tools
  • Custom integrations between QuickBooks, ServiceTitan, BuildOps, Salesforce, HubSpot, etc.
  • Workflow automation in tools like Zapier, n8n, Make, or custom Python scripts
  • Custom AI agents, prompts, RAG systems, fine-tuned models built for specific business processes
  • Internal mobile apps for field crews, technicians, sales teams

Process improvement with technical uncertainty:

  • Re-engineering job-costing methodology with new data sources
  • Building new estimating models using historical data
  • Designing custom QA processes with measurement and iteration
  • Implementing predictive maintenance algorithms

AI-specific implementation work:

  • Custom GPT/Claude/Gemini integrations beyond basic API calls
  • RAG pipelines built on company-specific data
  • Fine-tuned models or LoRA adapters
  • Voice AI integrations for call handling, dispatch, or scheduling
  • Computer vision systems for site monitoring, equipment tracking, or QA

What does NOT qualify:

  • Buying off-the-shelf software (the vendor already did the R&D)
  • Standard QuickBooks setup and bookkeeping
  • Marketing campaigns and copywriting (no technological uncertainty)
  • Hiring a virtual assistant
  • Customizing existing templates without iteration
  • Subscribing to ChatGPT and using it without custom integration

The general line: writing code, designing a model, or engineering a new system is a starting point, not proof. The work qualifies only if it meets the four-part test, the internal-use software tests where they apply, and, for contractor spend, the economic-risk and rights conditions.

The documentation problem (and how to solve it)

The R&D credit has a reputation for being audit-bait. We have no verified examination-rate data by credit size, so plan as if the claim will be examined. The IRS can ask for documentation that establishes:

  1. What you were trying to develop (project description, business component)
  2. What was uncertain at the start (the technical questions)
  3. How you experimented (iteration log, testing notes)
  4. Who did the work (employee time, contractor invoices)
  5. What you spent (payroll records, invoices)

The good news: much of this documentation may already exist in your project management tools. Slack threads, Linear/Jira tickets, GitHub commits, contractor invoices with line-item descriptions, and meeting notes from "let's try a different approach" conversations can serve as contemporaneous evidence when they tie to a specific business component and technical question.

The work in claiming the credit is mostly in organizing existing artifacts into a research narrative for each project. As a planning assumption, not a measured average, budget roughly 8-15 hours of specialist or EA time for a $5M service business with 2-4 candidate projects. Poor records push that higher.

How to actually file

The mechanics:

Form 6765, "Credit for Increasing Research Activities," filed with your tax return. If you meet both qualified small business conditions, you can make the payroll tax offset election on Form 6765 with a timely filed return. Then file Form 8974 with Form 941, starting with the first quarter that begins after you file that return.

Election deadline: the payroll tax offset election must be made on or before the due date of the originally filed income tax return, including extensions. A return or amendment filed after that deadline generally cannot add the election. An amended return can still claim an income-tax research credit for an open year when its requirements are met. Ask your preparer about any relief applicable to your facts. The Form 6765 instructions also prohibit an election if one was made for five or more preceding tax years.

A planning trigger: if candidate QREs exceed $50K or the software classification is complex, obtain a scoped review from a qualified tax adviser. This is a decision threshold, not a measured break-even point. Fee arrangements vary. Treat any percentage-of-credit or flat-fee figure you hear as a quote to compare, not a benchmark we have measured. Ask how the fee is set, and have the adviser explain which professional fee rules apply to your filing. Compare any fee against the credit computed at the correct 6% or 14% rate, after Section 280C.

Three questions to ask your tax adviser

1. Was the activity eligible, rather than simply expensive?

Ask the adviser to separate technical experimentation from routine implementation. Cost alone, a custom codebase or a large number of prompts does not establish eligibility.

2. Does the documentation describe the uncertainty at the start?

A useful project file identifies the business component, technical question, alternatives tested, results and qualifying staff time. Reconstructing a story after the project is weaker than dated records. Ask which activities and invoices the adviser excluded, too.

3. Is the payroll election available to this business?

An eligible credit does not automatically qualify for the payroll offset. Confirm receipts history, predecessor and controlled-group treatment, prior elections, the filing deadline and employer tax liability before counting that cash benefit.

What to do in the next 30 days

If you've spent meaningful money on custom software, AI implementation, or technical process work in 2024 or 2025, here is the playbook:

Week 1: List all custom development projects from the past 24 months with: project name, what you were trying to build, what was unclear at the start, who worked on it, and approximate spend.

Week 2: Match each project against the four-part test. Be honest. Back-office software must also pass the internal-use software tests, and contractor spend must meet the economic-risk and rights conditions. Marketing and routine operational projects usually don't qualify.

Week 3: Calculate estimated QRE: qualifying contractor invoices × 65% + wages allocated to qualifying activities. Then check whether you had QREs in each of the prior three tax years. If any year was zero, use 6% of current QRE. Otherwise use 14% of QRE above half the prior three-year average.

Week 4: Bring this to your CPA or to an EA experienced in R&D claims. If your CPA's first response is "we don't usually do those," find a second opinion. Amended returns can generally still claim the credit for open years, subject to the refund claim deadline, generally the later of three years after filing or two years after paying, with exceptions, but generally cannot add the payroll offset election after the original return's extended due date. Refund claims need their own supporting detail. Amending a 2022-2024 return may also involve Section 174 adjustments, so ask your preparer.

The tax code rewards risk-taking, experimentation, and innovation. Section 41 is one of the few places where it does so explicitly. Some service businesses leave the credit on the table because nobody checked whether it applied. For others, the honest answer after the tests is that it doesn't. The point is to check.

Check your numbers with Find Your Gap or book a free 30-min audit. We'll review your custom development spend and help you decide whether a credit study is worth the cost. Eligibility and the final computation belong with your CPA or EA.

Share

Get the next one

Want next week's benchmark in your inbox?

One email a week. Real numbers from 2,200+ contractors in the research universe. No fluff. Unsubscribe anytime.

Kenneth May

About the author

Kenneth May

Partner, Tax Strategy

Enrolled Agent and tax planning specialist with 45+ years of practice. Owner of B A Services Inc. (Standish, Michigan), focused on tax strategy for medical, legal, real estate, and e-commerce businesses in the $1M-$5M revenue band. As an EA, federally licensed to represent taxpayers before the IRS in all 50 states. Specializes in entity structuring, strategic tax deferral, R&D and other under-claimed credits, and retirement-plan design for owner-operators. Brings the tax-strategy lens to Level's content, the part most fractional CFOs ignore.

LinkedIn

See how your tax and cash plan benchmarks.

Start with a free conversation about your priorities. With agreed access to the relevant records, we compare your numbers with applicable benchmarks and identify what to review first.

2,200+ businesses benchmarked$13.25B in revenue analyzedWeekly action cadence

No credit card. Start with a 15-min call. We only follow up if we can actually help.

No commitment. Real numbers, not generic advice.