Founders

6

min read

The Five Founder Conversations That Usually Lead to an R&D Tax Relief Claim

Most R&D Claims Don't Start With Tax

Ask an R&D specialist where most successful claims begin, and the answer probably won't be what you expect. It isn't with a spreadsheet, a tax return or an accountant. It usually starts with a conversation. A founder casually mentions a challenge they've been facing. A developer explains why something took six months longer than expected. A product manager describes why they had to redesign an entire feature. A CTO talks about rewriting the architecture for the third time.

To them, it's simply part of building a business. To an R&D specialist, those conversations often reveal genuine innovation. The challenge is that founders rarely describe their work as Research & Development. They describe it as surviving startup life, which is exactly why asking the right questions matters.

Innovation Doesn't Announce Itself

Very few founders say they've been undertaking qualifying R&D this quarter. Instead, they say things like: we're trying to make this work, nothing else could solve the problem, we had to build our own system, we've rewritten it again, our developers have been tearing their hair out. Innovation often hides inside ordinary business conversations. The role of a good adviser isn't to look for tax. It's to recognise when innovation might be happening.

Conversation One: We've Built Our Own Platform Because Nothing Else Could Do What We Needed

This is perhaps the most common conversation we hear. A founder explains that they looked at existing software, trialled several platforms, and none delivered what the business needed, so they built their own. That immediately raises interesting questions: why wasn't existing technology sufficient, what technical challenges had to be overcome, how much development was involved, what experimentation took place. The fact that software was built doesn't automatically mean the work qualifies, but it's certainly worth exploring further.

Conversation Two: We've Had to Rewrite the Product Several Times

Founders often see this as failure. In reality, it's frequently evidence of innovation. Perhaps the original architecture couldn't scale, performance wasn't good enough, security requirements changed, or customer demand revealed technical limitations. The development team started again, then started again, and again. Every rewrite tells a story, not about poor planning, but about learning, experimentation and technical uncertainty. Exactly the sort of activity that deserves closer examination.

Conversation Three: Our Developers Spent Months Trying to Solve This

Every founder has experienced moments where a seemingly simple feature becomes unexpectedly difficult. What looked like a two-week sprint becomes a three-month challenge. Developers investigate multiple approaches, performance issues emerge, testing reveals new problems, and nothing works quite as expected. Eventually the team finds a solution. Those additional months weren't simply delays. They often represent genuine technological problem-solving. The question isn't why it took so long. It's what made it technically difficult.

Conversation Four: We Built Something That Didn't Exist Before

Innovation isn't always about inventing entirely new technology. Sometimes it's about creating a solution that didn't previously exist for your market, your customers or your industry, whether that's a bespoke AI platform, a new manufacturing process, an advanced logistics system, a complex software integration, a proprietary workflow engine or a unique automation solution. Founders often describe these projects as having no choice but to build it themselves. That's an important conversation.

Conversation Five: We Tried Lots of Different Approaches Before It Finally Worked

Perhaps the biggest misconception surrounding R&D is that success is what matters. In reality, experimentation is often far more significant. Think about what happens during product development: you test, you fail, you improve, you test again, you abandon one solution, you build another, and eventually something works. That iterative process demonstrates uncertainty, and uncertainty is one of the defining characteristics of genuine R&D.

Why Founders Rarely Recognise These Conversations

Most founders are incredibly close to their business. What feels extraordinary to an external adviser often feels completely normal to them. After all, building difficult products is their job, solving technical problems is expected, and creating new technology is simply another Tuesday. That's why founders frequently overlook opportunities. They're too busy building to stop and recognise what they've achieved.

The Questions Every Founder Should Ask

Rather than asking "can we claim R&D tax relief?", try asking what technical problems you've solved this year, where your developers spent most of their time, which projects required experimentation, what didn't work first time, and where you built something because existing technology couldn't. These questions usually generate far more useful conversations.

These Conversations Should Happen Before Year-End

One of the biggest mistakes innovative businesses make is leaving R&D discussions until after the financial year has ended. By then, projects are finished, developers have moved on, details have faded, and evidence becomes harder to gather. Instead, founders should make innovation part of regular business discussions, perhaps every quarter or after major development milestones. Capturing technical decisions while they're fresh creates stronger governance and better evidence.

Innovation Isn't Limited to Technology Companies

While software startups often dominate R&D discussions, these conversations happen across many industries. Manufacturers redesign production methods. Engineers develop new techniques. Construction businesses solve site-specific challenges. Food producers improve manufacturing processes. Healthcare companies create new diagnostic tools. Renewable energy businesses improve efficiency. The common thread isn't the industry. It's the willingness to solve difficult technical problems.

Why These Conversations Matter to Investors

Investors don't simply invest in ideas. They invest in execution. Businesses that document innovation effectively often demonstrate better governance, stronger technical leadership, more disciplined product development and greater commercial maturity. Understanding available innovation funding also demonstrates that founders think strategically about capital allocation. Every additional pound of non-dilutive funding improves resilience.

Founder Communities Can Encourage Better Conversations

Founder communities play an important role in helping entrepreneurs learn from one another. Imagine if every founder regularly asked what technical problems others had solved recently, what lessons they'd learned from building their product, and what funding opportunities they'd explored. Communities become significantly more valuable when they encourage practical commercial conversations rather than focusing solely on fundraising. Innovation funding deserves to be part of that discussion.

How PSS Tax Helps Founders Recognise Innovation

At PSS Tax, we don't begin every conversation by talking about tax. We begin by asking founders about their journey: what were you trying to build, what made it difficult, what failed, what eventually worked. Those discussions often uncover innovation that founders never realised could qualify for support.

We then work with technical teams to assess eligibility, prepare robust claims and provide ongoing guidance, allowing founders to stay focused on growing their businesses. We also partner with founder communities to deliver educational webinars, founder funding clinics and office hours, helping entrepreneurs understand how innovation funding fits into a broader growth strategy.

Final Thoughts

Most successful R&D claims don't begin with legislation. They begin with curiosity, with someone asking what the hardest problem your team solved this year was. For founders, those stories often feel ordinary. For specialists, they may represent significant innovation.

The next time you're discussing product development with your team, don't just ask what you built. Ask what was difficult, what almost didn't work, and what you learned. Because hidden inside those conversations may be one of the most valuable funding opportunities your business has yet to discover.

About PSS Tax

PSS Tax is a specialist UK R&D tax relief consultancy, helping founders, startups and innovation-led businesses identify qualifying R&D and unlock valuable non-dilutive funding. Through partnerships with founder communities, accelerators and startup ecosystems, we provide educational content, webinars, office hours and expert support that help founders build stronger, more resilient businesses while continuing to innovate.

This article provides general information only and does not constitute tax, accounting or legal advice. R&D tax relief depends on the facts, the accounting period and the legislation in force. Businesses should obtain advice based on their specific circumstances before making a claim.

Not sure whether a client qualifies?

We would rather have that conversation before anything is submitted than after HMRC starts asking questions.

Book a call