-
Notifications
You must be signed in to change notification settings - Fork 794
Create CSM and TAM roles of engagement document #16533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
31842d4
Create CSM and TAM roles of engagement document
tjcran 6af2423
Revise dual coverage roles for CSMs and TAMs
tjcran 349a888
Update contents/handbook/growth/sales/csm-tam-overlay-coverage
tjcran 7c23531
Update contents/handbook/growth/sales/csm-tam-overlay-coverage
tjcran eeac67a
Update contents/handbook/growth/sales/csm-tam-overlay-coverage
tjcran b4e3364
Update contents/handbook/growth/sales/csm-tam-overlay-coverage
tjcran 7a5c0c5
Update contents/handbook/growth/sales/csm-tam-overlay-coverage
tjcran a4a3bd1
Update renewal logistics and credit negotiation details
tjcran fc243db
Add CSM and TAM dual coverage link to navigation
tjcran 69d66ef
Merge branch 'master' into tam-csm-overlay-handbook
tjcran File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,60 @@ | ||
| --- | ||
| title: 'CSM + TAM rules of engagement' | ||
| sidebar: Handbook | ||
| showTitle: true | ||
| --- | ||
|
|
||
| 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. | ||
|
|
||
| Both roles have a real relationship with the customer. Both are in the Slack channel. Both know what's happening on the account. The difference is _focus_, not ownership. | ||
|
|
||
| The customer should never have to figure out who to contact. They reach out to either person, and PostHog sorts it out internally. | ||
|
|
||
| ## What each role focuses on | ||
|
|
||
| ### CSM | ||
|
|
||
| - Operational health and [health score](/handbook/cs-and-onboarding/health-tracking) monitoring | ||
| - Support escalation and follow-through | ||
| - Credit usage optimization | ||
| - Onboarding, training, getting new users set up | ||
| - Renewal process end-to-end | ||
| - Day-to-day responsiveness | ||
| - Health of the technical implementation | ||
| - Surface cross-sell signals from product usage and conversations to TAM | ||
|
|
||
| ### TAM | ||
|
|
||
| - Cross-sell strategy and execution | ||
| - Credit discount negotiation and deal structuring for new credit purchases, invoicing | ||
| - Use case discovery, mapping products to problems | ||
| - Multi-threading into new teams and stakeholders | ||
| - Account planning (quarterly in Vitally) | ||
| - Stakeholder management | ||
|
|
||
| ### Both | ||
|
|
||
| - General customer questions (whoever sees it first) | ||
| - Implementation reviews | ||
| - Retention. TAMs are not off the hook here. Understanding health and usage is a prerequisite for cross-selling, not work that gets delegated. | ||
|
|
||
| ## What good looks like | ||
|
|
||
| - Customer reaches out to either person and gets a fast, informed response. They never think about who to contact. | ||
| - Both go deeper on their focus area than either could alone | ||
| - Customer knows both people, trusts both, feels like they have a team | ||
| - Neither person is surprised by what the other communicated | ||
| - Both are visible in Slack, not just when they need something | ||
| - Both are aligned on the current state of the customer, risks, opportunities and what their counterpart is working on. | ||
| - TAM and CSM alignment on the account happens in public, not DMs | ||
|
|
||
|
tjcran marked this conversation as resolved.
|
||
| ## What bad looks like | ||
|
|
||
| - Customer gets told "that's not my area, let me get [other person]" | ||
| - Customer only hears from the TAM when PostHog wants to sell something | ||
| - Customer gets asked "how are things going?" by both people in the same week | ||
| - CSM discusses pricing without knowing the TAM had a deal in play | ||
| - TAM sends a cross-sell email without knowing the customer filed 3 support tickets yesterday | ||
| - Neither person responds because each assumed the other would | ||
| - TAM checks out on health because "the CSM handles that now" | ||
| - Customer has to explain the same thing twice | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.