01 / Tell us what you are building
Describe the player experience, your priorities and what you already have. For an existing game, include its condition and the changes you need. A concise brief is more useful than a long list of features without priorities.
02 / Define the first scope
We review requirements and clarify open questions. The proposal should state deliverables, exclusions, dependencies, responsibilities, review points and commercial arrangements. Detailed technical investigation is scoped and quoted when needed.
03 / Build and review
Implementation follows the agreed stages. Review playable work against the intended behaviour and provide consolidated feedback. New ideas are welcome, but changes to the agreed scope need their impact on cost and timing discussed.
04 / Test the agreed experience
Review core interactions, important edge cases and supported devices. The test plan depends on the game and may include progression, controls, UI and existing-data behaviour. Testing reduces risk; it is not a guarantee of commercial performance or platform approval.
05 / Handover and the next stage
Agree what will be transferred, how source access is managed and which documentation is needed. Discuss asset licences and any third-party dependencies. Further updates and support are arranged according to the work required.