The honest version. What a build actually costs, how long it takes, and the tells that separate a quote you can trust from one that will overrun.
Bespoke software is a system built for one business rather than sold to thousands. In the UK in 2026 it typically costs between £10,000 and £500,000, and most business projects we see land in the £40,000 to £150,000 band. That range is wide for a good reason: a single-department internal tool and a platform serving thousands of users are different projects, and quoting one figure for both would help nobody. This guide gives you the numbers, the timelines, and the questions that tell a safe quote from a risky one.
The market has grown up. Custom software was worth about £1.9 billion in 2024 and is forecast to roughly triple by 2030, which means bespoke is no longer an edge case for large firms. Plenty of ten-person companies now run on something built for them. The question has shifted from whether to build to how to buy a build without joining the long list of projects that go wrong.
Cost tracks scope, and scope has a shape. Here is how UK 2026 pricing tends to break down once you attach it to the kind of thing being built.
| Project type | Typical UK cost | Rough timeline |
|---|---|---|
| Focused internal tool, dashboard or portal | £10,000 to £35,000 | 4 to 8 weeks |
| Customer-facing web application | £30,000 to £100,000 | 8 to 16 weeks |
| Complex platform with integrations and roles | £50,000 to £200,000 | 4 to 12 months |
| Enterprise or multi-tenant system | £150,000 and up | 6 months plus |
If your project sits at the top of one of these bands, expect the team to show you comparable work before you commit. If it is quoted well above the band with no technical reason given, ask for the reason. A good supplier will have one or will move the number.
Most of a quote is people. UK developer day rates in 2026 run to a fairly settled pattern: mid-level engineers around £400 to £550 a day, senior developers around £600 to £800, and lead architects, the people responsible for whether the thing scales and stays secure, at £800 to £1,200 or more. An agency then adds roughly 40% to 60% on top of raw developer cost to cover design, testing, project management and the overhead of keeping a team assembled.
That markup is not waste. It is the difference between a lone coder and a group that includes someone thinking about security, someone testing the work, and someone making sure the build matches what you asked for. A medium project needs a lead, one or two mid-level developers, a designer, part-time QA and a project manager. When a quote for a real system is priced as if one mid-level developer will build it alone, that is not a bargain. It is a warning.
Software is not a purchase, it is a tenancy. Once it is live it needs hosting, security patches, fixes and small changes as your business moves. Budget 15% to 25% of the build cost every year for that upkeep. A build that skips architecture to hit a low headline price tends to demand this in full and then some, because cheap code accrues debt that gets paid back later at a worse rate. Read the maintenance line in a quote twice. It tells you whether the supplier expects to still be around.
The base rates are sobering. Across the industry, only 31% of software projects succeed, half are challenged, and roughly a fifth are cancelled outright, on the long-running Standish CHAOS research. Size is the strongest predictor: small projects succeed around 90% of the time while large ones succeed less than 10%. Analysis by McKinsey and Oxford found large IT projects run 45% over budget and deliver 56% less value than predicted.
The good news hides in the same data. The single biggest cause of failure is not bad code, it is unclear requirements, behind roughly two in five failures. The projects that come in clean tend to do three unglamorous things: they write down exactly what the software must do before building, they ship the smallest useful version first, and they keep the pieces small enough that a person still owns each one. None of that is a technology choice. It is discipline, and you can check for it in a sales conversation.
This is the same principle behind how we run our own operation. A job gets mapped into steps, the risky steps get watched, and nothing large ships without a person signing it off. If you want to see that thinking applied to publishing rather than software, the notes on running a publishing operation with no content team lay it out.
Off-the-shelf almost always wins on day one. It is cheaper to start, faster to switch on, and someone else maintains it. Bespoke wins later, and only sometimes. It earns its cost when a standard product forces your team into workarounds, when per-seat licensing climbs with headcount, or when the way you work is itself the advantage and a generic tool would flatten it. The honest test is not which is better in the abstract. It is whether the fit problem you are paying to solve is bigger than the price of solving it.
A common and expensive mistake is treating this as a technical decision. It is an operating decision. You are choosing how work moves through the business and what you can change later without asking a vendor's permission. Our software engineering work starts from that question rather than a feature list, and the wider services and platform pages show where a build fits alongside automation. If you want to score your own business rather than take our word for it, the bespoke vs off-the-shelf decision tree turns this section into a five-question test.
The first brief is almost always too big. The strongest projects begin with the smallest version that proves the business value, then grow on evidence rather than on the original wish list. This is not a way to spend less, though it often does. It is a way to be wrong cheaply and early, while the cost of changing your mind is a conversation rather than a rebuild. A supplier who pushes you toward a leaner first release is usually protecting your budget, not shrinking their own.
Before you sign anything, get clear answers to these. Vague answers are the finding.
Get those five answered in writing and you have already dodged most of the ways a build goes sideways. The teams that answer them plainly are the ones worth shortlisting.
Most UK bespoke projects land between about £10,000 and £500,000, with the bulk of business systems falling in the £40,000 to £150,000 band. The figure is driven by scope, integrations and the seniority of the team, not by the agency's postcode.
A focused internal tool can ship in four to eight weeks. A first version of a larger system with real users usually runs eight to sixteen weeks, and a complex platform with several integrations often takes four to twelve months. Timelines stretch fastest when requirements are still moving after the build starts.
Rarely at the point of purchase. Bespoke wins over a few years when per-seat licensing, workarounds and lost time on a poor fit would have cost more than a build you own outright and can change on your own schedule.
Unclear requirements are the single biggest cause. Scope that keeps growing, a team too junior for the work, and integrations discovered late all push cost up. A detailed specification agreed before a line is written is the cheapest insurance you can buy.
A freelancer suits a small, well-defined job. An agency suits a system that needs design, engineering and QA together without permanent hires. An in-house team makes sense once the software is core and needs constant change, which usually means after the first version proves its value.
If you already know the problem you want software to solve, the useful next step is a scoped conversation rather than a longer guide. We give a straight answer on shape, cost and whether a build is even the right call. Start on the how we work page or go straight to contact.
A free call with one purpose: a straight answer on whether a bespoke build fits your business. If it does not, we will say so.
Book a 30-minute fit call