The short answer
One of the first questions organisations ask when considering bespoke software is also one of the most difficult to answer: how much will it cost?
The honest answer is that there is no standard price. A simple internal application and a complex system used across several departments may both be described as "bespoke software", but they are very different projects.
As a broad planning guide, smaller bespoke systems may fall somewhere around £5,000–£20,000, a more substantial business system might be in the region of £20,000–£50,000, while complex systems with extensive integrations, migration or enterprise-level requirements can reach £50,000 or more.
These figures are deliberately broad. They are not a quotation from Illuminaries, and the right budget for a particular project can only be established once the requirements are understood.
What are you actually paying for?
It is easy to think of software development as paying someone to write code. In reality, the code is only one part of the project.
A properly built bespoke system involves understanding the organisation, designing the data structure, defining workflows, creating the user interface, developing the software, testing it, deploying it and supporting it afterwards.
At Illuminaries, we have been building bespoke IT systems for organisations for more than 30 years. The projects vary considerably, but the same principle applies: the more specific the problem and the more complex the solution, the more work is required before the system can be considered finished.
This is why two software development quotes can look very different even when the initial descriptions of the projects sound similar.
Typical bespoke software cost ranges
It can be useful to have some numbers to work with when preparing an initial business case. The following bands are intended as planning guidance rather than fixed prices.
| Project type | Indicative range | Typical characteristics |
|---|---|---|
| Focused internal system | £5,000–£20,000 | A defined workflow, database, user accounts and straightforward reporting. |
| Business application | £20,000–£50,000 | Multiple workflows, user roles, reporting, integrations and more complex data. |
| Complex business platform | £50,000+ | Multiple departments, substantial integrations, complex security, migration or large-scale operational requirements. |
A project can, of course, fall outside these ranges. A small but technically unusual system may require more work than its size suggests, while a well-defined application with limited functionality may be considerably simpler.
What drives the cost of bespoke software?
The most useful way to think about software cost is not in terms of screens or lines of code, but in terms of the complexity of the problem being solved.
1. The complexity of your requirements
A system that records customer details and produces a handful of reports is fundamentally different from one that manages referrals, approvals, documents, financial information and multiple stages of a business process.
Every additional rule or exception adds complexity. If a process has ten different possible outcomes depending on circumstances, the software needs to understand all ten.
This is why defining requirements properly at the beginning can save money later.
2. The number and type of users
A system used by three people in one office has different requirements from one used by hundreds of people across multiple locations.
Different users may also need different permissions. Managers may need access to reports that other staff should not see. Administrators may need additional controls. External users may need access to a restricted portal.
User roles, permissions and security all add design, development and testing requirements.
3. Your data and database requirements
Most business software is ultimately about data. What information do you need to store? How is it related? Who needs to access it? What needs to be reported? What must be retained?
A well-designed database is therefore an important part of a bespoke system, rather than something added at the end.
If you already have years of information stored in Excel, Access or another legacy system, the project may also need to include data cleansing and migration.
If your organisation is struggling with spreadsheets, our article When to Replace Excel with a Database explains some of the warning signs that it may be time to move to a more robust system.
4. Integrations with other systems
A bespoke application rarely exists completely on its own.
You may need it to exchange information with accounting software, CRM systems, payment providers, email platforms, government services or existing internal systems.
Each integration introduces additional technical requirements. The other system may have an API, authentication requirements, data limitations or its own rules that the new application needs to understand.
Integrations can therefore make a significant difference to both development time and project cost.
5. Reporting and business intelligence
Reporting is often underestimated at the start of a project.
It is relatively straightforward to store information. It is considerably more difficult to make sure that the right information can be extracted, filtered and presented in a way that helps people make decisions.
If your system needs dashboards, complex reports, scheduled exports or different views of the same data, those requirements need to be considered from the beginning.
6. Data migration
Moving from an old system to a new one is rarely as simple as copying the data across.
Existing databases and spreadsheets often contain duplicates, inconsistent formats, missing information and fields that have changed meaning over the years.
Migration may therefore involve analysing, cleaning, transforming, validating and importing the existing data.
For an organisation that has been operating for many years, this can be a significant part of the project.
7. Security and compliance
The more sensitive the information, the more carefully the system needs to be designed.
User permissions, authentication, audit trails, encryption, backups and access controls can all form part of a software project.
These requirements should not be treated as optional extras. Security is much easier to design into a system from the beginning than to retrofit later.
Why is one software quote cheaper than another?
If you ask several development companies for a quotation, you may receive figures that vary considerably.
That does not necessarily mean that one company is overcharging or another is offering a bargain.
The quotes may simply be based on different assumptions.
One developer may have included requirements analysis, testing, deployment, documentation, training and post-launch support. Another may have priced only the development work.
Before comparing prices, make sure you are comparing the same thing.
Don't forget the cost of not fixing the problem
The cost of bespoke software is only one side of the calculation.
If an organisation is currently spending several hours every week maintaining spreadsheets, manually producing reports, re-entering information or working around limitations in an existing system, those costs can easily disappear from the software budget because they are hidden inside people's salaries.
The same applies to errors. A reporting mistake, duplicated record or missed piece of information may have a financial or operational cost that is much harder to see than a software invoice.
This is why the right question is often not:
"Can we afford bespoke software?"
It is:
"What is the current way of working costing us?"
Is bespoke software always worth the investment?
No.
We don't believe bespoke software is automatically the right answer for every organisation.
If your requirements are standard and an established product already does exactly what you need, buying that product is likely to make more sense.
The problem occurs when an organisation spends years adapting its processes around software that was never designed for the job.
We explore this in more detail in Why Bespoke Software Outlasts Off-the-Shelf.
The decision should ultimately come down to the problem being solved, the expected lifespan of the system and the total cost of the available options.
How do you get an accurate software development quote?
The best starting point is not a list of features.
It is an understanding of what the organisation is trying to achieve.
Before a realistic estimate can be produced, it is useful to understand:
- What problem the software needs to solve
- Who will use the system
- What information needs to be stored
- How the organisation currently works
- Which processes need to be automated
- What reports and information are required
- Which existing systems need to integrate
- Whether existing data needs to be migrated
- What security and access requirements exist
- How the system is expected to develop in the future
Once those questions have been answered, it becomes much easier to separate essential functionality from nice-to-have features and establish a sensible development plan.
Do you need to build everything at once?
Not necessarily.
One of the most effective ways to control the cost of a bespoke software project is to identify the smallest useful version of the system and build from there.
That might mean replacing the most problematic spreadsheet process first, introducing the core database, and then adding reporting, integrations or additional workflows once the foundation is working.
This approach can make a project easier to budget and gives users the opportunity to start working with the system while later improvements are developed.
The real question is whether it is worth it
Bespoke software is an investment. It requires more thought upfront than downloading a piece of off-the-shelf software and signing up for a subscription.
But when an organisation has a genuinely specific process, valuable data, inefficient manual work or software that no longer fits, the calculation changes.
The right system can remove repetitive work, improve the quality of information, make reporting easier and give an organisation a platform it can continue to develop over many years.
The objective is not to build software simply because bespoke software is available.
The objective is to build something that solves a problem well enough to justify the investment.
Considering bespoke software?
We help organisations across the UK design and develop bespoke software around the way they actually work — from database-driven internal systems to more complex business applications.
If you're considering a project but aren't sure what it should cost, what approach is appropriate or whether bespoke is even the right answer, we can start by understanding the problem before recommending a solution.