About the studio

A small room in Chonburi for a very specific craft


Cloudqueuegrid exists because too many teams in Thailand inherited a push vendor and never inherited a measurement practice. We teach the second thing.

Small group in conversation around a table

Mission

We want product, CRM, and growth people to defend a push number in front of finance without waving at a green dashboard. That means naming the queue, the token, the OEM constraint, and the attribution window in the same sentence.

We are not a media agency. We do not run your campaigns. We train the people who will still be in the building when the agency retainer ends.

Pedagogy

Every module starts with an export you already have — CSV, BigQuery dump, or a vendor UI screenshot if that is all finance will give you. Faculty annotate the holes before they introduce a framework. Slides arrive after the critique, not before.

Homework is deliberately uneven. Some weeks ask for a one-page metric dictionary. Others ask you to sit with engineering for an hour and return with a latency diagram. We would rather you miss a polish pass than invent a clean dataset.

Community

Cohorts stay small on purpose. Alumni keep a private mailing list for token-health incidents and festival-calendar notes. There is no public Slack full of unread channels. If you want a loud community product, we will point you elsewhere.

Several alumni work from Bangkok, Hat Yai, and remote seats across ASEAN. The studio itself remains in Pattaya so that in-person weeks can use one timezone and one set of quiet-hour assumptions.

People

Who holds the room

Portrait of Nalinee Prasert

Nalinee Prasert

Measurement lead

Former CRM analytics lead at a Bangkok multi-brand retailer. She designed the Lab’s token-health checklist after watching invalid tokens inflate “audience size” for three consecutive Songkran campaigns.

Portrait of Marek Lindqvist

Marek Lindqvist

Queue systems faculty

Visits from the infrastructure side. He teaches workers, backoff, and why a “sent” event in your app database is not the same as an APNs accept.

The student journey

Most people arrive mid-career: a CRM manager who can write SQL, a product analyst who owns a notification epic, or a founder who still approves copy in a group chat. We do not admit complete beginners to mobile development; you need at least one live push programme behind you.

  1. Enquiry and a thirty-minute diagnostic call. We will tell you if the Lab is a mismatch.
  2. Pre-work: export one campaign and label every column you can name without guessing.
  3. Twelve studio weeks, one live critique, one revised metric dictionary.
  4. A six-month check-in. We ask which artefacts you still use. That number appears on the home page because we actually collect it.

If you only need a one-day briefing for leadership, look at fees rather than the Lab. The Desk Seat exists for that shorter conversation.