The honest answer: a custom software development cost in the UK ranges from £15,000 for a focused internal tool to £150,000+ for a complex, multi-module platform. That range is wide because the variables are real, and anyone quoting you a number without understanding your business is guessing.
This page sets out the actual numbers. What different types of project cost, what drives the price up and down, and how to think about the return on the investment. No contact forms to unlock the pricing. No "it depends" without explaining what it depends on.
We have been building custom web applications since 2005. We have quoted and delivered enough projects to give you concrete figures, and enough honesty to tell you when a £50/month SaaS subscription is the better answer.
What custom software actually costs in the UK
Custom software development pricing varies by complexity, not by magic. Here are realistic UK price ranges based on what we have seen across 50+ projects.
Simple internal tool: £15,000 to £30,000
4 to 8 weeks. Staff scheduling board, equipment booking system, simple approval workflow. One user type, limited integrations, straightforward data model.
Mid-complexity business system: £30,000 to £75,000
8 to 16 weeks. CRM with custom pipeline stages, order management with invoicing, client portal with document sharing. Multiple user roles, several integrations, reporting requirements.
Complex multi-module platform: £75,000 to £150,000
4 to 8 months. Operations platform connecting sales, delivery, and finance. Multi-tenant system serving several client organisations. Significant integration work and complex business logic.
Enterprise-grade system: £150,000+
6 to 12+ months. Full business operating system with mobile apps, third-party integrations, real-time dashboards, and complex role-based access across departments.
These figures cover discovery, design, development, testing, deployment, and initial training. They do not include ongoing maintenance, which typically runs at 10 to 15% of the build cost per year.
A few notes on reading these ranges. Most projects we build fall in the £30,000 to £75,000 range. The jump from "simple" to "mid-complexity" is rarely about the number of screens. It is about the number of rules: conditional logic, edge cases, permission levels, and integrations that multiply the work beneath the surface.
Failure mode: skipping discovery to save money. A £3,000 to £5,000 discovery phase typically saves £15,000 to £30,000 in rework. Projects that skip straight to code almost always hit scope changes by week four, because nobody mapped the process properly. The cheapest phase to get wrong is discovery. The most expensive phase to get wrong is also discovery.
What drives custom software development cost up and down
The bespoke software cost for any project depends on specific, measurable factors. Here is what actually moves the number.
User roles and permission levels
A system with one user type (everyone sees everything) is straightforward. A system with five roles, each seeing different data, different actions, and different dashboards, adds meaningful complexity. Every role needs its own test scenarios, its own UI states, and its own edge cases. Budget an extra one to two weeks per distinct role beyond the first.
Integration count
Each API connection to an external system (Xero, HubSpot, a legacy database, a courier API) adds one to three weeks of development. The variation depends on the quality of the third-party API. A well-documented REST API with a sandbox environment takes a week. An undocumented SOAP interface from 2009 takes three.
Connecting multiple systems together compounds the complexity. When data flows between your custom application and three external systems, you need conflict resolution, retry logic, and error handling for every direction of data flow. Our guide to API integrations covers the engineering patterns in detail.
Data migration complexity
Moving data from a clean, structured CSV is a few days of work. Migrating from an Access database with 15 years of accumulated data, inconsistent formatting, duplicate records, and undocumented relationships is a project within a project. Budget one to four weeks depending on the source system.
Authentication requirements
Basic email and password login: included in the base cost. Single sign-on (SSO) with Azure AD or Google Workspace: add a week. Multi-factor authentication, IP whitelisting, and session management policies: add one to two weeks. These are not optional extras for most business systems. They are requirements that emerge during discovery.
Reporting complexity
A summary dashboard with five key metrics is part of the standard build. An ad-hoc query builder that lets users construct their own reports across any combination of data fields is a significant feature in its own right. The gap between "show me today's orders" and "let me build any report I want" is typically three to six weeks of development.
Cost reducers
Not everything pushes the price up. Several decisions reliably bring it down.
-
Phasing the build Launch with the core workflow first. Add secondary features in phase two. This reduces the initial investment and lets you validate the approach before committing to the full scope.
-
Using standard patterns Authentication, user management, notification systems, and audit logging all follow established patterns. We do not reinvent these. Boring technology keeps costs predictable.
-
Clear process documentation If you arrive at discovery with your workflows already mapped (even on paper), you save one to two weeks of process analysis. Our process mapping guide can help with this.
The cost of not building
Custom software development cost is only half the equation. The other half is what your current workaround costs you every year.
Manual data entry
A team member spending three hours per week re-entering data between disconnected systems costs more than it looks. At £15 per hour, that is £2,340 per year for one person. If three people do variations of the same work, the annual cost reaches £7,020. Over five years: £35,100. A £25,000 system that eliminates this work pays for itself before year four.
Error rates from manual processes
Manual data transfer between systems typically carries a 1 to 3% error rate. In an order management context processing 200 orders per month, that is two to six errors per month. Each error costs time to identify, time to fix, and sometimes a refund or a re-delivery. At an average cost of £50 per error, that is £1,200 to £3,600 per year in error correction alone, not counting the customer goodwill you cannot recover.
SaaS cost scaling
Per-seat SaaS pricing works well for small teams. It becomes a liability as you grow. A tool costing £50 per user per month looks reasonable at 10 users (£500 per month, £6,000 per year). At 50 users, that same tool costs £2,500 per month, or £30,000 per year. Over five years at the larger team size: £150,000. Custom software has no per-seat cost. The fortieth user costs the same as the fourth: nothing extra.
Opportunity cost
This is harder to quantify but often the largest number. If a manual process takes your sales team 30 minutes per quote and a custom system reduces that to five minutes, you have freed 25 minutes per quote. At 20 quotes per week, that is over eight hours per week of recovered selling time.
Custom software vs SaaS: five-year cost comparison
Here is a worked example comparing custom software development cost against a typical SaaS tool, using realistic UK figures. The scenario: a 20-person company growing to 40 people over five years, needing an operations management system.
| Cost element | Custom software | SaaS platform |
|---|---|---|
| Year 1: Build / subscription | £55,000 (build) | £12,000 (£50/user x 20 users) |
| Year 1: Hosting and infrastructure | £1,800 | Included |
| Year 2: Maintenance and new features | £6,000 | £15,600 (25 users, price rise to £52) |
| Year 3: Maintenance and new features | £6,000 | £19,500 (30 users, price rise to £54) |
| Year 4: Maintenance and new features | £6,000 | £25,200 (35 users, price rise to £60) |
| Year 5: Maintenance and new features | £6,000 | £31,200 (40 users, price rise to £65) |
| Hosting years 2 to 5 | £7,200 | Included |
| Five-year total | £88,000 | £103,500 |
The SaaS platform starts cheaper. By year three, the annual costs converge. By year five, the custom system is £15,500 less expensive in total, and the gap widens every year after that.
This comparison does not account for three additional factors that favour custom software.
Fit
The SaaS tool requires you to adapt your process to its workflow. Custom software encodes how you actually work.
Ownership
You own the custom software outright. The SaaS vendor can change pricing, remove features, or discontinue the product. The question of owning versus renting your systems is a strategic one.
Hidden SaaS costs
Premium tiers, add-on modules, data export fees, and API access charges often double the headline price. A CRM that advertises £50 per user frequently costs £85 per user once you add reporting, automation, and integrations.
Failure mode: hidden SaaS costs. A logistics company chose a SaaS platform at £40 per user per month. Within 18 months, they needed the premium reporting module (£15 per user), API access for their warehouse system (£500 per month flat fee), and additional storage (£200 per month). Their effective per-user cost reached £72, nearly double the original figure. The five-year cost at 35 users exceeded £150,000, more than a custom build with better process fit.
How we price projects
We quote fixed prices for defined scope. No hourly billing, no open-ended retainers during the build phase, no surprises on the invoice.
The process works in three steps.
Discovery first
Every project starts with a paid discovery phase (typically £3,000 to £5,000, lasting one to two weeks). We map your processes, define the scope, identify integrations, and document the requirements. Discovery produces a specification document and architecture diagram that you own, regardless of whether you proceed with us.
Fixed quote from the specification
The specification removes ambiguity. We know what we are building, how long each component takes, and where the risks sit. The quote is fixed. If we underestimate, that is our problem, not yours.
Transparent change management
Requirements change during a build. That is normal. When new requirements emerge, we scope and quote them separately. You decide whether to include them now, defer them to a later phase, or skip them entirely. No change goes ahead without your approval and a clear cost.
This approach means you know the total cost before committing to the build. The discovery fee is the only at-risk investment, and the output (your specification document) has value even if you choose a different developer.
You can read more about how we work and what each phase involves.
What you get for the investment
The custom software development cost covers more than just code. Here is what is included in a typical IGC project.
-
Complete source code ownership You own everything we write. The code lives in your repository. You can hire another developer to maintain it, move it to different hosting, or extend it yourself. No licence fees, no lock-in.
-
Documentation Technical documentation covering architecture decisions, database schema, API endpoints, and deployment procedures. Written for the developer who maintains this system after us, not for a sales deck.
-
User training Hands-on training sessions for your team, recorded for future reference. We train the people who will use the system daily, not a project manager who then has to relay the information.
-
Deployment and infrastructure Production environment setup, SSL certificates, automated backups, monitoring configuration, and a deployment pipeline that allows updates without downtime. The infrastructure is sized for your actual needs, not over-engineered for theoretical scale.
-
Post-launch support A support period (typically four weeks) after launch to handle questions, fix issues, and make minor adjustments as your team settles into the new system. After that, ongoing support is available on a pay-as-you-go basis or a monthly retainer. We are still maintaining systems we built in 2008. Long-term support is not an upsell. It is how we work.
-
Data migration If you are replacing an existing system, we handle the data transfer. Schema mapping, validation, cleaning, and a parallel running period where both systems operate side by side until you are confident in the new one. Migration is where most bespoke software projects carry hidden risk. We treat it as a first-class workstream, not an afterthought bolted on the week before launch.
Reducing cost without cutting corners
If the numbers above stretch your budget, there are legitimate ways to reduce the initial investment without compromising the quality of what you build.
Phase the build
You do not need everything on day one. Identify the single workflow that causes the most pain, build that first, and launch it. Phase two adds the next priority. This approach lets you spread the investment over 12 to 18 months and validates the system with real users before committing to the full scope.
A phased approach typically costs 10 to 15% more in total than building everything at once (because of repeated deployment and testing cycles), but it reduces the initial outlay and the risk.
Start with an MVP
A minimum viable product is not a half-finished system. It is the smallest version of the system that delivers real value. For an order management system, the MVP might handle order creation, assignment, and completion tracking. Reporting, invoicing, and customer notifications come in subsequent releases.
The MVP should be production-quality code. Cutting corners on architecture to save money in phase one creates technical debt that costs more to fix in phase two. Build less, but build it properly.
Buy commodity, build core
Not every part of your system needs to be custom. Use Xero for accounting. Use SendGrid for email delivery. Use Stripe for payments. Build custom software only for the parts of your business where off-the-shelf tools force you to compromise your process. This is the central question in build vs buy decisions, and getting it right can halve your initial investment.
Prepare before discovery
The more clearly you can articulate your current process, pain points, and priorities before discovery begins, the faster (and cheaper) discovery runs. Sketch your workflows. List your integrations. Write down the five things that frustrate you most about your current setup. This preparation can save a full week of discovery time.
Next steps
If you are weighing up the cost of custom software against the cost of continuing with your current setup, a conversation is a good starting point. We will give you a realistic budget range for your specific situation, and we will be honest about whether custom software is the right approach or whether an off-the-shelf tool would serve you better.
Book a discovery call