How much does custom software cost in the UK? A 2026 guide

The cost of custom software depends on scope, integrations and risk. Here's what moves the number, what you pay after launch and how to keep spending under control.

Key takeaways

  • Cost follows scope, integrations and risk, and you can estimate each of them before anyone writes code.
  • Plan for ongoing costs of roughly 15 to 20 percent of the build cost each year, plus hosting.
  • Scope has the biggest effect on cost. A tightly defined first release is cheaper and safer than a big-bang build.
  • A good quote lists deliverables, assumptions and exclusions as well as a total.

“How much does custom software cost?” is the first question every buyer asks, and the least satisfying answer is “it depends”. It does depend, but on things you can name. Cost follows scope, complexity, integrations and the team you hire, and you can estimate each of them before anyone writes code.

This guide describes the main types of custom software project, explains what pushes the cost up or down and covers the costs that arrive after launch. It also covers how to reduce spend without cutting corners and how to read a quote so you can compare agencies fairly.

Typical custom software projects by type

The table below describes four common project types for B2B companies, with a typical timescale and what each usually includes. The timescales are planning guides. Team seniority, the number of integrations and the specifics of your project can move any of them.

Project type Typical timeline What you usually get
Internal tool 6 to 12 weeks Admin dashboards, workflow tools, reporting, role-based access, one or two integrations
Customer portal 2 to 5 months Secure login, account management, documents, billing views, notifications, integration with your CRM or ERP
SaaS MVP 3 to 6 months Core product workflow, multi-tenant accounts, subscription billing, admin tools, basic analytics
Complex platform 6 to 18 months Multiple user roles, heavy integrations, real-time features, compliance requirements, high-scale infrastructure

Cost rises with the length of the timeline and the size of the team, so a complex platform costs a good deal more than an internal tool. Senior-heavy teams charge more per day but often finish sooner with less rework. A guide like this one can’t replace a scoped estimate.

If you want a price for your own project, book a free scoping call and we’ll follow up with a fixed, written quote.

Internal tools

Internal tools replace spreadsheets, email chains and manual data entry. They’re usually the cheapest category: the users are your own staff, the design can be utilitarian and you control the rollout. Cost rises when the tool has to sync with several legacy systems or enforce complex approval rules.

Customer portals

A portal is customer-facing, so design polish, security and reliability matter more. Authentication, permissions, audit trails and email notifications all add effort. If the portal pulls live data from an ERP or billing system, the integration work often costs as much as the portal itself.

SaaS MVPs

A SaaS MVP is more than a web app. It needs multi-tenant data separation, subscription billing, onboarding and an admin console to run the business. Our SaaS development work is built around getting to a first paying customer without overbuilding.

Complex platforms

Platforms with marketplaces, real-time collaboration, heavy data processing or regulatory requirements sit at the top end. Budgets at this level should include a paid discovery phase, because the biggest risks are in what you don’t yet know.

What drives the cost

Almost every estimate comes back to the same few factors.

  • Scope and feature count. Each feature carries design, build, testing and maintenance cost. Features interact, so cost grows faster than the feature list.
  • Integrations. Connecting to Salesforce, Xero, NetSuite, Stripe or a legacy system with a poor API is where estimates tend to grow. Every integration has authentication, error handling and edge cases. We cover integration costs in more detail below.
  • Design depth. A functional interface is cheaper than a fully custom design system with animations, accessibility testing and multiple brand themes.
  • Data complexity. Migrating years of messy records, or modelling a domain with many exceptions, takes real analysis time.
  • Security and compliance. UK GDPR, ISO 27001, PCI and accessibility requirements add engineering, documentation and testing.
  • Scale and performance. Software for 50 users and software for 50,000 users are different engineering problems.
  • Team composition. A senior engineer has a higher day rate than a junior one and usually costs less per feature.
  • Clarity of requirements. Vague requirements are the most expensive kind. Clarifying them before the build is almost always cheaper than finding gaps mid-project.

What do custom integrations cost?

Integrations are the line in a quote that moves most between agencies, because the effort depends on the other system more than on yours. Four things set the price of a custom integration:

  • The quality of the other system’s API. A documented REST API with a test environment is quick to work with. A legacy system with no API, or one that only exports files overnight, needs more work to read from and write to.
  • Which way the data flows. Reading data one way is the simplest case. A sync that runs both ways has to decide which record wins when both sides change, and that logic takes time to design and test.
  • What happens when it fails. An integration that moves orders or invoices needs retries, alerts and a way to replay a failed run. One that copies a report overnight can simply run again the next night.
  • How much the data has to change. Mapping fields one to one is cheap. Merging records, cleaning duplicates or translating between two different ways of describing a customer adds analysis time.

