Planning & production
How to brief a game development studio
A useful browser game brief explains the business objective, audience, intended experience, brand assets, supported devices, launch date and approval process. Include the action you want players to take and how you will judge the result. You can start with these decisions even if the game mechanic is still open.
Write the objective in one sentence
Start with the business need rather than the format: “Introduce our new product to campaign visitors and give interested players a route to enquire.” That sentence helps everyone assess whether the game idea is doing its job.
Choose a primary outcome and keep supporting measures separate. Plays describe participation. A visit to a product page describes another action. Neither should be silently treated as a sale or a measure of brand lift.
Describe the audience and entry point
Explain who will play and where they will find the link. Someone scanning a QR code at an event may have different needs from a desktop visitor exploring a product launch page.
Specify the target devices, likely screen orientation, expected session and language. Note any accessibility requirements and the review needed to confirm them. Avoid promising “works everywhere” without a defined test scope.
List the creative inputs and constraints
Share the brand guidelines, product assets, campaign idea, approved copy and references. Explain what is fixed and where the studio can propose alternatives. A reference is most useful when you say which part you like: controls, pace, visual style or structure.
Identify asset owners and approval contacts. If a project uses a partner's brand or work from a previous employer, resolve permission and credit requirements before treating it as campaign material.
Make the brief usable
Use this checklist as the outline of an email or project document. Unknown answers are useful too: marking a decision as open lets the studio focus the first conversation.
- Company and contact: who is commissioning the work?
- Objective: what should this experience help achieve?
- Audience: who plays and where do they arrive from?
- Experience: what should players do and discover?
- Next action: what happens after the game?
- Assets: what is approved and ready to supply?
- Technology: devices, browsers, hosting and integrations?
- Measurement: which events or outcomes matter?
- Schedule: first playable, reviews and public launch?
- Budget: target range and essential scope?
- Approvals: who gives consolidated feedback and signs off?
- Operation: who owns updates, support and the campaign end?
Agree milestones before adding features
A first playable should help you evaluate the mechanic, controls and relationship to the brand. Later reviews can focus on polish, content and launch readiness. Name what is expected at each stage and who is available to review it.
For a scoped game, playbrief's first playable estimate is approximately one week. That estimate does not remove the need for approvals and testing. Give the studio the real launch constraint so the full schedule can be assessed.
Use real examples to discuss the idea
The Kylaq Sportline project shows a campaign theme translated into fast-paced gameplay. The Museum shows exploration with a treasure hunt. Our independent concepts demonstrate multiplayer and a serving game. They are different starting points for a discussion, not promises of identical results.
Read the project credits and concept notices alongside the examples. When you send your brief, tell us which mechanic or interaction seems relevant and why. That is more useful than asking to reproduce a whole project.
Project references: Škoda Kylaq Sportline and Škoda Museum were developed during a previous role by a member of our team. HOLY and fritz-kola are independent pitch concepts. Read the credits and reported outcomes in each story.