SoftwareUp
Back to all posts

How much does custom software cost? A realistic guide

Ask a software company what custom software costs and you’ll usually hear “it depends.” That’s true, but it’s no help when you’re trying to set a budget. So here are real numbers.

Typical price ranges

Across the European market, a first version usually lands in one of three bands:

  • A focused tool: around €10,000 to €30,000
  • A connected system: around €40,000 to €100,000
  • A core platform: around €80,000 to €250,000

Large enterprise projects can go well beyond that.

These are broad market ranges, not Softwareup prices or quotes. The bands overlap because scope matters more than the label. Where your project sits depends on what the software needs to do, what it connects to and how much data it handles. The rest of this guide explains what moves a project up or down.

What you’re paying for

You’re not paying for lines of code. You’re paying for the work it takes to turn the way your business runs into software your team will actually use. Depending on the project, that includes:

  • Working out what the software needs to do, before anything is built.
  • Designing the screens and the steps your team will follow.
  • Building and testing it.
  • Connecting it to the tools you already use and moving your existing data across.
  • Setting it up and getting it live.

The ranges above cover that initial build. After launch come the running costs: hosting, any licences, support, fixes and improvements. A common rule of thumb is to set aside 10% to 25% of the original build cost each year.

When you get a quote, ask what’s included, what’s ongoing and whether VAT is on top.

Three types of project

Two projects in the same band can still differ a lot. Use these to place yourself, not as a price list.

A focused tool

Typical range: €10,000 to €30,000

One job, done well, for one team. For example, replacing the spreadsheet you use to track stock with a proper tool. The price depends on how many people use it, what data it holds and whether it needs to talk to anything else.

A connected system

Typical range: €40,000 to €100,000

Several workflows joined up and used every day. Think of a business that handles customer orders, site visits and invoicing in one place instead of three. Integrations, data migration and how different teams work together drive the cost.

A core platform

Typical range: €80,000 to €250,000+

The software a large part of your business runs on, often handling customers, payments or large volumes of data. Security, reliability and support matter more here, because downtime costs money. Large enterprise platforms sit above this band.

What moves the price

Features and scope. Every workflow has to be designed, built and tested. The biggest saving comes from being honest about what the first version must do and what can wait.

Integrations and data. Connecting your accounting, payment or delivery systems adds work. So does moving existing data, especially if it needs cleaning first.

Design. A clean, standard interface suits most internal tools. More tailored design pays off when customers use the software, or when staff spend all day in it.

Testing, security and performance. You won’t see these on screen, but they decide whether the software holds up. The right level depends on what’s at stake if something goes wrong.

Unknowns and changes. An unfamiliar system or a vague requirement makes effort harder to predict. Changing direction halfway through means redoing finished work. Ask what’s still unknown, and how changes will be agreed and priced.

A worked example

Say a wholesale business with a team of ten tracks its stock in a shared spreadsheet. Orders get missed and counts drift.

At its simplest, a stock tool for that team is a focused tool: one workflow, a handful of users, no connections. That sits at the lower end of the first band.

Now add a link to the accounting system so stock and invoices match. Add a cleanup of five years of spreadsheet data. Add a phone app for the warehouse floor. Each request is reasonable, and each one moves the project up, towards the top of the first band or into the second.

Nothing about the business changed. The scope did. That’s why two quotes for “a stock system” can be far apart.

How to compare quotes

A lower quote doesn’t automatically mean something’s been missed. One company may have scoped less; another may have included work you don’t need. Before you compare totals, ask each one:

  • What’s included, and what isn’t?
  • Which integrations, data migration and testing are covered?
  • Is this a fixed price or an estimate? How are changes priced?
  • What will hosting, licences and support cost after launch?
  • What will you own when it’s finished, including the code?

Give every company the same answers to the same questions, then ask them to explain any big gaps. Our guide to why software quotes vary so much goes through these checks in more detail.

How to keep your budget under control

Start small. Build the part that delivers value first, put it in your team’s hands, then grow from there. A daunting total becomes a series of smaller steps you can check as you go.

Define the outcome, not the feature list. Say what the first version has to achieve, including any security or compliance needs. Every feature should earn its place against that.

Agree what “done” means. Set clear acceptance criteria before work starts, so both sides are checking against the same thing.

Plan for life after launch. Agree how fixes, support and new features will be handled and charged, so running costs don’t come as a surprise.

Ask for a breakdown, not a single number. A useful proposal ties the price to the scope, states its assumptions and names what’s still unknown. A company that can explain where the money goes has thought about your project.

So, where does yours fit?

If your project does one job for one team, start from the first band. If it joins up the way several teams work, plan for the second. If your business will run on it, budget for the third. Then use the questions above to narrow it down.

The fastest way to a real number is a conversation about your scope.

Not sure which band you’re in? Tell us what you need and we’ll tell you where it’s likely to land, and what we’d build first.