How much custom software costs, and why nobody gives you a clear number

When someone asks how much an app costs, they expect a number, like asking the price of a car. And they almost always get an uncomfortably wide range or an 'it depends'. It's a frustrating answer, but it's usually the most honest one available given what you've told them.

The trouble is that 'an app' can mean a thousand things. It's like asking how much a house costs. A studio or a detached house? Renovated or yet to be built? Software is worse still, because a lot of the work sits in things you can't see: what happens when something fails, how many users it holds at once, what security sits behind it.

What actually drives the price usually isn't what the client thinks. The pretty screen is the cheap part. The expensive part is the odd rules of your business and the connections to systems you already run. Two apps that look identical can cost one three times the other because of what's inside them.

So be a little wary of anyone who throws out an exact number on the first call, before understanding what you need. Either they've assumed a pile of things that may not hold, or they plan to charge you for the extras later once you're already in. A wide range at the start that narrows as things get specific is usually a sign the person is taking it seriously.

The healthy way to handle this is the reverse of how it's usually asked. Instead of 'how much does all of it cost?', ask 'what's the smallest thing that solves my problem, and what does that cost?'. You build that first version, see it working, and decide the next step with data in hand rather than a giant budget signed blind.

Custom software done well is rarely cheap. But it's worth looking at two numbers, not one: what it costs to build, and what it saves or earns you each month once it runs. The second one can be estimated, and it's the conversation actually worth having before you sign anything.