Mariel Desailly

A quote that comes back within a day is a bad sign. An experienced provider responds with a list of questions: about who owns the data and what happens on failure. A supplier that quotes without asking anything is simply working from a template, and a guess will be corrected later — and you will pay for it.

Watch for any distance between the team in the pitch and the people who will code. Request named engineers in the agreement, with a provision covering replacement. A team that talks only about a pool of resources and will not commit to people is keeping the right to assign anyone it consulting services likes.

Ask for the source repository from day one. A partner that shows a build only at the end of each phase is asking you to trust a black box. Daily commits show you how many people are really working far better than a slide deck. The same applies to the automated test suite: if there is no pipeline, quality claims are just talk.

Ambiguous wording in the contract around IP is rarely a formality. The document must state explicitly that the code, designs and documentation transfer to your software development company in united kingdom upon settlement of the relevant invoice. Also check which country's law applies and how payments are structured: heavy prepayment with no milestone tied to it eliminates any leverage you would otherwise keep.

Last, examine the working rhythm. Establish what overlap the teams will share with your working day, which person answers day-to-day questions and on what response times. Some genuine overlap generally works; zero overlap stretches a five-minute question into a lost day. Unclear written communication in the early emails will not improve later.