Service model
The engagement process
A predictable sequence so blueprints and reviews finish with artefacts your team can keep—not a slide deck that expires.
-
Intake — name the stuck decision
We start with one decision your team cannot settle: a disputed conversion path, a retention 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 blueprint or audit.
-
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 plan — ranked by shipping impact
Fixes are ordered by how much they change decisions you make this quarter. Nice-to-have 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 Blueprint. If a single conversion path is already arguing with reality, tell us which path and we will suggest Path Instrumentation QA instead.