Bespoke vs off-the-shelf software for UK SMEs and R&D relief

Last checked: October 2026. Buy off-the-shelf software when your process is common and the package fits with configuration. Commission bespoke software when the process is what sets your business apart, or when no package can be bent to fit without costly workarounds. Many SMEs end up with a hybrid: packages for generic tasks, bespoke for the core.

The cost and trade-off statements in this article come from software suppliers' published guides, which have a selling interest. We found no independent UK benchmark for SME total cost, so we describe the pattern rather than quote figures. The R&D tax relief part draws on GOV.UK guidance and HMRC's own manuals. This is general information, not tax or legal advice.

Off-the-shelf software

Box UK describes off-the-shelf software as ready-to-use tools available on the mass market, typically licensed or sold as a subscription (SaaS). It is quick to get running and usually needs less upfront investment. The drawbacks: in Headchannel's words, some customisation is possible but within predefined boundaries, and Box UK warns that packages are prone to feature bloat, so you may use only a small portion of what you pay for.

Bespoke software

Software designed and built around your process. It can match your exact workflows and change as the business changes. The trade-off is time: Headchannel speaks of months of planning, design, development and testing, while a package can often be ready within days or weeks.

Hybrid

Box UK suggests combining both: off-the-shelf tools for common processes such as time tracking or inventory management, with bespoke elements, custom middleware or APIs for the requirements specific to your organisation.

Suppliers broadly agree on the shape. Headchannel and Box UK both describe a higher upfront investment for bespoke work and a lower entry cost for packages, whose ongoing licensing, support and add-on fees can add up. Box UK argues that bespoke software removes the need for ongoing licensing costs and so can drive greater return on investment over the long term. Rise Up Labs publishes a simplified three-year cost-of-ownership model, but it is the work of a bespoke developer, in US dollars, and notes that actual costs vary.

What this means for you:

• Compare over a fixed horizon, such as three to five years, not on the first invoice.
• Count users: per-seat subscriptions grow with headcount.
• Count workarounds: staff time spent bridging a poor fit is a real cost.
• Count change: ask how each option handles a new product line, a new location or a new regulation.

The standard UK VAT rate of 20% applies to both routes. GOV.UK allows VAT-registered businesses to reclaim VAT on items bought for business use, with exceptions such as the Flat Rate Scheme, so compare net or gross consistently.

With a package, Box UK notes, you do not own the software but rent it for a period of time. With bespoke software you should have complete ownership over the technology and your roadmap. That matters if you want control of features, data structure and exit.

Ownership brings responsibility. Box UK points out that you become responsible for coordinating your technology ecosystem, which may include hosting, security updates and integration with existing services. Headchannel's comparison puts maintenance and updates of bespoke software on the client, while a SaaS provider handles maintenance, updates and security. If you do go bespoke, price the support in at the start, and agree who holds the source code, documentation and hosting accounts.

If the software handles personal data, UK GDPR responsibilities apply either way. The ICO distinguishes the controller, which decides the purposes and means of processing, from a processor, which processes personal data on the controller's behalf. With a package you need to understand which role the vendor plays and what its terms say. With bespoke software you decide how data is stored and who can access it.

Score each statement from 0 to 2 (0 = not true, 2 = very true) and add up the answers.

The score is a conversation starter, not a verdict. Where the answers are mixed, a hybrid is usually worth costing.

The UK now has a merged R&D scheme. According to GOV.UK, the merged R&D expenditure credit (RDEC) and enhanced R&D intensive support (ERIS) replaced the old RDEC and SME schemes for accounting periods beginning on or after 1 April 2024. The merged RDEC is a taxable credit at a rate of 20%. ERIS is only for loss-making R&D-intensive SMEs, whose relevant R&D spending is at least 30% of total expenditure: they can deduct an extra 86% of qualifying costs, 186% in total, and claim a payable credit worth up to 14.5% of the surrenderable loss. A company eligible for ERIS can choose the merged RDEC instead, but cannot claim under both for the same expenditure.

The first test is the project, not the product. HMRC's manual on software says the advance must be in overall knowledge or capability, not the company's own, and that it is the underlying technology that counts rather than the commercial output. It calls it unlikely that configuring existing software to a company's own requirements would qualify, and says that assembling program components to an established pattern is not R&D. Johnston Carmichael notes that HMRC's earlier guidance gave using an off-the-shelf package to build a bespoke website as an obviously non-qualifying example. In plain terms, configuring a package rarely qualifies, and building a conventional business system to a known design often does not either.

Genuinely novel work can qualify. The same manual names the implementation of a novel algorithm that significantly increases capability as one example. On commissioned work, the HM Treasury technical note says that a company with a valid R&D project which contracts a third party for qualifying work may claim the relevant costs, and the contractor may not claim for work that delivers another company's project. HMRC's manual adds that R&D incidental to the supply of a product or service is not contracted out, and weighs factors such as the contractor's autonomy, financial risk and who keeps the IP. So if you commission a supplier, who may claim depends on the contract and the facts.

Practical steps: ask your accountant early, before you sign, and agree with the supplier how technical uncertainties and the work done will be recorded. Do not buy bespoke software mainly for the relief.

These are hypothetical examples to show the reasoning, not client stories.

A small firm with standard accounts and bookings

Its processes match what thousands of similar firms do. A package, configured well, is likely to be the quickest and cheapest route. Bespoke work would add cost without a clear gain.

A business with a unique pricing or scheduling process

Staff keep the real logic in spreadsheets because no package copes. A bespoke core, linked to a package for accounts, may be worth costing against the hours lost to workarounds.

A company whose product is the software

Here the software is the business. Ownership, control and the ability to change quickly weigh heavily, which usually points to bespoke development with a plan for maintenance.

Whichever route you choose, think about leaving on the first day. With a package, check how you export your data and in what format. With bespoke software, check that you hold the source code, build instructions and hosting access so another supplier could take over.

Ask for these in writing, and test them. A data export that exists in the sales deck but fails on real records is not an exit route. A short migration rehearsal in the first year, even if you never switch, can show whether the promise holds.

1. Which parts of my process need custom code, and which can use an existing tool?
2. What are the running costs after year one?
3. Who owns the code and where is it hosted?
4. What happens if you stop trading or I want to move?
5. How will you document the work, including any technical problems solved?
6. Can we release a first version in stages?

We build websites, web applications and custom software, and we are happy to say when a package is the better choice. See our services, look at references for examples of our work, or describe your project through the quote form or contact page.

• R&D tax relief: the merged R&D expenditure credit scheme and enhanced R&D intensive support – GOV.UK
• Technical note on changes to R&D tax reliefs at Autumn Statement 2023 – GOV.UK
• CIRD81960 – R&D tax relief: BIS Guidelines (2004): application to software – HMRC internal manual
• CIRD84250 – R&D tax relief: subcontracted activities, meaning of subcontracted – HMRC internal manual
• New HMRC guidance clarifies R&D tax relief for software development – Johnston Carmichael
• Bespoke vs off-the-shelf software – Box UK
• Bespoke software vs off-the-shelf software vs SaaS – Headchannel
• Bespoke software development – Rise Up Labs
• VAT rates – GOV.UK
• Charge, reclaim and record VAT: Reclaim VAT on business expenses – GOV.UK
• What are ‘controllers’ and ‘processors’? – ICO