Most businesses should buy most of their software. Accounting, payroll, email, CRM and bookings are solved problems, and a product with a monthly fee will beat anything you commission. Bespoke software earns its cost in a narrower set of cases: the process is the thing that makes you different, your packaged tools can’t talk to each other, or per-user fees have grown faster than the value you get from them.
The UK government’s Technology Code of Practice draws the line in much the same place. Its purchasing guidance, last updated on 3 September 2026, says building may suit you when your “user need is unique or rare” or you “need to own your technology to keep the flexibility to modify it”. Buying suits you when “there is a commercially available way to meet most of your user needs”.
- Buy for anything standard. Build only where the software carries a process your competitors don’t have.
- Try configuring an existing product or a low-code tool before you commission code, but stop if you find yourself bending it out of shape.
- Compare costs over three to five years, including per-seat fees at your expected headcount, integration work, maintenance and the cost of leaving.
- AI coding tools have made a first version cheaper. They have not made ownership free.
Step 1 of 5
Buy
Start with a product built for the job if the process is the same as everyone else's.
Step 2 of 5
Configure
Use the product's own fields, workflows and automations before anything custom.
Step 3 of 5
Low-code
Assemble forms and approval flows in a low-code tool if the gap is small.
Step 4 of 5
Cost it
Compare five-year totals at your expected headcount, including the cost of leaving.
Step 5 of 5
Build
Commission bespoke software only where the process is your edge and the sums work.
When off-the-shelf software is the right answer
Buy when the job is the same in your business as in everyone else’s. A dental practice does not need its own payroll system. A gift shop does not need a custom checkout when Shopify exists. The vendor spreads development, security patching and compliance updates across thousands of customers, and you get them for a subscription.
Buying also wins when you’re not yet sure what you need. A subscription you can cancel is a cheap way to learn. If you are still testing whether customers want the thing at all, read our guide on validating a business idea before you build anything first.
The honest test: if you would have to change how you work to fit the product, would that change hurt? Often the product’s way is fine, and adopting it is cheaper than preserving a habit.
The middle route: configure or use low-code first
Between buying and building sits a wide middle ground. Most serious products can be configured with custom fields, workflows and automations. Low-code and no-code tools let a capable non-developer assemble forms, databases and approval flows. For many teams this is where a creaking spreadsheet should go next, and we cover the warning signs in when to replace a spreadsheet with a custom app.
There is a limit. The government guidance is blunt about it: “Even small modifications to OTS software can remove most of the benefits of using it.” Heavy customisation of an off-the-shelf (OTS) product raises costs, complicates maintenance and can stop you upgrading. If your configuration has grown into a tangle of workarounds that one person understands, you have built bespoke software anyway, on someone else’s platform and on their terms.
Four signs that bespoke software will pay off
1. The process is your edge
A specialist insurer’s quoting rules, a logistics firm’s routing, a training provider’s assessment method. If the way you do something is why customers choose you, forcing it into a generic tool flattens the advantage.
2. Integration pain is costing real hours
Count the time staff spend copying data between systems, fixing mismatches and chasing exports. When three or four products each hold part of the picture, a custom layer that joins them can pay for itself in saved labour.
3. Per-seat fees are scaling against you
Subscriptions priced per user are cheap at ten people and expensive at a hundred, especially when most users only need one screen. Bespoke software costs roughly the same to run whether 20 or 200 people log in.
4. You need to own the data and the roadmap
If the software is part of what you sell, or it holds data you could not afford to lose access to, depending on a vendor’s pricing and priorities is a risk. This is the usual reason to commission a bespoke platform or SaaS product of your own.
How to compare the total cost over five years
Monthly fees look small and build quotes look large, so compare them over the same period. Three to five years is sensible for most business software. Include licences at your expected headcount, add-ons and connectors, set-up and training, hosting, maintenance and changes, and what it would cost to leave.
Here is a made-up example to show the method. Say you run a 40-person property maintenance firm. A job management product costs £45 per user per month, plus £2,400 a year for connectors and add-ons. A bespoke system is quoted at £60,000 to build, then £12,000 a year for hosting, support and small changes. These figures are illustrative only and are not a price guide.
| Cumulative cost (hypothetical) | Subscription, 40 users | Bespoke build |
|---|---|---|
| End of year 1 | £24,000 | £72,000 |
| End of year 3 | £72,000 | £96,000 |
| End of year 5 | £120,000 | £120,000 |
On those numbers the two routes meet at year five, which means buying wins: you carry less risk and can leave sooner. Now double the headcount to 80. The subscription rises to £45,600 a year, or £228,000 over five years, while the bespoke figure barely moves. The answer flips. Your own numbers will differ, and the point of the exercise is to find which assumption the decision hangs on. For what drives a build quote, see how much it costs to build an app in the UK.
Lock-in and exit: plan the ending first
Both routes can trap you. With a subscription, the trap is your data and your habits living in a system you can’t easily leave. Before signing, ask how you export everything, in what format, and what it costs. The Competition and Markets Authority’s cloud services market investigation, which published its final decision on 31 July 2025, examined fees for moving data out and technical barriers to switching, so this is a recognised problem and not a niche worry.
With bespoke, the trap is a supplier who owns the code or is the only one who understands it. The government’s guidance is a decent checklist for a small business too. It says contracts should be explicit about who owns the data and the intellectual property, and that, where economic, they should include a break clause at a maximum of two years with minimal exit costs. Insist on owning the code, having it in a repository you control, and documentation a different developer could pick up.
Has AI made bespoke software cheap?
Cheaper to start, yes. AI coding tools are now ordinary practice: 84% of respondents to Stack Overflow’s 2025 Developer Survey said they used or planned to use them, and its 2026 survey reports that over 70% of respondents use AI daily. In our view that has pulled the cost of a first working version down, which moves the break-even point towards building for smaller projects.
The same survey is a useful corrective. In 2025, more developers said they distrusted the accuracy of AI output (46%) than trusted it (33%). The most common frustration, cited by 66%, was “AI solutions that are almost right, but not quite”, and 45% said debugging AI-generated code takes more time. Someone still has to review the code, test it, secure it, host it and change it when your business changes. That work recurs every year you own the software, and AI has not removed it.
If the software itself uses AI models, there is a usage bill too. We explain how to estimate it in what AI costs to run.
The same test applies to the system most businesses argue about: the CRM. If your sales process is standard, buy one. If the CRM has to run your jobs, quotes and invoices as well, a CRM built around your process can be the cheaper option over five years, and our comparison of custom and off-the-shelf CRM costs shows the sums.
Common questions
Can we start with a subscription and build later?
Yes, and it is often the best order. A year on an off-the-shelf product tells you which features you use and where it fails you, which makes a far better brief. Check the export route on day one so the move is possible.
Does bespoke software qualify for R&D tax relief?
Sometimes, but only where the project tackles real technological uncertainty. Routine development does not count. Our primer on R&D tax relief for software and AI projects sets out the test.
If you’d like a second opinion on a build or buy decision, tell us what you’re weighing up and we’ll give you a straight answer.
Sources
- GOV.UK, Technology Code of Practice: Define your purchasing strategy (updated 3 September 2026)
- GOV.UK Service Manual: Choosing technology, an introduction (updated 15 October 2024)
- Competition and Markets Authority: Cloud services market investigation (final decision 31 July 2025)
- Stack Overflow: 2025 Developer Survey, AI (2025)
- Stack Overflow: 2026 Developer Survey, AI (2026)