09 Dec 2025 · Guest · live-ops pod, Bangkok

A live-ops KPI stack that fits a six-person studio

We do not have an analyst. We still need a Friday note. This is the stack we kept after the Proxy Routecore KPI Clinic — not the one we arrived with.

Our idle title ships from a room of six. Before the clinic, the Friday doc had eleven charts, three of which nobody could define if a designer walked in. After three days we were allowed three numbers and one explicit ignore list.

The three we kept

Session health. Share of install-week users with at least one session of eight minutes or more, cut by store. Not average session length — that number flattered whales who AFK in the guild screen.

Offer conversion. One named offer event, attempts versus grants, refunds noted in the same cell. If we run two offers, we still only headline one. The second lives in an appendix.

D7 for the latest complete install week. No D1 on that slide. We calculate D1 internally so we notice disasters; we do not perform it.

The ignore list

Raw DAU during collab weeks, uncut ARPU, and a “content engagement score” a previous contractor invented. Ignoring them felt rude. It also freed Thursday afternoon.

This is Gaming App Analytics at the scale we actually operate: not a warehouse manifesto, a weekly ritual. The Telemetry Desk page is basically our wall checklist with nicer sentences.

Limits, because the clinic asked for one

We still cannot do device-class cuts without borrowing someone’s laptop and a weekend. The Studio would go deeper; we did not have twelve weeks. If your pod is the same size, the clinic is the honest buy. If you need dictionaries rewritten under mentor hours, read the flagship syllabus instead.