Skip to content
SaaS agency software developer working on bespoke code in a London office, with financial documents visible on a second monitor

Tax and Compliance

R&D Tax Credits for SaaS Agencies Building Bespoke Software

7 min read · ·

Photo: Markus Winkler / Pexels

JW

Editorial Lead · Published 16 May 2026 · Updated 17 May 2026

Editorial content from the Agency Founder Finance team. For decisions specific to your agency, book a call.

Key takeaways

  • SaaS agencies building bespoke software can claim R&D tax credits if the work involved technical uncertainty not solvable by standard industry practice.
  • Qualifying R&D includes developing novel algorithms, custom integrations, or data processing solutions with no off-the-shelf alternative.
  • Routine web development using established methods, such as building Shopify stores or integrating Stripe, does not qualify for R&D tax credits.
  • HMRC's R&D test requires a project to seek an advance in science or technology by resolving scientific or technological uncertainty.
  • SME R&D relief and the RDEC scheme are the two main R&D tax credit routes, with eligibility depending on your agency's size and circumstances.

If your SaaS agency builds bespoke software for clients, you might be leaving thousands of pounds on the table. R&D tax credits aren't just for pharmaceutical companies or hardware engineers. They apply to software development too, provided the work involves technical uncertainty.

The challenge is that most agency founders don't think their work qualifies. They assume "R&D" means lab coats and petri dishes. In reality, HMRC's definition covers projects where you had to overcome technical challenges that weren't solvable by standard industry practice. If you've ever built a custom integration, developed a novel algorithm, or solved a data processing problem that had no off-the-shelf solution, you've probably done R&D.

This article covers what qualifies for R&D tax credits for SaaS agency work, what doesn't, and how to prepare a claim that HMRC will accept without a fight.

What Actually Counts as R&D in Software

HMRC uses a specific test. To qualify, your project must have sought an advance in science or technology by resolving scientific or technological uncertainty. For software, that means you were trying to do something that wasn't already known to be possible within the industry.

That uncertainty can take several forms:

  • Technical feasibility. You didn't know if a particular approach would work at all.
  • Performance constraints. You needed to process data at a scale or speed that existing methods couldn't handle.
  • Integration complexity. You had to connect systems in ways that had no documented precedent.
  • Algorithm development. You created a new mathematical model or method to solve a specific problem.

The key is that you couldn't just look up the answer. If you found a Stack Overflow post that solved your exact problem, it's not R&D. If you spent weeks testing different approaches because no standard solution existed, it probably is.

Examples That Qualify

Let me give you real scenarios from agencies we've worked with:

A 15-person digital agency in Bristol built a custom analytics platform for a retail client. The client needed to combine sales data from 12 different POS systems, each with different data formats and update frequencies. The agency had to develop a novel data normalisation layer and a real-time reconciliation engine. No off-the-shelf tool could handle the combination of data volume, format inconsistency, and latency requirements. That's R&D.

A Manchester-based SaaS agency developed a machine learning model to predict churn for a subscription business. The standard models didn't work because the client's customer base had unusual behaviour patterns, long sales cycles, irregular usage, and multiple decision-makers. The agency had to experiment with different feature engineering approaches and model architectures. That's R&D.

A web design agency in Shoreditch built a custom CMS for a publisher that needed to serve 50,000 concurrent users during live events. Standard WordPress couldn't handle the load, and off-the-shelf caching solutions didn't work with the publisher's real-time content updates. The agency built a custom caching layer and database architecture. That's R&D.

Examples That Don't Qualify

Not everything counts. Standard web development, even if complex, doesn't qualify if you're using established methods. Building a Shopify store with custom plugins, setting up WordPress with standard themes, or integrating Stripe for payments, none of that is R&D. It's skilled work, but it's not pushing the boundaries of what's technically known.

Similarly, routine software maintenance, bug fixes, and performance optimisation using standard techniques don't qualify. If you're applying known solutions to known problems, HMRC won't accept it.

The Two R&D Schemes and How They Apply to SaaS Agencies

There are two main schemes, and which one you use depends on your company's size and circumstances.

SME R&D Relief

