Off-the-shelf or bespoke software: how to tell which you need

Most businesses start with off-the-shelf software. It is quick to set up and cheap to try. Then the workarounds begin.

Someone exports data every Friday so it can go into another system. Two people type the same order into two places. You pay for features nobody uses. The one thing you really need is never on the vendor's plan.

Each workaround looks small. Together they cost staff time, cause errors and slow decisions. Over time the software starts to shape how you work, instead of the other way round.

This article helps you judge whether to keep your current tools, connect them better, or build something of your own.

Where the hidden cost comes from

The licence fee is the cost you see. The bigger costs are usually hidden. Look for these:

• Duplicate data entry. The same details typed into more than one system. This wastes time and causes mistakes.
• Manual exports and imports. Spreadsheets moved between tools by hand, often by one person who knows how.
• Unused features. You pay for a full package but use a small part of it.
• Process bent to fit the tool. Staff follow steps that suit the software, not the customer.
• Missing features. The thing that would make the biggest difference is not on the vendor's roadmap.

A useful test: ask your team where they keep a separate spreadsheet "just to make it work". Each one is a sign of a gap.

When off-the-shelf is the right answer

Off-the-shelf software is often the sensible choice. It is a good fit when:

• Your process is standard, such as accounting, payroll or email.
• Many businesses work the same way you do, so the product is built for you.
• You need to start this month, not next quarter.
• The tool does what you need without heavy workarounds.

In these cases, building your own adds cost without adding value. Do not build software just to have it.

When bespoke software makes sense

Bespoke software means software built around your own way of working. It makes sense when the way you work is part of what makes you different.

Common signs include:

• Your process does not fit any product on the market.
• You run several sites and need stock, bookings or sales to work across all of them.
• Customers, staff or partners need their own portal with their own view of the data.
• Your current system no longer copes as you grow.
• You are thinking of selling the software itself as a subscription product.

Here the trade-off changes. You pay more at the start. In return you stop paying for workarounds, and you own the result.

The middle path: connect what you already have

Sometimes the tools are fine. The problem is that they do not talk to each other. In that case you may not need new software at all.

Integration means linking systems so data moves between them on its own. For example, an online order could go straight into your stock and accounts system. No one retypes it. Good integration and automation can remove the worst workarounds at lower cost than a full build.

This is a good first step if most of your pain is copying data between tools. It is less useful if the tools themselves cannot support how you work.

If you build, what to insist on

Bespoke software only pays off if it is built well and stays yours. Before you sign, check these points:

• You own the code and accounts from day one. This includes hosting, domains and app store accounts. Otherwise you are tied to one supplier.
• You see working software often. Weekly progress in a staging environment, a private test copy of the system, lets you change priorities based on what you learn.
• Work happens in short, fixed-scope phases. Each phase has a clear goal. This keeps cost and risk under control.
• Automated tests are included. These are small programs that check the software still works after each change.
• Documentation and a handover come with it. Another team should be able to pick up the work if needed.
• The technology suits your situation. Common, well-supported tools are easier to hire for and maintain.

If you want a fuller picture of what this looks like in practice, our bespoke software page sets out how we approach it. If you are still testing an idea, a smaller first version may be wiser. Our guide to MVP development covers that route.

A simple way to decide

You can make this decision in four steps:

1. List the workarounds. For two weeks, ask staff to note every export, re-type and side spreadsheet.
2. Estimate the time. Roughly how many hours a week do these take? Who does them?
3. Sort the causes. Is the problem a missing link between tools, or a tool that cannot do the job?
4. Match the fix. Missing links point to integration. Tools that cannot do the job point to bespoke software. If neither is a real problem, keep what you have.

This gives you a decision based on your own evidence, not on a sales pitch.

Next step

Start with the workaround list. It costs nothing and it will show you where the real problem is. If the list points to a build, bring it to a first conversation with any supplier. It will make every quote easier to compare.