How much does custom software development cost?

What custom software actually costs in the UK

Custom software cost varies by complexity, not by magic. Here are realistic UK price ranges based on what we have seen across a wide range of projects.

These figures cover discovery, design, development, testing, deployment, and initial training. They represent the total cost of ownership for the build phase only. They do not include ongoing maintenance, which typically runs at 10 to 15% of the build cost per year.

That maintenance figure is not a vague retainer. It covers four concrete areas: security patches and dependency updates (keeping the system safe), infrastructure costs (hosting, backups, monitoring), minor feature enhancements (the tweaks your team requests once they start using the system daily), and support (someone to call when something is not working as expected). Skip maintenance and you accumulate technical debt that compounds. A system that costs £6,000 per year to maintain costs far more to rescue after three years of neglect. Our software maintenance guide breaks this down in detail.

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.

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. Our legacy migration guide covers the technical approach, and data modelling explains how we structure the target schema to avoid carrying old problems into the new 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. Our real-time dashboards page covers the engineering involved, and dashboard design addresses the UX side of making data genuinely useful.

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.

UK-specific cost factors

Two financial factors specific to the UK materially affect the real cost of a custom software project. Neither appears on most pricing pages, but both matter when you are building a budget.

VAT recoverability

Custom software development is a standard-rated service in the UK. If your business is VAT-registered, you can reclaim the VAT on development invoices through your normal VAT return. On a £60,000 project, that is £12,000 recovered, bringing the effective cost to £48,000. SaaS subscriptions are also VAT-recoverable, so this does not change the relative comparison, but it does change the absolute number you need to budget for. Your accountant should confirm your specific position, but most trading businesses reclaim this as a matter of course.

GDPR and data compliance

Any system handling personal data (customer records, employee information, order histories) needs to comply with UK GDPR. This is not a separate project, but it does add scope to the build. Consent management, data retention policies, right-to-erasure workflows, and audit logging for data access all require development time. Budget one to two weeks of additional work for systems with significant personal data handling. Our security and operations guide covers the technical patterns involved, and audit trails explains the logging architecture in detail.

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. If your business runs on spreadsheets, shared inboxes, and manual re-keying, you are already paying for software. You are just paying in labour, errors, and friction instead of in a development invoice. Our page on when spreadsheets break covers the tipping points in detail.

Manual data entry

A team member spending three hours per week re-entering data between disconnected systems costs more than it looks. Calculating the return on investment on a custom build starts here. 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. (We cover the full custom vs SaaS decision separately.) 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.

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 break-even point has already passed. The gap widens every year after that.

This comparison does not account for three additional factors that favour custom software.

How we price projects

We quote fixed prices for defined scope. No day rate billing, no open-ended retainers during the build phase, no surprises on the invoice.

The process works in three steps.

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 good custom software delivery includes

The custom software development cost covers more than just code. Here is what a well-run project delivers.

• ✓
  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.

Comparing quotes from different developers

If you are getting quotes from several UK development companies (and you should), the numbers will vary. Sometimes by 2x or more. That variation is not random. It reflects genuine differences in what is included, how risk is allocated, and what happens after launch.

When comparing quotes, check these specifics.

• ✓
  Scope definition A lower quote may cover fewer features, exclude data migration, or assume you will handle user acceptance testing yourself. Compare like for like. Ask each company to itemise what is included and what is not.
• ✓
  Pricing model Fixed-price quotes transfer cost risk to the developer. Time-and-materials contracts transfer it to you. A lower T&M estimate can end up more expensive if the project runs over. Understand which model each quote uses.
• ✓
  Post-launch costs Some quotes include three months of support. Some include none. Ask what happens on day one after handover, and what the ongoing maintenance arrangement looks like.
• ✓
  IP and code ownership Confirm that you will own the source code outright. Some agencies retain IP or use proprietary frameworks that create lock-in. You should be able to take the code to any other developer if the relationship ends.
• ✓
  Technology choices A quote built on a mature, well-supported framework (like Laravel) carries less long-term risk than one built on a niche stack. The initial build cost might be similar, but finding developers for maintenance years later will not be.

The cheapest quote is rarely the best value. The most expensive quote is not automatically the safest. Understanding custom software cost means looking beyond the headline figure to what you are getting, what it will cost to maintain, and what happens when requirements change.

A note on cost anxiety

Spending £30,000 to £80,000 on software for the first time is a significant commitment, particularly for an owner-managed business. The numbers on this page are real, and they are large enough to warrant careful thought. That caution is reasonable.

The purpose of our process is to de-risk the decision at every stage. The discovery phase (£3,000 to £5,000) gives you a detailed specification before you commit to the full build. Phased delivery lets you validate with real users before spending the full budget. Fixed-price quoting means the number you agree to is the number you pay. And the specification document you receive from discovery has value regardless of whether you proceed with us or take it to another developer.

You do not need to be certain that custom software is the right answer before making contact. That is what the initial conversation is for. We will tell you honestly whether your situation warrants a custom build, or whether a SaaS tool, a better-configured spreadsheet, or a process automation layer would serve you better at a fraction of the cost.