Bespoke software does not have a useful fixed price because the work can range from a focused automation to a platform serving several departments. The better question is what level of solution is justified by the problem.
Typical project bands
As a broad planning guide, a small prototype or workflow automation may require a few thousand pounds. A focused first version of a business application can move into the tens of thousands. A complex, multi-role platform with integrations, migration and extensive governance can require substantially more.
What affects the cost?
- The number and complexity of user journeys
- Different roles, permissions and approval rules
- Connections to accounting, payment, CRM or other systems
- Data migration from spreadsheets or existing products
- Reporting, audit history and regulatory requirements
- Mobile access, offline behaviour or native app requirements
- Testing, training, hosting and ongoing support
Begin with the highest-value workflow
The safest route is often a short discovery stage followed by a focused first release. Map the current process, identify its most expensive friction and test a proposed experience before building the complete system.
This makes scope visible, gives users an early voice and lets investment increase only after the product proves useful.
Compare the cost of doing nothing
Manual work also has a price. Include the hours spent copying information, preparing reports, correcting mistakes and working around disconnected systems. Add subscriptions that could be replaced and the value of opportunities delayed by poor visibility.
A useful business case compares the complete three-year cost of the current process with the complete cost and expected benefit of the proposed software.
What should a proposal include?
- The problem and intended outcome
- Users and agreed first-release scope
- Design, development and testing stages
- Assumptions, exclusions and client responsibilities
- Hosting, security, support and ownership arrangements
- Milestones, review points and payment schedule
Is bespoke software worth it?
It can be when a distinctive or important process is being constrained by generic tools. It is less likely to be justified when a mature product already solves the need well.
Read our guide to bespoke versus off-the-shelf software, explore software development in Northern Ireland, or ask JellyStorm for a practical first view.