Account Atlas
A living map of how we group accounts for B2B app analytics—so your team shares names before the next briefing.
How we sequence an account engagement
Each step produces an artifact your analytics and product partners can keep after we leave.
Signal inventory
We list every account field you already collect—org ID, billing entity, domain, seats—and note where they disagree.
Schema draft
We propose named tiers with inclusion rules, exclusions, and the primary metric each tier is meant to move.
Contrast pass
We compare activation, expansion, or retention across priority cohorts and flag journeys that stall inside accounts.
Briefing package
You receive a written report or memo your stakeholders can reuse in planning—without waiting for a dashboard redesign.
Example account cuts
Illustrative tiers we often start from for Thailand-based B2B product teams. Final schemas are tailored in the audit.
Trial & evaluate
Focus: New workspaces still proving value with limited seats
Signal: Invite events, first module completion, admin setup
Review cadence: Weekly activation and time-to-second-seat
Growing mid-market
Focus: Paying accounts expanding seats or modules
Signal: Seat growth, feature adoption depth, support load
Review cadence: Bi-weekly expansion readiness
Enterprise portfolio
Focus: Multi-workspace orgs with hierarchical reporting needs
Signal: Parent org mapping, SSO domains, contracted seats
Review cadence: Monthly health and renewal risk
Dormant / thin coverage
Focus: Accounts missing reliable usage or identity signals
Signal: Null org IDs, conflicting domains, silent seats
Review cadence: Tracked as a coverage KPI, not a growth segment