Field notes
Retention signals in Thai SaaS
Bangkok product teams often read retention charts as moral judgments: a dip means the release failed. In practice, Thai SaaS calendars include holidays, corporate budget cycles, and school-term patterns that bend weekly active curves without any product change.
Separate calendar from craft
During Retention Narrative Lab, we ask learners to annotate cohort charts with known calendar events before proposing experiments. Songkran weeks, year-end freezes, and mid-year budget resets show up repeatedly. Ignoring them produces journey reports that blame the wrong owner.
Activation still beats vanity stickiness
Several alumni discovered that “returned in seven days” meant little if users never completed the first valuable action. Customer journey reporting should highlight that first success explicitly — funded wallet, first shipment booked, first lesson completed — before celebrating raw return rates.
A mild warning
Retention language is easy to overclaim. We coach teams to write “consistent with” instead of “caused by” unless they ran a designed test. That discipline keeps application analytics trusted when leadership is skeptical.