Each integration also has a running cost. APIs change, credentials expire and the other supplier releases new versions, so integrations are one of the main reasons software needs maintenance after launch.

For simple, low-volume connections between popular tools, an automation platform can be cheaper than custom code. We compare the two, including how the costs change as volume grows, in custom integration or automation platform.

Hidden and ongoing costs

The build is only part of what software costs over its life. Budget for the following from the start.

Maintenance

A common rule of thumb is that ongoing maintenance costs 15 to 20 percent of the original build cost each year. That covers dependency updates, security patches, bug fixes, small improvements and keeping integrations working as third-party APIs change. Skipping maintenance leads to a larger bill later.

Hosting and infrastructure

Production software needs servers, databases, backups, monitoring and a safe way to deploy. Costs depend on traffic, data volume and availability requirements, so a modest internal tool needs far less than a high-availability platform. We host on AWS in London and quote hosting monthly based on your requirements.

Third-party services

Email delivery, payment processing, error tracking, search, maps and AI model usage are usually billed per use or per seat. Each is small, but together they add up.

Internal time

Your team will spend time in workshops, reviewing demos, testing and training users. That time is a real cost, even if it never appears on an invoice.

Change requests

Requirements evolve once people see working software. Budget a contingency of 10 to 20 percent for changes, or agree a process for trading scope in and out.

How to reduce the cost

You can lower the cost of custom software without lowering its quality, mostly by being clear about what you build first.

  1. Start with an MVP. Identify the one workflow that proves the value and build only that. You learn from real users before spending on the rest.
  2. Phase the work. Split the roadmap into releases that each deliver usable value. Phasing spreads the cost out and lets you stop or change direction.
  3. Buy what isn’t differentiating. Authentication, payments and email are solved problems. Use proven services instead of building your own.
  4. Cut the nice-to-haves. Sort features into must-have, should-have and later. Be strict about the first group.
  5. Invest in discovery. A short, paid discovery phase that produces clear requirements and a prototype usually saves more than it costs.
  6. Make decisions quickly. Waiting for approvals and feedback stretches timelines and adds cost on any time-based engagement.

If you’re weighing a bespoke build against off-the-shelf tools, our guide on build vs. buy for B2B custom software walks through the trade-offs.

How to read a quote

Two quotes for the same project can differ widely and both be reasonable, because they assume different things. When you compare quotes, look for the following.

  • A defined scope. Deliverables should be listed in plain language, ideally with acceptance criteria. In the UK this is usually set out in a statement of work. “Customer portal” isn’t a scope.
  • Stated assumptions. Number of integrations, user roles, devices supported and data volumes should be explicit.
  • Exclusions. What isn’t included matters as much as what is. Check for design, data migration, training, QA and project management.
  • Pricing model. Fixed price, time and materials or a hybrid each shift risk differently. We cover this in fixed price vs. time and materials. If the quote is built on day rates, ask how many days it assumes and what happens if the estimate is exceeded.
  • VAT. Check whether the total includes VAT. If your business can’t reclaim it, VAT adds to the cost.
  • Ownership terms. You should own the code and be able to host it anywhere. Confirm this in writing.
  • Post-launch support. Look for the warranty period, maintenance terms and response times.
  • Team and timeline. Who will do the work, and how often will you see progress?

Getting to a number you can trust

The most reliable way to get an accurate price is a short discovery phase. You describe the business problem, the team maps the workflows, data and integrations, and the output is a prioritised scope with an estimate you can plan around. It also tells you whether you want to work with the team.

You can see how we run engagements on our process page. If you already have a rough brief, send it through the contact page and we’ll tell you whether the budget and scope line up.

The bottom line

The cost of custom software for B2B companies varies widely, from a focused internal tool built in a matter of weeks to a complex platform built over more than a year. Scope, integrations and risk account for most of the difference.

Plan for the full picture: the build, roughly 15 to 20 percent of the build cost each year in maintenance, hosting, third-party services and your own team’s time. You can reduce cost by building an MVP, phasing releases and buying commodity features. Judge any quote by its scope, assumptions and exclusions as well as its total.

If you’d like an estimate for your project, our custom software development service for UK businesses starts with a conversation about the problem you’re solving. After a call we give you a fixed, written quote.

Keep reading

Have a project in mind?

Tell us what you need and we'll reply within one working day. Once it's sent, you can book a free 30-minute call with Louie, our founder, and we'll follow up with a written quote.