I build the machinery lifecycle marketing runs on, and measure whether it works.I build the machinery lifecycle marketing runs on, and measure whether it works.

Problem

Event sign-in was a printed name list at a door. Queues formed while staff searched pages by hand, walk-ups had no waitlist, and the final attendance figure was transcribed from paper the following day.

Solution

Audience

Students and guests signing up for committee events, including walk-ups

Trigger

An event opens for registration — and later reaches capacity

Message

A bilingual Thai/English sign-up form issues a time-limited QR ticket; once an event is full, new sign-ups join a waitlist automatically instead of being turned away at the door.

• QR
• Email
• Live display

Problem

Committee membership lived in a Google Form response sheet. Duplicate and mistyped entries accumulated, nobody chased inactive members, and answering a question about the roster meant reading the sheet by eye.

Solution

Audience

Committee members — about 200 people

Trigger

A member misses a session, or their activity drifts toward inactive

Message

Personalised absence follow-up emails and a soft warning before a member goes inactive — sent from a registry kept clean by validated sign-up and AI-assisted duplicate detection, so every nudge reaches the right person.

• Email
• Discord

Problem

Four Apps Script systems had grown up separately, each with its own login, its own spreadsheet, and its own idea of who a committee member was. Staff re-entered the same person into three places, and nobody could answer a question that crossed two systems.

Solution

Audience

Committee staff and members across every sub-organisation

Trigger

Events, assignments, and deadlines — sent on a schedule, not on every change

Message

One portal for members, events, inventory, and tasks, with an in-app notification centre and LINE push for anything time-sensitive, batched into digests so people keep reading.

• LINE
• Email
• In-app