Not every seat loved every week. That is recorded too.
These notes come from people who finished a Switch Flowcore program. We keep the mild reservations. Fake five-star walls do not help you decide.
After Destination Funnel Studio we stopped reporting a single “search success” rate. Splitting one-way, return, and open-jaw queries made the leak obvious on foreign-card checkout.
★★★★☆4 / 5
Retention After the Booking was the first class that treated post-purchase silence as a product surface. I wanted more Android examples; the drills leaned iOS.
The Corridor Seasonality Lab finally gave us a Songkran window that finance would accept. Anan’s holiday table is now in our planning repo.
Mira’s offline itinerary session saved us from double-counting saves when the ferry Wi-Fi came back. Dry delivery, exact diagrams.
Case note · 11 weeks
Regional OTA, Bangkok hub
A twelve-person product analytics group joined Destination Funnel Studio after their board asked why Phuket conversion lagged Chiang Mai even when ads were cheaper.
They arrived with one blended funnel. By week three they had three corridor funnels and a latency flag for partner hotel inventory. Checkout completion on the Phuket corridor rose 6.2 percentage points over the following quarter. They still struggle with open-jaw trips — a limitation Kamonwan flagged in class and they have not staffed yet.
Attribution: full name withheld at the company’s request. Role: head of product analytics.
Case note · itinerary tool
European startup selling Thailand trips
Two analysts took Retention After the Booking while their engineers shipped an offline map pack. Before class, “Day 7 retention” mixed people who had already travelled with people still planning.
They rebuilt cohorts around departure date instead of install date. Support tickets about “missing trip” dropped once the silent week emails only went to travelers whose departure was still ahead. One analyst noted the homework assumed English event names; their schema was partly German, which slowed week two.
