The biggest cost driver is rarely the choice of framework — it is almost always uncertainty. Every ambiguity in the brief becomes a contingency somewhere in the quote. A team that has no visibility into the exceptions and edge cases will assume the worst. Putting two weeks into a proper discovery can cut the final cost much more than negotiating the rate.

Connections to other systems remain the next major multiplier. A form that saves data is low risk; the same functionality connected to a payment provider and a CRM is a different problem. The unknown sits in the third party: rate limits and sandbox access, slow approval cycles, inconsistent data. Ask any vendor to list every external system, because this is the usual source of overruns.

Non-functional requirements quietly rewrite the estimate. An internal tool used by twenty people costs far less than the same functionality handling public traffic. Compliance work, availability guarantees, performance under load, data retention rules and localisation each add real engineering time. State them early livewire or vue you can expect them priced as extras.

Who actually does the work matters. A rate card tells you almost nothing on its own: an experienced engineer at twice the price is often less expensive in the end than two juniors who require constant review. Check too who else is billed: coordination, QA, DevOps and UX design have to be done by someone, but they should be visible in the estimate.

The build price is rarely the full cost of ownership. Expect cloud costs, subscriptions and licences, logging and seo for saas company alerting and an ongoing support budget each year. A useful planning figure says that a live system consumes a recurring percentage of the initial investment per year in fixes, updates and small changes. Leaving it out of the budget has always been the most frequent planning error.