PostHog Handbook Library / Growth

3,914 words. Estimated reading time: 18 min.

CSM + TAM rules of engagement

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. What each role focuses on for overlay accounts
  2. tl;dr
  3. CSM
  4. TAM
  5. Both
  6. Where to expect overlap
  7. Day to day questions
  8. Renewals

Some accounts have both a CSM and a TAM. The point is depth: two people sharing the load so each can focus on what they're best at, and the customer gets a better experience than one person stretched across everything.

Account allocation covers why: the CSM is the base layer on every $20k+ account, and a TAM is an overlay while there's an expansion opportunity worth working. This page is about what the two of you do once you're both on.

Both of you are expected to have a relationship with the customer, be in the Slack channel and know what's going on. The difference is _focus_, not ownership. The customer shouldn't have to work out who to contact: they message either of you, and we sort it out internally.

The structure outlined on this page should be treated as a guideline & should be tweaked as needed for different accounts:

What each role focuses on for overlay accounts

tl;dr

CSM

TAM

Both

<summary>What good looks like</summary>

<summary>What bad looks like</summary>

Where to expect overlap

There will be overlap and you'll step on each other's toes - that's by design. The goal isn't a perfect division of work between the two roles, it's to play to your strengths and hit the goals set for the account. Where overlap shows up most:

Day-to-day questions

Whoever sees it first answers. If one of you has replied and the other has something better to add, chime in anyway. Two helpful answers beats one person holding back because someone got there first.

Renewals

Renewals sit with both of you for overlay accounts. The TAM leads the commercial conversation: stakeholder approval, quotes, accounting for growth and upsells, order forms. The CSM owns the value case behind it: what the customer used, what they got out of it, and where usage is heading.

A competitor showing up before a renewal on a CSM-only account is one of the best reasons to add a TAM (Competitive renewal has more details). Between both of you, coordinating the timing is important: start the renewal conversation 3 months out, since adding a TAM 30 days before is too late to shift a competitive evaluation.

Account health

The CSM owns reading the health score and keeping it current, but it isn't the CSM's problem alone. Both of you watching it might feel like duplicated work, but you're asking different questions despite looking at the same numbers.

The score on its own also won't tell you enough, as it's only designed to answer whether an account is at risk. Product engagement makes up most of it which usually confirms something that already happened rather than warning you. Total product count, a better headroom signal for a TAM, doesn't count much towards it. And it won't show you a single team going quiet, which is most likely on strategic accounts where several teams use PostHog for different things.

A few tips to help you approach this better:

Cost efficiency vs. growth

The CSM's job includes helping a customer spend less. The TAM's job includes growing the account. Some situations might make you both pull in opposite directions.

At the end, efficiency should win, because a customer paying for waste has a reason to leave, and a right-sized customer expands better than a resentful one. More importantly, neither of you wants the customer to find out about this first.

Here's how you should consider handling it:

When you disagree

Usually the lists above settle it: whoever's focus area it sits in makes the call. On shared ground, default to whoever is closest to the live conversation, and have them post what they decided and why.

Two things worth keeping to:

If you're stuck, bring your team leads in early. Both of you care about the customer and want to see them succeed, so it's rarely a disagreement about where you're headed.

Kicking off the overlay

When a TAM joins an account, or a CSM gets added to one that already has a TAM, use this list as a guide on how to kick things off strongly. Especially for larger/strategic accounts, try to adhere to it as much as possible, but the first three need to be followed regardless of account size:

The internal channel replaces DMs about the account, and you're both responsible for making sure the other has enough context to be useful. Working in the open there also ensures that it's easy for anyone to look up historical context around decisions in the future.

Get current on the account

If you're new and your counterpart has the relationship

Gather as much context as you can before jumping in with questions. Share what you find, and let the gaps guide what you ask.

As a CSM, treat it like your standard deep dive when inheriting an account, pointed at where you can add value fastest:

As a TAM, come at it through use-case selling. Start from the job they already use PostHog for, then work out what's missing yet adjacent to what they're using:

