Skip to content

What is bespoke software, and when does it beat off-the-shelf?

By the E-Solutions Web editorial team. Published , updated . How we write

The short answer

Bespoke software is software built for one organization’s processes and owned by it, as opposed to off-the-shelf software, sold to many customers as a license or subscription. Off-the-shelf is faster and cheaper to start when it covers your process. Bespoke pays off when your process sets you apart, when packages force workarounds, or when you need to own the code and the data.

“Should we build it or buy it?” comes up in almost every software decision, and the honest answer is often a mix of both. This guide explains what bespoke software is, compares it with off-the-shelf products criterion by criterion, and points out the two contract questions most buyers only discover too late: who owns the code, and how you leave. It is not legal advice; the legal points below were read on the official texts on October 1, 2026.

What is bespoke software?

Bespoke software is software designed and built for one organization, around its own processes, users and systems, and owned by that organization once the rights are assigned. “Bespoke” is the British word; in the United States, people usually say custom software. Off-the-shelf software, sometimes called packaged software or COTS (commercial off-the-shelf), is one product sold to many customers, as a license or, more often today, a subscription.

Bespoke does not mean starting from a blank page. A bespoke application is usually built on standard frameworks, open-source components and cloud services, and connected to off-the-shelf tools you keep, such as your accounting package or your CRM. What is bespoke is the part that encodes your rules: how you price, plan, approve or serve customers. That is the part our custom software development work focuses on.

Typical examples of bespoke software:

  • A business application that runs a process no package handles well, such as quoting with your own pricing rules or planning around your sites and shifts.
  • A client portal where customers follow orders, files or requests without calling you.
  • An internal tool that replaces a critical spreadsheet, with access rights, history and checks the spreadsheet never had.
  • A layer that connects existing tools, so that data entered once flows to the ERP, the CRM and the reports.

Bespoke vs off-the-shelf software: the comparison

Off-the-shelf wins on speed and starting cost; bespoke wins on fit, ownership and control over the roadmap. The table compares them on the criteria that usually decide.

CriterionOff-the-shelf softwareBespoke software
Time to startDays or weeks: sign up, configure, trainWeeks or months before the first version is in production
Upfront costLow: setup and subscriptionHigher: design and development
Running costGrows with users, volume and optionsHosting and maintenance, which you budget yourself
Fit with your processYou adapt your process to the productThe software follows your process
RoadmapThe vendor decides what comes next, for all its customersYou decide what is built and when
IntegrationConnectors the vendor chose to offerBuilt for the systems you actually run
OwnershipYou hold a license; the code stays the vendor’sYou own the code if the contract assigns it
ExitDepends on export features and contract termsDepends on having the code, the documentation and the accounts

For market price ranges on either side, see our guide to custom software development cost, which lists what agencies, review platforms and surveys published in 2026, with their sources.

When off-the-shelf software is the right call

Buy when a product on the market covers most of your needs as it is, and your process is not what sets you apart. The UK government’s guidance on technology purchasing, updated on September 3, 2026, lists the cases where buying fits: a commercially available product meets most of your user needs, suppliers can configure it to your needs, you do not need a high level of customization or bespoke changes, the expertise and support you need are available on the market, and your organization has the capability to support what it buys.

The same guidance warns about a common trap: “Even small modifications to OTS software can remove most of the benefits of using it.” It recommends configuring settings rather than changing the product, so that the vendor’s new versions still work for you. Customizations and workarounds, it adds, can increase costs, make maintenance harder and restrict you from upgrading later.

Payroll, email, standard accounting and office tools are classic examples. Building them would cost more and bring nothing your customers would notice.

When bespoke software pays off

Build when the process the software supports is specific to you, when packages force your team into spreadsheets on the side, or when you need to own the technology. The same UK guidance lists the cases where building fits: a user need that is unique or rare, few suppliers able to meet your requirements, commercial products that cannot be scaled, adapted or integrated to meet your core needs, the need to own the technology to keep the freedom to modify it, and access to the capability to manage the project.

Three signs usually show that a company has reached that point:

  1. The workarounds have their own workarounds. Exports to spreadsheets, manual copy and paste between two tools, a colleague who checks everything by hand at the end of the month.
  2. The subscription grows faster than the value. Every new user, module or volume tier raises the bill for the same process.
  3. The rules that make you competitive live outside the software, in someone’s head or in a fragile spreadsheet.

When the need is an internal tool for one team or one process, our page on business applications shows what that looks like in practice. When customers are the users, a client portal is often the first bespoke piece worth building.

Bespoke software advantages and disadvantages

Bespoke software gives you fit and control, and asks you in return to fund the build, choose the team well and keep the software maintained. The trade-offs, side by side:

AdvantagesDisadvantages
Fits your process instead of forcing it to changeHigher upfront cost, and a wait before the first version
No per-seat fee that grows with each new userMaintenance and hosting are yours to budget
Integrates with the systems you already runQuality depends heavily on the team that builds it
You decide the roadmap and the release datesPoorly built software accumulates technical debt quickly
You can own the code, the data and the documentationOwnership only exists if the contract says so
AI features can be built in where they help, such as reading incoming documentsEach feature has to be specified, tested and documented

Most disadvantages are risks you can manage in the contract and in the way the project runs: a written scope and a fixed price before work starts, demos of working software every week, automated tests, and a maintenance plan agreed with the build.

Who owns the code: the clause to check

