"It depends on scope" is accurate and useless, so writing cost as scope times rate times risk, plus the cost to operate, is a better answer for founders. It shows which terms they can actually change.

The point that a smaller scope at a higher rate often beats a bloated scope at a low rate is the one buyers most need to hear. The other is year one: hosting, paid APIs, store fees, and 15 to 25 percent maintenance belong in the budget, not in a surprise later.

At Ascendra Ventures we work the same way from the other side. The scope term is fixed first as one atomic problem with written acceptance cases, then the price is fixed for that scope, and the running costs are listed next to it so nobody compares a build quote with a full year of ownership.

Which of the six drivers do founders most often underestimate in your experience: roles, integrations, or the admin side?