SourSpark · Creator and Brand Games →
What should a game studio deliver?
Compare game studio proposals using playable builds, source files, artwork, test coverage and maintenance. Define clear acceptance criteria before production begins.
Updated: 2026-10-31
These images are from our own SourSpark projects and provide visual references for this topic. Original screenshots retain the app’s existing language.
Write acceptance criteria before file lists
Specify what the prototype must do, how many levels the first release includes and which devices will be tested. Use observable outcomes to decide whether a delivery is complete.
List source files and access separately
Project code, artwork, audio, build notes and any server setup are separate deliverables. Clarify who manages store accounts, service access and the handover process.
These images are from our own SourSpark projects and provide visual references for this topic. Original screenshots retain the app’s existing language.
Compare support after release
Bug fixing, new features and third-party running costs need separate treatment. Record their scope, the support contact and how additional requests will be assessed. A clear handover should leave these responsibilities understandable.
Verify deliverables through observable behaviour
When accepting a prototype, go beyond a claim that it has a level system. In the demo, check that three levels open in sequence, missing food prevents completion, rocks block movement and restarting resets the current level. Write similarly observable conditions into your own acceptance checklist. Source code, platform packages and maintenance should be separate deliverables.
SourSpark
What game could your character belong in?
Share your channel, character and audience so we can define the first playable version together.
Tell us about your character and game