“The PQL Instrumentation Lab forced us to throw out a lead score that looked busy and kept almost nothing that predicted paid seats. Sales still complain about volume; at least they complain about the right accounts.”
Reviews
Notes from people who brought their own warehouse.
Attribution styles vary because operators asked for different levels of named credit. We do not edit out mild reservations. Banned marketing clichés stay banned.
★★★★☆
Signal to Expansion, 2025 evening cycle. Faculty mark-ups on the event dictionary were stricter than our internal review. I wanted more time on packaging analytics; that is not really this course.
We sent two analysts to the Cohort Narrative Studio after a board meeting where three people described the same retention chart three different ways. The written narrative we use now names the segment cuts and the Songkran dip instead of smoothing them. I would not call the six weeks gentle. I would call the Monday pack readable for the first time.
Client in industrial procurement software. Took Activation Desk Intensive while rebuilding onboarding. The job-sequence artefact survived a vendor change; the old “time-to-first-click” metric did not. They still run a heavy sales motion and said so plainly — the intensive did not pretend otherwise.
“Module 04 of Signal to Expansion is where we finally split first value from first invoice. Our CS team had been celebrating the wrong moment for two years. The evening schedule was awkward for the Singapore teammate; we rotated who attended live.”
Short note: Observatory Fellowship walkthrough found identity double-counting across LINE login and email. Not glamorous. Paid for itself in one quarter of cleaner expansion math.
Case study
Seventeen activation events, one surviving definition
B2B workspace · ~40 people · SEA
A regional collaboration product arrived at Sensor Cloudhub with seventeen events labelled “activation” and a monthly board slide claiming 61% activation. Sales used a different number. Customer success used a third. Nobody could reproduce any of them from the warehouse without a private spreadsheet.
During Signal to Expansion, the team collapsed activation to three jobs inside fourteen days: create a shared space, invite one teammate, publish a template another person used. Accounts that finished the template job expanded seats at roughly twice the rate of accounts that only invited. The 61% figure left the board pack.
What did not get solved: packaging. Two price tiers still cannibalise each other, and analytics did not pick a winner. The client’s mild reservation, recorded in the closing studio, was that twelve weeks was “enough to define the weather, not enough to change the catalogue.” We agree. That work sits outside the syllabus.
Name withheld at the company’s request. Figures rounded. Taught in the 2025 Bangkok evening cycle.
Case study
A PQL that sales were allowed to reject
Payments-adjacent SaaS · PQL Instrumentation Lab
The company had a lead score that incremented on almost every in-app click. Pipeline looked healthy; win rates did not. In the five-week lab they introduced three vetoes: no treasury job completed, identity unresolved across merchant IDs, and a billing admin who had never opened the export tool.
Volume to sales dropped. Win rate on accepted PQLs rose enough that the VP of Sales stopped asking for the old score. One AE still dislikes the vetoes on Fridays. That disagreement is now visible instead of buried in a 0–100 slider.
Limitation recorded: the lab does not fix CRM hygiene. Several rejected PQLs were actually duplicates. The team had to run a separate cleanup. Faculty noted it in the mark-up rather than stretching the syllabus to cover Salesforce janitorial work.