What is bespoke software?

Bespoke software is software written for one organisation, around the way that organisation actually works. Off-the-shelf software is written for a market and asks every customer to work the same way. The difference sounds small and decides almost everything that follows: what it costs, how long it takes, who owns it, and whether it still fits in three years.

Three ways to get software

Most businesses end up with a mixture of all three, and the right question is which jobs belong in which.

Off-the-shelf. You buy a subscription to a product built for thousands of customers. Email, accounts, payroll, document storage and most booking systems live here, and should. The product is cheap because the cost is shared, it is maintained by someone else, and your process is not special enough to need anything different.

Configured. You buy a platform and shape it: a CRM with custom fields and pipelines, a project tool with your own templates, a no-code automation that moves data between the two. This covers a lot of ground and is often the right first step. The limit is that you are still working inside someone else's model of the job. When the model and the job diverge, the workarounds start, and the workarounds are where the hours go.

Bespoke. Someone builds the thing itself: a database shaped like your records, screens shaped like your tasks, rules shaped like your rules. It costs more up front than a subscription, it takes longer to arrive, and it does exactly what you need and nothing you do not. Done properly, you own it.

When bespoke is the right answer

A few signals are reliable.

• The process is the business. If the way you do the work is what customers pay for, a tool that forces a generic process is quietly eroding the thing that makes you different.
• The workarounds have become the system. Five subscriptions, a shared spreadsheet that reconciles them, and one person who knows how it all fits together. That person is a single point of failure and the spreadsheet is unpaid software.
• The same job is done many times over. An awards operator running nine programmes was chasing the same photos, bios and confirmations nine times over. A system that knows the cycle does the chasing once.
• The data lives in three places. When answering a simple question means opening three tools and a calculator, the cost is not the minutes, it is the questions nobody asks because the answer is too much trouble.
• You have outgrown the configuration. The platform's custom fields are full, the automations have exceptions to the exceptions, and each new client or product needs a workaround.

When it is not

Bespoke is often the wrong answer.

• The need is a commodity. Nobody should build their own email, accounting or payroll.
• It is a one-off. A job that happens once does not need a system; it needs an afternoon.
• Nobody will own it. Software needs someone on your side who understands what it does and can say when it should change. Without that person, the best-built system drifts.
• You have not tried the configured version. If a well-set-up platform has never been tested against the job, it is too early to know that it fails.

What "bespoke" means now

Ten years ago a bespoke build meant a long specification, a large team and a launch date that slipped. Two things have changed.

The first is that building is faster. AI-assisted development often shortens the time to a working first version, which makes a small build practical for a single-site business that could not have justified one before.

The second is that building faster has made the other half of the job more important, not less. Anyone can produce a prototype in an afternoon now. What is hard is understanding the work well enough to build the right thing, and building it properly enough that it survives real users, real data and a business that keeps changing. A demo that impresses in a meeting is not a system. The difference between the two is still the difference between advice and a developer, and the best outcomes come when the same person does both.

Two examples

An operations platform for nine awards programmes. Care Events UK runs the Great British Care Awards and eight sister programmes, each with the same annual cycle of nominations, judging, finalists and a gala evening. Until 2026 it all ran on spreadsheets, inboxes and memory. The bespoke answer was one multi-tenant system with a programme switch in the top bar: finalist portals, automated chasing, judging schedules, nomination forms and a document vault, live since September 2026.

Kitchen tools for a single pub. The Plough in Harborne wanted the tooling larger groups take for granted, built around its own kitchen. The result was a set of small working tools rather than one big system: a hiring assessment, a menu checker that tests a draft against the kitchen's own station and cook-time data, a competitor monitor, and a recipe database that produces costing and allergen documents. Each was scoped, built and handed over as a working piece rather than a roadmap.

Questions to ask before you commission anything

1. What is the one number this should move, and how will we measure it before and after?
2. Which jobs stay in the tools we already pay for, and which one job is this for?
3. Who on our side will own it once it is live?
4. Who owns the code, the hosting and the data, and in whose name are the accounts?
5. What is the smallest first piece that would prove the number, and what does it cost?

If the person you are talking to cannot answer the last one with a fixed price and a timescale, the scope is not yet clear enough to buy.

Where to start

The honest starting point is not a specification. It is a conversation about where the hours go, followed by the smallest build that would give some of them back. If that is a configured platform, say so. If it is bespoke, keep the first piece small enough that the number is visible early, ideally within the first month.