Bespoke software or off the shelf: how to tell which you need

The honest version of this question is not "bespoke or off the shelf". It is "which parts of how we work are genuinely ours, and which parts are the same as everybody else's". Buy the second sort. Build the first sort, and only when the difference is costing you money.

The test, in one question

If a competitor bought the same software tomorrow, would you have lost anything?

If no, buy it. Accounting, payroll, email, document storage and general CRM are the same job in every business, they are solved by mature products with hundreds of engineers behind them, and no custom build will catch up.

If yes, that is where custom software earns its money. The scheduling logic nobody else uses, the pricing rules that took fifteen years to learn, the way your particular data actually flows. Those are the parts a product cannot sell you, because they only exist in your business.

Three signs you have outgrown off the shelf

You are paying people to move data between systems. Someone exports a spreadsheet from one product and re-keys it into another every week. That salary cost is real, and it is usually the first thing that justifies a build, though often what you need is an integration rather than a new system.

Your process lives outside the software. The product does 70% of the job and the rest happens in a shared spreadsheet, a WhatsApp group and somebody's memory. That gap is where mistakes and key-person risk live. It is the pattern behind most of the platforms we build, including a cleaning operation whose rota lived in a spreadsheet and got re-sent on WhatsApp every time it changed.

You are paying per seat for features you do not use. Twenty licences at £80 a month is £19,200 a year. Five years of that is a six-figure sum, and it buys a system somebody else controls, priced by somebody else, changed on somebody else's schedule.

Three signs custom is the wrong answer

Less often said, and worth more.

The problem is a process problem. If nobody agrees what the current process is, software will not settle it, it will encode the confusion and make it expensive to change. Sort the process first, on paper, and you may find you do not need the build.

You want it because the current system is annoying. Annoying is not the same as costing money. Write down what the annoyance actually costs in hours a week and a rate, and see whether the number justifies a build. Sometimes it plainly does. Often it buys some training and a better configuration instead.

You cannot fund year two. A custom system needs a running budget every year to stay healthy, and if that is not there the system decays into the thing you have to replace. Off the shelf includes that cost in the subscription, which is part of what you are paying for.

The middle option most people miss

It is rarely all or nothing. The arrangement that works most often is to keep the products that are good at their jobs and build the connective tissue and the bits that are genuinely yours.

Keep Xero. Keep your email platform. Build the portal your customers log into, and connect it to both. You get the leverage of mature products where the problem is generic and something bespoke where it is not, and you do not pay to rebuild accounting.

That shape is what most of our work looks like in practice: systems that talk to each other properly rather than one enormous replacement for everything.

What buying looks like versus building

	Off the shelf	Custom
Upfront	Low, often nothing	From around £1,500 for something simple, see what it costs
Ongoing	Per seat, rises as you grow	A yearly budget to keep it running
Time to value	Days	Weeks to months
Fits your process	You fit its process	It fits yours
Changes	When the vendor decides	When you decide
Leaving	Export what they let you	You own the lot

The row that decides it most often is the last but one. If the way you work is a genuine advantage, handing control of it to a product roadmap you do not influence is the actual risk, and it is invisible until the day the vendor removes something you rely on.

Before you brief anyone

Write down, in plain sentences, the three things that go wrong most often in a normal week and what each one costs. Not features. Not screens. Problems and numbers.

Any decent agency can turn that into a scope. Nobody can turn "we need a new system" into one, which is how projects end up costing double and doing things nobody uses.

If you want a straight opinion on which side of this your situation falls, tell us what you are trying to build. We will tell you when the answer is to buy something instead, which happens more often than you would expect from people who make their living building.