The single largest cost driver is not the technology stack — it remains uncertainty. Each unanswered question in the specification becomes a buffer somewhere in the quote. A vendor that has no visibility into the exceptions and edge cases will assume a pessimistic case. Investing a few days in requirements work often reduces the overall figure much more than haggling over hourly rates.

Third-party integrations tend to be another reliable source of cost. A form that saves data is low risk; the same functionality connected to an old accounting system is not. The effort sits in the third party: undocumented APIs, slow approval cycles, inconsistent data. Ask each bidder to break integrations out as separate items, as this is the usual source of overruns.

The requirements nobody writes down can easily double the estimate. A tool used by a handful of staff is a very different build from the same functionality serving a hundred thousand users. Audit and compliance requirements, availability guarantees, scalability, traceability and localisation all add real engineering time. State them early livewire or alpine js expect the estimate to move later.

The mix of people behind the number changes the arithmetic. An hourly rate says very little on its own: an experienced engineer at twice the price frequently turns out to be cheaper overall than a pair of junior hire developers in europe who require heavy code review. Also ask which roles are billed: delivery management, testing, DevOps and UX design have to be done by someone, social media marketing agency but they should be visible in the estimate.

The number in the proposal is never what you will actually spend. Budget for infrastructure, paid APIs, monitoring and a change budget annually. A useful planning figure holds that software in active use consumes a meaningful share of the original budget every year simply to stay current. Treating the launch as the finish line remains the most frequent planning error.