Client stories

Evidence from catalogues that held

These notes come from product and analytics leads who booked workshops or instrumentation reviews. They mention specific constraints — not generic praise.

“We finally stopped counting client ‘Buy’ taps as revenue. The instrumentation review forced the checkout confirmation onto the server event our ledger already used.”

Hafiz Rahman

Product lead, subscription learning app · Kuala Lumpur

“The taxonomy workshop was slower than I wanted on day one — we argued over three entitlement names for almost an hour — but the catalogue has held through two major releases.”

Siti Noor

Analytics manager, regional commerce app

“Retained support sounds minor until a release adds six new handlers. Having Priya on the calendar meant the decision log stayed current instead of living in Slack.”

Jason Lim

Engineering manager, multi-app fintech portfolio

“I wished we had shared sanitised payloads earlier; the first review week was mostly waiting on access. Once that cleared, the annotated map for renewals was concrete enough for tickets.”

Melissa Ong

Data lead, media streaming app · Penang (remote engagement)

Extended stories

Subscription learning app — instrumentation review

The team’s board pack showed weekly “purchases” 18% higher than finance settlements. Server Canvas Base traced the gap to a client event firing on payment sheet open. The review remapped three journeys (trial start, first paid period, renewal) onto handlers that write the entitlement table. Implementation took the client’s engineers nine days; the following month’s board pack matched settlement within normal chargeback variance.

Constraint worth noting: staging lacked realistic promo codes, so one property had to be validated in production with a feature flag and a short dual-write period.

Regional commerce app — taxonomy workshop

Two Android squads and one iOS squad had invented parallel names for cart and checkout server callbacks. A full-day workshop in Klang produced a shared catalogue of twenty-two events and a decision log for the five most contested names. The mild reservation from their analytics manager — that day one felt slow — reflected real disagreement that needed airtime before documentation could stick.