Service model
Engagement playbook
A predictable sequence so baselines and path reviews finish with artefacts your team can keep—not a deck that expires after the kickoff glow.
-
Frame — one decision worth answering
We start with the measurement question that is blocking shipping: a disputed path, a session chart that moved after an SDK change, or a catalogue nobody owns. Scope stays narrow on purpose.
-
Access — read-only where possible
You grant temporary read access to the analytics tool, event stream, and relevant docs. We do not need write rights to your production schema for a baseline or path review.
-
Inventory — make the mess visible
Events, properties, path steps, and identity rules are listed before any recommendation. Synonyms and silent gaps show up here, not in a late-week surprise.
-
Repair order — ranked 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 your team owns
You leave with written definitions, QA scripts, and a walkthrough. We do not keep operating your stack unless you separately book Analytics Office Hours.
Ready to place a request?
Most teams begin with a Measurement Baseline Review. If a single conversion path is already arguing with reality, tell us which path and we will suggest Conversion Path Instrumentation instead.