How much does bespoke software cost in the UK?

13.07.26

For most small and medium-sized businesses in the UK, a bespoke software build costs somewhere between £5,000 and £50,000. That is not a hard rule. It is simply the range we have quoted for most often, and most of the projects we see come inside it. Simple internal tools sit at the lower end. Multi-user platforms that work across web and mobile sit higher. The range is wide because the price is decided less by the idea and more by a handful of specific things: how many types of user it serves, how much it has to connect to other systems, how complex the data is, and how clearly you can describe what you want.

We price and build this work for a living. Where we quote a wider market figure rather than our own, we say so.

What you actually pay for

A bespoke price is mostly people's time. The headline number is a function of how many senior days the work takes, and what gets built in those days. That is why two apps that look similar can be priced thousands of pounds apart. One has a single type of user and no integrations. The other has three user roles, runs on web and mobile, and sends push notifications to people's phones.

So the useful question is not "what does an app cost". It is "what about my project pushes the number up or down". Here is the framework we use when we scope.

The five things that move the price

1. User roles. One kind of user is cheap. Every additional role, such as admin, manager, customer or approver, adds screens, permissions and logic to build and to test.
2. Integrations. Every external system you connect to is a small project of its own: payment gateways, accounting tools, mapping, push notifications, single sign-on.
3. Data complexity. Simple records are quick. Relationships between records, reporting and data that has to stay accurate under load all cost more.
4. Migration. Replacing a system people already rely on is harder than building from nothing, because you have to move live data without breaking the business in the process.
5. Platforms and reach. A web app is one thing. Add a mobile app on iOS and Android, and you are building and testing across more surfaces, which adds cost.

Move up on two or three of these at once, and the price rises with them.

Two ways to price a build, and why your clarity decides which

There are two common ways a build gets priced, and which one you can use depends on how clearly you can describe what you want.

Fixed price. When the specification is clear, the whole build can be committed to a fixed price. That is how we delivered Benefits Buddy, a staff-benefits platform with several types of user across web and mobile. The scope was written down in phases before any code, so the price was firm and the risk of overrun sat with us, not the client. A fixed price is the calmer option for you as the buyer. It needs the up-front work of a clear specification to be possible at all.

Day rate, or time and materials. When the idea is still taking shape, a fixed price would be a guess, and a bad one. For an assistive-technology app we built with the University of Bath, the goal was to turn an early idea into something that worked, and the shape of it changed as we learned. There we worked to an estimate based on a day rate, which kept things flexible while the product found its feet. The trade-off is that more of the risk sits with you if the work runs longer than expected.

The pattern underneath both is simple: the clearer you are about what you want, the easier it is to price, and the more of the risk you can hand to your supplier. If you cannot describe it precisely yet, that is fine. It just means starting with a scoping step or a short day-rate phase to get there.

The thing most cost articles miss: a fixed price you can take anywhere

The widest, most useless cost ranges online exist because nobody has scoped the work. We deal with that before the build. Our scoping step interviews your key people, defines what is in and out, and gives you a detailed specification, interactive wireframes, and a fixed-price quote valid for six months. You own that specification. You can bring the build to us, or take it to any other supplier. Either way you have turned a frightening range into a firm number, and you keep something of value even if you walk away.

We would rather give you a real number after a short paid scope than a scary range before it.

What about hiring a contractor instead?

Another route is to hire a developer through a recruitment agency. That is usually priced as a day rate, and the recruiter's margin typically adds 15% to 20% on top of what the developer is paid. You also take on directing the work and the risk if it goes wrong. It can be the right model when you have the in-house expertise to lead the work. It is the wrong one when you need a team that owns the outcome and hands you finished, tested software.

When bespoke software is not the right answer

Sometimes it is not. If you are still testing an idea that might not survive contact with customers, an off-the-shelf tool or a no-code build is the sensible, cheaper first step, and we will tell you so. Bespoke earns its cost when the software is core to how your business runs, when off-the-shelf tools force you to work the wrong way, or when you have outgrown a quick build and need something you can rely on and own outright. If none of those is true yet, spend less and come back when one of them is.

What to do next

Run your project past the five factors above and you will have a feel for where in that range you sit before you speak to anyone. Then ask yourself how clearly you can describe what you want, because that decides whether you can get a fixed price or should start with a scope.

What are you trying to build, and how clearly can you describe it today? That is the conversation worth having.