PostHog Handbook Library / Customer Success

2,703 words. Estimated reading time: 13 min.

How we work

Auto TL;DR

At a Glance

This long page covers these main areas. The list is generated from the article headings, so it updates with every handbook rebuild.

  1. Main metrics for each role
  2. Book of business
  3. Weekly Customer Success standup
  4. How CSM bonus works
  5. How NRR is calculated
  6. Which accounts count toward your NRR
  7. Adding accounts
  8. Removing accounts

This page covers more of the operational detail of how our team generally works - for a broader overview of roles and responsibilities, visit the customer success team page.

Main metrics for each role

Book of business

Each CSM is assigned customer accounts accumulating to ~$2.5m ARR to work with. We use the account relationship history in PostHog Customer Analytics to track this against goals. Don't assign yourself as the CSM on an account - allocation is up to the CSM Team Leads and Simon.

Weekly Customer Success standup

In addition to the weekly sprint planning meeting on a Monday, we do an account review standup on Wednesday to discuss any at-risk accounts.

The objective of the meeting is to hold each other to account, provide direct feedback, and also support each other. It is a great place to ask for help from the team with thorny problems - you should not let your teammates fail.

How CSM bonus works

How NRR is calculated

Which accounts count toward your NRR

Your book is the set of accounts where you're the CSM in PostHog Customer Analytics. We use the account relationship history there, so changes can be made at any time and we can still see who held what, and when.

An account counts toward your NRR for a quarter if all of these are true:

  1. You're the assigned CSM on the second-to-last day of the quarter.
  2. You've held it for at least one month of that quarter.
  3. It isn't in a grace period or an approved exception (see below).
  4. It isn't excluded (see "Excluded accounts" below).
Adding accounts
Removing accounts
Grace period: accounts nobody has looked after
Taking over an account from someone else
Exception: accounts at risk of churn
Excluded accounts

These never count toward CSM NRR:

Working with engineering teams

We hire Technical CSMs. This means you are responsible for dealing with the vast majority of product queries from your customers. However, we still work closely with engineering teams!

Product requests from large customers

Sometimes an existing or potential customer may ask us to fix an issue or build new features. These can vary hugely in size and complexity. A few things to bear in mind:

Inviting a product engineer into a customer conversation

Separately from product requests, there are moments where it's worth seeing whether a product engineer wants to join a customer conversation - as much for what _they_ get out of it as the customer. Always pitch this as an open invitation ("this might be an interesting call, would anyone like to join?"), never as "we need an engineer on this call." Situations where it's usually worth asking:

Why not just always invite one?

CSMs here are technical enough to solve real problems without asking our engineers. You're the expert! Bringing an engineer in is the exception, earned by genuine two-way value (one of the cases above), not a default or a comfort blanket. If you can't say what the engineer would get out of it, that's your answer.

Finally, if you are bringing engineers onto a call, brief them first - what is the call about, who will be there. And then afterwards, summarize what you talked about. This goes a long way to ensuring sales <\> engineering happiness.

Complicated technical questions

You will run into questions that you don't know the answer to from time to time - this is ok! Some principles here:

Working with customers in Slack

Most of our customers use Slack, and it's a great way for us to be responsive to them. Everyone has the permission in Slack to create a Connect channel with a customer, and you should do this as early as possible in your relationship with them.

When you've created the channel you should also add SupportHog, our own tool that syncs Slack conversations with PostHog so that our Support and Engineering teams can work on customer issues in a familiar context. Follow the shared Slack channel setup steps to invite SupportHog and configure the channel.

Once it's in the channel, you can add the :ticket: emoji to a Slack thread — or mention @SupportHog — to create a new ticket in PostHog Support. Customers can also do this.

It's your job to ensure your customer issues are resolved, make sure you follow up with Support and Engineering if you feel like the issue isn't getting the right level of attention.

Extended Time Off

During extended periods away from work (generally more than two weeks) it's important that we maintain customer relationships - we don't want to leave emails or Slack messages unanswered. For planned time off, it's recommended that you make a list of your accounts, then add an appropriate colleague to the Slack channel. Try and balance the workload, but our policy of working transparently (eg. ensuring conversations on Slack don't happen in DMs) makes it easier for others to dip in seamlessly.

The expectation is that this temporary CSM will ensure your customers aren't completely ignored. This may mean answering questions themselves or opening support tickets on a customer's behalf, but not attend routine meetings (eg. monthly check-ins) or pro-active work. For standing meetings in your absence customers should be notified that the meeting is cancelled but any questions can be asked through normal channels.

For longer periods away, your team lead may look to reassign some or all of your accounts.

Tools we use

Gmail: We use Gmail for email. Pick whichever client works best for you – some of the team prefer Superhuman or Spark, and others stick with the default Gmail web interface. To set up your email signature, copy the signature from someone else on the team (like Simon) and fill in your own details.

Calendly: We use Calendly for scheduling meetings. In order to schedule a meeting between a customer and multiple members on the PostHog team, click on "Event types" in the left hand navigation, then click "+ New Event Type" button in the top right, and select "Group" from the dropdown. This will allow you to create a group meeting and add multiple team members to the event and create a link you can share with the customer.

Zoom: We use Zoom for all customer and sales calls. If you have Calendly properly integrated, calls that are booked through the tool will default to Zoom. You can find backgrounds to use for the calls here: This is fine \(and other awesome PostHog wallpapers\). You can also add a PostHog video to your Zoom waiting room for customers who join early.

Gong: We use Gong to record calls. Once it's set up, Gong automatically joins your Zoom calls and saves the recording to a shared library the whole team can search and review. See sales & CS tools for how to connect Gong to your Zoom calls. BuildBetter is still where we store historical demos and meetings, and some teams continue to use it.

Granola: We use Granola for transcripts and AI notes. It runs on your laptop and transcribes whatever call you're in, so you get a transcript without adding another bot to the meeting.

Canonical URL: https://posthog.com/handbook/customer-success/how-we-work

GitHub source: contents/handbook/customer-success/how-we-work.md

Content hash: 73b20fbff03fbaf1

Static reader notes
  • MDX_COMPONENT_STATIC_ADAPTER: Adapted interactive MDX components for static reading: PrivateLink.