Utilitystudiopath started because too many Kuala Lumpur publishers were making catalogue decisions from a single Play chart exported at midnight. The store is not a liar, but it is a poor narrator. Refunds hide inside a country mix. A family SKU looks healthy until you notice nobody can actually share the content.
We took a room — Office 7, 38 Test Road — and limited the work to in-app purchase performance: what is sold, what is refunded, what renews, and what the listing promises. The name is awkward on purpose. It was the folder the first reports lived in, and it stuck.
We are not a development studio. We do not ship binaries. We do not buy ads. When a finding needs an engineer, we write the finding so an engineer can argue with it.
How we sit with a publisher
The first conversation is almost always about access. We want exports, not a shared login. We want the paywall that is live, not the one in a pitch. If legal in your company needs a week, we wait; we do not start the clock on guesswork.
Malaysia is the home market we know in our bones — SST conversations, bank-app payment methods on Play, the way a RM 0.99 tier still shows up in old catalogues. We also read Singapore, Indonesia, and the Philippines when those countries are in the report. We will not pretend to know Japan from one audit.
Values that actually change the work
- The catalogue is the source. If a slide and a product ID disagree, the product ID wins.
- Country mix is not a footnote. A renewal that holds in the United States and fails in Malaysia is two findings.
- We write in sentences. If a paragraph cannot name a SKU, a day, or a paywall line, it is cut.
- One audit at a time. Overlap makes us sloppy, and sloppy purchase advice is expensive.
If that sounds like the right kind of slow, request a briefing.