Activation is not a single event
Why “first key action” collapses in implementation-heavy SaaS, and what to timestamp instead.
Bangkok desk · SaaS App KPI Analytics
Most teams we meet already own a warehouse, a BI tool, and a weekly slide. What they lack is a shared grammar for activation quality, expansion that is not just invoice noise, and a north-star that survives a sceptical board.
Flagship
The course is built for people who have already argued about “the one metric that matters” and watched the argument collapse into a dashboard with twelve charts. You will draft a north-star, pressure-test it against activation and expansion, and write the caveats a finance lead will actually accept.
We work from Thai and regional B2B SaaS examples — seat-based billing, implementation-heavy onboarding, and the peculiar way professional services inflate NRR. The syllabus is not a tour of chart types.
From the room
After week four of North-Star Architecture I finally retired our “weekly active companies” chart. It moved when we sent more emails, not when the product got better. The replacement metric is slower and slightly embarrassing in sales calls, which is probably the point.
The Activation Funnel Instrumentation module made our CS team stop counting “logged in once” as activated. We still disagree on the exact D7 window — I wanted five days, they wanted ten — but at least we argue about the same event now.
I came in hoping for a template pack. Metric Nodecore does not really sell that. The Board-Ready KPI Narratives sessions forced me to write two caveats under every number, which my CEO found fussy at first. One reservation: if your warehouse is still a spreadsheet export, you will spend the first fortnight catching up before the critiques get useful.
What leaves with you
You learn to pick a metric that would go down if the product got worse — and to retire vanity proxies that only celebrate traffic.
First value is defined as a user-visible outcome, timestamped, and checked against early retention instead of a single “aha” checkbox.
Expansion, contraction, and services revenue are separated so NRR stops flattering implementation-heavy books.
Each weekly number arrives with source, window, and the two things it cannot explain. That is the whole deliverable.
Desk notes
Why “first key action” collapses in implementation-heavy SaaS, and what to timestamp instead.
Seat true-ups, professional services, and multi-entity invoices quietly inflate the ratio.
A layout small enough to live in a weekly doc, not only in a BI bookmark nobody opens.
Course ledger
If you do not need the full 11-week architecture course, the shorter desks cover instrumentation, churn reading, and experimentation hygiene. Browse the ledger or write to the desk about fit.
The desk is in Bangkapi. Fees are listed without checkout theatre. Tell us which metric currently embarrasses you.