A large company suggests depth; a small studio suggests direct contact. Those impressions are not enough to choose. A large organisation may assign a small team, while a small studio may bring in partners for part of the work.
Compare the people and working arrangements proposed for your project. The logo on the proposal does not explain who will be available during a difficult week before launch.
List the capabilities the project needs
Do you need research, design, development, migration, testing and ongoing support? For each activity, ask who will do it and how much availability they will have.
One person can cover several roles. The plan still needs to account for their actual time rather than assuming they can perform every task at once. Ask about other commitments for key people during your delivery period.
Check cover and information sharing
What happens when the lead developer is absent? Who knows the decisions, has the necessary access and can take over communication? If partners are involved, establish who is responsible for their work and who resolves disagreements.
Ask for an example working rhythm: progress updates, demonstrations, risk reporting and change approval. That also reveals how much time your own team must contribute.
Compare the service, not only the rate
One company's price may include coordinating several specialists; another arrangement may leave some of that work to you. Establish who consolidates feedback, manages dependencies and checks that delivery is complete.
Include a relevant past project and a discussion with the proposed team in your evaluation. The choice should be explainable through suitable experience and availability, rather than company headcount alone. Use the selection process appropriate to your purchasing arrangements.
Every number in this article, plus thousands of other contracts, is in the database.
Open the database