The single largest cost driver is not technology — it is how much is still undecided. Every open question in the brief is converted into a buffer inside the number you receive. A vendor that cannot see the exceptions and edge cases has to assume the more expensive option. Putting two weeks into a discovery phase can cut the final cost much more than any rate negotiation.
Integrations tend to be the second big multiplier. A screen that writes to your own database is predictable; the same screen talking to a payment provider and a CRM is not. The unknown hides in the counterparty: poor web development outsourcing documentation, slow approval cycles, inconsistent data. Ask each bidder to list every external system, because this is the usual source of overruns.
Quality attributes quietly rewrite the budget. A tool used by a handful of staff is a very different build from the same idea serving a hundred thousand users. Security reviews, availability guarantees, performance under load, audit logging and localisation all add weeks of work. Put them in the brief laravel or symfony expect them priced as extras.
Who actually does the work matters. A day rate tells you almost nothing on its own: an experienced engineer at twice the price frequently turns out to be cheaper overall than two juniors who need heavy code review. Also ask who else is billed: coordination, QA, DevOps and UX design are legitimate costs, but they must be named rather than hidden inside a blended rate.
The number in the proposal is rarely the full cost of ownership. Expect hosting, paid APIs, logging and alerting difference between livewire and react a maintenance allowance for every year the custom software vs saas runs. A reasonable rule of thumb is that a live system requires a meaningful share of the original budget per year simply to stay current. Leaving it out of the budget has always been the classic mistake.
