
Key takeaways
- UK businesses can claim R&D tax relief for software development work contracted to an external agency.
- The 'contracted out' rules determine whether the company paying for the R&D or the company performing it makes the claim.
- Careful planning and documentation from project inception are crucial for a successful HMRC R&D claim.
- A specialist R&D tax adviser must sign off your claim, working alongside your software delivery partner.
- Understanding the 'scientific or technological uncertainty' is key to justifying software R&D expenditure to HMRC.
Understanding Contracted Out Software R&D
Many UK businesses innovate by commissioning custom software from expert development agencies. When this work involves resolving scientific or technological uncertainties, it may qualify for R&D tax relief. HMRC's rules for 'contracted out R&D tax relief contracted out software' are specific, focusing on who initiated the R&D, bears the risk, and ultimately owns the intellectual property.
The core distinction lies in whether your company is 'contracting out' R&D to an agency or 'contracting to do' R&D for a client. As the client commissioning the software, your company is generally the one making the claim for the R&D expenditure incurred. This hinges on your company being the one seeking an advance in science or technology, rather than merely acquiring a solution to a known problem.
From April 2024, the merged R&D scheme streamlines the previous SME and RDEC regimes, though specific provisions for R&D intensive SMEs persist. Understanding this framework is essential for accurately assessing your eligibility and potential claim value when engaging a software development partner for innovative projects.
Eligibility: Who Can Claim What?
HMRC’s guidance, particularly within the Corporate Intangibles Research and Development Manual (CIRD), clarifies the intricacies of contracted-out R&D. For your software project to qualify, your company must be the one identifying the scientific or technological uncertainty and seeking to resolve it. The development agency, like Techsleight Labs, performs the R&D on your behalf.
The contract between your company and the software agency is paramount. It should clearly indicate that your business is the one bearing the financial risk if the R&D is unsuccessful and that you retain the rights to any intellectual property arising from the R&D activities. Vague contract terms can lead to challenges regarding who is the 'contractor' and who is the 'customer' for R&D purposes.
For non-R&D intensive SMEs, qualifying contracted-out expenditure is treated under the merged scheme. R&D intensive SMEs (spending 30% or more of total expenditure on R&D) can benefit from a higher payable credit rate, making careful categorisation of your business crucial for maximising relief. This ensures that genuine innovation, even when delivered externally, receives appropriate support.
- Your company identifies the scientific or technological uncertainty.
- Your company bears the financial risk of the R&D project.
- Your company retains the IP rights to the R&D outcomes.
- The contract specifies the R&D nature of the work.

Crafting a Robust Technical Narrative
A successful R&D claim for software relies heavily on a clear, compelling technical narrative that demonstrates 'scientific or technological uncertainty' and an 'advance in science or technology,' as defined in CTA 2009. This isn't about routine coding; it's about tackling problems where the solution isn't readily deducible by a competent professional.
On a recent UK retail build for a new inventory management system, we meticulously documented the trials of integrating disparate legacy warehouse systems using novel API approaches. This detailed log, including dead ends, refactored solutions, and the rationale behind each technical decision, formed a critical part of the client's successful R&D claim, demonstrating genuine technological uncertainty rather than routine development.
Your narrative should detail the specific challenges faced, the methodologies attempted, the failures encountered, and how these efforts contributed to an overall advance. It needs to articulate why the solution was not obvious and how your project pushed the boundaries of what was known or achievable in that specific field of software engineering.
- Identify specific technical challenges and uncertainties.
- Detail the systematic investigation and experimentation.
- Explain failed approaches and iterative development.
- Demonstrate how an advance in technology was sought.
Worked Example: Software R&D Relief Calculation
Let's consider a UK logistics company, an R&D intensive SME, commissioning Techsleight Labs to develop a custom AI-assisted platform for route optimisation. This project involves significant technological uncertainty in developing novel algorithms for dynamic routing under real-time constraints, qualifying for R&D tax relief under the merged scheme's intensive SME provisions.
The total qualifying expenditure for this project, including our development fees (staff costs, software licences, and consumable materials directly attributable to the R&D), amounts to £150,000. As an R&D intensive SME, the company can enhance this expenditure by 86%, and then claim a payable tax credit of 14.5% on the enhanced figure.
This example illustrates how a substantial portion of your innovative software development costs can be reclaimed, significantly reducing the net investment required for cutting-edge projects. It underscores the financial incentive for UK businesses to innovate and work with expert development partners.
- Qualifying Expenditure: £150,000
- Enhancement Rate (R&D Intensive SME): 86%
- Enhanced Expenditure: £150,000 x 186% = £279,000
- Payable Tax Credit Rate: 14.5%
- Total R&D Tax Relief: £279,000 x 14.5% = £40,455
Essential Evidence and Record Keeping
Effective record keeping is the bedrock of a successful R&D tax relief claim. It is far easier to document the R&D activities as they happen than to reconstruct them retrospectively. This means integrating claim requirements into your project management from day one, ensuring that all relevant data is captured systematically.
A client came to us mid-project with an urgent need to claim R&D tax relief for their supply chain optimisation platform. While we could help them reconstruct some technical narratives, the lack of contemporaneous sprint reports, design decision logs, and time tracking against specific R&D activities made evidencing the 'uncertainty' and 'advance' much harder than if we had planned for it from the start. This led to a more conservative claim than initially hoped.
Key documents include project plans outlining objectives and technical challenges, regular sprint reports detailing progress and obstacles, technical design documents, meeting minutes where technical problems were discussed, and detailed time sheets linking engineer effort to specific R&D activities. Robust evidence directly supports the 'what,' 'why,' and 'how' of your R&D.
- Project initiation documents detailing R&D objectives.
- Technical design specifications and architecture diagrams.
- Meeting notes discussing technical challenges and solutions.
- Time tracking records for R&D-focused developer hours.
- Version control logs and code commit messages.

