Player funnel and retention audit

This is the piece of work most studios ask for first. It is for live or late-soft-launch mobile and hybrid-casual titles whose producers can no longer defend the funnel they quote to a publisher.

Who it is for

You have a title already on the Play Store or App Store, or a closed country build with enough sessions to argue about. Someone on the team can export events, or sit with us while we look at the existing analytics room. You do not need a full-time analyst. You do need one person who can change the tutorial, the first-day goals, or the event list.

What you leave with

A written readout that names which events still describe a player, which ones describe a build artefact, where the first session actually stalls, and which retention questions your current list can honestly answer. The last afternoon is a workshop with design, live-ops, and whoever owns the store listing — not a private briefing for one lead.

What is included

• A shared intake on the title, stores, countries, and the last three patches that touched the first session
• An event taxonomy pass: names, firing points, duplicates, and tutorial-gated events that masquerade as “players”
• Reconstruction of the first-session path from the events you already fire
• D1 and D7 read against that path, with a plain-language note on what those days currently measure
• One on-site or remote workshop (half a day) to walk the readout and mark what the next patch should even try to answer
• A short follow-up note within five working days of the workshop, capturing decisions the room actually made

What is not included

We do not write new tracking code, migrate you onto another analytics vendor, run paid user acquisition, or redesign the game. We do not promise a higher D1. If the honest finding is that D1 cannot be read until the tutorial events are cleaned, that is the finding.

Who does the work

Aisha Rahman leads the audit. Wei Jun Tan joins when the event list is noisy or the title mixes IAP and ads in the same session. Priya Nair runs the workshop notes so the room’s arguments survive the week.

How the weeks run

Week one is intake and taxonomy. Week two is reconstruction and the first draft of the readout. The workshop sits at the end of week two or the start of week three, depending on patch freezes. Remote sit-ins follow the same calendar; we still want a single block of hours, not a trail of fifteen-minute calls.

Duration, place, preparation

Two to three weeks of calendar time, with concentrated hours rather than a thin retainer. We prefer the Level 7 room in Johor Bahru when the team can travel. Otherwise we sit on a shared call with the same agenda. Before we start, send a build or store link, a list of countries in the current store week, and whoever owns the event list.

Constraints

We need a real event export or admin access already used by the team. We will not scrape stores or guess at numbers from public charts. If a publisher NDA forbids sharing logs, say so on the intake call; we will stop rather than invent a workaround.

Price basis

A fixed project fee, scoped after the intake call once we have seen how messy the event list is. See Rates for starting bands. The next step is to ask about this readout with the title name, store, and a sentence on what you currently quote as D1.