Audits

Work we take on a living event catalogue

Each engagement starts from payloads and screens, not from a generic analytics checklist. Choose the audit that matches how stuck the names have become.

A person reviewing printed documents and a laptop at a desk
Notebooks, printed pages, and a pencil laid out for a careful document review

Flagship audit

Parser event validation

A close reading of the payloads your app actually emits, compared against the names, types, and required properties your reports still assume.

From RM 7,800 · Usually two to three weeks from sample receipt

A written checklist and planner open on a wooden desk

Catalog work

Event taxonomy cleanup

Collapse duplicates, retire dead names, and leave one agreed catalogue so checkout_completed and order_success stop competing in the same report.

From RM 9,400 · Three to five weeks, depending on catalogue size

Hands writing notes beside a laptop during a planning session

Source of truth

Tracking plan reconstruction

Rebuild the written plan from what ships today, with owners, triggers, and property definitions, instead of a stale spreadsheet from the last launch.

From RM 6,200 · Two to four weeks

Colleagues gathered around a table during a working session

Working session

Instrumentation handover session

A half-day in Seremban or online in which we walk engineers and analysts through the findings, the rename map, and the first week of fixes.

RM 2,400 · Half a day, plus a written recap within three working days