account-handover
Account Handover Notes
Draft a structured handover document when transitioning a PostHog account from one TAM or CSM to another. The document gives the incoming owner everything they need to pick up the account without the customer noticing a gap.
Input: Account name (and optionally: reason for transition, any context the outgoing TAM wants to include)
Core Workflow
- Ingest context — Read what the TAM provides (account name, transition reason, anything they want to flag)
- Pull Vitally account data — Account health, contacts, notes, conversations
- Pull PostHog usage data — Product usage, event volume, feature adoption
- Pull billing context — Spend breakdown, plan tier, billing trend
- Synthesize handover document — Compile into the structured format (see Output Format)
- TAM review — Present the draft for the outgoing TAM to fill in gaps the data can't capture
Step 1: Pull Vitally Account Data
Search for the account and pull everything relevant. Run these in parallel where possible.
More from posthog/skills
posthog-debugger
Debug and inspect PostHog implementations on any website. Use this skill when a user wants to understand how PostHog is implemented on a page, troubleshoot tracking issues, verify configuration, check what events are being sent, or audit a PostHog setup. Works with Chrome DevTools MCP and Playwright MCP to inspect live websites.
107integration-nextjs-app-router
PostHog integration for Next.js App Router applications
102instrument-product-analytics
>-
91feature-flags-nextjs
PostHog feature flags for Next.js applications
88instrument-feature-flags
>-
87error-tracking-nextjs
PostHog error tracking for Next.js
85