When Contracted-Out R&D Is Not the Right Choice
While R&D tax relief offers significant financial benefits, it's not universally applicable. If your software project involves routine development, utilising established technologies without facing genuine scientific or technological uncertainty, it is unlikely to qualify. Simply implementing a common feature or customising an off-the-shelf product rarely meets HMRC's criteria.
The process of preparing an R&D claim incurs costs, both in terms of internal resource time and fees for specialist R&D tax advisers. For smaller projects with minimal qualifying expenditure, these costs might outweigh the potential relief, making the exercise less financially viable. Always weigh the administrative burden against the expected benefit.
Furthermore, if your company is already receiving other forms of state aid, such as certain Innovate UK grants, for the same project, the R&D tax relief claim may be affected. Combining different funding streams requires careful navigation to avoid falling foul of state aid rules, often leading to adjustments in the R&D claim calculation.
- Project involves only routine development.
- No genuine scientific or technological uncertainty exists.
- Cost of claim preparation outweighs potential relief.
- Other state aid funding is already in place for the same activities.
Partnering for a Successful Claim
Navigating the complexities of R&D tax relief for contracted-out software requires a coordinated approach. Techsleight Labs works alongside your chosen R&D tax adviser, ensuring that the technical aspects of your software build are meticulously documented to support a robust claim. Our on-shore UK engineers understand the nuances of evidencing innovation.
By integrating R&D claim requirements into our project planning and delivery processes from the outset, we help you capture the essential evidence as your project progresses. This proactive approach minimises the effort of retrospective reconstruction and strengthens the credibility of your submission to HMRC. We focus on 'Built on Experience, Expertise, Authority & Trust' in our delivery.
Engage with us early in your project lifecycle. Encourage the reader to plan the build with Techsleight Labs so the record keeping supports their claim from day one. Our expertise in custom software development, web applications, and AI-assisted tooling can be structured to maximise your R&D potential, ensuring your innovation is financially recognised.
FAQ
What is 'contracted out' R&D for software?
It refers to a UK business paying an external agency, like Techsleight Labs, to carry out R&D activities on their behalf. The client company typically initiates the R&D, bears the risk, and seeks the technological advance.
Can I claim R&D tax relief if I hire a UK development team?
Yes, if the work performed by your hired UK development team involves resolving scientific or technological uncertainties to achieve an advance in science or technology, your company can claim R&D tax relief.
What documentation is needed for a software R&D claim?
Key documentation includes project plans outlining technical challenges, design documents, sprint reports, meeting minutes of technical discussions, and detailed time sheets linking developer effort to R&D activities.
How does the merged R&D scheme affect contracted out software claims?
The merged scheme, effective from April 2024, generally treats contracted-out R&D expenditure similarly, though R&D intensive SMEs may benefit from a higher payable credit rate, making eligibility assessment crucial.
Do I need an R&D tax adviser for my software claim?
While not legally mandatory, engaging a qualified R&D tax adviser is highly recommended. They ensure compliance with HMRC guidelines, maximise eligible expenditure, and manage the submission process, often working with your development partner.
Ready to build in the UK?
Talk to a senior software team.
Share your roadmap, current stack, and timeline. We will help you choose the right developer, team, or managed project model.
Get a free quote in 24h