Software Development
What Is Bespoke Software? Meaning, Examples and When You Need It
Written by Tehreem FatimaReviewed by Umaid Asim
Published 14 min read

Bespoke software is software designed and built for one business, around the way that business works. Instead of buying a ready-made product and changing your process to fit it, you commission software that follows your process. You decide what it does, it connects to the systems you already use, and with the right contract you own the code.
Most UK firms already run on software. In 2023, 69% of UK firms with at least 10 employees used cloud-based computing systems, and 61% used specialised software Source [1]. So the real question is rarely whether to use software. It is whether to buy a product, adapt one, or have something built.
This article is for UK business owners and managers weighing up that choice. It explains what bespoke software means, gives 12 bespoke software examples, and shows the in-between options that often cost less. It also covers who owns the code, what it costs, and how to tell whether your business needs it.
What Does Bespoke Software Mean?
Bespoke software means software made for one particular business rather than for a whole market. A supplier, or your own team, designs and builds it around your workflows, users and data. It is the opposite of off-the-shelf software, which is built once and sold to many customers with similar needs.
"Bespoke" is a British word best known from tailoring, where a bespoke suit is made for one person. Cambridge Dictionary marks it as UK English and defines it as "specially made for a particular person, organization, or purpose". It even gives "bespoke software" as an example Source [2]. A bespoke system can be an internal tool used by five staff, a portal used by thousands of customers, or the product your business sells.
Is Bespoke Software the Same as Custom Software?
Yes. Bespoke software and custom software mean the same thing, as do tailor-made and made-to-measure software. The Oxford Learner's Dictionary labels bespoke as especially British English and notes that North American English usually says custom-made Source [3]. So UK suppliers tend to say bespoke, and US firms custom.
Bespoke vs Off-the-Shelf Software at a Glance
Off-the-shelf software is ready-made and sold to anyone who needs it. NIST, the US standards body, describes commercial off-the-shelf products as "ready-made and available for purchase by the general public" Source [4]. Bespoke software is the reverse: built for one buyer, slower to start and more expensive upfront, but shaped entirely around that buyer.
| Aspect | Off-the-shelf software | Bespoke software |
|---|---|---|
| Built for | Many businesses with similar needs | One business and its own process |
| Upfront cost | Low: a subscription or licence fee | Higher: you pay for design and build |
| Time to start | Days or weeks | Usually months |
| Fit | You adapt your process to the product | The software follows your process |
| Ownership | You hold a licence; the vendor owns the software | You can own the code, if your contract says so |
| Changes | The vendor decides what changes and when | You decide, and pay for the work |
| Ongoing costs | Often a fee per user, per month | Hosting, support and new features |
Built for
- Off-the-shelf software
- Many businesses with similar needs
- Bespoke software
- One business and its own process
Upfront cost
- Off-the-shelf software
- Low: a subscription or licence fee
- Bespoke software
- Higher: you pay for design and build
Time to start
- Off-the-shelf software
- Days or weeks
- Bespoke software
- Usually months
Fit
- Off-the-shelf software
- You adapt your process to the product
- Bespoke software
- The software follows your process
Ownership
- Off-the-shelf software
- You hold a licence; the vendor owns the software
- Bespoke software
- You can own the code, if your contract says so
Changes
- Off-the-shelf software
- The vendor decides what changes and when
- Bespoke software
- You decide, and pay for the work
Ongoing costs
- Off-the-shelf software
- Often a fee per user, per month
- Bespoke software
- Hosting, support and new features
Neither column wins outright. A UK firm might run off-the-shelf accounting and email, and still need a bespoke system for the one process that sets it apart.
Five Ways to Get Software That Fits Your Business
Buying a product and building from scratch are not the only choices. Between them sit three middle options: configure a product, connect the tools you already use, or extend a platform with your own screens. A business can often solve the problem at one of these steps, for less money and in less time than a full build.

