Bespoke Software

Bespoke vs Off-the-Shelf Software: How to Decide

22 September 2026|6 min read

Bespoke and off-the-shelf are both right answers, for different businesses. The decision is about fit and control, not technology, and most of the bad outcomes we see come from answering it by reflex: a business that bought a package because it was cheaper on day one, or one that commissioned a build because a package felt beneath it. This guide compares the two on the things that matter, says when each wins, describes the hybrid that is often the real answer, and ends with a ten-question checklist.

The comparison

On	Off-the-shelf	Bespoke
Fit to your process	The vendor's idea of typical. You adapt to it.	Yours. The software adapts to you.
Upfront cost	Low. A subscription and some setup.	Higher. A fixed price per phase, quoted after discovery.
Running cost	Per seat, per month, for ever, rising with headcount.	Hosting in your own account. Optional support.
Ownership	You rent it. The data is exportable in theory.	You own the code, the database and the account.
Time to first use	Days.	Weeks. A first phase usually within eight weeks of sign-off.
Changing it	A feature request to a vendor, on their roadmap.	A phase of work, on your timetable.
Integration	Whatever the marketplace connectors cover.	Built to talk to what you have, including the awkward systems.
If the vendor disappears	You migrate, in a hurry.	Nothing changes. Any competent developer can pick it up.

When off-the-shelf wins

The process is standard for your industry, and you have no reason to be different
The team is small and will stay small
The job is accounting, payroll, email, or a brochure website with no integrations
You need it next week
You want the option of switching vendors later

In these cases a package will do the job for less, and we will say so. Configuring it well is a real skill, and a studio that only builds has a reason not to admit that.

When bespoke wins

The process is the advantage: the way you do it is why customers choose you
The package has become the bottleneck, with a workaround spreadsheet beside it
The real job is connecting systems that were never meant to meet
Licence costs, multiplied by headcount and years, would pay for a build
A legacy system has to be replaced anyway, so the choice is which new thing to build
You need audit trails or data handling the package cannot give you

The hybrid answer

Most businesses do not have to choose. Keep the accounts package, the email and the payroll. Build the layer that makes them work together: the portal that shows customers their invoices from the accounts system, the booking flow that writes to the job system, the dashboard that reads from all of them. The package does what it is good at and the bespoke part does what nothing off the shelf would. See bespoke systems for the shapes this usually takes.

The ten-question checklist

Answer yes or no. Six or more yes answers points to bespoke, or at least to the hybrid.

Is there a spreadsheet beside the package that is really the system?
Do people say “the system won't let us” more than once a week?
Does the package need to talk to two or more other systems?
Would you describe your process as different from your competitors'?
Is the licence cost rising with every hire?
Has the vendor said no to a feature you need?
Is any part of the current system tied to one PC or one person?
Would a regulator, insurer or auditor ask for records the package cannot produce?
Do you expect the process to change in the next two years?
Would you be in trouble if the vendor was bought or closed?

What to do next

If the checklist points to bespoke, the next step is discovery, not a quote. The Workflow Audit finds where the time actually goes and turns it into a scope. If it points to a package, we will help you choose and set it up, and what drives the cost explains why we would rather do that than build the wrong thing.