If your agency has fewer than 500 employees and either turnover under €100 million or a balance sheet under €86 million, you're likely an SME for R&D purposes. The SME scheme gives you:

  • An enhanced deduction of 186% on qualifying R&D expenditure (for accounting periods starting on or after 1 April 2023). That means for every £100 you spend on qualifying R&D, you can deduct £186 from your taxable profits.
  • If you're loss-making, you can surrender those losses for a cash payment, up to 14.5% of the surrenderable loss for R&D intensive companies, or 10% for others.

For a profitable agency spending £50,000 on qualifying R&D, the enhanced deduction reduces your taxable profit by £93,000. At 19% corporation tax, that's a tax saving of £17,670. If you're loss-making, the cash credit can be even more valuable.

RDEC (Research and Development Expenditure Credit)

If your agency is too large for the SME scheme, or if you're claiming for subsidised or contracted R&D, you'll use the RDEC scheme. RDEC gives you a taxable credit of 20% of qualifying expenditure. After tax, that works out at around 15-16% net benefit.

Most SaaS agencies will use the SME scheme. But if you've received grant funding for your R&D work, or if you're a large group, RDEC may apply.

What Costs Can You Include?

For a SaaS agency, the main qualifying costs are:

Want this checked against your specific situation?

Leave your details and a one-line summary. An agency finance specialist will reply within 24 hours, with no obligation.

Free interactive tool

Free Agency tax compliance and VAT tool

Compare VAT schemes for your agency

Our interactive tool is built for a larger screen. Tell us your agency numbers and an agency finance specialist will send your figure and the sensible next step, with no obligation.

Get the VAT scheme comparison model

Standard versus Flat Rate side by side, with the limited-cost-trader test built in. Agencies are nearly always limited-cost traders (16.5% rate on gross turnover), so the standard scheme usually wins after reclaiming input VAT.

Instant access on this page. No spam.

  • Staff costs. Salaries, employer NI, and pension contributions for employees directly involved in R&D. That includes developers, architects, testers, and project managers who spend time on qualifying projects.
  • Externally provided workers. Contractors and freelancers working on R&D projects. You can include 65% of the payments made to them.
  • Consumables. Software licenses, cloud hosting costs, and data costs directly used in the R&D. If you're running experiments on AWS or Azure, those costs can qualify.
  • Subcontracted R&D. If you pay another company to do R&D work for you, you can include 65% of the cost.

You cannot include overheads, marketing costs, or general business expenses. And you cannot include the cost of creating the final product if that work is routine development, not R&D.

The Common Mistakes We See

Most rejected R&D claims from SaaS agencies fail for the same reasons. Here are the three biggest ones.

1. Describing the Project, Not the Uncertainty

HMRC doesn't care that you built a great platform. They care about what you didn't know how to do at the start. A claim that says "we developed a custom CRM for a client" will be rejected. A claim that says "we had to develop a novel method for synchronising data across three incompatible legacy systems in real-time, because no existing solution could handle the data volume and latency requirements" has a much better chance.

Your technical narrative must describe the uncertainty, what you tried, what failed, and how you eventually succeeded. HMRC wants to see the struggle, not just the result.

2. Including Too Much Routine Work

If your claim includes every hour your developers worked, HMRC will push back. You need to separate qualifying R&D from routine development. If a developer spent 60% of their time on a qualifying project and 40% on standard maintenance, you can only include the 60%.

Time tracking is essential. If you don't have detailed timesheets, you'll struggle to defend your claim.

3. Not Identifying the Competent Professional

HMRC uses the "competent professional" test. Would a competent software developer with the same knowledge and experience have known how to solve the problem? If yes, it's not R&D. If no, it probably is.

This is where many agencies go wrong. They describe a problem that any senior developer could have solved with standard techniques. The problem needs to be genuinely novel, at least for the context.

How to Prepare a Claim That Will Survive HMRC Scrutiny

HMRC has increased its scrutiny of R&D claims significantly in the last two years. Random compliance checks are up, and the number of claims being rejected has risen sharply. If you're going to claim, you need to do it properly.

Here's what we recommend to our clients at Agency Founder Finance:

