Service model
Engagement playbook
A fixed sequence so schema and path work ends with artefacts your team owns—not a deck that expires when the consultant leaves.
-
Scope — name the stuck decision
We begin with one decision your team cannot settle: a disputed conversion path, a retention swing after an SDK change, or a schema nobody owns. Breadth stays intentionally narrow.
-
Access — read-only by default
You grant temporary read access to the analytics tool, event stream, and relevant docs. Write access to production schemas is not required for design or clinic work.
-
Inventory — surface the contradictions
Events, properties, path steps, and identity rules are listed before recommendations. Synonyms and silent gaps appear here, not as a Friday surprise.
-
Plan — rank by shipping impact
Fixes are ordered by how much they change decisions you make this quarter. Cosmetic renames wait behind broken step events and identity resets.
-
Handoff — artefacts stay with you
You leave with written definitions, QA checklists, and a walkthrough. We do not keep operating your stack unless you separately book Analytics Office Hours.
Ready to start?
Most teams begin with Event Schema Design. If a single conversion path already disagrees with product reality, tell us which path and we will suggest a Conversion Path Clinic instead.