Articles de blog de Mariel Desailly

Tout le monde (grand public)

The dominant factor is never the choice of framework — it is almost always uncertainty. Every ambiguity in the requirements becomes a buffer inside the number you receive. A vendor that has no visibility into the exceptions and edge cases will assume the more expensive option. Spending a week on a discovery phase can cut the overall figure by far more than any rate negotiation.

Connections to other systems tend to be the second big multiplier. A screen that writes to your own database is predictable; the same screen talking to an old accounting system is a different problem. The effort hides in the third party: poor documentation, waiting on someone else's team, data that does not match your model. Ask each bidder to price integrations separately, since this is where estimates break.

Non-functional requirements quietly rewrite the estimate. An enterprise application development with java used by a handful of staff has almost nothing in common with the same feature set handling a hundred thousand users. Compliance work, uptime targets, performance under load, data retention rules and accessibility each add measurable effort. State them early or expect the estimate to move later.

The mix of people behind the number changes the arithmetic. A day rate reveals almost nothing on its own: a senior engineer at a premium rate frequently turns out to be cheaper overall than two inexperienced developers who require supervision and rework. Ask as well what is langchain rag else appears on the invoice: delivery management, QA, release engineering and analysis are real work, but they should be named rather than hidden inside a blended rate.

The number in the proposal is never the total cost. Plan for infrastructure, paid APIs, logging and alerting and an ongoing support budget annually. A common working assumption says that software in active use consumes a meaningful share of its original build cost annually in fixes, updates and small changes. Ignoring this has always been the most frequent planning error.