About Web Studio Core

Quiet office corridor with soft daylight

Web Studio Core began as a small desk in Petaling Jaya for product people who were tired of launch parties that could not answer a simple question: did anyone take up the new work?

We are not a software house. We do not keep your analytics account. We are hired for a stretch of weeks to read a feature the way a careful outsider would: by sitting with event names, with a sampling window, and with people who used the path or walked past it.

Origin

The first paid study was for a neighbourhood retail app whose “repeat last order” control looked busy on day one and idle by day ten. The owners wanted a chart. What they needed was a sentence about shoppers who had tapped the control because it sat in the old button’s place. That sentence still shapes how we write.

Malaysia’s app teams often serve mixed hours — lunch counters, night markets, payday Fridays, school pickup. Feature adoption here is rarely a single curve. It is a set of rooms. We stay close to those rooms.

How we work with you

A named analyst owns the engagement from intake to readout. We ask for a product owner who can answer within two working days. We prefer anonymised exports over live poking at production. Interviews happen with consent handled on your side before we are introduced.

We will decline work whose only purpose is to decorate a board slide, and we will say when the events you have cannot support the question you want asked.

People

Portrait of Amira Latif

Amira Latif

Leads feature adoption studies. Previously sat with operations groups in retail and school-parent apps across Selangor.

Portrait of Daniel Khoo

Daniel Khoo

Reads event maps and payday-sensitive windows. Keeps the written account honest when first-tap counts look kinder than return use.

Portrait of Siti Rahmah

Siti Rahmah

Runs workshops and interviews in Malay and English. Holds the room when a team would rather talk only to fans of a release.

Values we will say out loud

Silence is a finding. Shared buttons are a problem. Averages that mix lunch and night shift are usually a mistake. The client still owns the product; we own the wording of the account until the readout is over.

If you want to see the weeks on a page, read how we work. To commission a study, write to us.