How Much Does Bespoke Software Cost in the UK?

Typical UK market ranges in 2026

There is no official price list for custom software, so the honest answer is a range. Two published sources checked in October 2026 give a sense of the market:

• One UK software agency publishes a 2026 cost guide (updated 1 October 2026) that puts bespoke software at £15,000 to £500,000+. It gives simple internal workflow tools at £10,000 to £20,000, mid-complexity customer portals at £25,000 to £60,000, and complex custom CRM or ERP systems at £150,000 to £500,000.
• IT Jobs Watch reports a median UK Software Developer contract rate of £525 a day over the six months to 10 October 2026, with the 10th to 90th percentile sitting between £365 and £612. Agency rates are usually higher than contractor rates because they include project management, testing and cover.

Treat these as a sanity check, not a quote. Two systems that sound alike ("a customer portal") can differ by a factor of five once you list what they actually need to do.

What actually drives the price

Most of the cost sits in a handful of things that are easy to underestimate:

• Integrations. Every connection to Xero, Sage, Stripe, Shopify or an old in-house database needs authentication, error handling, retries and testing against the other system's rules and rate limits.
• Business rules. Pricing matrices, approval chains, VAT edge cases and exceptions ("except for trade customers on account") take longer than screens.
• Users and permissions. One login type is simple. Staff, managers, customers and suppliers each seeing different data needs role-based access and an audit log.
• Data migration. Moving ten years of spreadsheets or an Access database means cleaning, mapping and checking, not just importing.
• Reporting. Dashboards and exports that finance trusts need agreed definitions and test data.
• Non-functional needs. Uptime, backups, GDPR controls, accessibility and security testing all add effort, and all matter.

How to keep the cost down without cutting corners

The cheapest software is the feature you do not build. Practical ways to spend less:

1. Start with the painful process. Build the part that removes the most retyping or errors first, then add the rest in phases. Our MVP guide explains the approach.
2. Use off-the-shelf where it fits. Let Xero do accounting and Stripe take payments. Custom code should glue them together and handle what makes your business different.
3. Write things down. A clear spec removes guesswork from a quote. See how to write a software requirements spec.
4. Pick a mainstream stack. PHP 8 with Laravel, or Node.js with TypeScript, plus MySQL or PostgreSQL, means any competent developer can maintain it later.
5. Budget for running costs. Hosting, monitoring and updates are a yearly cost. Our maintenance budget guide covers it.

Fixed price, time and materials, or phased?

Fixed price suits a defined scope: you know the cost, and the supplier carries the risk of their own estimate. Time and materials suits open-ended research or a product that will change weekly, but needs close budget control. A phased plan combines the two: a fixed price for phase one, then a fresh fixed price for each later phase once you have learned from real use.

Whichever model you choose, check what is included: testing, deployment, documentation, a warranty period for defects, and handover of the source code.

Worked example: one requirement, three prices

Take a common request: "we want customers to log in and see their orders and invoices". Three suppliers could reasonably price it very differently, because the sentence hides several decisions.

• Version A reads orders from your existing database, shows them in a simple list, and lets customers download invoice PDFs that already exist. One customer type, email and password login.
• Version B adds a live link to Xero so invoice status and balances are always current, a pay-now button through Stripe, and separate logins for several people at the same customer company, each with their own permissions.
• Version C adds reordering with customer-specific price lists, credit limits checked against the ledger, delivery tracking from a courier API, Microsoft single sign-on for staff, and an audit log for every change.

All three are "a customer portal". Version C might take several times the effort of version A, because each addition brings its own integration, rules, testing and support. That is why a quote without a written scope is a guess, and why comparing a low quote for version A with a higher quote for version C tells you nothing.

When you ask for prices, say which version you mean, list the systems involved, and say how many users and records you expect. If you are not sure, ask the supplier to price a small first phase and list the rest as options. That gives you a firm figure to start with and a clear view of what each extra feature adds.

When to talk to dijitul

dijitul has built bespoke web-based software since about 2011, starting with automated billing software that invoiced customers for electricity, water and gas use. We do not publish prices because two projects are never the same. Instead, we start with a free chat, run a short discovery and scoping stage, then give a fixed-price quote for a written scope. You own the code and the data at the end. If you have a rough idea and a budget in mind, ask for a quote and we will tell you plainly what is realistic.

Related