Document the uncertainty at the start. Before you begin a project, write down what you don't know. What technical challenges do you expect? What approaches are you planning to test? What would count as success? This contemporaneous evidence is far more valuable than a retrospective narrative.

Track time by project. Use your accounting software, Xero, QuickBooks, FreeAgent, whatever you use, to tag time to specific R&D projects. If you use a time tracking tool like Toggl or Harvest, tag qualifying hours there too.

Keep records of failed approaches. HMRC wants to see that you tried things that didn't work. Keep notes, emails, and code commits that show the iterative process. A claim that only describes the successful outcome looks suspicious.

Work with an accountant who knows R&D. This is not a DIY area. The technical narrative needs to be written by someone who understands both the technology and HMRC's requirements. Working exclusively with agency founders, we see claims that would be straightforward but are rejected because the narrative is wrong.

When to Claim and When Not To

Not every SaaS agency should claim R&D tax credits. If your work is genuinely routine, building standard websites, integrating standard APIs, applying known techniques, then claiming would be a mistake. HMRC will reject it, and you'll waste time and money on the process.

But if you're building bespoke software that pushes technical boundaries, the R&D tax credits for SaaS agency work can be substantial. A £30,000 claim for a profitable agency saves over £10,000 in corporation tax. For a loss-making agency, the cash credit can be a lifeline.

The threshold is lower than most founders think. You don't need to be inventing a new programming language or building a quantum computer. You just need to be working on problems that didn't have known solutions at the time.

If you're unsure whether your work qualifies, talk to an accountant who specialises in R&D claims. Most will give you an initial assessment for free. And if they tell you it doesn't qualify, that's valuable information too, it saves you from a rejected claim and potential penalties.

For more on how R&D fits into your overall tax strategy, read our guide to tax and compliance for agency founders. If you're considering restructuring your agency to optimise for R&D claims, our incorporation and structure articles cover holding companies and group structures that can help.

Frequently asked questions

What's the minimum spend on R&D for a SaaS agency to make a claim worthwhile?
There's no legal minimum, but practically, we'd suggest not claiming for less than £10,000 in qualifying costs. The administrative effort and the risk of HMRC scrutiny mean that smaller claims often aren't worth the hassle. For a profitable agency, £10,000 in qualifying spend saves roughly £3,500 in corporation tax. That's meaningful, but you'll spend time preparing the claim. If your qualifying spend is under £5,000, it's probably not worth it unless it's part of a larger claim across multiple projects.
Can I claim R&D tax credits if my agency is loss-making?
Yes, and it can be more valuable than for profitable agencies. Under the SME scheme, loss-making companies can surrender their R&D losses for a cash payment. For R&D intensive companies (where qualifying R&D spend is 30% or more of total costs), you can get up to 14.5% of the surrenderable loss as cash. For other companies, it's 10%. That means a £50,000 qualifying spend could generate £7,250 in cash. The cash is tax-free and can be a significant boost for early-stage SaaS agencies that are investing heavily in development.
How far back can I claim R&D tax credits for my SaaS agency?
You have two years from the end of the accounting period to submit a claim. For example, if your accounting year ends on 31 March 2024, you have until 31 March 2026 to file the claim. You can also amend a previous year's corporation tax return to include an R&D claim, provided the amendment is made within 12 months of the filing deadline. If you've never claimed before, you can go back up to two accounting periods. After that, the claims are time-barred. So if you've been doing qualifying work for years, act now before you lose the ability to claim.
Will claiming R&D tax credits increase my chances of an HMRC investigation?
It can, but the risk is manageable if your claim is properly prepared. HMRC has increased its compliance activity on R&D claims significantly since 2023. Random checks are more common, and claims over £50,000 are automatically reviewed. The key is to have a well-documented technical narrative and supporting evidence. If your claim is based on solid records and genuine technical uncertainty, an HMRC review should be straightforward. If your claim is vague or includes routine work, you're inviting problems. Work with an accountant who understands R&D to minimise the risk.

Need specialist accounting for your agency?

We work exclusively with agency founders. Book a free call to talk through your tax position, salary structure, or any finance question. No jargon, no hard sell.

We respond within 24 hours and store your details securely.

Compare VAT schemes for your agency