Who this is for
Publishers who already sell through in-app purchases and cannot tell, from the store charts alone, why money appears in week one and thins out by the first renewal. Typical rooms: a two-person studio in Petaling Jaya shipping a language app; a KL media company with a news subscription; a game team whose gem packs refund more than they expected after a festival sale.
If you have not shipped a paid SKU yet, wait. There is nothing honest to audit.
What you receive
A written briefing (usually twelve to eighteen pages) covering:
- which product IDs actually collect money versus which only collect impressions
- where the paywall sits relative to the first useful moment in the app
- refund clusters by day, SKU, and country, including Malaysia where the sample is large enough
- for subscriptions: trial conversion, introductory-price hangover, grace period, and billing retry
- a short list of changes we would make, in order, and a shorter list of changes we would not make
The briefing is followed by a ninety-minute working session. You may take that session in Office 7, or on a call if the team is not in Kuala Lumpur.
What we look at
We read the catalogue you sell, not a generic ‘funnel’. That means product IDs, price tiers, introductory offers, family sharing, promotional offers, restore-purchase behaviour as you describe it, and the exact paywall copy on the build you currently have in review or in production.
Store reports come from App Store Connect and Google Play Console in the form you can legally export. We do not ask for your account password.
What we do not do
We do not rewrite your app. We do not submit a new binary. We do not run paid user acquisition. We do not promise a lift in revenue. We do not keep a copy of your reports after the engagement unless you ask us, in writing, to retain them for a follow-up.
If the real question is ‘should we add a weekly plan’, the SKU and price ladder review is the tighter piece of work.
How the weeks run
Week one. We confirm the catalogue, the stores, and the countries that matter. You send exports and paywall screenshots. We flag missing SKUs before we start writing.
Week two. We read refunds against paywall copy, and renewals against the introductory price. If a finding depends on a country mix (Malaysia versus Singapore versus the rest of Southeast Asia), we say so instead of averaging it away.
Week three. You receive the briefing. Two working days later we sit with it. You leave with a marked order of work, not a second document.
Preparation
Before week one we need: a product-ID list with prices and intro offers; one month of purchase, refund, and (if you sell subscriptions) renewal reports; screenshots of every paywall, including the ones shown only to lapsed subscribers; and a note on any store-policy warning you have received in the last quarter.
Sandbox receipts are useful. Production receipts are better. If legal will not release production numbers, say so early — the briefing will be thinner and the fee does not drop by much, because the reading time remains.
Constraints
We take one full audit at a time. If your catalogue has more than eighty paid product IDs, the fee rises and the three-week clock may become four. Apps that sell only through a third-party web checkout are outside this desk.
Price basis
From MYR 12,800 for a single store and a catalogue under twenty paid SKUs. Both stores, or a larger catalogue, is quoted after we see the product-ID list. A thirty percent deposit holds the week. The balance is due when the briefing is delivered, before the working session.
Next step
Write to the Kuala Lumpur office with the app name, the stores, and a rough SKU count. If the fit is poor, we will say so rather than stretch the audit into something else.