Service model
How work moves from intake to handoff
A fixed sequence so workshops and studies finish with artefacts your team can keep—not a deck that expires when we leave.
-
Intake — name the stuck decision
We open with one question your team cannot settle: a disputed path, a cohort that moved after an SDK change, or a schema 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. Audits and walkthroughs do not require write rights to your production schema.
-
Inventory — make drift visible
Events, properties, path steps, and identity rules are listed before recommendations. Synonyms and silent gaps appear here, not as a late-week surprise.
-
Repair ranking — shipping impact first
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 you keep
You leave with written definitions, QA scripts, and a walkthrough. We do not keep operating your stack unless you separately book an Instrumentation Clinic retainer.
Ready to request work?
Most teams begin with a Schema Alignment Workshop. If a single conversion path already argues with reality, tell us which journey and we will suggest a Path Verification Walkthrough instead.