How Much Does Bespoke Software Cost in the UK?

I get asked "how much would this cost?" most weeks, usually before I know enough about the job to give a sensible answer. That's not evasiveness on my part. Bespoke software pricing genuinely does swing from £3,000 to £150,000 depending on what "bespoke" means in your case. This is my honest attempt to explain why, and what you can expect to pay for different types of project.

"Bespoke software" covers a lot of ground

The phrase gets used for wildly different things. A one-page tool that automates a single spreadsheet task is bespoke software. So is a multi-tenant SaaS platform with billing, permissions and an API. Both get quoted, and the numbers look nothing alike. Before you can compare prices, you need to know roughly which category you're in:

• A single automation or integration, connecting two systems you already use, or replacing one manual task with a script.
• An internal tool or portal, used by your own staff or a defined set of clients, with logins, roles and a database behind it.
• A customer-facing product, like a booking system, member area or app that the public interacts with directly.
• A full platform or SaaS product, with subscriptions, multiple user types, and features you'll keep adding to for years.

Rough cost bands, based on real projects

These aren't rate-card figures, they're the kind of numbers projects in each category tend to land on once scope is properly defined:

• Simple automation or integration: £1,500 to £8,000. Think "pull orders from Shopify into Xero" or "generate a PDF and email it automatically". Small, well-bounded, usually finished in one to three weeks.
• Internal tool or admin system: £6,000 to £25,000. A job-tracking system, a stock management tool, a client portal with a handful of screens. Complexity comes from the number of workflows and edge cases, not the number of buttons.
• Customer-facing app or booking system: £15,000 to £45,000. Payments, reminders, mobile-friendly design and real-world reliability all add cost, because they get tested by people outside your organisation who won't be forgiving of bugs.
• Full platform or SaaS product: £30,000 upwards, often £60,000 to £150,000+ for a first proper version. This is where subscriptions, multi-tenancy, and long-term architecture decisions start to matter.

If your project is a SaaS product specifically, I've written a more detailed breakdown of MVP costs elsewhere on this site. This article is about bespoke software more broadly, including the internal tools and integrations that never make it into "SaaS pricing" conversations but make up most of the actual demand.

What actually moves the price, beyond "how big is it"

Two projects with a near-identical feature list can cost very different amounts. The gap usually comes from a handful of things that don't show up on a feature list:

• How well-defined the requirements are. A clear brief with real screens, data fields and edge cases sorted out in advance is cheaper to build than a vague idea, because less time gets spent guessing and rebuilding.
• What it has to connect to. Every third-party system you integrate with (payment providers, accounting software, a CRM, an existing database) adds work, and sometimes adds risk if that system's API is poorly documented.
• Who uses it and what happens if it breaks. Software used by three internal staff who can shrug off a bug is a different risk profile to software handling customer payments at 2am. Reliability costs money to build in.
• Data migration. Moving existing records out of spreadsheets or an old system and into the new one is routinely underestimated. It's rarely a clean export.
• What happens after launch. Ongoing hosting, monitoring, and the odd fix as real usage reveals things testing didn't catch. This is separate from the build cost but part of the real total.

Why quotes for the "same" project vary so much

Get three quotes for what feels like the same job and you'll often see a three or four times difference. Some of that is padding, but a lot of it is real:

• An agency quote usually includes account management, a project manager, and several people's time on your job. That's not wasted money, but it is overhead you're paying for that a solo developer doesn't carry.
• Working with me directly, you're paying for one experienced person's time and nobody else's. No handoffs between a salesperson, a project manager and a junior developer who's never spoken to you.
• Cheap offshore quotes sometimes reflect genuinely lower costs, and sometimes reflect a much thinner understanding of your actual requirements, discovered later as change requests.
• The biggest driver of a bloated quote is usually scope creep baked in at quoting stage, someone pricing in features you didn't ask for because they assumed you'd want them.

How to sanity check a quote

Ask what's included in the number. A quote that separates "build", "testing" and "deployment" as line items, with rough hours against each, is more trustworthy than a single lump sum with no breakdown. Ask what happens if requirements change mid-build, since that's when relationships (and budgets) usually go wrong. And ask who owns the code and the account keys once it's built, because a cheap build that leaves you locked into the developer isn't actually cheap.

If you're still working out whether custom software is the right call at all, rather than an off-the-shelf tool, my build vs buy calculator is a quick way to check before you start collecting quotes. And if you want to see how I actually run a project, from first conversation to launch, that's laid out on how I work.

The honest short answer

For a small automation, budget low thousands. For an internal tool your team will use daily, budget five figures. For anything customer-facing with payments or an app store listing, budget towards the higher end of that. And for a proper SaaS platform, treat the first version as the start of an ongoing cost, not a one-off purchase. None of these numbers are fixed, but they're a far better starting point than a day rate multiplied by a guess.