Bangkok studio · live cohorts · ICT evenings

Numbers that follow the traveler, not the dashboard template.

Switch Flowcore trains product and analytics people to read travel apps as journeys: multi-city search, payment friction, silent days after booking, and the reopen that happens on the tarmac.

Aircraft wing above clouds, photographed from a cabin window

17: Cohorts run from the Ekachai desk since 2019
2,140: Seats issued across live and recorded programs
63: Partner apps whose event maps we have reviewed
8.4 wks: Median length of a full studio program

The desk

We teach from Thailand because the traffic here is honest.

Bangkok is a hub for regional OTAs, airline super-apps, and boutique itinerary tools that serve both Thai baht checkout and foreign cards on the same screen. That mix exposes event design mistakes that a single-market SaaS template never sees.

Our pedagogy is slow on purpose. You leave with a named event grammar, a corridor calendar, and a reporting shape a product lead can argue with — not a pile of unlabelled charts.

How the studio works →

Long-tail boats in turquoise water off a Thai coast

Traveler comparing a paper map with a phone at a cafe table

Flagship program

Destination Funnel Studio

A six-week live seat for teams who own search-to-book conversion. We rebuild the funnel around multi-city queries, THB versus foreign-card drop-off, and partner inventory latency — the three leaks that generic e-commerce funnels ignore.

Evenings in ICT. Informational fee: THB 48,500 per seat. No checkout on this site.

Read the curriculum

What we insist on

Travel App Analytics is a craft, not a plugin.

Name the corridor before you name the KPI.

Bangkok–Chiang Mai in April is not the same product as Bangkok–Seoul in October. We teach you to slice cohorts by route season, not by calendar month copied from a SaaS playbook.

Instrument the silent week after booking.

Most travel apps celebrate a paid reservation and go quiet. Travelers reopen the app to check baggage, gates, and weather. If those events are missing, your retention story is fiction.

Treat offline saves as first-class events.

Itinerary tools die in tunnels and on islands. We cover queued writes, retry grammar, and how to keep analytics honest when the network returns hours later.

Write reports a skeptical PM will finish.

A destination funnel that needs a thirty-minute walkthrough is unused. Every program ends with a one-page shape: leak, cause, next experiment, owner.

From recent seats

People who sat in the room, not a composite.

The Destination Funnel Studio forced us to stop averaging Bangkok and Phuket into one “Thailand” step. Conversion moved once we split those corridors.

Nalinee K., analytics lead · regional OTA

I still think the homework load in week four is heavy if you also run a live app, but the offline-save module paid for the late nights.

Marcus · Berlin, itinerary startup

8/10 after Corridor Seasonality Lab. Clearer Songkran planning. Wish they had published the spreadsheet template on day one instead of week three.

Client in airline super-apps

Longer case notes →

Programs