Bespoke software vs off-the-shelf: how to choose for your business

Sooner or later every growing business hits the same question. Do we keep bending an off-the-shelf tool to fit how we work, or do we build something that fits us properly? There is no single right answer, but there is a sensible way to decide.

What we mean by off-the-shelf and bespoke

Off-the-shelf software is a ready-made product used by many businesses, usually paid for by monthly subscription. Think rota apps, booking platforms, CRMs and accounting packages. Bespoke software is designed and built around one organisation’s processes, and the business usually owns it.

In between sits a very common middle ground: off-the-shelf tools connected together, or extended with small custom pieces. For many businesses that is the right answer.

When off-the-shelf is the right choice

• The process is standard and well understood, such as payroll, accounting or email marketing
• A mature product already does 90% of what you need
• You need it working next week, not next quarter
• The cost of the subscription is small compared with the value it delivers
• Compliance or regulation is complex and a specialist vendor handles it for you

If that describes your situation, buy the product and spend your energy on using it well. We will happily tell a client that bespoke is not the answer.

When bespoke software makes sense

• Your process is part of what makes you different, and generic tools force you to work around them
• Your team relies on spreadsheets, paper forms or workarounds to fill the gaps between systems
• Per-user subscription costs are growing faster than the value you get
• You need several tools to share information and they do not connect well
• You want to own the data, the roadmap and the intellectual property

Compare the real costs, not just the price

The sticker price rarely tells the whole story. When comparing options over three to five years, include:

1. Subscriptions over time, especially per-user or per-site fees that rise as you grow.
2. The cost of workarounds: hours spent re-typing data, reconciling spreadsheets or chasing information.
3. Build and support costs for bespoke work, including hosting, security updates and improvements.
4. Switching costs if the product changes, raises prices or is discontinued.
5. Opportunity cost: what your team could do with the time a better tool gives back.

Once those are on the table, the gap between the two options is often much smaller, in either direction, than it first appears.

Questions to ask before you decide

• What exactly is slowing us down today, and how much time or money does it cost each month?
• Could we fix it by using our current tools differently, or connecting them?
• Is this process stable, or is it likely to change a lot in the next year?
• Who will own the system, look after it and ask for improvements?
• What is the smallest version that would solve the real problem?

Start small and grow it

If bespoke is the right route, resist the urge to build everything at once. The most successful projects start with a focused first version that removes the most painful problem, gets into real use quickly, and then grows based on what the team actually needs. That keeps costs predictable and avoids building features nobody uses.

It also pays to build on open, well-documented technology. Web-based systems built with widely used languages and frameworks are easier to host, support and extend, and you are never locked into a single supplier.

Consider connecting before building

Sometimes the answer is neither a new product nor a new system, but making the tools you already pay for talk to each other. Our article on business process automation covers where that tends to pay off fastest.

Frequently asked questions