Bespoke software development in the UK: costs, contracts and how to brief a supplier
Commissioning bespoke software is a business decision as much as a technical one. What drives the cost, what belongs in the contract under UK law, and how to write a brief suppliers can price.

In this article
From Leeds to Belfast, Birmingham to Liverpool, many UK organisations reach the point where off-the-shelf tools no longer fit: processes are bent around software, data is copied between systems and spreadsheets fill the gaps. Bespoke software can fix that, but only if it is commissioned well. This guide covers when it pays off, what drives the cost, what belongs in the contract and how to brief a supplier.
When bespoke software pays off
- Your process is a competitive advantage that packaged software would force you to give up.
- Staff spend significant time re-keying data between systems.
- Licence costs grow with every user while the software still does not fit.
- You want to offer customers a portal, app or service of your own.
Often the right answer is a mix: packaged software for accounting, HR and CRM, with bespoke software for the portals, workflows and integrations that make your business different.
What drives the cost
- The number of user roles, workflows and exceptions the system must handle
- Integrations with existing systems and the quality of their interfaces
- Security, availability and compliance requirements
- Data migration from legacy systems and spreadsheets
- Hosting, support and further development after launch
A short paid discovery phase usually saves money. It turns assumptions into a prioritised scope, so the supplier can offer a fixed price for a first phase instead of padding an estimate for the unknown.

What belongs in the contract
- Intellectual property: under UK law, copyright in code written by an outside developer generally stays with the developer unless it is assigned in writing. Make sure the contract assigns the bespoke code and documentation to you.
- Source code access: you should have the repository, not just a running system.
- Data protection: a data processing agreement under UK GDPR, including where data is hosted.
- Acceptance: how deliverables are tested and signed off, and what happens if they fail.
- Change control: how new requirements are estimated and approved.
- Support: response times, maintenance and the cost of ongoing development.
This is guidance, not legal advice; have a solicitor review significant contracts.
Security expectations
Many UK buyers, especially in the public sector and regulated industries, expect suppliers to follow recognised security practice. Cyber Essentials, the government-backed scheme, is a common baseline, and larger customers often send detailed security questionnaires. Ask suppliers how they handle access control, encryption, backups, vulnerability management and incident response, and make sure the answers are reflected in the system's design.

How to write a brief suppliers can price
- The business problem and how you will measure success
- Who will use the system and what they need to do
- The systems it must connect to
- Constraints: deadlines, budget range, compliance requirements
- What is out of scope for the first phase
A brief like this lets suppliers ask better questions and makes their proposals comparable.
Conclusion
Bespoke software is worth it when it removes real friction or creates something customers value, and when the contract protects your ownership and data. Start with discovery, fix the scope of the first phase and keep the code in your hands. Smartechor builds bespoke software, integrations and SaaS platforms for UK organisations, with fixed-scope proposals in sterling through our UK-registered company.
Software Engineering
All insightsKeep reading
Related insights
- Software Engineering
6 min readMost companies pick a development partner on price or a slick portfolio — and regret it. Here's what actually predicts whether an engagement succeeds.How to choose a software development company (without getting burned)
- Software Engineering
6 min readBuilding custom software is sometimes the smartest decision a company makes — and sometimes the most expensive mistake. Here's how to tell which one you're facing.Custom software vs off-the-shelf: when is it worth building?
- Software Engineering
5 min read“A few months” is the honest answer no one likes. Here's what actually determines the timeline — and how to ship something real, sooner.How long does it take to build custom software?
Building something like this?
Tell us what you're building. We'll discuss the goals, the architecture and how we'd approach it.
