Guide · 8 minutes
What does custom software cost?
A credible price does not start from the number of screens. It starts from the processes that have to change, the data that already exists and the risks that have to be removed.
Updated
Why there is no universal price
Two applications that look identical in a one-sentence description can require wildly different effort. A CRM for a team noting down customer conversations is a different project from a CRM that calculates quotes, validates documents, requests approvals and synchronises data with accounting.
The big difference does not come from colours or from how many pages the interface has. It comes from rules, exceptions, integrations and the consequences of an error. An estimate given before those are understood is either a guess or a price that will be renegotiated once the project starts.
The six components of an estimate
A useful quote separates the work into components. That is how you see what can go into version one and what can wait without blocking the outcome.
- Clarifying the flows and the prototype: who uses the application, what decisions they make and what they need to see.
- Building the core functions: authentication, roles, operations, reports and notifications.
- Integrations with external services: invoicing, payments, couriers, ERP, suppliers or other APIs.
- Importing and cleaning data from the old application, spreadsheets or inconsistent databases.
- Testing, hardening and preparing the production environments, backups and monitoring.
- Launch, training people and the stabilisation period after go-live.
What information makes an estimate more accurate
You do not need a technical specification. A short recording of the current process, examples of the files in use and three or four situations that produce the most errors are often worth more than a long feature list.
It helps to state who makes decisions, how many people will use the first version, which systems cannot be replaced, and whether there is a deadline imposed by a season or by legislation. Unknowns should not be hidden; they should be marked and investigated before they turn into unplanned costs.
How to compare two quotes properly
Do not compare only the total. Check whether both quotes include the same things: data migration, infrastructure, publication, tests, documentation, source code and the remediation period. A smaller quote may exclude exactly the unavoidable work at the end.
Look for the written assumptions. If the supplier assumes the partner's API works, that the data is clean, or that feedback arrives the same day, those assumptions must be visible. They explain why a deadline can move and let both sides decide early what to verify.
How to cut cost without wrecking the project
The healthiest saving is a smaller first version, not dropping testing, security or documentation. Pick one complete flow that produces value, put it in the hands of real users, and add the rest once you see where time is being won.
Before commissioning development, check whether an existing product solves the problem well enough. Custom software is worth it when your own process gives you an advantage, when integration is essential, or when the cost of manual work has grown larger than the cost of change.