The hidden bill: how software quietly costs more than the quote

The quote says one number. The software ends up costing another, usually larger, number. This is not always because someone was dishonest. It is because the quote covers the part you can see, and software has a habit of costing money in places you cannot.

If you are about to spend real money building something, it helps to know where the rest of the bill hides.

The running cost nobody mentions

Software is not a painting you buy once and hang on the wall. It runs, and running it costs money every month: the servers it lives on, the services it calls, the storage it fills. A system that was built without an eye on this can technically work perfectly and still quietly drain a few hundred, or a few thousand, a month more than it needed to.

Ask what it costs to run, not just to build. A good builder will know the answer to the pound. If nobody can tell you, that is the answer.

The cost of rework

The cheapest code to write is the code you did not need. A surprising amount of software spend goes on building things that turn out to be wrong, then unbuilding them, then building the right thing. Every one of those laps costs money, and the meter runs the whole time.

This is why working out the right thing to build first, before anyone writes code, is not a delay. It is the single biggest saving available, and it never appears on a quote.

The cost of the shortcut

Under time pressure, builders take shortcuts. Sometimes that is fine and sensible. But a shortcut that is not written down and not planned for is a debt, and like all debts it collects interest. The bill arrives later, when a small change turns out to require unpicking three others, and the quick job takes a fortnight.

You cannot avoid shortcuts entirely. You can insist they are named, so the interest is a decision and not a surprise.

The most expensive mistake of all

None of these is the big one. The big one is building the wrong thing well. A beautiful, robust, thoroughly tested piece of software that nobody actually needed is the most expensive outcome there is, because you paid full price for something with no value.

This is why the most useful money you spend is often the money spent before building, working out what is truly worth making. It feels like the least productive stage. It is the most.

How to read a quote honestly

So when you get a number, ask three questions. What does it cost to run each month? What are we assuming, and what happens to the price if those assumptions are wrong? And what is the cost of finding out, cheaply and early, whether we are building the right thing at all?

The answers will not be on the quote. They are the difference between the number you are shown and the number you actually pay.