Instructor · Nalinee Prasert
Measurement lead. She holds most studio weeks. Marek Lindqvist joins for the queue-latency module. Read more on the about page.
Flagship programme
Delivery Intelligence Lab
Twelve weeks, eight seats, one live campaign from your own stack. You leave able to explain drop-off between accept, display, and tap without hiding behind a vendor colour.
Modules
What the twelve weeks actually hold
01
Metric dictionary
Name accept, retry, display, collapse, tap, and attributed action. Ban synonyms that finance already uses differently.
02
Token health
Invalid, stale, and dual-SIM tokens. Why “audience size” can grow while reachable devices shrink.
03
Delivery versus display
Vendor delivered columns, OEM battery restrictions, and collapsed notifications on Android.
04
Quiet hours
Thailand evening windows, festival calendars, and the difference between polite policy and tap-through.
05
Queue latency
Workers, backoff, and proving the delay sits in your house rather than at Apple or Google.
06
Attribution windows
Six-hour versus twenty-four-hour claims. How to stop CRM and finance running two clocks.
07
Cohort charts
Re-engagement after week four. Which segments still tap once novelty dies.
08
Live critique
Faculty annotate your export in the room. No fictional retailer. Gaps stay labelled as gaps.
Learning outcomes
- Write a metric dictionary your finance partner will initial.
- Separate token decay from creative failure.
- Produce a latency diagram with an owner, not a vague “engineering issue.”
- Choose an attribution window and defend it in a board pack.
- Revise one live dashboard using the Grid Method layers.
Informational fee
THB 86,000 per seat for the Atelier Cohort format. Deposit holds the chair. This site does not process payment. See studio fees and refund terms.
FAQ
What is explicitly out of scope?
This studio does not cover in-app messaging or email. We stay inside push queues, device tokens, and the metrics those systems produce. If your stack is mostly lifecycle email, this is the wrong room.
Do I need to fly to Pattaya every week?
Two weeks are in person at the Chonburi desk. The rest can be remote, same ICT afternoon slot. Missing both in-person weeks without notice forfeits critique time; we do not record those sessions.
How much SQL is required?
Enough to join an events table to a user key. We will not teach SQL from zero. Growth interns usually pair with an analyst; that pairing has worked, as noted in reviews.
Can my vendor sit in?
No. Vendor account managers create a political problem in critique. You may share anonymised notes with them afterwards.
Notes from Lab alumni
Week two’s token checklist paid for the seat. I wish the latency homework had a lighter template — I spent a weekend drawing boxes — but the live critique was the first time someone told us our “delivered” column was a vanity number.
★★★★★
Quiet-hours week was local in a way vendor academies never are. Songkran planning actually used the calendar we built.