Bespoke Software Development in the UK: What Decides the Cost, When Off-the-Shelf Wins, and What to Put in the Contract

The Short Answer

Bespoke software development is worth paying for when the way your business works is the thing that makes it money, and no off-the-shelf product fits that way of working without expensive compromises. It is the wrong choice when a mainstream tool already does the job and the only problem is that nobody has set it up properly. What a bespoke build costs is decided by four things far more than by any day rate: how many distinct jobs the software has to do, how many systems it has to talk to, how messy the data it inherits is, and how much of it has to work offline, on mobile or for the public rather than just your team.

Every BigBerri project is quoted as one fixed price against a written scope after a free discovery call, so this guide does not publish figures. It sets out what moves the number, how the three realistic routes compare, and the handful of contract points that decide whether you actually own what you paid for.

Bespoke, Customised or Off-the-Shelf: The Three Real Routes

Most businesses asking about "custom software" are really choosing between three things, and the honest answer is often the middle one.

If you recognise your business in the first column, keep your money and spend a few days configuring the tool properly. If you are in the second column, a customised platform is usually cheaper and lower-risk than starting from nothing. Bespoke earns its place in the third column, and in the cases below.

When Bespoke Software Is Genuinely Worth It

Your team re-keys the same information into two or three systems every day. A bespoke layer, or a bespoke system that replaces the patchwork, removes the re-keying and the errors that come with it. This is the most common reason UK businesses commission software, and often it is an integration project rather than a whole new system — see AI Integration.

Your pricing, scheduling or allocation rules are too specific for any product. A haulier planning loads around its own customers and vehicles, a clinic group with rules about which practitioner sees which patient, a manufacturer quoting from its own cost model. Off-the-shelf tools handle the general case; your margin often lives in the specific one. Our page for AI for Logistics & Haulage Companies shows how that plays out in one sector.

You are building a product to sell, not a tool to use. If the software is the business — a platform, a portal your customers pay for, an app — renting someone else's product is not an option. That is usually an MVP first; MVP Development covers how we scope the first version.

Per-seat subscriptions have outgrown the value. When a growing team pays per user, per month, for a tool it uses a fraction of, a one-off build with modest running costs can be the cheaper path over a few years. Do that sum on your own numbers before anyone sells it to you.

What Actually Decides the Cost

The number of distinct jobs. "A system for our business" is not a scope. Taking an enquiry, quoting, booking, invoicing and reporting are five jobs, each with its own screens, rules and edge cases. The cost follows the list, which is why the discovery call spends most of its time making that list.

Integrations. Every system the software reads from or writes to — accounts, CRM, payments, a supplier's portal — is its own piece of work, and its difficulty depends on what that system exposes. A documented modern API is quick; an old system with no API is not. AI Integration Cost UK: What Actually Decides the Price in 2026 explains that split in detail, and it applies to ordinary software just as much as to AI.

The data you inherit. Moving years of records out of spreadsheets or an old system is often a larger job than people expect, because the data is rarely as clean as it looks. Budget time for cleaning and checking it, not just copying it.

Who uses it, and on what. An internal tool for five colleagues on laptops is a different build from a customer-facing portal that must be accessible, work on every phone, handle strangers signing up and stand up to abuse. Mobile apps add store review and two platforms — What Decides What It Costs to Build an App in the UK? A 2026 Guide covers that route.

Security and compliance. Personal data, payments, health information and regulated sectors each add real work: access controls, audit logs, testing and documentation. That work is not optional, and a quote that leaves it out is not cheaper, only incomplete.

Who Owns the Code: Read This Before You Sign

This is the point UK businesses most often get wrong, and it is written into law rather than left to good faith.

Under the Copyright, Designs and Patents Act 1988, copyright in a work belongs to the person who creates it. The National Archives' own guidance on commissioned work spells out what that means in practice: unless the commissioning contract assigns the copyright, it stays with the creator. Paying for software does not, on its own, make you the owner of it. An employee's work is generally owned by the employer; a contractor's or agency's is not, unless the contract says so.

