Plan Conversion Analytics Lab
The full reading method: paywall taxonomy, cohort windows, and a written diagnostic of your own upgrade path.
Open the syllabusBackup Nodehub · Bangphlat studio
Plan conversion is a reading problem, not a dashboard shortage.
We teach product and growth teams how to trace upgrade intent across paywalls, plan ladders, and billing states — work that rarely shows up in a default analytics template.
Browse the catalogue
Studio desk notes from Lab Cycle 14 — paywall state map before the cohort readout.
The studio
A small Bangkok practice, not a content mill.
Backup Nodehub opened in Bangphlat in 2016 to help subscription apps stop treating “upgrade rate” as a single number. Most teams we meet already have event volume. What they lack is a shared language for plan surfaces, trial artefacts, and the moments a user actually considers paying more.
Our teaching is built around Thailand and Southeast Asia billing realities — carrier billing, regional storefronts, VAT on digital goods — without pretending every market behaves like a US SaaS template. If you want a generic growth sloganeering course, this is the wrong address.
Catalogue
Three ways into the work
Trial-to-Paid Diagnostic
A short course for teams whose trial looks healthy until the card is requested. We isolate friction from genuine disinterest.
See listing
Paywall State Taxonomy
Name every paywall state your app actually has — including the ones your schema still calls “other”.
See listing63product teams taught since 2016
11-weekflagship lab cadence
47documented paywall patterns
From recent seats
What people actually said
“The paywall state map from week three is still taped above our stand-up board. We stopped arguing about ‘the upgrade screen’ once we had twelve named states.”
The Lab Cycle expects you to bring a usable event taxonomy. We spent the first fortnight cleaning ours before the lectures landed. After that, the pricing-ladder diagnostic was the part we kept.
Method
We teach reading, then instrumentation.
Most analytics courses start with tools. We start with the commercial question: who is considering a higher plan, when, and what evidence would change your mind? Only then do we touch events, windows, and dashboards.
Name the surface
Plan ladders, add-ons, and paywalls are different objects. Mixing them in one funnel hides the conversion you actually care about.
Window the cohort honestly
Upgrade intent in Thailand often follows billing cycles and festival calendars. A 7-day window copied from a US playbook will lie to you.
Write the limitation down
Every lab readout includes what the data cannot claim. That discipline is part of the grade, not a footnote.
Journal
Field notes from the studio
Reading upgrade intent without vanity metrics
Why “viewed paywall” is almost never the event you think it is, and what to log instead.
Why plan ladders stall across Southeast Asia
Storefront currency, carrier billing, and family plans that never appear in a US case study.
If your upgrade story still lives in a single chart, write to the studio.
We reply from Bangphlat within two working days. No automated sales sequence.
Write to Backup Nodehub