game-studio-delivery-and-commercial-operations

name	game-studio-delivery-and-commercial-operations
description	Use when running game discovery, estimation, staffing, RACI, greenlight, statements of work, milestone governance, outsourcing, client demos, change control, launch command, postmortems, or evidence-based case studies.
metadata	{"portable":true,"compatible_with":["claude-code","codex"]}

Game Studio Delivery and Commercial Operations

Make scope, uncertainty, content throughput, accountability, acceptance, and commercial change visible from discovery through support.

Use When

• Planning or governing a client game engagement, studio milestone, outsourcing package, greenlight, launch, or case study.

Do Not Use When

• Creative, technical, legal, or financial specialists have not approved their own assumptions.

Required Inputs

Client/owner decision, product/platform/audience scope, evidence, team/vendor capabilities, dependencies, rights, risks, milestone model, content inventory, throughput history, business-model hypotheses, budget/runway/contract constraints, acceptance, change process, support obligations, and stop conditions.

Workflow

1. Run discovery and technical due diligence; separate facts, assumptions, exclusions, and client-owned inputs.
2. Estimate systems and content with range/confidence, throughput basis, rework, integration, certification, contingency, and recalibration triggers.
3. Define milestone RACI, RAID, decision rights, artefacts, objective acceptance, demo script, and payment/change links.
4. Gate vendors with provenance, source-file, technical, security, and integration acceptance.
5. Conduct greenlight and milestone reviews from evidence; rehearse launch command, support, rollback, and postmortem.