About Web Lighthouse

Web Lighthouse started because two of us kept being asked, after the fact, why last month’s push numbers could not be compared with the month before. The answers were rarely glamorous: a quiet-hours rule changed, Android started grouping messages, someone renamed an event to please a slide.

We kept the work in Petaling Jaya on purpose. Festival calendars, prepaid mobile habits, and dual-language copies are not footnotes here; they are the conditions under which a notification is seen or ignored.

How we work

We would rather under-claim. If an open rate moved because you sent at 8 a.m. instead of 9 p.m., we write that. If we cannot see the underlying deliveries, we stop the sentence. Clients who want a permanent dashboard are kindly pointed back to the vendor they already have.

People

Aisha Rahman

Spent a decade inside telco messaging teams before she began charging for the uncomfortable readouts. She leads programme reviews and still insists on seeing the actual copy, not a summary of the copy.

Tan Wei Jun

Came from a payments app where “conversion” had meant three different things in one quarter. He runs the event-naming workshops and checks that iOS and Android are not being added like identical fruit.

Priya Menon

Handles office hours and the paper trail — what we asked for, what arrived, what we promised to destroy. She is the person who will tell you the draft is late rather than quietly slipping the date.

We are not a large bench. If two programme reviews overlap, the later one waits. That is written into the quote.

Values we will actually defend

Confidentiality before cleverness. Plain language in the findings. No theatre about “the future of messaging.” A notification is a tap on a lock screen at a particular hour in Malaysia, and the analytics should stay that small and that honest.