1. Lifecycle map & contested metrics
Inventory current slides, list disputes, and rewrite stage boundaries in plain language.
Flagship course
Lifecycle Engagement Analytics
An eleven-week studio for product and analytics pairs who need application analytics for lifecycle engagement reporting that survives executive review.
11 weeks
Live cohort + office hours
Informational price: THB 42,000
What you will leave with
- Documented stage definitions for activation, habit, and risk
- Cohort windows matched to renewals, billing, or usage cycles
- A monthly engagement brief template with owner fields
- A limitation note that keeps stakeholders honest about sample gaps
Who it fits
Teams with at least a basic event stream who struggle to agree on which numbers describe engagement quality. Less ideal if you still lack any product analytics tooling.
Modules
Each block ends with a deliverable you can drop into a real reporting week.
2. Event quality for engagement
Select the properties that explain depth and return timing; drop decorative events from the pack.
3. Cohort windows that match the product
Compare 7 / 14 / 28 / billing-aligned windows and document why one becomes the default.
4. Activation & habit scorecards
Build lightweight scorecards with thresholds your PMs can defend without a data scientist present.
5. Risk signals & quiet churn
Surface early warning metrics without turning every dip into an emergency narrative.
6. Stakeholder storytelling lab
Rehearse a 12-minute lifecycle brief with peer critique and a written limitations appendix.
Instructor
Arisa Wongsawat
Former product analytics lead for consumer apps across Southeast Asia. Arisa now coaches teams on lifecycle narrative design from our Bangkok studio, with a focus on reports that stay short enough to be read.
Informational pricing
THB 42,000 per seat
Includes live sessions, critique circles, and template packs. This site does not process payments—contact us to enroll or discuss team seats.
Request enrollment detailsFAQ
Do I need SQL fluency?
Comfortable filtering and joining event tables helps. If you only export CSVs today, plan for a teammate who can pull cohorts during weeks 3–5.
Is this tool-specific?
No. Examples draw from common product analytics stacks, but deliverables are method-first so they transfer across vendors.
What is a real limitation of the course?
We do not rebuild your warehouse or implement tracking plans end-to-end. Instrumentation gaps will still need engineering time after the cohort; the course clarifies what to ask for, not how to ship every pipeline change.
Can two people from one company join?
Yes—and we recommend a PM + analyst pair. Shared language sticks faster when both roles critique the same brief.
Reviews from this course
Module 3 alone paid for the seat. We retired a misleading 7-day retention chart and leadership stopped asking why “the numbers never match finance.”
Critique sessions were sharp. I still wish there were one more week on mobile offline events—our field agents create messy timestamps.