Feature adoption study

This is the work most teams ask for when a feature has been live long enough to leave a trail, but not long enough for folklore to replace facts.

Who it is for

Product owners, research leads, and founders who can name the feature in one sentence — “the savings pocket,” “the split-bill step,” “the parent reply thread” — and who still cannot say whether the people they built it for returned after the first tap.

The result

You receive a written adoption account. It describes first contact, repeat use, and drop-off in the language of the people on the app, not in slogans. A two-hour readout sits with your team so the account can be questioned while the evidence is still on the table.

Scope

One feature, or a pair that share a single door (for example a new menu item that opens two related screens). We do not fold an entire app into one study.

Included

• An intake conversation that names the feature, the audience, and the dates it went live
• A review of the event names you already collect, including gaps that would hide adoption
• A sampling window, usually fourteen to twenty-eight days after launch or after a quiet period you choose
• Six to ten short interviews with people who tried the feature and people who never reached it
• Tables of first use and return use, annotated in plain language
• The written account and the readout session

Excluded

We do not write application code, redesign screens, buy advertisements, or run your analytics account after the study ends. If events are missing, we will say so; we will not invent counts.

Who does the work

Analysts at Web Studio Core, based at Level 12, 64 Sample Avenue, Petaling Jaya 00000. Interviews may be in Malay or English according to the people you introduce.

How the weeks run

Week one is intake and the event map. Weeks two and three are the sampling window and interviews. Week four is drafting. Week five is the readout and a short period for factual corrections.

Duration and place

Five weeks is typical. Sessions are remote. One working day can be held in Petaling Jaya or at your office in the Klang Valley if the team wants the readout in the same room.

What you prepare

A named owner who can answer questions within two working days. Access to anonymised event exports or a view into the analytics workspace you already use. A short list of people we may invite to interview, with consent already considered on your side.

Constraints

We will not accept a study whose only goal is to decorate a board deck. If the feature has not been used by anyone in the window, the account will say so. That is still a completed study.

Price

From RM 18,400 for a single-feature study. Travel inside the Klang Valley is included; travel beyond that is quoted separately. See fees for what moves the figure.

Next step

Request a scoping call and name the feature. We reply within two working days with whether this study, a shorter launch readout, or an event map review is the honest fit.