When does a business actually need custom software?

There's a version of this article a software company could write that ends with "so you should build everything custom". This isn't it. Off-the-shelf software is often the faster, cheaper and more reliable choice, and we'll say so when it is.

But there's a point where bending your business around software costs more than having software built around your business. Here's how to recognise it.

Start with the problem, not the product

The question isn't "custom or off-the-shelf?" It's "what is costing us time, money or customers, and what would fix it?"

Write down the process that's causing pain, step by step: how an enquiry arrives, what happens next, who does what, where information is recorded and where things go wrong. That list will usually point to the answer.

Signs that off-the-shelf will do

Established software is probably right if:

• your process is similar to most businesses in your sector;
• a product covers 80–90% of what you need, and the rest is "nice to have";
• you can adapt slightly to the software's way of working without real cost;
• you need it running next week, not next quarter;
• the per-user cost is reasonable at your size.

In that case, the most valuable help is usually setting it up properly, migrating your data and connecting it to your website and other tools. That's often a small project compared with building something new.

Signs that you've outgrown it

Custom software starts to make sense when:

• Your process is genuinely different. Hire businesses with turnaround rules, manufacturers with configurable products, or service businesses with complex scheduling often fall here.
• You're paying for several tools that each do part of the job, and staff copy data between them.
• Workarounds have become the system. A spreadsheet "bridge" between two products that only one person understands is a warning sign.
• Per-user costs are climbing as you grow, for features you don't use.
• The way you work is your advantage. If your process is why customers choose you, software that forces you into a standard mould can erode it.
• Customers need access. Portals, online approvals and self-service bookings are often where products fall short.

How to start without over-committing

Bespoke software doesn't have to mean a large, risky project. A sensible approach looks like this:

1. Discovery

Map the process, the people involved and the information that flows between them. Agree what success looks like: hours saved, errors avoided, faster payment, more bookings.

2. Prototype

A clickable prototype lets you and your team try the screens before anything is built. It's the cheapest point at which to change your mind.

3. A focused first version

Build the part that removes the most pain first. For a trades business, that might be quoting and scheduling; invoicing integration can follow. You get value sooner and learn what really matters.

4. Grow in phases

Add features based on what you learn using the system, not on a wish list written before anyone used it.

Questions to ask a developer

• Who will own the code, and what happens if we part ways?
• What technology will you use, and is it widely supported?
• How will the system be hosted, backed up and secured?
• How will we see progress during the build?
• What does ongoing maintenance involve and cost?
• Could an existing product do this instead? (A good developer will answer this honestly.)

The bottom line

Custom software is worth it when it removes real, recurring cost or unlocks something your business can't do otherwise. It isn't worth it to replicate a product you could subscribe to.

If you're not sure which side you're on, describe the problem and we'll tell you, even if the answer is "use an existing tool and we'll help you connect it".