Bespoke vs off-the-shelf software for SMEs

I lead engineering at Naitiv. Before that I was CTO at Ecologi, where I built the backend and software, and CTO at Just. This is how I'd answer the question if you asked me directly.

What are the advantages and disadvantages of bespoke vs off-the-shelf software?

Off-the-shelf wins on cost to start, speed and maintenance. Bespoke wins on fit, ownership and anything that makes you different. Most of the disadvantages of one are the advantages of the other.

	Off-the-shelf software	Bespoke software
Cost to start	Low. A monthly subscription, often per user.	Higher. You pay for the build before you use anything.
Time to first use	Days or weeks.	Days for a prototype, longer for a finished tool.
Fit to your workflow	You change your process to fit the product.	The software fits the process you already have.
Maintenance	The vendor does it.	You do, or you pay someone to.
Roadmap	The vendor decides, based on all its customers.	You decide.
Pricing over time	The vendor can raise prices or change terms.	You control hosting and maintenance costs.
Data	Held in the vendor's system, exported in the vendor's format.	Held where and how you choose.
Competitive advantage	None. Your competitors can buy the same product.	Possible, if it does something competitors can't easily copy.
Risk	Tested by thousands of other customers.	Untested until you use it. A bad brief produces bad software.

The advantages of off-the-shelf software are mostly about time and risk. Other businesses have already found the bugs. You can be using it next week, and when it breaks at 2am, fixing it is someone else's job.

The disadvantages of off-the-shelf software show up later. Per-user pricing means the bill grows every time you hire. The parts of your process that don't fit the product end up in spreadsheets. And because your competitors can buy the same tool, it can never be the reason a customer picks you.

The advantages and disadvantages of bespoke software are the mirror image. It fits, you own it, and nobody else has it. But you pay before you see anything, and every bug is yours.

On cost, The AI Consultancy's 2026 build vs buy guide estimates £20,000 to £150,000 or more in first-year cost for a custom AI build, against £20 to £100 per user per month for a SaaS equivalent. They call these indicative UK market estimates, and I'd read them that way. The range is wide because "custom build" covers everything from a small internal tool to a product you sell.

Why does bespoke software cost less in 2026?

Because writing code takes much less time than it did. Engineers now use AI tools to draft, test and refactor code, so a small senior team can put a working prototype in front of users within days.

The saving is biggest on small tools. Most of an internal tool is routine work: forms, logins, admin screens, connections to other systems. The part that is specific to your business is often a small amount of logic in the middle. AI assistance speeds up the routine work most, and the routine work used to be most of the bill.

What has not got cheaper is deciding what to build. A fast build of the wrong thing still wastes money, and it's now easier to produce one. That's why we start with a business consultant, not an engineer, and build a prototype before anything bigger. You find out in days whether the idea holds up.

Two costs have not moved much. Someone still has to run and maintain the software once it's live. And a prototype is not a finished product: the same guide estimates three to nine months to value for a custom AI build. That fits larger systems. A tool that does one job is a smaller project, but it still needs testing, security and an owner.

We publish what our builds cost on our home page, so you can compare a build against a subscription before you speak to anyone.

What are the signs you should build bespoke software?

Build when at least one of these four is true. If two are true, take it seriously.

1. You have data nobody else has

Off-the-shelf products are designed for the average customer, so they treat your data in an average way. If your advantage sits in records you've built up over years, a generic tool will store them and do little else.

One test: could a competitor with the same subscriptions produce the same output? If not, your data is doing the work, and the software around it is worth owning.

2. The workflow is how you make money

If a process is what customers pay you for, don't bend it to fit someone else's product. Buy software for the processes every business has. Build for the one that makes yours different.

Our work for The Wild Company is built around one job: commercial land analysis in under half an hour.

3. You need glue between the tools you already pay for

This is the least glamorous case, and I think the most likely one for an SME. You keep the CRM, the accounts package and the job system. What you build is the small piece between them that currently lives in a spreadsheet, a copy-and-paste routine or one person's head.

This kind of bespoke software sits alongside your off-the-shelf tools and connects them. If that sounds like your business, our page on removing operational friction with software covers it in more detail.

4. The software would be a moat

If a competitor can buy the tool you use, that tool can't be why customers choose you. Software you own can be.

Be careful with this one. Software on its own is rarely a lasting moat, and cheaper building makes copying cheaper too. The advantage usually comes from the process and data the software encodes, and from the time it would take a competitor to learn what you learned building it.

When should you buy off-the-shelf software?

Buy whenever your process works the same way as everyone else's. Accounts, payroll, email, HR and, for most SMEs, the CRM are solved problems. The vendors have spent more on them than you ever would.

Most UK businesses already work this way with AI. In the Department for Science, Innovation and Technology's AI adoption research, 85% of UK businesses using AI use language processing and text generation. The researchers link this to how easy off-the-shelf generative tools are to get.

Buy when you don't yet know how you want the process to work. A subscription is a cheap way to learn. Once you can see which parts of the product you keep working around, you know what's worth building.

Buy when nobody would own a bespoke tool after launch. Software without an owner gets worse every month.

And before building anything, check the features in the tools you already pay for. The AI Consultancy's guide suggests testing off-the-shelf first, then the built-in features of platforms you own, then building only if both fail. I agree with that order. If you stop at step one or two, you don't need us, and I'd rather say that here.

Should I build or buy? A checklist

Run through this before you commit budget either way.

• Have you tried the off-the-shelf products for this job, and can you say in one sentence why they don't fit?
• Have you checked the features in the tools you already pay for?
• Is this a process customers pay you for, or one only your business does?
• Would the tool use data you have and competitors don't?
• Is the gap between two tools you already use, currently filled by a spreadsheet or copy-and-paste?
• Who will own the tool after launch, fix it and decide what it does next?
• Can you test a prototype with real users before paying for a full build?
• Have you budgeted for running costs, not just the build?

If you answered no to the first two, go and buy something. If you can't name an owner, don't build yet.

What should you do next?

Pick the one process that causes your business the most friction. Write down what it involves, which tools touch it, and one sentence on why the off-the-shelf options don't fit. If you can't write that sentence, buy. If you can, that sentence is the start of a brief.

A first conversation with us starts from that process. A business consultant works through it with you, we tell you whether we think you should build at all, and if we do, we scope a prototype. You can see what our builds typically cost on our home page, and read more about how Naitiv works with UK SMEs on our homepage.