One-Pager
A single-page pitch for a game concept — core loop, audience, platform, and key differentiator — used to align stakeholders before full design work begins.
A one-pager is the executive summary of a game concept. It is written before the GDD, before any systems design, and before production planning. Its job is to answer one question fast: is this game worth designing in more detail?
A strong one-pager covers: the elevator pitch (one sentence), the core loop (what does the player do every 30 seconds?), the target audience (who is this for?), platform and scope, tone and comparable titles (what does it feel like?), and the key differentiator (what makes this interesting instead of a clone?). All of this fits on one page — deliberately. If you can’t describe a game concept on one page, the concept isn’t clear yet.
One-pagers circulate quickly during pitch cycles and greenlight processes. They are shared with people who will not read a GDD: executives, production stakeholders, external partners. The one-pager becomes a reference document during production — the thing you check when a feature debate loses the thread.
How it works in Gameframe
In Gameframe, a one-pager is a document like any other: versioned, reviewable, and linked to the larger GDD it spawns. Teams keep one-pagers in a dedicated vault section alongside their pillars doc so the original concept is always one click from the current design.
Specialist Reviews can read a one-pager and flag tension between the concept and the current GDD — catching concept drift before it becomes a scope argument.
See Gameframe’s GDD templates for a one-pager starter structure.