How a sit-in week actually runs

The custom shape of our work: five to fifteen days beside a live title, with a written readout at the end — not a login you keep.

A sit-in is how we deliver gaming app analytics. Someone from the practice spends concentrated hours with your event list, your store week, and the people who can still change the build. You do not receive a product. You receive a week (or three) with a paper trail.

Before we agree

You send the title, the stores, the countries in the current week, and one sentence you currently quote as D1 or as a funnel step. We answer within two working days with whether the work is a funnel audit, a live-ops week, an economy pass, or a soft-launch sit-in. If the honest job is “install tracking,” we will say we are the wrong room.

The first shared hour

We look at when events fire, not at what they are named. Phones on the table help. So do the testers’ notes from the last Tuesday. We write down which questions the current list can answer and which questions will have to wait until a patch.

The middle days

Aisha or Wei Jun reconstructs the path. Priya keeps a log so the team cannot quietly change the definition of a “session” mid-week. If a patch lands, we mark it on the log instead of mixing two builds in one paragraph.

The last afternoon

A workshop, not a reveal. We walk the readout, mark what the next patch should try to answer, and leave the document with you. Five working days later you get a short follow-up of decisions the room actually made.

Practicalities

Johor Bahru teams can use the Level 7 room. Other Malaysian cities sit on a single block of remote hours with the same agenda. Bring whoever owns the event list. Leave user-acquisition managers out of the first hour unless they also own a live event.

When you are ready, ask for a readout or read the flagship funnel audit.