Custom software vs off-the-shelf: which is right for us?

What off-the-shelf does well

Let's be fair first, because most businesses should keep buying software off the shelf for most things. Generic tools are right when:

• The problem is genuinely generic. Accounting, email, payroll, standard CRM — millions of businesses do these the same way, and the tools are mature, cheap and maintained by someone else.
• You need it this week. Off-the-shelf is instant. Custom software is a project with a timeline, and timelines are real.
• Maintenance matters more than fit. Someone else patches, hosts and supports the tool. That's a real cost you avoid — and it's the part people forget when comparing prices.

If a £50/month tool covers 90% of what you need, buy it and move on. The remaining 10% is rarely worth a build.

When off-the-shelf starts costing you

The bill for generic software isn't the subscription — it's the workarounds. Watch for these signs:

• Your process bends to fit the tool. Your team has a ritual of exporting, reformatting and re-importing because the tool "doesn't quite do it that way." Every workaround is a process you own that the tool doesn't.
• You own five tools that don't talk. Data is entered once per tool. Nobody trusts any single number. The integrations you need are on the enterprise tier you can't justify.
• The workarounds have workarounds. Someone built a spreadsheet to manage the gaps in the tool. Someone else built a spreadsheet to manage *that* spreadsheet. This is more common than anyone admits.
• Your differentiator lives in the gap. If the way you operate — your quoting, your fulfilment, your client experience — is what wins you business, and the tool forces you to do it the generic way, you're paying the tool to make you ordinary.

What custom software actually buys

Custom software isn't about having something nobody else has — it's about having something that matches the work exactly. For most businesses that means the unglamorous middle layer: custom dashboards, customer portals and internal tools built around exactly how the business operates, not how off-the-shelf software thinks it should.

What you get, concretely: one place for the job instead of five disconnected tools; data entered once; reports that reflect your process rather than a generic template; and — the part that matters most — software shaped with the people who will use it daily, documented properly, and supported after launch. The risk people fear with custom software is being stuck with something unmaintainable. That risk is real with bad builds; it's managed by scoping with the users, building around roles and rules, and documenting everything.

The honest decision framework

Ask these in order:

1. Is the problem generic? If yes — buy. (Most problems are.)
2. What do the workarounds cost? Add up the duplicate hours, the errors, the decisions made on bad data. If that number is bigger than a build over two years, the "cheap" option is the expensive one.
3. Is the process your advantage? If how you work is why customers choose you, generic tooling is actively costing you differentiation.
4. Can you scope it? Custom software needs a defined job — dashboards, a portal, an internal tool. "Make us more efficient" is not a scope; it's a wish. Discovery turns the wish into a scope, screen by screen, with the people who'll use it.

And the honest answer to "which is right for us": off-the-shelf tools solve a generic version of your problem. Custom software is scoped to your exact process — and discovery shows honestly whether custom or off-the-shelf fits better. Any studio that answers this question before asking about your process is selling, not advising.

If you've worked through the framework and the answer is custom, our custom software development services page describes how we scope and build it — requirements and process mapping, custom build, integrations with the systems you keep, training and documentation. If the answer might be an AI agent embedded in that software, read our piece on AI agents vs chatbots next.