So the contract should say, in plain words, that the copyright in everything written for you is assigned to your company on payment. It should also say that the source code, the repository and every hosting, domain and app-store account are held in your company's name, not the supplier's. If a supplier resists either, ask why. At BigBerri both are standard: the code, repository and accounts are set up in your company name, so ending the relationship never ends the software.

The Other Clauses Worth Insisting On

A data processing agreement. If the software handles personal data — customers, patients, staff — the developer is very likely a processor for UK GDPR purposes. The ICO's guidance on contracts between controllers and processors is clear that Article 28 requires a written contract, including that the processor acts only on your documented instructions, keeps the data secure, does not bring in sub-processors without your authorisation, helps you respond to people's rights requests, and deletes or returns the data when the contract ends.

A security baseline. Cyber Essentials is the government-backed scheme run by the National Cyber Security Centre, built on five technical controls: firewalls, secure configuration, user access control, malware protection and security update management. The NCSC updated its requirements for assessments carried out in 2026, including stricter rules on multi-factor authentication. Ask any supplier whether they hold it, and if you sell to the public sector, check whether your own contracts will require it of the software too.

Change control. A written process for what happens when the scope changes: the change is described, re-quoted and agreed before any work starts on it. This single clause prevents most disputes.

Support and exit. What is covered after launch, how fast problems are answered, what counts as new work, and — just as important — what the supplier hands over if you leave: code, documentation, credentials and a working deployment.

Can You Claim R&D Tax Relief on Bespoke Software?

Sometimes, and far less often than some advisers suggest. HMRC's rules, now under the merged scheme for accounting periods beginning on or after 1 April 2024, apply the government's guidelines on what counts as research and development: the work must seek an advance in science or technology by resolving genuine technological uncertainty. Routine software development — building features that a competent developer knows how to build — is excluded. A system that is simply new to your business does not qualify. Work that solves a problem no competent professional could solve with existing knowledge might. Talk to your accountant before you build a budget around a claim, and treat any relief as a possible bonus rather than part of the price.

Questions to Ask Any Bespoke Software Company

1. 1. Will the copyright be assigned to my company on payment, and will the code and accounts be in my name from day one?
2. 2. Is this a fixed price against a written scope, or a day rate with an estimate?
3. 3. What happens, in writing, when the scope changes?
4. 4. Which of my existing systems have you connected to before, and what do they expose?
5. 5. Where will the software and its data be hosted, and will you sign a data processing agreement?
6. 6. Do you hold Cyber Essentials, and what security testing is included?
7. 7. What does support cost after launch, and what exactly does it cover?
8. 8. If we part ways, what do you hand over, and how long does it take?

If you are still deciding between hiring your own developer and using a company, Hire an AI Developer or Use an Agency? A UK Decision Guide for 2026 compares employing, contracting and agencies under the 2026 employment rules. For a web platform specifically, What Decides What a Website Costs in the UK in 2026? Routes, Ongoing Costs and What to Check on a Quote sets out the routes.

How BigBerri Builds Bespoke Software

We are a software house in Manchester, and most of what we build is ordinary, well-engineered software: web applications, customer portals, internal tools, mobile apps and the integrations between them, with AI added only where it saves someone a step.

• •Discovery call first. Thirty minutes, free, to list the jobs the software must do and the systems it touches — and to tell you honestly if an off-the-shelf tool would do.
• •Written scope, fixed price. One number for the build, testing and launch, agreed before work starts. Changes are re-quoted before they are built.
• •You own it. Copyright assigned to your company, code and accounts in your name, tests and documentation included.
• •Built in the UK, data in the UK or EU, under a data processing agreement.

See Web Development for how we scope web platforms, or book a free discovery call at our contact page and tell us what you want the software to do. You will leave with an honest view of whether bespoke is the right route and what would decide the price.