# PostHog Setup Checklist for B2B SaaS

## 1. Decision map

- Define the weekly questions product, customer success, growth, and leadership need answered.
- Write the activation definition before implementing dashboards.
- Decide which account-level outcomes matter: retention, expansion, contraction, support load, or usage depth.

## 2. Object model

- Document the user entity.
- Document the account or workspace entity.
- Document the core product objects that represent value delivery.
- Decide which identifiers must be present on every important event.

## 3. Tracking plan

- Name each priority event.
- Define the trigger rule for each event.
- Define required properties and acceptable values.
- Assign an owner for each event.
- Record which dashboard or report will use each event.

## 4. Group analytics

- Choose the PostHog group key.
- Attach account properties needed for segmentation.
- Confirm the same account identifier exists across product, billing, and CRM where needed.
- Ensure core events can be analyzed at both person and account level.

## 5. Implementation

- Instrument custom events for activation, value delivery, and account health.
- Use autocapture only as support, not as the primary source of truth.
- Add event descriptions and tags in PostHog after first ingestion.
- Build actions or composite definitions where the business logic requires them.

## 6. QA

- Test every priority event in a controlled session.
- Verify required properties are populated.
- Check event names against the approved taxonomy.
- Confirm account-level grouping works in queries and dashboards.
- Log any discrepancies before dashboards are shared.

## 7. First dashboards

- Activation and onboarding
- Feature adoption
- Retention and risk
- Revenue and plan movement
- Data-quality monitoring

## 8. Governance

- Store the tracking plan where product and engineering can both update it.
- Maintain a change log for event additions and deprecations.
- Review null rates, unknown events, and stale dashboards every quarter.
- Re-check the taxonomy whenever the activation path or pricing model changes.