Maintaining development costs while meeting the growing expectations of consumers
summary
Argues that budgets should be scoped in staff-months not vague totals, with pre-production of at least six months and user playtests every 3–4 months; shows cost multipliers when a one-month delay hits a 15-person team versus a 100-person team and cites millions wasted in late-stage cut content. Recommends lean teams, long discovery, using GitHub Copilot and ChatGPT for prototyping and telemetry parsing, AI-driven analytics to personalize gameplay and optimize live‑ops, and warns against AI art in pitches due to licensing risks.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:43Cost control and quality challenges
- 3:55Production costs in game dev
- 7:29Publisher-developer cost control
- 13:11AI balancing cost and quality
- 21:08Efficient development processes
- 28:59Marketing versus budgets
- 33:17Common pitfalls and fixes
- 41:24Outsourcing partnerships
- 44:21Neurodiverse talent support
- 46:32Closing and Q&A
related talks
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
34mGame Developers Are Becoming Directors, Not Coders
41mPanel: What Tools all Game Developers Should Have at Hand at all Times
41mHow To Ship A Top-Tier Game Without A Top-Tier Budget: Practical Tips For Cost-Effective.....
29mPanel: Beyond Downloads: The New Rules Of Games Marketing
58mCurrent challenges for game developers
21mWhen the Shit Hits the (RGB) Fan: What Can Go Wrong When Making Multiplayer Games
43mGame Developers Life Lessons