Write one page that makes an unsuitable supplier easy to reject. The product owner should own it, with the content lead defining essential coverage and engineering identifying implementation constraints.
Requirements checklist
- [ ] Business and presentation: identify the contracting entity and whether games appear in reviews, a discovery directory or an entertainment portal.
- [ ] Domains: list production domains, subdomains, staging environments and any proposed apps separately.
- [ ] Audience: identify intended US states or other territories, languages and audience characteristics. Separate targeted markets from incidental visits.
- [ ] Essential content: list must-have titles and studios; distinguish launch blockers from desirable additions.
- [ ] Delivery method: specify external play links, supplier-hosted iframes, widgets, self-hosted files or downstream redistribution.
- [ ] Surrounding activity: describe advertising, affiliate links, age controls and any supplier-controlled promotions.
- [ ] Technical environment: name the CMS, hosting, cache/CDN setup, priority browsers and available backend capability.
- [ ] Commercial limits: set the procurement budget, recurring ceiling, decision date and maximum acceptable commitment.
- [ ] Success criteria: define launch behaviour, acceptable loading time, fallback behaviour and the evidence required for approval.
Stage output: an agreed brief, a prioritised title list and named decision-makers.
Stop condition: if the team cannot describe the intended use, do not ask suppliers for a generic price. First resolve what is actually being purchased.