Cross-reference what you find against recent Slack threads and Customer Analytics notes. You want a current read on the account that your counterpart can sense-check.

Ideally, you come up with a recommendation for a first action item to share with the customer. Then post in the internal channel with your questions, ideas, and that action item (example).

Your goal: create value fast while learning as much as you can about your customers' business & usage, so you can start building rapport immediately with them.

If you're the one with the relationship

Share whatever's top of mind in the internal channel as a starting point. If there's context a quick call would convey better than the paper trail, do that.

Your counterpart is already gathering context from what's written, so don't be exhaustive. Focus on:

Add your counterpart to the external Slack channel (#posthog-[customer_name]). Use your judgment on when to introduce them to the wider customer team, and say what you're thinking so you stay aligned on timing.

When you do introduce them, frame it positively: the customer is growing and we want to support them better by having more hands on deck, not that they're being handed off (here’s a solid example).

Run the intro past your counterpart first. They'll often spot something that makes it warmer: history with a similar customer, a specialty that lines up with what this one struggles with, or calling out their experience for clout. A customer who's excited to meet someone starts better than one politely acknowledging a new name.

If you know of low-hanging fruit that would land well, hand it to your counterpart and let them deliver it. It's a cheap way for them to start on a good note, and it's worth more coming from the person who needs to build the relationship.

Your goal: share as much helpful and relevant context as possible with your counterpart, focusing on the things that aren't easily figured out by scanning the customers' site, usage or existing notes.

Staying in sync

To make sure you're both on the same page and to ensure continuity if someone new takes over the account, there a few things worth maintaining:

| What | Where | Why there | | --- | --- | --- | | Who's who at the customer | Org map artifact linked in the channel | One place to look, kept current | | Open follow-ups, action items & assignees | Task list artifact linked in the channel | The current list at a glance | | Per-call agenda | Thread in the internal channel | Tied to a date, and notifies you both | | Any info that anyone outside of you needs about this account | Account plan note in Customer Analytics | Easily searchable, and lives outside the channel |

Before a call

If you're both joining, start a thread in the internal channel a few days ahead and draft the agenda together: who covers what, who leads which section, and roughly how long each part gets. Sorting that out beforehand will make for a much more impactful call.

Make sure you both get at least some time to speak, even if one of you doesn't have an explicit agenda item. Two voices helps break the monotony if you're both on the call.

Use this same thread to also keep in touch while on a call. While Slack can be distracting on a call, having the thread opened up in a new window can help you both coordinate while on the call.

After a call

Update both artifacts: add anyone new to the org map, and add a dated section to the task list with the assigned follow-ups. Same after an async exchange that moved something along.

A post-call debrief huddle or thread in the channel is worth it too: what happened, what's next, who you think should pick up what and feedback on the call. Proposing the split is easier to react to than a list of notes your counterpart has to divide up themselves.

Tracking people and tasks

Either of you should be able to answer who someone is, or whether something got done, without asking the other. So each internal channel wants two links that are easy to find, pinned or bookmarked:

Use whatever you'll both keep current: a Slack canvas, a Customer Analytics note, a Google Doc. The examples below use canvases because they sit where the conversation already happens. On a smaller account, one pinned message often covers both.

<summary>Example: an org map as a canvas</summary>

A canvas called [customer_name] - People, with a table in it:

| Name | Title | Who has the relationship | | --- | --- | --- | | Ana | VP Engineering, exec sponsor | TAM | | Dev | Staff engineer, owns the implementation | CSM | | Mo | PM, heaviest Experiments user | CSM | | Sam | Data lead, team we haven't landed yet | TAM |

You're not mapping the whole org, just keeping something easy to refer back to. Add people as you meet them.

<summary>Example: a running task list as a canvas</summary>

A canvas called [customer_name] - Tasks. After every conversation, add a dated section at the top with a one-line heading for what happened, then a checklist of follow-ups with the CSM or TAM against each:

Sep 12, 2026 - Call with champion re: renewal prep and Experiments issues

Aug 28, 2026 - Implementation review with the platform team

Older sections stay put. That's what makes the list useful three months later, when you're trying to remember if anyone ever answered a specific question.

Recording who has the relationship is very useful in the org map because it means they should flag if that contact goes abnormally quiet.

On tasks, keep the newest ones at the top and make sure someone's assigned to each one. If something has sat unchecked for a while, have a chat in the internal channel with your counterpart on whether it's still important

Neither doc is searchable the way Customer Analytics is, so roll the developments that matter into the account plan note as you go.

Sharing DMs

DMs with customer contacts happen, and that's fine. What you want to avoid is the account picture living only in one person's DMs.

Post a short summary in the internal channel whenever a DM changes the plan, surfaces a risk, or commits PostHog to something. Your counterpart needs to know what shifted or if there was a win in the DM, especially if there are joint follow-ups coming out of it.

Who joins which call

On strategic accounts, default to both of you on most calls. We don't run many in the first place, and the context you each pick up will be very helpful even if you don't have anything to discuss.

On smaller growth accounts, both of you joining every call is likely overkill. One of you running a routine check-in is fine, as long as the follow-up lands in the internal channel.

Either way, the calls worth both of you being on are the ones where the relationship or the commercial picture is changing: renewals, business reviews, potential expansion conversations, competitors surfacing or anything going sideways.

Sync cadence

Meet at least once a month, or more often if you need to. Either way, what comes out of it should land back in the internal channel, since most of it feeds account planning.

How you create value together

Two people on an account buys depth and breadth: relationship-building, use case optimization, implementation audits, and much more. To get that, have good communication on who's doing what.

A good starting point is to find the gaps in coverage and the open threads, then prioritize. Here are some questions worth working through together:

Prioritize together, then explicitly assign each other paths to run with. Think of it as delegating what you'd otherwise do yourself if you were alone on the account. Give each other the work streams where you're each most likely to succeed, and if a TAM already has a warm relationship with the champion for an expansion, they should keep it rather than hand it off mid-flight.

<summary>An example of both of you creating value in separate product areas at the same time, while playing to your unique strengths as a TAM and CSM</summary>

None of this is a hard rule (CSMs on instrumentation, TAMs on expansion). You'll overlap and switch at times, and be more siloed at others. Bigger accounts need the split made explicit because there's more in flight while on a smaller one, it's often obvious enough to leave alone.

Here's a good way to test this: ask yourself whether you can say what your counterpart is working on right now? If not, ask in the internal channel more often. What you're avoiding is duplicative or irrelevant work, so honor each other's time by communicating clearly and often.

Guidelines for stepping on toes

How can you both be the driver if there are two people in the same car? It's okay to step on toes as long as you don't stomp each others' feet or trip over each other. A few habits that protect your autonomy without blocking each other:

  1. Post often in the internal channel: what you're thinking about, who you have a call scheduled with, open questions, an opportunity you're chasing down... anything. Write as generously and freely as you would on a private scratchpad - it's the closest thing we have to a shared brain.
  2. Document as much as you can in Customer Analytics, the artifacts and the internal channel: details, developments, learnings and plans from your internal threads should end up as a note on the account in Customer Analytics.
  3. Use each other to sense check: consider a monthly call where you catch up on your shared accounts. Talking through what you're thinking often reveals parallel work streams.
  4. Debrief after customer calls: this is where you'll feel the superpowers that come with a CSM + TAM overlay - give each other feedback, get clear on next steps, and review how the call went.
  5. Tag team follow ups: one of you plugs something in the customer channel; the other stands by to chime in with a follow-up to get a response. Works like a charm for unresponsive customers.

Canonical URL: https://posthog.com/handbook/growth/sales/csm-tam-overlay-coverage

GitHub source: contents/handbook/growth/sales/csm-tam-overlay-coverage.md

Content hash: 86da17a5af6a8e5e

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