FOR MOBILE GAME STUDIOS
Discuss your retention question →
01 / MAP THE PLAYER JOURNEY
Start with what players do
In the first weeks of a Growth Diagnosis, we walk the live game from install to first value. We map tutorial friction, the core action, progression, and the first reason to return.
WHAT TO BRING
Bring the game build, its main player journey, and the question your team needs to answer.
First: follow the player path
02 / READ THE SIGNALS
Trace the Day 7 loss
We compare install cohorts, Day 1 and Day 7 return, event definitions, and current research. We check whether live-ops prompts, content, or rewards support a real reason to play again.
WHAT TO BRING
Bring aggregate retention data, event definitions, and known tracking gaps. No private player records are needed.
Then: separate signal from assumption
03 / CHOOSE ONE MOVE
Make the next test clear
The diagnosis ends with a shared priority and one measured change. Your team can test the smallest useful improvement, with a decision rule set before it ships.
WHAT YOU GET
A written review, a signal map, up to three ranked findings, data limits, and one recommended next test.
HOW TO START
Tell us where players stop returning and what your team has tried. We will use the first conversation to set the scope. Do not send credentials or private player records.
Should we hire a consultant or a full-time lead?
Use a focused diagnosis when the cause of player loss is unclear and your team can build the fix. Hire for a standing role when retention work needs daily ownership.
What should a first proposal include?
Ask for the player journey to inspect, the data definitions to check, written findings, one test, and clear ownership. Compare candidates against the same question.