The biggest cost driver is rarely technology — it is uncertainty. Every ambiguity in the specification is converted into a contingency inside the number you receive. A vendor that cannot see what happens on the unhappy path must assume a pessimistic case. Spending a week on a proper discovery frequently cuts the total by far more than haggling over hourly rates.

Integrations remain the second big multiplier. A feature that touches only your own data is predictable; the same screen talking to an old accounting system is not. The unknown sits in the third party: poor documentation, slow approval cycles, data that does not match your model. Ask any vendor to list every external system, because this is the usual source of overruns.

The requirements nobody writes down can easily double the estimate. An web application development for edtech used by a handful of staff is a very different build from the same functionality serving thousands of external customers. Compliance work, uptime targets, performance under load, data retention rules and multi-language support add real engineering time. State them early or else expect them to arrive later as change requests.

Who actually does the work matters. A day rate reveals almost nothing on its own: one senior developer at a premium rate is often less expensive in the end than two inexperienced developers who require supervision and rework. Check too which roles are billed: project management, quality assurance, DevOps and design have to be done by someone, but they should be visible in the estimate.

The number in the proposal is never the full cost of ownership. Expect hosting, paid APIs, logging and alerting and a change budget for every year the custom software vs saas runs. A useful planning figure holds that a live system requires a recurring percentage of the original budget per year simply to stay current. Treating the launch as the finish line has always been the most frequent planning error.