Week three’s cold-start budgets finally gave platform a number they could refuse in release review. I still wish the warehouse homework had come with a dbt starter — we lost two evenings inventing our own.
Flagship programme
Signal Architecture Studio
An eight-week critique studio on mobile performance KPI frameworks. You bring a live dashboard. You leave with an event contract, a health ladder you can explain, and a Monday slide that fits in twelve minutes.
Cohort Bench seat · informational price ฿16,900 · remote with optional Phetchabun office hours
Outcomes
What “done” looks like
- A written event contract: name, owner, join key, retirement rule, and PII stance for every KPI-feeding event.
- A health ladder that keeps crash-free, ANR, hang, and silent failure in separate rooms.
- Cold-start budgets annotated with the network traces you actually measured — not a vendor default.
- A retention map that states seasonality and festival effects instead of hiding them in a rolling average.
- One exec slide with three numbers and one spoken limitation.
Who it is for
Metric owners, not spectators
Product managers who present the weekly board, platform leads who own crash health, and data partners who must join mobile events to a warehouse. We ask that the person who speaks on Monday attends. Analysts-only seats produce homework that never lands.
You should already ship a consumer or prosumer Android/iOS app. Pre-launch teams without telemetry should start with Field Ledger.
Modules
Eight weeks, critique cadence
-
01
Instrumentation ethics & event contracts
We name what an event is allowed to claim. Duplicate “screen_view” variants get retired in public. You draft the contract faculty will mark in week two.
-
02
Crash, ANR, hang, and silent failure
Four different questions. We stop averaging them into a “stability index.” Dual-SIM drop behaviour in Thai consumer apps is treated as a first-class case, not an anecdote.
-
03
Cold-start budgets on uneven networks
First paint versus time-to-interactive, measured on commute traces. Office Wi-Fi is disallowed as the only benchmark. You leave with a budget and a method for revisiting it.
-
04
Session health versus engagement vanity
Foreground time, job completion, and background pings. We practise saying “DAU is the wrong weekly ritual” without sounding theatrical.
-
05
Retention maps that survive seasonality
Songkran, payday, and school-calendar effects. Rolling averages that hide a festival cliff are rewritten. You produce a map with explicit “do not compare” windows.
-
06
Store listing metrics as a feedback loop
Conversion and ranking treated as product signals. Thai-language metadata and screenshot claims are checked against what the app actually does on first open.
-
07
Exec rituals: one slide, three numbers
You draft the Monday slide. Faculty interrupt. Footnotes longer than the number are sent back to research. Twelve minutes is the hard stop.
-
08
Studio critique of your live dashboard
Final week is not a recap quiz. It is an annotated pass over the board you still use at work. Completion means the critique exists in writing, not that you “passed.”
Instructor
Arunwadee Phan
Studio director · former mobile platform lead
Arunwadee spent a decade owning crash and start-up health for a Bangkok super-app before founding the critique circle that became Logicauditgrid. She still reads ANR traces for fun, which alumni find either reassuring or alarming. She teaches weeks 1–3 and 7–8; visiting faculty cover retention and store loops.
She does not consult for attribution vendors. If a tool appears in class, it is because a student brought it, not because it bought a logo slot.
Informational pricing
Cohort Bench · ฿16,900
One person, eight weeks, alumni Monday channel included. War Room facilitation for a team of up to six is listed separately on enrolment. No payment is taken on this site.
Field Ledger notes (฿3,800) cover the Atlas and worksheets without live critique — useful if your telemetry does not exist yet.
Reviews from this studio
★★★★☆
Signal Architecture Studio · “one slide, three numbers” module. The exec interruption practice was uncomfortable and exactly why we enrolled.
FAQ
Plain limits
Do we need a particular analytics vendor?
No. Bring whatever you already use. Faculty will not install a preferred stack. If your vendor cannot export an event dictionary, that limitation becomes part of the critique.
Is there a real limitation we should know before enrolling?
Yes. We do not teach paid user-acquisition scaling, creative testing, or media mix. Teams hoping for growth-marketing training will be disappointed — this studio stops at product telemetry and performance KPIs. If acquisition is the wound, this is the wrong room.
Can two people share one seat?
No. The critique cadence assumes one voice per dashboard. A second person from the same squad should take a second Cohort Bench seat or wait for War Room.
What if our app is iOS-only?
That is fine. Examples skew Android because that is the majority of Thai consumer volume, but the contracts and rituals are platform-agnostic. You will still need crash and start-up traces from your own store build.
How do refunds work?
See the refund notice. Live seats have a shorter window once week one critique has begun.