What founders should know about the R&D tax credit

The R&D tax credit (formally the credit for increasing research activities on Form 6765) is a federal incentive tied to qualified research expenses, not a prize for shipping product. IRS materials describe qualified research through a multi-part test that includes technological information, a business component, and a process of experimentation, applied per business component. Form 6765 is how taxpayers figure and claim the credit, including elections such as the reduced credit under section 280C. This post is founder orientation on awareness, evidence, and operating habits. It is not tax advice, and it does not say whether your company qualifies. Confirm eligibility, calculations, and filing with a CPA who works research credits.

What the R&D tax credit is asking you to prove

Awareness starts with proof, not with a spreadsheet of hoped-for refund dollars. Your advisor will ask which projects tried to resolve technical uncertainty, which expenses attach to those projects, and how you tracked them contemporaneously.

Illustrative founder summary (composite only): "We keep a quarterly project list, tag engineering time to those projects, store vendor invoices for cloud experiments, and hand the pack to our CPA each April and October."

Name an internal owner who is not the CEO if the CEO will not open the folder monthly. Credits stall when ownership is "everyone." Put the owner's name on the components table header and on the recurring calendar invite.

Do not treat "we write software" as automatic qualification. The instructions for Form 6765 walk through qualified research concepts and qualified research expense categories such as in-house wages for qualified services, supplies, certain computer rentals, and contract research (often subject to percentage limits). Your CPA maps those words onto your facts.

Also separate section 174 research or experimental expenditure capitalization and amortization topics from the section 41 credit conversation. They interact in real returns, but founders who mash them into one Slack thread confuse both. Ask the CPA which pack supports which form.

Separate hope from a business-component list

Build a living list of business components: products, processes, software, techniques, formulas, or inventions you are trying to improve. The Form 6765 instructions emphasize applying the research tests separately to each business component.

Illustrative rule (composite only): if you cannot fill Uncertainty and Experimentation in one sitting, the row is not ready for a credit discussion.

Keep marketing launches and pure content work off this list unless counsel says otherwise. Inflating the list with every sprint title wastes CPA hours.

When a project ships and research ends, freeze the row with an end date. Continuing to tag routine maintenance to a closed component pollutes wage exports. Illustrative freeze (composite only): "Checkout latency v3 research ended 31 March; April tags move to sustainment unless a new uncertainty opens."

Know the expense types advisors will ask about

Qualified research expenses discussed in Form 6765 materials commonly include wages for qualified services, supplies used in qualified research, certain amounts for computer use, and contract research payments subject to statutory percentages (for example, many contract research amounts are included at 65 percent, with different percentages in specified cases such as certain consortium or energy research payments). Do not memorize percentages from a blog when your return is due; read the current instructions with your CPA.

Illustrative wage capture (composite only): engineers log hours to "Checkout latency v3" in the task system; the finance owner exports hours monthly and stores them beside payroll registers.

Supervisors should spot-check that titles in payroll match people who actually performed qualified services. Paying a salesperson from the same register does not make sales time a research wage.

Illustrative supply or cloud capture (composite only): a temporary GPU cluster used only for model experiments is categorized under a dedicated Expenses category such as "R&D cloud experiments," with the project name in the description.

Contract research needs the agreement, statements of work, and invoices. If a vendor does mixed support and research, ask the CPA how to allocate before you claim the whole bill.

Foreign research rules can limit what counts. Do not assume offshore contractor invoices automatically qualify because the work felt innovative. Flag location of performance for the CPA on every research vendor.

Capture evidence while the work is happening

Credit claims fail in practice when evidence is rebuilt from memory in April. Run a light monthly capture:

1. Update the business-component table.
2. Export time tagged to those components.
3. Export Expenses filtered to R&D categories with receipts attached.
4. File contractor invoices and SOWs in the same folder.
5. Note abandoned experiments (failures still matter for the story of uncertainty).

Illustrative folder layout (composite only): /finance/rd-credit/2026-q1/ with components.csv, wages-export.csv, expenses-export.csv, and contracts/.

At quarter close, freeze the folder: no silent edits after the CPA receives the pack unless you send a dated addendum. Version fights create indefensible files.

In Expenses, use stable categories and merchants so exports do not need a scavenger hunt. Scanning receipts at the moment of purchase beats reconstructing card statements later.

Recurring Expenses help for subscriptions that support experiments, but still require project tags in the description. A bare "AWS" label without a component name forces the CPA to guess.

Use planning tools without pretending they file Form 6765

Financial Planner can hold Notes about assumptions and Model Inputs for costs, including lines you treat as research spend in scenarios. That helps cash planning beside burn rate. It does not compute the research credit or replace Form 6765.

Illustrative planning habit (composite only): a Notes tab bullet states "Q2 research cloud budget 12k tagged to ranking experiments; CPA to review for QRE treatment." The number feeds runway scenarios; the CPA decides credit treatment.

Keep investor slides honest. Saying "we will offset payroll with the R&D tax credit" before a CPA signs off on eligibility is a forecast, not a fact. Label it as an assumption.

If the credit is material to runway, put a low and base case in Financial Planner Notes rather than a single heroic number. Then refresh after the CPA's draft calculation, not after a blog estimate.

Watch filing mechanics your CPA will own

Form 6765 is filed with the return to figure and claim the credit for increasing research activities. Instructions discuss regular and alternative simplified credit approaches, elections such as the reduced credit under section 280C, and, for many filers in later years, business-component detail in Section G. For tax years beginning before 2026, Section G is described as optional for all filers in the December 2025 instructions; for tax years beginning after 2025, Section G is generally required unless an exception in those instructions applies (including certain qualified small business payroll-tax credit claimants and certain small-QRE original-return filers). Amended-return claim rules also appear in the instructions. Your CPA chooses methods and attachments.

Illustrative calendar hold (composite only): eight weeks before the return due date, "R&D pack freeze" so the CPA is not waiting on missing invoices.

If you extend the return, extend the freeze reminder too. An extension is not permission to keep inventing documentation.

Payroll-tax offset options for certain qualified small businesses exist in the statute and form instructions. Treat them as CPA-led elections, not a self-serve toggle inside your ops tools.

When instructions change year to year, especially around business-component reporting in Section G, re-read the revision your CPA cites. Do not rely on a prior-year checklist printed from someone else's engagement.

Review the evidence pack each quarter

Thirty to forty-five minutes with the technical lead and finance owner:

Illustrative outcome sentence (composite only): "Two components closed; one new ranking experiment opened; cloud category clean; contractor SOW updated."

Archive the sentence in the same quarterly folder. Twelve sentences make a year of diligence answers without rewriting history from Slack.

The R&D tax credit rewards documented qualified research, not optimism. Founders who keep a boring evidence pack spend CPA time on calculation, not archaeology.

Share the quarterly outcome sentence with whoever owns payroll and whoever owns engineering management. Credits die in the gaps between those teams when wage tags and project names diverge for a full year.

State tax research credits, if any, are separate regimes. Keep a second note titled by state only after the CPA says a state credit is in scope. Do not assume federal documentation automatically satisfies a state form. Ask for a one-line yes or no from the CPA before you open a state folder and before you promise state credits in a board deck or hiring plan in board materials.