Onboarding a new CSM (team leads)
Contents
So you've got a new CSM joining your team! This page is for team leads - the joiner-facing plan is new starter onboarding. Here's what to prepare and when:
- Before they join - prepare their book, book the 1:1s, plan the in-person week
- First week - welcome 1:1, get the team sharing calls and tips
- In-person week (usually week 2) - 3-4 days working together, agenda template below
- First month - any spillover from in-person onboarding
Before they join
Prepare their book of business:
- Accounts come from a few places (listed by priority): CSMs can offload accounts if they're overloaded, product-led sales and new business sales can have accounts waiting for a CSM handover, and Simon frequently pulls net-new accounts - ask all groups to see what needs coverage.
- Tee up ~20 accounts so they're not at capacity immediately - it also leaves room for late handovers.
- Follow the capacity model, and bonus points if accounts can line up with their previous experience.
Book the 1:1s: Welcome 1:1 on day 1, a recurring 1:1, and (optionally) an extended 1:1 every 4 weeks.
Find an onboarding buddy: Another CSM (same geography) to schedule a 1:1 and provide additional support if they need it. Plan the in-person onboarding: Usually week 2 - the agenda below is what we've been running. Logistics that help:
- Ask the wider team to see if they're free to drop by for a day or two
- Put sessions in your own calendar so you’ve got time blocked for onboarding
- Post in the local city channel about the onboarding and organize a dinner with local PostHog humans
First week
Welcome 1:1:
- Walk through their onboarding plan - week 1 is a lot of reading, watching and shadowing. It'll feel unproductive!
- How we work - sprint planning, account review, ask in public by default.
- Our feedback culture, and give them their SuperDay feedback.
- How you want to use 1:1 time. Management at PostHog is relatively light-touch - worth resetting expectations upfront, especially if the new CSM is used to heavier structure.
- Additional things if there’s time:
- Share your readme.
- Ask them to post their first five customer calls in the team channel for feedback - gets them used to sharing in public early.
- Ask how they like to receive feedback (and praise!)
Example welcome 1:1 agenda - to copy into your 1:1 doc
Ask the team to share things! And for calls the new CSM can shadow on.
Optionally, a check-in 1:1 on day 3. The first week is a lot of solo reading - a midweek touchpoint helps. Also check to see if the onboarding buddy has scheduled a 1:1 as well!
In-person week (usually week 2)
In-person onboarding covers the company-wide process. Below is how we run the CSM week over 3-4 days - there's a 4-day agenda template to start from, which we copy into a canvas in their onboarding channel. It's a living template - add what you learn from each onboarding. 3 days can feel tight with a lot of information, but it's enough to cover all the content!
By the end of the week they should:
- Know how to use the data we have to tell whether a customer is getting value from PostHog, prioritize their book, and plan next steps
- Know where to find answers and how to verify them
- Have their own Vitally / Customer Analytics views set up, and a first outreach drafted - maybe even sent!
Sessions tend to work best as observe, do, review - you do it once, they try it on their own, and you give feedback.
Topics to cover
Context (day 1)
- CSM overview - who we cover, why we exist, how comp works, the CSM + TAM overlay
- How we work - sprint planning, account review, the quarterly goal
- Tools & access check
- Agent setup - MCPs, a PostHog repo clone, impersonation, and a list of GTM skills from the skills store
- Finding info - where to look (handbook vs repo vs Slack), maybe even a working exercise (e.g. "what is the Teams plan?")
Understanding a customer's usage (day 2)
- What is the customer using PostHog for? The products they pay for, the events they capture, what they do with the data
- How's the relationship? The active users and what they're doing (candidates for outreach), recent tickets and calls, which PostHog humans they've talked to (AE, onboarding, TAM, CSM)
- Are they set up well and getting value? Run the basic implementation review and health check
- Commercials:
- Monthly usage - forecasted MRR, billing limits, platform add-ons
- The contract, if they're on one - how much credit they bought, when they renew, are they on track? Talk through contract rules and the tools we use (QuoteHog, PandaDoc, Salesforce)
Prioritizing across the book + deciding next steps (days 3-4)
- Prioritizing a book - the signals we look at and which ones are more worrisome, both when a book is first assigned and on an ongoing basis. Have them set up their own Customer Analytics views
- Deciding next steps - by now they should have a read on where each account's at (or know how to find out). Use next steps that haven't come up yet as chances to talk them through - e.g. a new Slack channel (invite you + support-hog), an upcoming renewal (how renewals work)
Throughout the week
- Demo practice with feedback (the more team members attending, the better)
- No stupid questions sessions
- Their feedback on the week at the end
Optional
- PostHog fundamentals - a walkthrough, depending on their familiarity with the product
- Working with support - how tickets flow, handling customer issues
- Quarterly goal brainstorm - useful when they join near the start of a quarter
- Billing mechanics - billing-limit grace periods and trust scores, giving credits, chasing overdue invoices, the spike detector
- Vitally mechanics - playbook indicators, renewal alerts
First month
From here it's much less structured - what to cover and when is your call. Use the 1:1s to go through anything you couldn't fit into the onboarding week, and be okay with repeating things that were covered - onboarding is a lot to take in.
- Ask for feedback on the onboarding week, especially on the content covered, so we can keep improving it
- Optional: a book walkthrough around week 3-4 - they walk you through their read of their book
- Optional: another practice demo, async