Let's talk about the question everyone wants answered but few companies will address directly: what does custom software actually cost?
I understand the frustration. You ask for a price and you get "well, it depends." And while that's technically true, it's also a bit of a cop-out. So let me give you something more useful — real ranges, the honest factors that move the number, and how to make sure your money goes as far as possible.
The honest ranges (in plain numbers)
Every project is different, but here's a realistic picture of what you're looking at when working with a skilled team:
- A simple MVP or internal tool: roughly £8,000–£25,000. Think a focused web app, a straightforward mobile app, or a tool that automates one specific process.
- A mid-sized product: roughly £25,000–£75,000. A proper SaaS platform, a customer-facing app with multiple features, or a system with integrations and user accounts.
- A complex platform: £75,000 and up. Multi-user systems, heavy integrations, AI features, real-time data, or anything at serious scale.
These numbers assume you're working with an experienced offshore or blended team. Build the same thing purely with a UK or US agency and you can comfortably multiply by three or four.
What actually drives the price
Complexity of features
This is the big one. A login screen is cheap. Real-time collaboration, payment processing, AI-driven recommendations, or complex business logic — those cost real money because they take real engineering. Every "wouldn't it be cool if…" adds to the bill.
How clear your requirements are
This one surprises people. Vague requirements cost more, not less. When we're guessing what you want, we build, you say "not quite," we rebuild. Clear requirements mean we build it right the first time. Time spent getting clear upfront is the cheapest time in the whole project.
Integrations
Connecting to other systems — your CRM, payment gateways, third-party APIs, legacy databases — adds complexity. Sometimes those systems are beautifully documented and it's a breeze. Sometimes they're a nightmare from 2009 with no documentation. It varies wildly.
Design polish
A functional interface is one price. A gorgeous, pixel-perfect, delightful experience with animations and careful attention to every detail is another. Both are valid — it just depends on how much the experience matters for your product.
Where people waste money (avoid these)
Having seen a lot of budgets, here's where money tends to evaporate:
- Building everything at once. Trying to launch with every feature instead of starting focused and expanding. This is the single biggest budget-killer.
- Changing direction constantly. Every major pivot mid-build means throwing away work you paid for.
- Skipping discovery. Diving into code without a clear plan feels faster but almost always costs more.
- Choosing purely on price. The cheapest quote often becomes the most expensive project once you factor in rework and delays.
How to get the most for your budget
Here's the advice I'd give a friend. Start with the smallest version of your idea that delivers real value. Get it in front of real users. Learn what they actually want (it's never exactly what you assumed). Then reinvest in what's working. This approach means you spend money on the right things instead of guessing.
Also, be honest with your development partner about your budget. I know the instinct is to hide it so you don't get "charged up to it." But a good team uses your budget to help you prioritise — to tell you what's essential now and what can wait. We can't help you spend wisely if we're working blind.
A quick note on the cheapest option
I won't lecture you, but I'll say this once: the temptation to go with the rock-bottom quote is real, and it burns people constantly. Software that's built badly doesn't just cost you the rebuild — it costs you the lost time, the missed opportunities, and the stress. Value and cheapness are not the same thing. Aim for value.
Want a real number for your project?
The only way to get a genuinely accurate figure is a proper conversation about what you're actually trying to build. We offer free scoping calls where we'll ask the right questions and give you an honest ballpark — no obligation, no pressure.
Tell us about your idea and we'll give you a straight answer on what it'll take. Get in touch today.