About the studio

A small teaching house for people who ship apps into new Thai and SEA markets.

Vault Flowcore started because too many expansion decks treated Thailand as a row in a global spreadsheet. We built a studio in Din Daeng where operators sit with live storefronts, not slideware.

Team discussing work around a table

Mission

Make regional app analytics boringly specific.

Our mission is narrow: help product, growth, and research teams read a market they do not yet live in, without pretending a single MMP dashboard is enough. Thailand is our home ground. Neighbouring corridors are the comparison set, never a blur.

We refuse vanity metrics in class. If a number cannot survive a question from a sceptical finance partner in Bangkok, it does not go on the scorecard.

Pedagogy

Evenings, artefacts, and disagreement on purpose.

Live artefacts over lectures

Each module produces a worksheet you can take back to work: a storefront annotation, an attribution window map, or an exec scorecard with explicit limits. Slide decks exist, but they never replace the artefact.

Disagreement is scheduled

One session in every track is a structured argument: a student defends a metric, another student attacks it, and the instructor only referees. Thailand’s mixed iOS/Android reality makes this less theoretical than it sounds.

Qualitative pairing

We walk nearby storefronts and payment kiosks when the cohort is in Bangkok. Remote students complete a guided intercept script with a local colleague. Numbers without a human sentence are incomplete.

English room, Thai context

Instruction is in English. Examples, listings, and guest notes stay rooted in Thai and nearby markets so the language of teaching does not wash out the market itself.

Community

Operators who stay in touch after the last lab.

Alumni sit in a quiet mailing list and a quarterly Bangkok breakfast. We do not run a loud social network. People trade storefront screenshots, warn each other about chart artefacts, and occasionally hire across companies.

Guests have included research leads from regional publishers, a payments analyst who specialises in PromptPay funnels, and a former Play Console reviewer who now teaches listing policy as a craft.

Student journey

From first email to a scorecard your exec will actually read.

  1. 01

    Intake conversation

    You tell us the corridor, the current stack, and what must be true in ninety days. If a briefing is enough, we say so. If the flagship is too light for a ten-person team, we point you to the atelier.

  2. 02

    Cohort weeks

    Evening labs twice a week, one async critique, and a mid-track office hour. You work on your own app unless you prefer a studio case.

  3. 03

    Scorecard defence

    The last session is not a certificate ceremony. You present the expansion scorecard, including the limitation you are least comfortable naming.

  4. 04

    Aftercare

    Thirty days of written questions, then the alumni list. We do not offer ongoing retainers through the school; that keeps teaching honest.