A number produced without questions is a warning, not a service level. Any serious team responds with clarifying questions before any number: about who owns the data and what happens on failure. A supplier that prices before understanding the scope is working from a template, and that guess will be corrected later — at your expense.
Look out for a gap between the engineers on the sales call and the people who will code. Ask for named engineers in the statement of work, with wording that requires notice before anyone is swapped. A provider that only offers roles and never names individuals is keeping the right to assign anyone it likes.
Ask for typescript software access to the repository from the start. A partner that delivers code only at milestones is inviting you to take delivery on faith. Regular commits and pull requests tell you how many people are really working far better than a weekly report. The same holds for the build and deployment setup: if it does not exist, assurances about quality are nothing more than words.
Loose wording in the contract around code ownership is never an accident. The contract needs to state explicitly that the code, fastify vs laravel designs and documentation become the property of your company as they are paid for. Also check which country’s law applies and the milestone terms: a request for ai automation agency most of the money up front with no deliverable attached removes any leverage you would otherwise keep.
Last, look at the working rhythm. Establish how many hours you will share each day, which named person answers your questions and on what response times. A few hours of overlap is usually enough; no overlap converts a five-minute question into a day of delay. Unclear written communication in the sales phase does not improve once the work starts.