Evaluate work relevant to your game
Look beyond visual polish. Ask what the developer actually delivered and which parts were provided by others. A movement-heavy exploration project and a progression simulator can demand different experience. Where confidentiality limits what can be shared, ask for a clear explanation of responsibilities and confirmed functionality. Do not assume a portfolio image proves every system behind it.
Compare proposals on the same basis
Give each team a consistent brief and ask for explicit inclusions, exclusions and dependencies. Compare review stages, device coverage, asset responsibilities and handover as well as price. A proposal that leaves these items unstated is harder to assess, even if the headline quote is appealing.
Make acceptance criteria understandable
Describe the behaviour that will show a feature is complete. For example, explain the expected collection, sale and upgrade flow instead of asking only for a “simulator system.” Acceptance criteria can evolve during scoping, but both sides should understand what is being reviewed.
Agree how communication will work
Identify the decision-maker, how feedback is consolidated and the tools you will use. Discuss time-zone overlap, the expected review rhythm and how urgent issues are raised. Ask how changes to requirements affect the agreement rather than treating every new idea as automatically included.
Discuss access and handover early
Clarify source ownership, who controls the project accounts, what permissions are needed and how access is removed later. Use the platform’s available collaboration controls where appropriate. Never place account passwords or API keys in an enquiry form. Documentation, third-party licences and final access arrangements should be agreed before handover.
Use a balanced decision
A larger organisation, a small studio and an independent developer can each be appropriate depending on the work and responsibilities. Choose based on relevant evidence, communication, scope clarity and practical fit. Treat guarantees of player numbers, revenue or platform approval cautiously: development alone cannot determine those outcomes.