The biggest cost driver is rarely the technology stack — it is unclear scope. Every open question in the requirements is converted into a contingency in the estimate. A supplier that does not know the edge cases has to assume a pessimistic case. Investing a few days in a discovery phase frequently cuts the overall figure by far more than haggling over hourly rates.

Integrations are the second big multiplier. A screen that writes to your own database is easy to estimate; the same screen connected to an old accounting system is a different problem. The unknown sits in the other system: undocumented APIs, slow approval cycles, fields that mean something different on each side. Ask any vendor to price integrations separately, as that is where the numbers slip.

Non-functional requirements silently change the estimate. A tool used by twenty people is a very different build from the same feature set serving a hundred thousand users. Audit and compliance requirements, uptime targets, performance under load, audit logging and node.js consulting services localisation add real engineering time. State them early or you can expect them priced as extras.

Who actually does the work changes the arithmetic. An hourly rate tells you almost nothing on its own: a senior engineer at a higher rate frequently turns out to be less expensive in the end than two inexperienced developers who require supervision and custom software development rework. Also ask who else is billed: project management, testing, DevOps and UX design have to be done by someone, but these should be itemised.

The quoted figure is never what you will actually spend. Expect cloud costs, paid APIs, logging and alerting and an ongoing support budget annually. A common working assumption says that a live system consumes a recurring percentage of the original budget every year for updates, security patches and small improvements. Treating the launch as the finish line remains the classic mistake.