Journal · 14 Feb 2026
Reading Thailand-market cohort curves after a regional launch
Regional launches love a single “go-live” date. Thailand rarely offers one. The Play listing may appear on Tuesday, the Thai language pack on Thursday, PromptPay on the following Monday, and the LINE entry point whenever the brand team finishes the rich message. If you cohort everyone from Tuesday, your early curve is a mix of English-only users, unpaid users, and people who never saw the feature in Thai.
Three clocks
We teach students to label three clocks on every Thailand readout: store-available, locale-ready, and tender-ready. Exposure should not start before locale-ready if the feature’s copy is load-bearing (legal text, amount confirmation, error states). Trial should not be expected before tender-ready if the job requires a local payment method.
A travel team in class once showed a beautiful week-one trial rate that vanished in week two. The week-one group was mostly staff and bilingual Bangkok testers using international cards. Locale-ready users arrived later, hit Thai error strings that still pointed at an English help article, and left. The cohort was not “cooling off.” It was two populations.
What to do in the warehouse
Carry locale, payment-method availability, and entry source on the exposure event. Build habit windows from locale-ready, not from install. If product insists on an install-based chart for the board, keep it in an appendix and refuse to let it set the floor.
None of this is unique to Thailand, but Thailand makes the mismatch obvious. Use it. A clean SEA launch story that ignores language and tender clocks is just activation theatre with better slides.