Access & responsibilities
Identify who controls the build, store accounts, analytics and infrastructure. Agree the permissions needed for the work.
Choose a focused scope around the work your studio needs. For each project, agree the deliverables, responsibilities and schedule before work begins.
Event calendars, update checklists, player feedback and support workflows. Set coverage hours, escalation contacts and approval responsibilities around the release schedule.
Store listing preparation, submission checklists and release coordination. Confirm supported platforms, territories and publishing rights for each title.
Plan the text, store copy and assets needed for each target language. Include in-build checks for text length, layout, terminology and cultural context.
Review hosting requirements, account ownership, access, monitoring and load-test plans. Choose regions and protection options around the game’s architecture and launch needs.
Prepare creative briefs and small acquisition tests. Agree the budget, attribution setup and review criteria before increasing campaign spend.
Define events for onboarding, sessions, purchases and progression. Use consistent reporting to compare retention, conversion and the impact of updates.
A useful scope names the output, the owner and the point at which the work is ready to review.
Identify who controls the build, store accounts, analytics and infrastructure. Agree the permissions needed for the work.
Set the handover format, review dates and acceptance criteria. Keep a record of decisions that affect the release.
Define update ownership, incident contacts and coverage hours. Review the arrangement when the title’s needs change.
Tell us what is already covered in-house and where you need another pair of hands. A focused brief helps establish a workable scope.
Talk to our team