With bespoke software, ownership of the code is not automatic: it depends on the contract, and the law usually requires the transfer to be in writing. Three legal systems, read on October 1, 2026:

  • United States. A “work made for hire” is either a work prepared by an employee within the scope of employment, or a commissioned work in a short list of categories, with a signed written agreement (17 U.S.C. § 101). Software is not named on that list, so contracts with outside developers usually rely on an assignment, and a transfer of copyright ownership “is not valid unless” it is in writing and signed by the owner of the rights (17 U.S.C. § 204).
  • United Kingdom. The author is the first owner of copyright, and an employer owns works made by employees in the course of their employment (Copyright, Designs and Patents Act 1988, section 11). For an outside contractor, section 90(3) applies: “An assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor.”
  • European Union countries have their own rules. In France, for instance, assignment clauses are usually drafted on the model of Article L131-3 of the Intellectual Property Code, which lists each right transferred and limits its scope, place and duration.

Without an assignment, the developer can remain the owner and grant you only a license, which makes changing supplier hard. The GOV.UK guidance asks public buyers for contracts that are explicit about the ownership of data and of intellectual property, “including software code and the business rules.” Any buyer should ask the same. On our projects, the code, the accounts and the rights are yours.

Leaving: what the Data Act covers, and what it does not

For cloud and SaaS products, the EU Data Act now protects your right to switch provider; for bespoke services, it protects you less, and your contract has to do the rest. The Data Act, Regulation (EU) 2023/2854, has applied since September 12, 2025. It requires contracts for data processing services to let customers switch provider or move their data to their own infrastructure, with a maximum transition period of 30 calendar days (Article 25). From January 12, 2027, providers may no longer charge switching fees (Article 29).

There is an exception that matters here. Article 31 says the switching-fee rule and some technical obligations do not apply to services whose main features have mostly been “custom-built to accommodate the specific needs of an individual customer,” when those services are not offered at broad commercial scale. In other words, for bespoke software hosted by a supplier, the regulation gives you fewer guarantees. Write the exit into your contract, with the source code, documentation, data export and access handed over at the end.

Combining off-the-shelf and bespoke software

For most companies, the best answer combines both: standard products for the standard jobs, and bespoke software for the process that makes the difference, connected to the rest. Before deciding, write one page that lists the process, its users, the tools it must talk to and the workarounds it causes today. That page tells you quickly whether a package can carry it.

If part of that process is reading documents, such as orders, invoices or delivery notes, our document extraction demo shows what an AI feature inside bespoke software can do with them.

Bring your one-page list to a free 30-minute assessment. We tell you which parts a product on the market already covers, which part is worth building, and what would move the price. The scope and price are fixed in writing before we start. Book your free 30-minute assessment: we reply within one business day.

Frequently asked questions

What is bespoke software?

Software designed and built for a single organization, around its own processes, users and systems. It is also called custom software, and "bespoke" is the word British buyers often use. The organization that commissions it normally owns it, provided the contract assigns the rights. Off-the-shelf software, by contrast, is one product sold to many customers.

What is an example of bespoke software?

A quoting tool that applies a manufacturer’s own pricing rules, a client portal where customers follow their orders, an internal app that replaces a critical spreadsheet, or a planning tool built around a company’s shifts and sites. Each one encodes rules that no package on the market knows, and connects to the systems the company already runs.

What are the disadvantages of bespoke software?

A higher upfront cost, a longer wait before the first version, and maintenance that is yours to fund. Quality depends heavily on the team that builds it, and poorly built bespoke software accumulates technical debt quickly. These risks shrink with a written scope, a fixed price, regular demos and a contract that hands you the code and the documentation.

Is bespoke software more expensive than off-the-shelf?

At the start, almost always. Over several years, it depends on how the subscription grows with users and volume, and on how many workarounds the package forces on your team. Compare the total cost over three to five years, including licenses, integration, training and the time lost to workarounds. Our guide to custom software development cost gives sourced market ranges.

Who owns the code of bespoke software?

The contract decides. Under US law, a transfer of copyright must be in writing and signed; under UK law, an assignment is not effective unless it is in writing and signed by the assignor. Without such a clause, the developer can remain the owner and grant you only a license. Ask for an explicit assignment of the code, the documentation and the data.

Sources

  1. Define your purchasing strategy (Technology Code of Practice, point 11), Government Digital Service and Central Digital and Data Office, GOV.UK, updated September 3, 2026, accessed October 1, 2026.
  2. 17 U.S. Code § 101, Definitions (work made for hire), Legal Information Institute, Cornell Law School, accessed October 1, 2026.
  3. 17 U.S. Code § 204, Execution of transfers of copyright ownership, Legal Information Institute, Cornell Law School, accessed October 1, 2026.
  4. Copyright, Designs and Patents Act 1988, section 11 (first ownership of copyright), legislation.gov.uk, The National Archives, accessed October 1, 2026.
  5. Copyright, Designs and Patents Act 1988, section 90 (assignment of copyright), legislation.gov.uk, The National Archives, accessed October 1, 2026.
  6. Regulation (EU) 2023/2854 on harmonised rules on fair access to and use of data (Data Act), EUR-Lex, Official Journal of the European Union, published December 22, 2023, accessed October 1, 2026.
  7. Code de la propriété intellectuelle, article L131-3, Légifrance, in force since July 3, 1992, accessed October 1, 2026.

And in your company?

Describe the work you want back. We reply within one business day.

We reply within one business day and only use your message for that. Privacy