The production process

How playable production works, from brief to handoff.

Five accountable steps. A human team owns the research, interaction, build, network packaging, and QA while you keep the decisions that matter.

  1. 01 / Intake

    Send the game.

    Share the build or capture, production-ready assets, current creative, test objective, target networks, and the person who will consolidate feedback.

    Start a playable brief
    A hand chooses between three colorful playable concepts in a bright device lab

  2. 02 / Scope

    Align the brief.

    We agree the interaction, master, purposeful variants, network exports, review points, and acceptance checks before production starts.

    Use the brief template
    A team compares colorful playable hooks across phones and a tablet in a bright device lab

  3. 03 / Interaction

    Build the master.

    Our team designs and implements one playable mechanic. You review the player action, feedback, completion, and call to action at agreed checkpoints.

    Play an example
    A hand triggers an original platform-game interaction on a tablet

  4. 04 / Variation

    Make controlled variants.

    We change the agreed hook, art treatment, difficulty, reward, timing, or copy while keeping the accepted mechanic and test hypothesis legible.

    Understand variants
    A hand swaps a game module beside three coordinated playable variants

  5. 05 / Delivery

    Review, package, and QA.

    We package the named network exports, record internal checks, and return the accepted source, build versions, QA receipt, and agreed deliverables.

    See the QA checklist
    A hand completes a check beside portrait and landscape playable builds

A useful brief makes the first decision easier.

Describe the player action and what the team hopes to learn. “Test whether sorting a small stack makes the reward easier to understand” is more actionable than “make it more engaging.” Include the game link, assets, target networks, language, and the person responsible for feedback.

Use our brief template and completed example to organize those inputs. Flag missing materials so they can be accounted for in the scope.

Review the mechanic before multiplying it.

The master establishes the interaction, visual feedback, completion behavior, and call to action. Review it against the accepted brief. A variant can then change an agreed hook, art treatment, difficulty, reward, timing, or copy. Replacing the core mechanic is new master work.

Compare Color Block Jam with Coin Sort, then use the master, variant, and export guide to count deliverables clearly.

Know what arrives at handoff.

  • The accepted source and the exports named in your scope.
  • A build/version record linking the master and its variants to their packages.
  • A QA receipt with checks performed, test conditions, results, and limitations.
  • A record of acceptance and any agreed follow-up work.

Network specifications differ. We agree which destinations to package and test before work starts. Read the network requirements guide and QA checklist to see what the handoff should answer.

What approval means: Your approval accepts the current production decision or delivery. Internal QA is not external network approval, and delivery is not campaign performance.

Original casual-game mechanic on a tablet and phone beside production sketches

Your next playable

Bring us the game. We’ll make the next step clear.

Tell us what you want to test, how much creative you need, and where it should run. We’ll discuss a scope and price with you.

Start a playable brief Review pricing and scope