Reviews

Not every note is glowing. The useful ones rarely are.

These comments refer to actual modules — MMP hygiene, SKAN mapping, incrementality design, the reconciliation workbook. We publish reservations when students allow it. Aggregate score from 86 written reviews: 4.3 out of 5.

Professional presenting to colleagues in a meeting

The partner-priority lecture saved us from double-counting LINE ads against our MMP. I still argue with creative about view-through, but at least the numbers now share a window.

Pimchanok T. · UA lead, Bangkok e-commerce

Wan’s SKAN labs assumed more iOS volume than our Android-heavy catalogue had, so I skimmed those weeks. The reconciliation spreadsheet is what I open every close.

Client in ride-hailing ops

★★★★☆

Dry in the best way. I wanted more time on device-farm fraud; the rest of the MMP module was exactly the mess we live in.

Arun · Chiang Mai · alumni board

I used the incrementality memo template almost verbatim with our CFO. He still wanted last-click in the appendix. The memo made that request look like a preference, not a law of physics.

S. V. · Singapore, remote Route Studio seat

★★★★★

Signal Desk recordings are tighter than I expected. Office hours 2 was the only time I got a live look at my conversion-value sheet. Worth booking both hours early.

Mali · in-app subscription product

Anonymous because my employer is sensitive. The fraud clinic did not “catch a ring.” It showed me our CTIT spike was a timezone misconfiguration. Slightly embarrassing. Very cheap compared with pausing spend.

Client in travel apps

Case notes

Two longer accounts

Team meeting with documents spread on a table

Marketplace UA, Bangkok — Route Studio

A regional marketplace arrived with three Android stores, one iOS listing, and an MMP that had not had its partner list reviewed since a 2022 agency handoff. During the MMP hygiene module they found view-through credit still open at 24 hours on a network that their contract described as click-only.

The capstone did not produce a heroic ROAS chart. It produced a one-page policy: click windows by network, a closed view-through list, and a finance note explaining why “installs” would drop 11% on paper after the change. Six months later they wrote to say the drop happened, finance had been warned, and nobody got fired.

Shared with permission · names withheld for vendor reasons

Two colleagues talking through a document

Fintech growth pod — Full Corridor

Naree’s team had a clean SKAN scheme and a messy Android story. The private audit after Route Studio focused on delayed revenue events: card applications that completed days after the click, well outside the window their US playbook recommended.

They did not lengthen every window. They split reporting: a short window for media optimisation, a longer observed window for finance, and a written rule that those two numbers would never be presented as one. Naree still calls the split “politically expensive.” She also says it ended the monthly argument about which dashboard was lying.

Naree S. · growth, Bangkok fintech