"How much does custom software cost?" is the most searched question in our category, and the most poorly answered. Most articles dodge the question with ranges so wide they are useless ("between 30,000 and 2 million euros"), or they refuse to give numbers at all and funnel the reader to a contact form. Neither is helpful if you are trying to budget an actual project

Choosing a software house is a high-stakes decision. For most companies, a custom development project represents six figures of investment and months of commitment. Yet the document that kicks off this relationship, the quote or proposal, rarely gets the scrutiny it deserves.

"Let's start with an MVP" has become the default opening line for almost every conversation about custom software. The logic sounds impeccable: build the smallest version that delivers value, test it with real users, then expand based on what you learn. Less risk, lower upfront cost, faster time to market.

Most proposals for custom software spend 90 percent of their pages on the build phase and one paragraph on maintenance. This reflects how most buyers think about the investment: the big decision is "who will build it," not "who will keep it running." It is also backwards.

When a custom software project fails, the reflex is to blame the vendor. Sometimes that is fair. More often, after 10 years of building software at codelabs.rocks, we have found the dominant cause sits on the client side: the organisation was not ready to run a project of this kind. The code might be fine, the deadlines may be hit, but the business never absorbs the software the way it was supposed to, and the investment produces less value than it should.