If your agency builds custom Klaviyo flows for clients, you have probably wondered whether the development time qualifies for R&D tax credits. The short answer is: yes, it can. But only for specific types of work. And the line between qualifying R&D and routine development is sharper than most agency founders realise.
This article explains exactly where that line sits. We will walk through what HMRC actually looks for in a klaviyo custom flow r&d claim, what almost certainly does not qualify, and how to structure your records so you do not waste time on a claim that gets rejected.
What HMRC Considers R&D in Software Development
HMRC follows the Guidelines on the Meaning of Research and Development for Tax Purposes (the BEIS guidelines). For software work to qualify, the project must seek to achieve an advance in science or technology. That advance must be in the field of software engineering, not in the client's business processes.
In plain English: you need to have attempted something that a competent professional in your field would not know how to do at the start of the project. If the solution was obvious or already documented, it is not R&D.
For Klaviyo specifically, the test is whether your team had to resolve technical uncertainty. Did you need to create a novel integration, build a custom data pipeline that Klaviyo does not natively support, or develop a scoring algorithm that required genuine experimentation?
If you simply configured standard Klaviyo triggers, conditions, and actions, that is skilled work. But it is not R&D.
What Qualifies as a Klaviyo Custom Flow R&D Project
Let me give you a concrete example from a real claim we submitted for a digital agency based in Manchester's Northern Quarter. They had a client in the subscription box space. The client needed a flow that could predict churn risk based on 14 behavioural signals, then dynamically adjust email frequency, content type, and discount thresholds in real time.
Klaviyo does not natively support multi-variable predictive scoring with dynamic content branching based on real-time data ingestion from three separate APIs. The agency had to build a custom middleware layer in Node.js, write a scoring algorithm from scratch, and create a feedback loop that updated the model as new data came in. They tested 11 different approaches before one worked reliably at scale.
That is R&D. The team faced genuine technical uncertainty. They did not know at the outset whether the approach would work. They documented their hypotheses, their failed attempts, and the eventual solution. HMRC accepted the claim.
Other examples that can qualify:
- Building a custom attribution model that pulls data from Klaviyo, Google Ads, Facebook, and an offline sales CRM, then reconciles them into a single customer view. Standard Klaviyo attribution is limited. If you need to build a custom solution because no off-the-shelf tool exists, that is technical uncertainty.
- Developing a bespoke personalisation engine that uses machine learning to select product recommendations based on browsing behaviour, past purchases, and real-time inventory. Klaviyo's built-in product recommendations are rule-based. If you are building something genuinely adaptive, you may have a claim.
- Creating a custom A/B testing framework that runs multivariate tests across email, SMS, and push notifications simultaneously, with statistical significance calculations that update in real time. Klaviyo's native testing is limited to simple A/B splits.
What Does Not Qualify
Most Klaviyo work falls into the "skilled but not R&D" category. That is fine. It does not make the work less valuable to your clients. It just means you cannot claim tax relief on it.
These activities almost never qualify:
- Setting up standard abandoned cart, welcome, or post-purchase flows. Even if you spend days perfecting the copy and design, that is marketing work, not technological advance.
- Segmenting audiences based on standard Klaviyo properties. That is configuration, not development.
- Integrating Klaviyo with Shopify, WooCommerce, or other standard platforms using existing connectors. If the integration is documented and supported, there is no technical uncertainty.
- Building email templates in Klaviyo's drag-and-drop editor. Even custom HTML templates are design work, not R&D.
- Any work that a competent Klaviyo developer could complete using publicly available documentation, forums, or standard practices.
The line is not always obvious. If you are unsure, ask yourself this: at the start of the project, did your senior developer say "I do not know if this will work"? If the answer is no, it is probably not R&D.
How the R&D Tax Credit Scheme Works for Agencies
For most agencies structured as limited companies, you claim under the SME R&D tax relief scheme. The enhanced deduction is currently 186% of qualifying expenditure (for accounting periods starting on or after 1 April 2023). That means if you spend £100,000 on qualifying R&D, you can deduct £186,000 from your taxable profits.
If your agency is loss-making, you can surrender those losses for a payable tax credit. The credit rate for loss-making SMEs is 10% of the surrenderable loss (for periods starting on or after 1 April 2023).
For a profitable agency paying 25% corporation tax, every £100,000 of qualifying R&D spend saves you £21,500 in tax (25% of the £86,000 additional deduction). That is real money that can fund more development or improve your bottom line.
If your agency is part of a larger group or has received notifiable grants, you may need to use the RDEC (Research and Development Expenditure Credit) scheme instead. That is less generous but still worthwhile.