Delivery
- Who will work on the project?
- What happens in the first four weeks?
- How are risks and changes reported?
Buyer notes
Buyer Guides for Switzerland Projects
Short, direct guidance for comparing companies, testing a proposal, and protecting the project before work begins.
Shortlist process
From Search to Signed Scope
A measured process helps buyers compare working methods instead of reacting to polished sales material.
01 Build the project brief
State the business problem, users, essential features, technical constraints, target date, and what is still uncertain.
02 Create a relevant shortlist
Choose companies with visible work close to your project type. Three well-matched providers are usually more useful than a long general list.
03 Test the proposed plan
Ask each company to explain discovery, delivery stages, technical choices, risks, testing, handover, and support in plain language.
04 Compare the working team
Confirm who will lead the work, who will build it, where the team is located, and how often you will communicate.
05 Protect ownership
Set out ownership of source code, design files, cloud accounts, data, documentation, and third-party licences before development begins.
06 Check after-launch support
Ask how defects, security updates, platform changes, analytics, content, and future releases will be handled.
Direct questions
Questions to Ask Before Hiring
Technology
- Why does the proposed stack fit?
- How will security and testing work?
- What documentation is included?
Ownership
- Who owns code and accounts?
- What third-party licences apply?
- How does handover work?
Game projects
What Should Game Startups Ask a Studio?
Short answer
Ask for relevant playable work, engine and platform experience, multiplayer and backend responsibility, art production capacity, build ownership, store submission support, testing, source code handover, and a realistic plan for post-launch updates.