A number produced without questions is a warning, not a service level. A competent team returns clarifying questions before any number: about who owns the data and what happens on failure. A supplier that prices without asking anything is simply working from a template, and the gap will be corrected later — at your expense.

Be wary of a mismatch between the engineers on the sales call and the developers actually assigned. Request named engineers in the agreement, with a provision covering replacement. A provider that will only describe roles and never names people is preserving its own flexibility at your cost.

Insist on commit-level visibility from day one. A provider that hands over a build only at the end of each phase expects you to trust a black box. Regular commits and pull requests show you who is really on the project far better than any status report. The same holds for the CI pipeline: if it does not exist, assurances about quality are just talk.

Vague contract language around IP is not an accident. The document should state plainly that all deliverables transfer to your business upon settlement of the relevant invoice. Look too at the jurisdiction and the milestone terms: a request for livewire vs alpinejs most of the money up front with nothing due in return for weeks eliminates any leverage you would otherwise keep.

Finally, pay attention to how they communicate. Establish how much working-fixed price vs time and materials overlap you will share with your timezone, which named person handles questions and how quickly. A few hours of overlap is normally sufficient; no overlap turns each small question into a day of delay. Unclear written communication outsourcing versus in house software development the early emails rarely improves once the work starts.