A spreadsheet that has become the centre of your operation rarely fails all at once. It creates duplicate entry, missed handovers, inconsistent reporting and a growing reliance on the one person who knows how it works. At that point, asking how much bespoke software costs is sensible. The more useful question is what it will cost to keep working around the problem.

For a growing UK business, bespoke software can cost anything from a few thousand pounds for a focused internal tool to well over £100,000 for a business-critical platform. That range is wide because bespoke software is not a product bought from a shelf. It is a piece of operational infrastructure designed around your processes, people and existing systems.

The right investment is not necessarily the cheapest build. It is the system that removes a meaningful constraint without creating more complexity than the business needs.

Typical bespoke software costs in the UK

As a working guide, most bespoke projects fall into a few broad bands. These figures are usually quoted excluding VAT, but always check what is included before comparing proposals.

• £5,000 to £15,000 can cover a tightly defined tool, such as a quoting calculator, job tracker, simple client portal or a workflow that replaces a difficult spreadsheet.
• £15,000 to £40,000 is a common range for a tailored internal system with several user roles, approval steps, reporting and integrations with one or two existing tools.
• £40,000 to £100,000 is more typical for a substantial operational platform that supports multiple departments, detailed permissions, complex workflows and a migration away from several disconnected systems.
• £100,000 and above applies where the system is central to the business, serves external customers, handles high volumes of data or requires extensive integration, security and ongoing product development.

These are not fixed prices. A £12,000 system can deliver a better return than a £75,000 platform if it removes the bottleneck that is holding back sales or operations. Equally, a low initial quote can become expensive if important requirements have been left vague and are later treated as change requests.

What drives the cost of bespoke software?

The cost is mainly determined by the amount of problem-solving, design, development and testing needed to make the system dependable in daily use. Screen count alone is a poor measure. A simple-looking screen can involve complicated rules behind it.

The clarity of the problem

A business that can clearly describe its current process, its pain points and the desired outcome will usually spend less than one that starts with a broad idea of needing “a new system”. That does not mean you need to write a technical specification before speaking to a developer.

It means the discovery work needs to happen somewhere. Someone must map how work moves through the business, identify exceptions and decide what the new process should do. Good discovery is paid work, but it prevents much more expensive assumptions later.

Workflow complexity and exceptions

A basic process follows a predictable path. A lead arrives, a quote is issued, the customer accepts, work is scheduled and an invoice is raised. Many businesses have a more realistic version: certain jobs need approval, prices vary by customer, information arrives late, staff work in different ways and some work must be escalated.

Bespoke software needs to deal with those real-world exceptions. The more rules, branches and approvals required, the more design and testing are involved. Trying to ignore them merely pushes people back towards email, spreadsheets and manual workarounds.

Integrations and data quality

Most businesses do not start with a blank slate. They may already use accounting software, a CRM, stock control, payment services, email tools or industry-specific applications. Connecting a new system to these can be extremely valuable, but integrations add cost.

The work is not just about moving data from A to B. It includes deciding which system is the source of truth, handling failed updates, matching records, managing permissions and testing what happens when information changes. Data cleanup can also be a significant part of the project, particularly where years of spreadsheet records contain duplicates or inconsistent formats.

Users, permissions and reporting

A system used by three people in one office is different from one used by administrators, managers, field staff, directors and customers. Each group may need different access, views and actions.

Reporting deserves the same care. If the business needs reliable visibility of pipeline, workload, job profitability or overdue actions, those measures should be agreed early. Reports built from poor or incomplete data only make decisions look more certain than they are.

Quality, security and long-term support

A quick tool can be appropriate for a contained internal task. A platform holding customer data or driving revenue needs stronger safeguards, documentation, backup arrangements, monitoring and maintenance. These are not flashy parts of a project, but they affect both cost and confidence.

Ongoing support should be discussed upfront too. Bespoke software is not a one-off purchase that can be forgotten after launch. Browsers, third-party services and your own business processes change. Allowing for improvements and maintenance is usually more commercially sensible than treating the launch as the finish line.

Why two quotes can differ so much

It is common to receive estimates that look impossible to reconcile. One supplier may quote £15,000 while another quotes £60,000 for what appears to be the same brief. Sometimes one quote is simply overpriced. More often, the suppliers have made different assumptions.

A lower quote may cover only a basic first release, with integrations, migration, reporting and training excluded. It may rely heavily on off-the-shelf components, which can be the right choice if they genuinely fit the process. Or it may not include enough time for discovery, testing or project management.

A higher quote may include all of those things, plus agency overheads and several layers of account handling. Larger teams can be useful for major programmes, but they are not automatically better for a small or medium-sized business. Direct access to the person who understands the process and builds the solution can reduce delay, misunderstanding and cost.

The answer is not to choose the middle quote by default. Ask each supplier what is included, what is excluded, what they are assuming, and what would cause the price to change. A good proposal should make this clear in plain English.

How to control bespoke software costs without cutting corners

The most effective way to keep a project affordable is to reduce uncertainty before development begins. Start with the operational problem, not a long list of features. For example, “reduce the time from accepted quote to scheduled job” is a better starting point than “build a job management system like the one we saw elsewhere”.

It also helps to separate essential workflow from useful extras. A first release should handle the process well enough that staff can use it confidently and the business can see an improvement. Nice-to-have features can follow once the foundation is working and real usage has exposed what matters most.

Phased delivery is often the most practical route. Rather than committing to a large system based entirely on assumptions, build the highest-value area first. This might be enquiry handling, job scheduling, production tracking or an approval process. The business learns from the first release, then invests in the next part with better information.

Be cautious about specifying a solution too early. Reproducing every column and formula from an old spreadsheet in a web system can make the new software costly while preserving the old inefficiency. The aim is to improve the process, not digitise every historical workaround.

Budget for the full cost, not just the build

Development is the main cost, but it is not the only one. There may be expenses for hosting, software licences, third-party services, data migration, training and ongoing support. Some are modest and predictable; others depend on volume or the systems being connected.

There is also an internal cost. Your team will need to explain how work happens, test early versions and make decisions. If nobody has time to contribute, the project slows down or developers are forced to guess. The best projects have a clear client-side owner who can answer questions and keep decisions moving.

That said, do not measure the investment only against the development invoice. Measure it against saved administration, fewer errors, faster turnaround, reduced rework and the capacity to handle more work without adding the same level of overhead. If a system gives a manager back a day each week, or stops jobs being missed, the value can become clear quickly.

Getting a useful estimate

A meaningful estimate normally follows a conversation about the business rather than a one-line request for “a CRM” or “an app”. The first stage should establish who uses the process, where information comes from, what happens today, where it breaks down and what a better outcome looks like.

From there, the work can be divided into a sensible first phase, with costs and assumptions made visible. This provides enough certainty to make a decision without pretending that every future requirement can be known before people use the system.

Bespoke software should earn its place in the business. If it removes a genuine operational headache, gives people clearer information and supports growth without more manual administration, the cost becomes an investment in running the business properly rather than another technology expense.