How to claim small-scale R&D tax relief for creative agencies without hiring a specialist

I remember the first time a creative agency client asked me whether their work could qualify for R&D tax relief. They were a small team producing interactive campaigns, bespoke web apps and motion graphics — not the sort of business people picture when they think “R&D”. After I dug in, I realised how many creative projects can legitimately meet HMRC’s tests if you frame and document them correctly. You don’t need to hire an expensive specialist to get started — you just need the right approach, evidence and a clear claim that ties technical uncertainty to eligible costs.

What counts as R&D for creative agencies?

HMRC’s R&D definition focuses on projects that seek to achieve an advance in science or technology, or resolve scientific or technological uncertainty. For creative agencies this often means:

• developing bespoke interactive platforms or web apps with novel technical challenges (integration, performance, data handling, complex algorithms);
• creating new visual effects, rendering techniques or animation pipelines that required technical problem-solving;
• building custom tooling, plugins or automation to solve workflow problems; or
• experimenting with emerging technologies (AR/VR, real‑time engines like Unreal/Unity, advanced machine learning applied to creative outputs) where the outcome wasn’t known in advance.

Creative thinking alone is not enough — the key is a technological or scientific uncertainty. If your team had to test, experiment and iterate because there wasn’t a clear, competent practise to follow, that’s often where R&D sits.

What costs you can include (and what to avoid)

In practice, the main cost categories I help clients capture are:

• Staff costs — salaries, employers’ NIC and pension contributions for the people directly involved. Record the time spent on the R&D tasks (timesheets or project management logs work).
• Subcontractors — payments to third-party developers or specialists you’ve hired to carry out R&D work. Note: payments to connected parties may be treated differently, so document relationships.
• Software and cloud costs — software licences and cloud hosting or compute used directly for the R&D work (e.g. GPU compute for rendering or model training).
• Consumables and prototypes — small hardware or materials bought to test ideas (e.g. sensors, VR kits).
• Externally provided workers — agencies or contractors supplied through intermediaries in some cases (treatment can be complex; document contracts).

What you should generally avoid including: normal commercial development where there was no technical uncertainty, marketing costs, routine design work without technical innovation, client project management costs not directly tied to the technical experiments, and capital expenditure on physical assets (unless consumable/used directly in R&D).

Practical step‑by‑step: how I put a claim together

Here’s the process I use with clients — it’s straightforward and repeatable.

• 1. Identify candidate projects. Walk through the last 12–24 months of work with your creative and technical leads. Look for projects where the team encountered unknowns: new techniques, performance ceilings, integration problems, or where multiple approaches were trialled and discarded.
• 2. Collect technical narratives. For each project, write a one‑page technical narrative describing: the business objective, the technical uncertainty, why the uncertainty couldn’t be solved by competent professionals, the approaches tried, experiments run and the outcome. Use plain English but include technical detail — names of libraries, engines, architectures and the problems they posed.
• 3. Map costs to projects. Allocate staff time, contractor invoices, software and cloud bills to the relevant project. If someone split their time between R&D and routine work, apportion their salary by hours or reasonable estimates supported by timesheets.
• 4. Assemble evidence. Keep commits, test logs, prototypes, meeting minutes, emails discussing technical issues, cloud logs, screenshots and invoices. HMRC looks for contemporaneous evidence showing experiments and decision points.
• 5. Prepare the claim figures and a short report. You can draft the R&D report yourself — it doesn’t need fancy language. Include the technical narratives, a cost breakdown and a summary statement of why each project meets HMRC criteria.
• 6. File with your CT600. The R&D claim is included in your company tax return (CT600). If you’re loss-making, you may be able to surrender qualifying losses for a payable credit — check current rates with HMRC or your accountant.
• 7. Keep records for at least six years. HMRC can ask to see details. Keeping everything tidy avoids headaches.

Example cost allocation (simple table)

How to write the technical narrative — a short template I use

Your technical narrative doesn’t need to be long. I give clients this structure to follow; it keeps HMRC happy and keeps your claim honest:

• Project name and dates.
• Objective. What were you trying to achieve commercially?
• Scientific/technical uncertainty. What specific problem did you not know how to solve?
• Why it wasn’t routine. Why couldn’t a competent developer solve this quickly using standard methods?
• Work undertaken (approaches/experiments). Describe the technical paths tried, failures, iterations and final learning.
• Outcome and knowledge gained. Did you create a new method, tool or performance improvement that can be reused?

Common pitfalls and how to avoid them

• Vague descriptions. “We experimented with code” won’t cut it. Be precise about the technical challenges.
• Mixing routine design with R&D. Creative iterations for aesthetics alone aren’t R&D. Focus on technical advances.
• Poor time allocation. If you can’t justify the hours claimed, you may get queried. Use timesheets or project tools (Jira, Trello, Clockify) to back up allocations.
• No contemporaneous evidence. Drafting narratives after the fact is common but riskier. Keep notes, commits and test files during the project.
• Overclaiming for subcontractors or connected parties. Check treatment of connected-party payments and get clear invoices showing the R&D work.

When to consider a specialist

You don’t need a consultant to make a valid claim — many agencies prepare credible claims in-house with basic accounting support. However, call in a specialist if:

• you’re unfamiliar with the corporation tax filing process or the claim rules;
• you expect a large claim and want to mitigate enquiry risk;
• you have complex subcontractor arrangements or connected-party issues;
• you want an objective technical validation letter to support your claim.

For routine claims I often recommend using your accountant (I use Xero and FreeAgent clients’ records to pull costs) and preparing the technical narratives with the team. If you do use a consultant, check their approach — some charge a fixed fee, others take a percentage. Beware contingency fees that incentivise overclaiming; I prefer transparent fixed-fee or hourly arrangements.

Practical tips so you can start today

• Run a quick internal workshop with project leads to flag potential R&D activities from the past year.
• Start a simple R&D folder on Google Drive or Dropbox where you save technical notes, test results and invoices as projects run.
• Use time tracking for R&D-related work — even a simple weekly log is better than nothing.
• Talk to your accountant early. They’ll ensure the financial side (CT600 entries, loss surrenders if applicable) is done correctly.
• Keep claims proportionate and factual — HMRC is more interested in robust evidence than clever language.

If you’d like, I can share a template R&D technical narrative or a simple spreadsheet I use to map staff costs to projects. Getting comfortable with the process will often reveal eligible spend you didn’t realise was claimable — and for small creative agencies that can meaningfully improve cashflow without the stress or cost of a full specialist engagement.