How Much Does Bespoke Software Development Cost in the UK?
Bespoke software in the UK typically costs between £6,000 and £80,000, with most business systems landing between £12,000 and £35,000. Day rates for UK developers run roughly £395 to £600. The range is wide because bespoke software describes everything from a single tool that replaces one spreadsheet to a platform that runs a company.
Prabhu SolutionsPublished 6 September 2026Last reviewed 15 September 20268 min read
On this page
What does each cost band buy?
Four bands cover almost every bespoke build, and most business systems land in the second one — £12,000 to £35,000, over three to five months. Figures below are UK market rates and describe the scope of a bespoke software development project rather than a licence fee.
| Cost | What it is | Timeline |
|---|---|---|
| £6,000 – £12,000 | One clear process. A job tracker, a booking system, a reporting dashboard, an integration between two systems. Single user type, handful of screens. | 6–10 weeks |
| £12,000 – £35,000 | Multiple connected processes, user roles and permissions, several integrations, migration from an existing system. Most common. | 3–5 months |
| £35,000 – £80,000 | Multi-site or multi-team, a customer-facing portal of the kind web application development covers, complex integration with production or finance systems. | 6–12 months |
| £80,000+ | Enterprise scale, regulatory complexity, high volume, multiple integrated modules. | 12 months+ |
Where do we sit in this?
Most of what we build is the middle band: a system covering two or three processes, joined to the accounting or stock package you already run. We do not publish a rate card, because the honest number depends on the things listed below rather than on a page count — so we scope it first and quote from the scope. What we build and how sets out the work itself.
What actually drives the price of bespoke software?
Six things, and the feature list is not really one of them. The number of distinct processes, the integrations, the permission model, the data migration, any offline requirement and how settled the brief is account for nearly all of the difference between a £10,000 system and a £40,000 one.
- Number of distinct processes. Not features — processes. A system handling quoting, scheduling and invoicing is three times the work of one handling quoting, even if the feature list looks similar.
- Integrations, and whether the other system co-operates. The biggest source of estimate overrun in this industry. Xero, Sage, QuickBooks, Microsoft 365 and most modern cloud products have decent APIs and are predictable. Older, industry-specific and on-premise systems vary enormously — some have a proper API, some have a database you can read, and some have neither, in which case you are into scheduled file exchanges and a lot of defensive engineering.
- User roles and permissions. “Everyone sees everything” is cheap. “Branch managers see their branch, regional managers see their region, finance sees costs but not margins, and contractors see only their own jobs” is a genuinely complex piece of design.
- Data migration. Getting years of accumulated records out of a system nobody has tidied since 2019, cleaned, de-duplicated and reconciled. Frequently more work than a client expects and almost never quoted honestly by anyone who has not looked at the data.
- Offline and mobile requirements. If your users are in vans, on sites or in buildings with poor signal, that is an architectural decision made at the start. Retrofitting it is expensive, and it is the same decision that shapes what it costs to build an app.
- How settled the requirements are. The variable most within your control, and the one that moves cost most. A clear brief costs meaningfully less than a moving one.
Should you pay a fixed price or a day rate?
Fixed price when the scope is genuinely clear, day rate when it will evolve — which it usually does. The honest middle path, and what we would generally recommend, is a paid discovery phase producing a specification, then a fixed price for a clearly defined phase one, then day rate for the iteration that always follows.
Fixed price transfers risk to the developer, who prices that risk in. Expect a fixed quote to carry a contingency of perhaps 20–30%, which is reasonable rather than sharp practice.
Day rate is cheaper if you manage it well and riskier if you do not. Anyone offering a fixed price on a vague brief is either padding heavily or planning to argue about scope later. Which model suits you also depends on who does the work, which is the question behind choosing between a freelancer, an agency and an in-house team.
The point
Anyone offering a fixed price on a vague brief is either padding heavily or planning to argue about scope later.
What does bespoke software cost after it launches?
Hosting runs £30 to £300 a month, third-party services are usage-based, and support and maintenance should be budgeted at 15 to 20% of the build cost every year. Software is never finished, so the months after launch always carry work nobody predicted.
- Hosting — £30 to £300 a month depending on load
- Third-party services — email delivery, SMS, payment processing, mapping
- Support and maintenance — budget 15–20% of build cost annually. Software is never finished; dependencies get security patches, browsers change, your business changes.
- Iteration — the first three months after launch always surface things nobody predicted. This is normal, not a failure of scoping.
When should you not build bespoke software?
Buy off the shelf when your process is broadly standard — accounting, payroll, general CRM, email marketing — when you need it working in weeks, when your budget is under about £6,000, when the requirement is still moving, or when a mature product already exists for your specific industry.
We build bespoke software, so weigh that accordingly. It is still true.
A middle path is worth considering: keep off-the-shelf products for the standard functions, build bespoke only for the part that is genuinely yours, and connect them with integration. Often the cheapest good answer, and we recommend it more often than a full custom build. It is the same logic that decides whether a custom CRM beats an off-the-shelf one, and it is how most CRM development projects should start.
The point
A middle path is worth considering: keep off-the-shelf products for the standard functions, build bespoke only for the part that is genuinely yours, and connect them with integration.
Questions people ask about this
Why is bespoke software so expensive?
It is people, almost entirely. A UK developer costs £395–£600 a day; a three-month project is roughly 60 developer days before design, testing, project management or data migration. There is no hidden margin making it expensive — it is the arithmetic of skilled time.
Can I get bespoke software for under £5,000?
Rarely anything worth having. At that budget you would get perhaps ten developer days, which is not enough for something reliable and maintainable. A well-configured off-the-shelf product will serve you better, and an honest developer will tell you so.
How do I know if a software quote is fair?
Divide the quote by a realistic day rate to see how many days you are being sold. Then ask whether that many days sounds right for the scope. It is a crude test and it catches most outliers in both directions.
Will I own the code?
You should. Ask explicitly, get it in writing, and confirm the repository is handed over. Not every developer answers this the same way.
What if we change our minds during the project?
Expected, and manageable if you work in sprints. What matters is that changes get a written note with cost and timeline impact, agreed before they are built — rather than being absorbed silently and appearing on a final invoice.
The work behind this article
Read next
Custom CRM vs Off-the-Shelf: The UK Cost Comparison
Five-year figures land closer together than anyone expects, which is why the spreadsheet is the wrong place to make this decision. The arithmetic, the signals that point each way, and the middle path most people miss.
How Much Does It Cost to Build an App in the UK?
Four build bands, the maintenance bill that decides whether an app is affordable at all, and an honest look at when a web app or a progressive web app is the better product.
How Much Does a SaaS MVP Cost in the UK?
Two bands, three line items that surprise every founder, and a clear account of what belongs in a first release. A properly scoped MVP will feel too small — that feeling is the point.