rn rnrn

The dominant factor is rarely technology — it remains unclear scope. Every open question in the requirements is converted into padding somewhere in the quote. A team that cannot see the exceptions and edge cases has to assume the worst. Spending a week on a discovery phase can cut the total much more than negotiating the rate.

Connections to other systems are the next major multiplier. A feature that touches only your own data is easy to estimate; the same functionality connected to an old accounting system is not. The unknown sits in the counterparty: poor documentation, waiting on someone else’s team, inconsistent data. Ask each bidder to break integrations out as separate items, because this is the usual source of overruns.

The requirements nobody writes down can easily double the estimate. An application used by a small internal team costs far less than the same idea handling a hundred thousand users. Audit and compliance requirements, high availability, load handling, data retention rules and angularjs vs vue localisation add measurable effort. State them early or you can expect them to arrive later as change requests.

Who actually does the work matters. An hourly rate says little on its own: a senior engineer at twice the price can be cheaper overall than a pair of junior golang consulting services developers who require heavy code review. Check too which roles are billed: coordination, testing, release engineering and design are legitimate costs, but they should be itemised.

The number in the proposal is rarely the full cost of ownership. Budget for cloud costs, third-party licences, logging and alerting and a change budget annually. A common working assumption is that any production system needs a meaningful share of the original budget every year simply to stay current. Leaving it out of the budget is the most frequent planning error.