The dominant factor is never the choice of framework — it remains how much is still undecided. Every ambiguity in the brief becomes padding in the estimate. A supplier that cannot see the exceptions and edge cases has to assume the more expensive option. Investing a few days in a discovery phase frequently cuts the total much more than negotiating the rate.

Connections to other systems are the second big multiplier. A screen that writes to your own database is low risk; the same screen talking to a legacy ERP is a different problem. The effort hides in the other system: rate limits and sandbox access, waiting on someone else’s dedicated development team vs outsourcing, data that does not match your model. Ask the estimator to break integrations out as separate items, because that is where the numbers slip.

The requirements nobody writes down can easily double the budget. A tool used by twenty people costs far less than the same idea handling public traffic. Audit and compliance requirements, availability guarantees, scalability, audit logging and localisation each add weeks of work. State them early or expect them to arrive later as change requests.

The mix of people behind the number matters a great deal. A rate card tells you little on its own: one senior livewire developer at a premium rate can be less expensive in the end than two inexperienced developers who require supervision and rework. Ask as well who else is billed: coordination, QA, DevOps and mvp development mistakes to avoid analysis are legitimate costs, but they should be named rather than hidden inside a blended rate.

The build price is not the full cost of ownership. Budget for cloud costs, paid APIs, observability and a maintenance allowance for every year the software runs. A common working assumption says that affiliate software development company in active use requires a recurring percentage of the initial investment per year in fixes, updates and small changes. Ignoring this is the most frequent planning error.