5 common projects that feel innovative but usually don’t qualify for R&D
Which of your recent projects involved real technical uncertainty, and which were commercially challenging but technically straightforward?
Some of the most commercially exciting projects don’t qualify for R&D tax relief.
And that’s completely fine.
One of the biggest risks in R&D claims is assuming that “innovative” automatically means “qualifying”.
In reality, many impressive, high-value projects fall outside the tax definition of R&D because they don’t involve resolving technological uncertainty.
Here are examples that often feel like R&D, but usually aren’t:
1. Implementing off-the-shelf software
Deploying a new ERP, CRM, or production system can be transformative.
But if the system works as designed and is configured using documented functionality, it’s unlikely to qualify, even if the rollout is complex.
2. Building a website or standard app
Creating a new digital platform may be new to your business.
But if it uses established frameworks, known integrations, and common development practices, it typically doesn’t meet the “advance in technology” test.
3. Scaling proven processes
Increasing output using established techniques, even at significant cost, does not automatically create technological uncertainty.
Operational complexity ≠ R&D.
4. Customisation for a specific client
Delivering bespoke solutions may involve skill and expertise.
But if you are applying known techniques to meet client requirements, rather than overcoming technological limits, it may not qualify.
5. Commercial reformulation without technical barriers
Changing ingredients, materials, or specifications to improve margin or meet market demand is not R&D unless genuine technical uncertainty exists that required experimentation to resolve.
This doesn’t mean these projects lack value.
It means that for R&D tax purposes, the test is very specific:
- Was there a technological limitation that competent professionals could not readily overcome?
- Did resolving it require experimentation or iterative development?
If not, it may be innovation, just not qualifying R&D.
Understanding that boundary is what protects businesses from compliance issues.
Pause for thought
Looking at your recent projects:
- Which were commercially challenging, but technically straightforward?
- Which genuinely required your technical team to “figure it out” through testing and iteration?
- Are you distinguishing between operational difficulty and technological uncertainty?
In today’s compliance environment, clarity on this distinction is what separates robust claims from risky ones.
