Flagship engagement
Retention Study
A four-to-six-week engagement that rebuilds your return tables, speaks with people who left, and leaves a written brief the product team can argue with.
The Retention Study is for a product owner, head of membership, or publisher who already ships an app and can share event history. It is not a software licence. You receive people in the room, a written brief, and a workshop — then we leave.
Who it is for
Teams with at least three months of identifiable return events (open, session, order, listen, or equivalent). Typical clients are grocery, ride, media, and community apps serving Malaysia or the wider region, with a counterpart who can explain event names without a week of delay.
What you walk away with
A bound brief (PDF and printed) covering: which weekly cohorts still return at week four and week twelve; which first-week jobs fail; summaries of eight to twelve lapsed-user conversations; and three to five recommended changes ranked by how much they ask of engineering versus operations. We do not hand over a live reporting product.
Scope
Included: reconstruction of weekly and monthly return tables from your export; a holiday calendar overlay for Malaysia; recruitment and interviews with lapsed users from a list you approve; one findings workshop of up to four hours; one round of written questions after delivery.
Excluded: building or hosting an analytics warehouse; implementing tracking; running paid acquisition; ongoing weekly reporting after the study ends.
Who does the work
Aisha Rahman leads the study. Tan Wei Ming rebuilds the tables. Priya Nair conducts interviews. You will not be passed to a rotating bench of contractors.
How it runs
A kickoff at our office or yours sets the product, markets, and event dictionary. Weeks one and two are spent on the tables. Weeks three and four are interviews. Weeks five and six are the brief and workshop. If a festive period (Hari Raya, Chinese New Year, Deepavali) falls inside the window, we extend by one week so those days are not treated as ordinary drop-off.
Duration and place
Four to six weeks of calendar time, with the team in Kuala Lumpur. Remote reading of files is fine; the workshop is in person unless the product team is entirely overseas.
Preparation
You provide a dated event export (or warehouse access limited to agreed tables), a definition of a “return,” a lapsed-user contact list with consent already in place, and one counterpart. We do not scrape stores or guess at numbers.
Constraints
We will not publish your figures. If event names are so inconsistent that a return cannot be defined, we stop at a diagnostic note and refund unused interview days as set out on the refund page.
Price
Quoted. A single-product Malaysian app with a clean export typically sits in a different band from a multi-country catalogue with five event taxonomies. See Rates for the factors we price against. No card is taken on this site.
Next step
Send a note with the app name, how you currently define a returning user, and whether a lapsed list already exists. We reply within two working days with a scope outline, not a contract in the first email.