File Lighthouse began after a series of Sabah product reviews in which the same argument kept returning: the app said the transfer had finished, the issuer said it had not, and the weekly pack treated both as facts.
We are not a software house. We take a named journey, sit with the people who handle exceptions, and write down what the events actually mean. The work lives at Level 10, 25 Sample Avenue, Kota Kinabalu 00000, with most Malaysian clients joining the walks by video after the first in-person day.
People
Aida Rahman spent years in e-wallet operations before moving to independent reviews. She still starts with the contact-centre reason codes, because those names often predate the event list.
Wei Liang Tan matches in-app “success” moments to settlement files and switch acknowledgements. He is the person who asks whether yesterday’s DuitNow count included items still pending at 23:59.
Priya Nair writes the packs. She used to prepare board extracts for a licensed insurer’s purchase funnel and is strict about stating what a sample cannot prove.
How we work
We accept a small number of audits at a time. If two clients in the same narrow product line would create a conflict, we say so before the first invoice. Findings are written so a risk partner who did not attend the walk can still follow the argument.
Malaysia, specifically
Licensing, e-KYC norms, DuitNow rails, and PDPA constraints shape what we will even look at. We will not pretend a method copied from a consumer shopping app applies to a loan origination flow that must survive a Bank Negara discussion.