Flagship · 6 weeks · ICT evenings

Destination Funnel Studio

A live seat for product and analytics people who own search-to-book conversion on a travel app. You leave with a corridor-aware funnel, not a relabelled e-commerce template.

Busy Bangkok street with traffic and illuminated signs at dusk

Who it is for

You already have events firing. You already suspect that “Thailand” as a single step is lying. You can get a product lead to look at a one-page argument. You do not need an introduction to what a funnel is.

Teams from OTAs, airline super-apps, and itinerary tools sit in the same room. Homework stays on your own schema. We never require revenue figures.

Informational fee

THB 48,500 per seat

Twelve to eighteen seats. Twice weekly, 19:00–21:00 ICT. One thirty-minute follow-up within six weeks of the last session. No payment is taken on this website — write to the desk to request an invoice.

Request a seat

Modules

1. Event grammar for multi-city search

One-way, return, and open-jaw queries are different products. We rebuild search events so origin, destination, trip type, and intended week travel together. You will throw away at least one vanity “search success” metric.

2. Checkout friction in THB versus foreign cards

Thai baht checkout and foreign-card checkout fail in different places: 3-D Secure, address formats, wallet buttons. The module maps drop-off windows we keep seeing on Bangkok-built apps.

3. Partner inventory latency as a drop-off cause

A spinner is not a bounce. You add a latency flag when live hotel or seat inventory is slow, then re-read “abandonment” with that flag on.

4. Post-search silence before pay

Travelers compare, leave, and return. We treat comparison windows as part of the funnel instead of noise, without turning the schema into a surveillance log.

5. A report a product lead will finish

The close is a one-page shape: leak, likely cause, next experiment, owner. If it needs a thirty-minute walkthrough, it is not done.

Learning outcomes

  • Name and version an event grammar that survives multi-city search.
  • Split checkout funnels by currency and card region without exploding the dashboard.
  • Attribute a measurable share of drop-off to partner latency rather than “UX.”
  • Present one corridor argument that a skeptical PM can challenge in ten minutes.
  • Know what this studio will not cover, so you do not fake a paid-media conclusion.
Portrait of instructor Kamonwan Srisuk

Instructor

Kamonwan Srisuk

Kamonwan led analytics at a Bangkok OTA desk before joining Switch Flowcore. She still reviews production event maps one day a week. Her teaching voice is precise, occasionally dry, and impatient with blended “Thailand” steps.

FAQ

Do I need SQL or a specific analytics vendor?

You need enough access to inspect your event stream and build a simple funnel. Vendor brand does not matter. We do not teach a single tool certification.

Can my whole team join?

Yes, if you book three or more seats from the same legal entity. Group pricing is quoted by email, not listed as a public discount ladder.

What does this studio not cover?

We do not cover paid user-acquisition creative testing, incrementality for ads, or creative scoring. Destination Funnel Studio stops at in-product measurement. If your brief is media mix, this is the wrong room — that limitation is intentional so the six weeks stay honest.

What if I miss a live evening?

Recordings of the lecture portion are available for two weeks. Homework critique is not recorded. One missed critique can be replaced by the included follow-up call.

From people who finished this title

Splitting Phuket from Chiang Mai in week two did more for our board pack than a year of blended conversion charts.

Pimchanok Wattana, senior PM

Kamonwan’s latency flag was the only new event we shipped that quarter. Checkout completion on one corridor moved. I still found the open-jaw homework under-specified.

Jonas · Amsterdam
4 / 5

Worth the ICT evenings if you actually own the funnel. Less useful if you only report weekly numbers you cannot change.

Client in regional OTAs

Write about the next cohort