Planning

Work we will actually put our name on

Each engagement produces a document or a punch list. None of them include a login to something we host. If you need a full dictionary, start with schema planning. If you already have a pile of names, start with an audit.

Planner spreading paper notes and a printed inventory across a wooden table

Flagship · Three to six weeks

Event Schema Planning

A written event dictionary for one app: names, properties, identity rules, and an engineering handoff that iOS, Android, and web can share.

Quoted from the event inventory. Most first plans land between RM 18,000 and RM 45,000.

Open the brief
Person reviewing printed tables and handwritten notes at a desk

Ten to fifteen working days

Tracking Plan Audit

A review of the events you already fire: duplicates, silent properties, and names that no longer match the screens they claim to describe.

From RM 8,500, based on the number of distinct event names in the export.

Open the brief
Small team comparing notes around a laptop in a bright meeting room

One to two weeks after a build is available

Instrumentation Review

A pass through the live app to check that events fire on the trigger named in the plan, with the properties the dictionary allows.

From RM 6,000 for a plan we wrote, or from RM 9,500 for a plan written elsewhere.

Open the brief
People seated around a conference table during a working discussion

Half day (four hours) plus a written recap within three working days

Naming Workshop

A half-day working session that leaves the product squad with a naming convention and a first list of events they will actually keep.

RM 3,200 for up to eight people. Additional seats by arrangement.

Open the brief