What is bespoke software? A plain-English guide with examples

Bespoke software is software built for one business and the way it works. What that means in practice, the kinds of things companies actually have built, and how to tell whether you need it.

Bespoke software, also called custom software, is software built for one particular business, around the way that business actually works. Rather than buying a product designed for thousands of companies and adjusting your process to fit it, you have a system made to fit your process.

The idea sounds grand, but most bespoke software is not. It is usually a fairly small, focused tool that does one job well: a quoting system, a booking screen, a dashboard that pulls figures from three places into one. This guide explains what the term really covers, gives examples of the kinds of things businesses have built, and sets out how to tell whether it is something you need.

Bespoke versus off-the-shelf

Off-the-shelf software is a ready-made product you subscribe to or buy: your accounting package, your email, a general CRM, an online shop builder. It is designed for the common case, which is exactly why it is good value. Somebody else builds it, maintains it and spreads the cost across every customer.

Bespoke software is designed for your case. The trade is straightforward. You get a system that matches how you work, that you own, and that can change when your business changes. In return you pay for the build yourself and wait for it to be made.

Most businesses use both. They keep ready-made products for the ordinary work and have something built only where their way of working is genuinely different. We cover how to make that call in custom software or off-the-shelf: how to choose.

Examples of bespoke software

The easiest way to understand bespoke software is to look at the problems it usually solves. These are typical of what businesses have built, from small firms to large ones.

A quoting and job management system

A trades or installation business prices every job from a spreadsheet full of rates, then copies the result into a document, then re-keys the accepted job into a diary. A bespoke system holds the rates, produces the quote, turns an accepted quote into a scheduled job with one click, and shows the office which jobs are booked, started and finished.

A customer portal

A service business answers the same questions by phone and email all day: where is my order, can I see my documents, when is my next appointment. A portal lets customers log in and see their own information, so the questions stop and the staff time goes back into the work.

A custom CRM

General CRMs are built around a sales pipeline. Plenty of businesses do not sell that way. A membership organisation, a recruiter or a lettings agent may need to track relationships that look nothing like "lead, prospect, customer". A bespoke CRM records what that business actually needs to know about its contacts and nothing else. We look at when this is worth it in custom CRM development: when it is worth it and what to expect.

Connecting systems that do not talk to each other

Sometimes the right answer is not a new system at all, but a link between the ones you already have. Orders from the website flow into the stock system, invoices into the accounts package, new sign-ups into the mailing list, with nobody copying anything between screens. This kind of integration work is bespoke software too, even though the people using it may never see a new screen.

Internal tools and dashboards

Managers often spend the start of each week assembling one report from several sources. A small internal dashboard pulls those figures together automatically, so the report is always up to date and nobody spends a Monday morning building it.

Replacing a spreadsheet that has become a system

This is the most common starting point of all. A spreadsheet that began as a simple list has grown into the thing the business depends on, with several people editing it, formulas nobody dares touch and copies saved under different names. Turning it into a proper application keeps everything the spreadsheet did well and removes the risk. If that sounds familiar, these are the signs your business has outgrown its spreadsheet.

What bespoke software is not

A few things get called bespoke software that are not quite the same.

A configured product. Setting up a ready-made CRM with your own fields and stages is configuration, not a bespoke build. It is often the right first step, and cheaper, but you are still working within somebody else's product.

A no-code app. Tools that let you assemble an app from building blocks sit between the two. They are quick for simple jobs and prototypes, and they can be a sensible way to test an idea. You remain tied to that platform's pricing, limits and future, which matters more as the app becomes important to the business.

Built from nothing. Bespoke does not mean every line is written from scratch. Good custom software is built on well-established, widely used foundations, with the bespoke part being the bit that reflects your business. That keeps it reliable and means another developer could pick it up later.

Who owns it

With bespoke software, ownership is one of the main reasons to build. Check before you start that the agreement gives your business the rights to the software and its code, and that you will be given access to it. You should never be in a position where only the original developer can keep your system running.

Ownership also brings responsibility. Bespoke software needs looking after once it is live: security updates, small fixes, and changes as the business evolves. Agree how that will happen at the start, rather than discovering the question after launch.

How to tell whether you need it

Bespoke software tends to be worth considering when several of these are true:

  • the work in question is central to how you win or deliver business, not routine admin
  • you have tried ready-made products and ended up with workarounds and side spreadsheets
  • information is being typed into more than one system by hand
  • per-user subscription costs climb steeply as you hire
  • the process is settled, so you know what you want the system to do

If only one of those applies, a ready-made product is very likely the better answer, and there is nothing wrong with that.

Where to start

You do not need a specification to have the conversation. The most useful starting point is a plain description of the problem: what happens today, where time is lost, and what you would like to be different.

Tell us what you are trying to fix and we will say honestly whether something bespoke would earn its keep or whether a product you can buy would do the job. Get in touch and you will get a straight answer either way.

Thinking about something like this?

We are happy to tell you when software is not the answer. If it is, we will give you a realistic view of what it takes.

Name
Email
Phone
How can we help?
I have read the privacy policy