“Module 07 made us delete a PQL component that had been inflating pipeline for a year. I still think the closing studio is too short if your identity graph is a mess — we had to finish stitching after the course — but the veto-rule language is what sales finally accepted.”
Flagship course
Signal to Expansion
A twelve-week Product-Led Growth Analytics intensive for operators who already have a stack and still cannot agree what “activated” or “qualified” means. Taught live from Bangkok with written critique on your own instrumentation.
Who this room is for
Product analysts, growth leads, and founder-operators who can already query an event stream. If you have never opened a warehouse note, start with the Activation Desk Intensive instead. If your motion is purely outbound and the product is a brochure, this syllabus will frustrate you — and we will say so on the diagnostic call.
You will work on your own product. Toy datasets appear only when a concept needs a shared example. The final artefact is an expansion scorecard plus a one-page PQL spec that another analyst could implement without calling you.
Modules
Twelve weeks, four movements
- 01–03
Instrumentation as literature
Event dictionaries, identity stitching, and the dark corners of the warehouse. You produce a written map of what you can actually know this quarter, including fields you must not pretend exist.
- 04–06
Activation without folklore
Replace “aha” language with a time-bounded job sequence. Studio work compares first value, first collaboration, and first invoice — three moments teams routinely collapse into one metric.
- 07–09
PQL vetoes and sales conversation
Design a product-qualified lead that a human can refuse. Includes a live critique with an operator who has sat on the sales side of a bad score.
- 10–12
Expansion weather
Separate new-logo motion from seat and usage expansion. Build the scorecard, write the weekly review ritual, and defend both in a closing studio.
Learning outcomes
What you should be able to do on week thirteen
- Defend an activation definition in writing, with a time window and explicit exclusions.
- Publish PQL rules that include at least one veto a salesperson can exercise without arguing with the model.
- Run a weekly expansion review that does not recycle acquisition charts.
- Hand another analyst an event dictionary and identity note they can follow without a walkthrough call.
- Name the methods that will not resolve given your sample size or sales-led residue — and stop using them.
Instructor
Pimchanok Rattanakul
Lead faculty. Formerly growth analytics at a Southeast Asian payments platform, where she spent four years arguing with a lead score that rewarded login frequency and ignored treasury jobs. She designed Sensor Cloudhub’s Observatory method after moving the reading group from a borrowed conference room in Thonburi into a standing atelier.
Visiting operators join modules 07–09 when a live sales-handoff problem is more useful than a case study. Faculty time on artefacts is the scarce resource; video replays are provided but are not a substitute for studio.
Informational fee
THB 48,000 per seat
Quoted in Thai baht, excluding any applicable VAT. This page does not collect payment. The Expansion Atelier tier on pricing matches this syllabus. Observatory Fellowship covers up to four seats plus a warehouse walkthrough.
Included: live sessions, two deep artefact mark-ups, closing studio, and twelve months on the alumni critique list. Not included: implementation labour, extra on-site days, or a certificate designed for LinkedIn.
Notes from the room
★★★★☆
Took Signal to Expansion after two failed attempts to “do PLG” with an agency playbook. The activation sequence work was slower than I wanted. The expansion scorecard is still on our Monday agenda.
FAQ
Plain answers, including a real limit
Do I need SQL?
You need to be able to read a query and argue with its grain. Faculty will not teach SELECT from zero. If that is your starting point, wait a cycle and do warehouse literacy first.
Can a sales-led company take this?
Yes, if the product already carries a meaningful self-serve or in-product motion. If every seat is closed by a human before first value, the PQL modules will feel theoretical. We would rather decline the seat than perform PLG theatre.
What if our weekly active accounts are small?
This is the limitation we will not sand down: below a few hundred weekly active accounts, several expansion methods in weeks 10–12 simply will not resolve. You can still finish the activation and instrumentation movements, and we will mark those artefacts. We will not invent statistical comfort you do not have. Teams in that range often do the Activation Desk Intensive instead, then return when volume exists.
Are sessions recorded?
Lectures yes. Studios no — critique is for the people in the room. Missed studios can be replaced once per cycle with a written submission.
Refunds?
See the refund policy. Withdrawing before the cycle starts is treated differently from leaving in week six.