How an engagement moves from extracts to a brief
This page describes the working order we use for usage audits and related assessments. It is the practical companion to our assessments list.
1. Intake
You send anonymized cloud usage or billing extracts covering a representative window, plus a short outline of primary customer journeys. We schedule a call to clarify architecture questions — not to collect production passwords.
2. Journey-to-resource mapping
We map the journeys you named to the cloud services that serve them. Gaps in tagging or naming become visible here. If the map cannot be completed from the materials provided, we pause and tell you what is missing.
3. Reading the extracts
With the map in hand, we read usage against journeys. Spikes get context. Steady baselines get noted. Ambiguous signals stay marked as ambiguous.
4. Written brief
You receive findings, risks, and a ranked shortlist of measurement priorities. The brief is yours to circulate; we do not lock it behind a product account.
5. Clarification call
Within two weeks of delivery for audits, we hold one follow-up call. Advisory and workshop engagements follow their own cadences described on each assessment page.