PLURY · SOFTWARE, PLANNED AND KEPT WORKING
§Budgeting

Why the cheap quote is expensive

Send one brief to three builders and the quotes come back far apart. The gap is rarely efficiency — it’s what each quote decided not to count.

Send the same brief to three builders and the quotes come back far apart. The instinct is to average them, or trust the middle one, or negotiate the lowest. All three instincts are wrong in the same way: they assume the quotes are for the same project. They aren’t.

Where the price actually lives

Custom software costs what four things cost, and only one of them is visible in a demo.

Integrations. Every other system yours has to talk to — payments, shipping, accounting, the government — adds a conversation, and every conversation has terms.

Data migration. Your existing data has to move into the new thing, be deduplicated, and be checked. It is slow, invisible when it’s done right, and catastrophic when it’s skipped.

Who sees what. Permissions sound trivial until the day someone sees a number they shouldn’t. Doing them properly touches every screen and every report.

Deciding. How much has been settled before the build starts. A brief with decisions made shrinks every honest quote. A brief with decisions deferred inflates all of them — someone pays for those decisions, eventually.

What the cheap one left out

A quote that comes in at half the others is not quoting the same work. It is quoting the visible parts — the screens, the flow, the demo — and leaving the rest to be discovered. The excluded costs don’t disappear. They arrive later, wearing different names: change requests, phase two, or the quiet version where the software just doesn’t get adopted and the money is gone.

The expensive quote isn’t necessarily more honest either. But a quote that is dramatically cheaper than its siblings has, with high reliability, excluded exactly the parts that make software real.

How to compare

Line by line, not number against number. For each quote: what does it include, what does it assume, what is explicitly out. Then ask every builder the same three questions. What happens to our existing data? What happens the day this breaks at month-end? What have you deliberately left out?

A builder who answers those three comfortably is quoting reality. The number is just where that shared understanding gets written down — and it’s the understanding you’re shopping for, not the number.


Working on something this applies to? Tell us about it — thirty minutes, no pitch.