ONE BOUNDED PROBLEM, TAKEN THROUGH THE CHANGE
Fix one high-priority game problem with a clear scope.
A short engagement for one high-priority progression, difficulty, onboarding, reward, economy, or LiveOps problem and the connected changes needed to solve it.
WHEN IT FITS
Use this when the next decision needs to be clearer.
- An audit has already identified the main problem.
- One progression band, system, feature, or player moment needs focused redesign or balancing.
- The team needs the change, developer handoff, and measurement plan in one bounded engagement.
WHAT WE AUDIT OR DESIGN
The work stays tied to the decision.
- The evidence behind the chosen problem and the systems it may affect.
- The current values, states, level layouts, rules, player friction, and technical limits.
- The smallest change that can solve the problem without creating another one elsewhere.
WHAT YOU RECEIVE
Your team gets clear instructions.
- The redesigned or rebalanced values, rules, levels, or player flow in scope.
- Specific implementation notes and edge cases for development and QA.
- A pre-release validation checklist.
- A post-release measurement readout when the timing and data access are included in scope.
What we need from you
A clear problem statement, relevant build or files, available evidence, technical constraints, and access to the people who will implement or approve the change.
How the work is measured
We agree on the baseline, target signal, guardrail metrics, and reporting window before the change is handed off. The exact plan depends on release traffic and the available telemetry.
RELEVANT WORK
See what this looks like on a real game.
QUESTIONS BEFORE STARTING
What teams usually ask.
How many problems fit in one sprint?
Usually one main problem and the connected changes needed to solve it. We set the boundary before the sprint starts.
Can you work directly with our developers?
Yes. We write the change for the people building it and can review questions, edge cases, and validation during the agreed sprint.
Does the price include post-release data?
It can. We confirm whether a measurement readout fits the release timing and available data when we set the scope.