Flagship reading

Portfolio Health Review

A time-boxed reading of crash clusters, retention cliffs, and release friction across every live app you own, delivered as a written brief and a half-day findings session in Seremban or on your floor.

Reviewer comparing printed charts and notes at a wooden desk

Who this is for

Product directors, heads of digital, and operations leads who already run several consumer or staff apps and cannot tell, from the weekly slides, which title is actually unwell.

What you leave with

A ranked picture of portfolio health: which apps are losing people after a release, which crash clusters are shared (SDK, login, payments), and which numbers are noise. You leave with a bound brief, a one-page heat table, and a recorded findings session.

Included

Intake call to lock the app list, storefronts, and the questions the reading must answer
Document-pack review: crash extracts, retention tables, release calendars, and known incidents from the last two quarters
Cross-app comparison of crash-free sessions, day-7 return, time-to-first-failure after a release, and support volume tied to version
Written brief (usually 12–18 pages) with a heat table, ranked findings, and a short list of next readings or dashboard work
Half-day findings session with the people who own the apps — not a slide walkthrough for a steering committee

Left out

We do not install analytics SDKs, rewrite tracking plans, or run your storefront listings
We do not staff an on-call rota or sit in your release train after the findings session
We do not produce a live dashboard in this engagement — that is a separate commission

Who does the work

Aisha Rahman leads the reading, with Lim Wei Han on the heat table and charts. Farah Idris chairs the findings session so product owners can argue with the ranking in the room.

Time and place

Ten working days from a complete document pack, plus a half-day findings session

Prepared in the Seremban office; findings session in Seremban, at your site in Peninsular Malaysia, or by video if the reading room cannot travel

Fee

Quoted from the number of live apps, storefronts, and analytics properties in scope. Reviews for four to eight apps typically start at RM 18,500.

How to begin

Write to the Seremban office with the number of live apps and the question you need the brief to settle. We reply within two working days with a scoped fee or a request for a clearer app list.

Write about this work

How the work runs

Lock the portfolio

We agree the live titles, the storefronts that count, and the two or three questions the brief must answer. Apps in private beta stay out unless you put them in writing.
Document pack

You send crash extracts, retention tables, release notes, and incident logs. We send a checklist. Incomplete packs pause the clock; we do not guess missing versions.
The reading

Two reviewers work the same pack independently, then reconcile. Shared failures (a login SDK, a payments webview) are called out as portfolio problems, not blamed on one product owner.
Findings session

Half a day. We walk the heat table, then sit with the disagreements. The brief is final after this session, not before, so the ranking can change if a constraint was missing.

Prepare before we start

Name a single counterpart who can obtain extracts from engineering and storefront teams. Warn product owners that the findings session is a working room, not a presentation. If crash exports are sampled, say so — we will treat them as sampled.

Limits we will not stretch

We need at least two quarters of comparable extracts. Brand-new titles with three weeks of traffic cannot be ranked against a mature app. We work in English. Classified or payment-card data must be stripped before it leaves your building.