Start at the left and move right only when the option before cannot do the job.
- Use as it is. Sign up and use the product's standard features. This is the quickest and cheapest route for common needs such as payroll, accounts and email.
- Configure. Change settings, fields and workflows that the product already offers, such as adding your own sales stages to a CRM (customer relationship management system).
- Connect. Link two or more existing tools so data moves between them without retyping. Orders from a web shop flowing into your accounts package is a typical example. When one of the connected tools is an AI agent, our guide to AI agent integration covers how to do it safely.
- Extend. Build your own screens or features on top of a platform you already pay for. Microsoft's Power Apps, for example, is built to let businesses "build custom apps for your business needs" on top of its platform Source [5].
- Build bespoke. Design and build new software around your process, when nothing on the market fits without costly workarounds.
The UK government's own technology guidance warns against the trap in the middle. It tells teams to use off-the-shelf products "as they were intended". The reason it gives: "even small modifications to OTS software can remove most of the benefits of using it" Source [6]. It adds that customisations and workarounds can increase costs, make maintenance harder and stop you upgrading later Source [6]. In practice, that means either configure a product cleanly or build properly. A heavily patched package can end up harder to run than either.
Bespoke Software Examples
Bespoke software examples range from small internal tools to full products. What they share is a problem that off-the-shelf tools handle badly. It might be a process specific to the business, data spread across several systems, or customers who need a service built around them. Table 2 lists 12 common examples and the problem each one fixes.
| Type | Bespoke software example | The problem it fixes |
|---|---|---|
| Used by customers | Client portal | Customers chase updates by phone and email; a portal shows status, documents and invoices in one place |
| Used by customers | Booking and scheduling system | Bookings depend on rules a standard tool cannot hold, such as staff skills, equipment or site capacity |
| Used by customers | Quoting and pricing tool | Quotes are worked out in spreadsheets, so two staff can price the same job differently |
| Runs the business | Job management system | Jobs are tracked across whiteboards, spreadsheets and messages, with no single record from enquiry to invoice |
| Runs the business | Stock and order system | Stock levels live in several places and orders are oversold or delayed |
| Runs the business | Mobile app for field staff | Engineers fill in paper forms, take photos on their own phones and type everything up later |
| Connects and automates | Integration between existing tools | Staff copy orders, customers or invoices from one system into another by hand |
| Connects and automates | Live reporting dashboard | Managers wait for monthly reports built from exported spreadsheets |
| Connects and automates | Approval workflow | Approvals happen over email, with no record of who agreed what and when |
| Replaces or adds | Legacy system replacement | An old system runs a key process, but nobody can safely change it |
| Replaces or adds | AI document processing | Staff read PDFs, forms and emails and key the details into another system |
| Replaces or adds | Software product (SaaS) | The software is what the business sells, so it has to be its own |
Type
Used by customers
- Bespoke software example
- Client portal
- The problem it fixes
- Customers chase updates by phone and email; a portal shows status, documents and invoices in one place
Type
Used by customers
- Bespoke software example
- Booking and scheduling system
- The problem it fixes
- Bookings depend on rules a standard tool cannot hold, such as staff skills, equipment or site capacity
Type
Used by customers
- Bespoke software example
- Quoting and pricing tool
- The problem it fixes
- Quotes are worked out in spreadsheets, so two staff can price the same job differently
Type
Runs the business
- Bespoke software example
- Job management system
- The problem it fixes
- Jobs are tracked across whiteboards, spreadsheets and messages, with no single record from enquiry to invoice
Type
Runs the business
- Bespoke software example
- Stock and order system
- The problem it fixes
- Stock levels live in several places and orders are oversold or delayed
Type
Runs the business
- Bespoke software example
- Mobile app for field staff
- The problem it fixes
- Engineers fill in paper forms, take photos on their own phones and type everything up later
Type
Connects and automates
- Bespoke software example
- Integration between existing tools
- The problem it fixes
- Staff copy orders, customers or invoices from one system into another by hand
Type
Connects and automates
- Bespoke software example
- Live reporting dashboard
- The problem it fixes
- Managers wait for monthly reports built from exported spreadsheets
Type
Connects and automates
- Bespoke software example
- Approval workflow
- The problem it fixes
- Approvals happen over email, with no record of who agreed what and when
Type
Replaces or adds
- Bespoke software example
- Legacy system replacement
- The problem it fixes
- An old system runs a key process, but nobody can safely change it
Type
Replaces or adds
- Bespoke software example
- AI document processing
- The problem it fixes
- Staff read PDFs, forms and emails and key the details into another system
Type
Replaces or adds
- Bespoke software example
- Software product (SaaS)
- The problem it fixes
- The software is what the business sells, so it has to be its own
Several of these overlap with other services. A field staff app is often a mobile app development project, and AI document processing is a common AI automation project. If you are unsure an AI idea will work, a short AI proof of concept tests it before you commit to a full build.
Bespoke Software SensViz Has Built
SensViz has designed and built several software products, each around a clearly defined user and task:
- GrantMatch: a grant discovery platform that combines user profiles, language models, recommendation logic and vector search to surface relevant funding opportunities.
- Playano Education: an interactive piano-learning application that uses computer vision to read hand movement and give visual guidance during practice.
- SIPP: a water-quality product that uses sensor data and time-series forecasting to support monitoring.
- AR Tile: a floor-visualisation experience that uses computer vision and augmented reality to let customers preview flooring in their own space.
Advantages and Disadvantages of Bespoke Software
The main advantage of bespoke software is fit: it follows your process, connects to your systems and changes when you decide. The main disadvantages are a higher upfront cost, a longer wait before you can use it, and paying for its upkeep. Whether that trade is worth it depends on what the fit is worth to you.
Advantages
- It fits the way you work. Staff stop running side spreadsheets and workarounds to make a product behave.
- You control the roadmap. You decide which features come next, rather than waiting for a vendor.
- It connects to what you already use. Integrations are designed in from the start.
- No per-user fees. Adding staff does not add a monthly licence for each one, although hosting and support still cost money.
- You can own it. With a written assignment, the code is an asset of your business (see the ownership section below).
Disadvantages
- Higher upfront cost. You pay for design, building and testing before anyone uses it.
- It takes longer. A ready-made product can be live in days; a bespoke system usually takes months.
- You pay for upkeep. Security updates, fixes and changes to connected systems all need budget. Neglect is expensive. In UK central government, keeping legacy systems running often costs "3 to 4 times that of modern alternatives" Source [7].
- It depends on the brief and the supplier. A vague brief or a weak team produces software that fits nobody.
When Does a Business Need Bespoke Software?
A business needs bespoke software when its process is specific to it, or is part of how it wins work. The second condition is that no product can be configured or connected to handle that process without workarounds. If a ready-made product covers most of the need, buying and configuring it is usually the better choice.

