What custom software should actually cost a founder

Why five quotes for one project don’t agree

Ask five firms to quote the same product and you’ll get five numbers that don’t look like they’re describing the same work. That’s not because four of them are lying. It’s because “a web app” isn’t a specification, and every firm quietly fills in the gaps with assumptions shaped by the kind of client they usually serve.

An enterprise shop assumes account managers, formal QA and a compliance review. A freelancer assumes you’ll make the decisions fast and accept some rough edges. Same brief, wildly different mental picture of the work — and the price follows the picture.

What actually drives the number

Three things move a software quote more than anything else: how many distinct user types the system has, how many external systems it must talk to, and how much of the requirement is still unknown. A single-user tool with no integrations and a clear spec is a small job. Add a second user type with different permissions, one payment provider and one accounting sync, and the surface area roughly doubles.

Unknowns are the expensive part. A firm quoting a vague brief either pads heavily to cover the risk, or quotes low and recovers it through change requests. Both are rational responses to ambiguity — which is why the cheapest thing you can buy first is clarity.

The ranges we actually see

For a scoped prototype and design system: low five figures, a couple of weeks. For a narrow first release that can genuinely take money — one workflow, one customer type, one payment path: mid five figures. For a multi-tenant platform with billing, admin tooling, two integrations and a mobile companion: low six figures, spread across months.

Enterprise agencies quote those same three projects at roughly three to five times those numbers. Much of the difference is account management, sales cost and risk padding rather than engineering — which is exactly why founders get quoted out of the room.

How to compare quotes honestly

Ask every firm the same four questions: what’s explicitly out of scope, who owns the code and cloud accounts, what happens to the price if a requirement changes at week six, and what you’d have if you stopped after the first stage.

Firms that answer those crisply are usually the ones who’ve done the work before. Firms that get vague are quoting the sale, not the build.

The cheapest first purchase

Buy the scope before you buy the build. Two weeks of design and technical scoping gets you a clickable prototype, an architecture outline and a fixed price per stage — and it’s portable.

Take it to three firms and you’ll get three comparable numbers instead of three guesses. If a firm won’t sell you that scoping work separately, that tells you something too.

---

Planning a build? Start a conversation and we’ll tell you what your idea would actually cost — before you talk to anyone selling hours.