The UK government's purchasing guidance gives a useful test. Building makes sense when your "user need is unique or rare", or when you cannot adapt or integrate commercial products to meet your core needs. It also makes sense when you need to own your technology so you can keep changing it Source [6]. Buying makes sense when "there is a commercially available way to meet most of your user needs" Source [6]. The Government Digital Service puts it more bluntly. Most needs "are more likely to be common than unique", so build what is core to your business and buy the rest Source [8]. If you want to score your own decision, Fossilite's build vs buy software guide walks through a weighted scoring sheet and a three-year cost comparison.
For a private business, the signs usually look like this:
- Your process is your advantage. The way you quote, schedule or serve customers is part of why clients choose you.
- Workarounds are eating time. Staff copy data between tools, keep shadow spreadsheets or check every result by hand.
- No product fits without heavy customisation. You have tried the obvious tools and each needs patching to work.
- Licence costs keep climbing. Per-user fees grow with every hire, for a product you only half use.
- You need systems to talk. Your tools cannot share data, and no ready-made connector does what you need.
The signs point the other way when the process is standard, such as payroll, accounts or email. They also point away from a build when configuration covers most of what you need, or when there is no budget to maintain software after launch.
Who Owns Bespoke Software?
In the UK, whoever writes the code owns its copyright first, unless a written agreement says otherwise. Code written by your own employees in the course of their work belongs to your business. Custom software written by an outside supplier stays with the supplier until they assign it to you in a written, signed document.
UK law treats a computer program, and the design material behind it, as a literary work Source [9]. The author is the first owner. The main exception is work made by an employee in the course of employment, which belongs to the employer unless agreed otherwise Source [10]. An assignment of copyright "is not effective unless it is in writing", signed by or for the person assigning it Source [11]. GOV.UK's own guidance says a contractor "will usually retain copyright" in the work they produce. Without a contract, a client may only have an implied licence to use it Source [12].
This matters in practice. In Clearsprings v Businesslinx, a company hired a software developer to build its management information system without a written assignment. The High Court found it held only "a non-exclusive, personal licence" under the copyright, with no right to license the system to others Source [13]. Off-the-shelf software works this way by design: you buy a licence to use it, not the software itself.
So before a project starts, agree in writing what you will receive at the end:
- a signed assignment of copyright in the code written for you
- the source code, in a repository your business controls
- admin access to every hosting, domain and third-party account
- technical documentation, and a list of any licensed components the system relies on
This is general information, not legal advice. Ask a solicitor to check the contract wording. Our guide to bespoke software cost in the UK covers the other contract points that change what you pay.
How Much Does Bespoke Software Cost?
At current UK contractor day rates, bespoke software costs roughly £9,000 to £36,000 for a small tool. A business system with several workflows costs about £27,000 to £120,000, and a complex platform £90,000 or more. Discovery, testing and contingency come on top, and running costs start after launch.
Those ranges come from multiplying typical effort by UK software developer contract rates. Our full guide to bespoke software cost in the UK shows the working, a worked example and the three-year cost of ownership. To compare bespoke software with a subscription, set its build and running costs against the subscription's per-user fees. Use the same period for both, such as three or five years.
How Bespoke Software Is Built
Most bespoke software development follows five stages: discovery, scoping and design, building in small releases, testing and launch, then support and improvement. Good suppliers show you working software early and often, so problems surface while they are still cheap to fix.
- Discovery. The team learns how the work happens today: the users, the rules, the exceptions and the systems involved. You provide access to the people who do the work.
- Scope and design. You agree what the first release must do, how screens and workflows will look, and how the system will connect to others.
- Build in small releases. Developers build in short cycles and show progress as they go. Your feedback after each release shapes the next one.
- Testing and launch. The team tests the main journeys, the business rules, permissions and integrations. Your own staff then test it against real work before release.
- Support and improvement. After launch, the supplier fixes issues, keeps the system secure and adds features as real use shows what is needed.
How SensViz Builds Bespoke Software
SensViz builds bespoke software for businesses in the UK and beyond, with regional offices in London and Lahore. Every project starts with the decision rather than the build. The team looks at what could be bought, configured, connected or improved first. It recommends a custom system only when a simpler option will not do the job.
First releases focus on the most important journeys. You see working software early and can test the riskiest assumptions before the scope grows. Ownership is defined in writing: the code, data, infrastructure, accounts, documentation and third-party components. Support can continue after launch. Projects start from $5,000 (about £4,000), and the final figure depends on what your software needs to do.
To find out more, see SensViz's bespoke software development service. If you are still comparing suppliers, our list of software development companies in the UK shows what to look for. When you are ready, talk to the SensViz team about your project.
Frequently Asked Questions
Short answers to the questions UK businesses ask once they start comparing options.
Is Bespoke Software Worth It for a Small Business?
Bespoke software is often worth it for a small business when it replaces a costly manual process or several subscriptions. Start small: one workflow, a few users, and a first release of 20 to 60 days. Compare its build and running cost over three years with the per-user fees you pay today.
How Long Does It Take to Build Bespoke Software?
Building bespoke software usually takes one to three months for a small tool and three to six months for a business system with several workflows. Complex platforms take six months or more. Team size, the speed of your feedback and the state of any systems it must connect to all move the date.
Can Bespoke Software Work With the Systems We Already Use?
Bespoke software can usually work with your existing systems through their APIs, the published connections that let one system send data to another. Many cloud tools publish one. Older or locally installed systems may not, which can mean exporting files on a schedule or replacing that part of the setup.
Is SaaS the Same as Bespoke Software?
SaaS (software as a service) is not bespoke or custom software. It is off-the-shelf software you use online for a subscription. NIST's definition says SaaS users get only "limited user-specific application configuration settings" Source [14]. You configure it, but the provider controls the product, its features and its release schedule.
Can We Get the Source Code if Our Software Supplier Goes Out of Business?
You can protect access to your source code if your supplier fails. The simplest way is to own the code and hold it in your own repository. If the supplier keeps ownership, it can deposit the code with an independent escrow agent. The code is then released to you on agreed events, such as the supplier becoming insolvent Source [15].
Thinking about bespoke software?
Talk to the SensViz team about how your business works, and get a straight view on whether to buy, adapt or build.
Sources
- [1] Office for National Statistics. Office for National Statistics: Management practices and the adoption of technology and artificial intelligence in UK firms, 2023 (24 March 2025) (opens in a new tab).
- [2] Cambridge Dictionary. Cambridge Dictionary: bespoke (opens in a new tab).
- [3] Oxford Learner's Dictionaries. Oxford Learner's Dictionaries: bespoke (opens in a new tab).
- [4] NIST. NIST Computer Security Resource Center: Glossary, commercial off-the-shelf (COTS) (opens in a new tab).
- [5] Microsoft. Microsoft Learn: What is Power Apps? (opens in a new tab).
- [6] GOV.UK. GOV.UK: Define your purchasing strategy (Technology Code of Practice) (opens in a new tab).
- [7] GOV.UK. GOV.UK: State of digital government review (21 January 2025) (opens in a new tab).
- [8] Government Digital Service. Government Digital Service technology blog: To build or to buy, that's the technology question (3 February 2021) (opens in a new tab).
- [9] legislation.gov.uk. legislation.gov.uk: Copyright, Designs and Patents Act 1988, section 3 (opens in a new tab).
- [10] legislation.gov.uk. legislation.gov.uk: Copyright, Designs and Patents Act 1988, section 11 (opens in a new tab).
- [11] legislation.gov.uk. legislation.gov.uk: Copyright, Designs and Patents Act 1988, section 90 (opens in a new tab).
- [12] GOV.UK. GOV.UK: Ownership of copyright works (opens in a new tab).
- [13] The National Archives. The National Archives, Find Case Law: Clearsprings Management Ltd v Businesslinx Ltd (High Court, 2005) (opens in a new tab).
- [14] NIST. NIST Special Publication 800-145: The NIST Definition of Cloud Computing (opens in a new tab).
- [15] Cabinet Office. Cabinet Office: Model Services Contract, Guidance for Authorities, version 2.2A (September 2025) (opens in a new tab).





