PostHog Handbook Library / Growth

6,450 words. Estimated reading time: 29 min.

Account allocation and handover

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. How coverage works
  2. CSMs are the base layer
  3. TAMs are an overlay
  4. A note on primary products
  5. Churn saves
  6. Competitive renewal
  7. Below $20k
  8. Account ownership in Customer Analytics

We have different roles who manage customers through their lifecycle. Customers typically sign up and start paying on their own, or land via a Technical Account Executive. Once an account hits $20k a year in usage-based spend, or is on a non-legacy Enterprise plan, a Customer Success Manager becomes the point of contact. A Technical Account Manager is added on top only where there's a qualified growth opportunity.

The customer journey and coverage model covers the phases an account moves through and who covers it at each one. This page covers the operational side: book planning, how TAMs get added and removed, and handover mechanics.

We're partway through this transition. Not every $20k+ account has a CSM yet, so some accounts are TAM-only for now. The rules below describe where we're headed. Where today works differently, we've noted it.

How coverage works

CSMs are the base layer

Every account at $20k+ in usage-based ARR, or on an Enterprise plan, gets a CSM. The threshold is what the customer actually consumes, not what they've contracted for: signing a prepaid or annual contract doesn't make an account a CSM account on its own. They own the relationship: onboarding depth, product health, engagement, retention. If nothing else is happening on an account, the CSM is who the customer knows.

TAMs are an overlay

A TAM joins an account only when there's a qualified expansion opportunity. That could be cross-sell, workload expansion, annual conversion, or a renewal worth actively working. How to judge whether an opportunity is real is covered in how to evaluate an account's revenue growth potential. Without a qualified opportunity, the account stays CSM-only.

In customer journey terms: a TAM is on an account while it's Expanding (or Implementing, when a deal closed with a qualified opp already attached). When the account reaches Steady state, the TAM comes off. The CSM was there the whole time, so nothing gets handed over.

When both are on an account, who does what is covered in CSM + TAM rules of engagement.

Where there's expansion potential but no TAM capacity yet, an account can sit CSM-only until a TAM can be added.

A note on primary products

We used to route accounts between TAM and CSM based on primary product adoption (Session Replay, Feature Flags, Error Tracking, tracked in Vitally as Paying for <Product Name>). That was the old model. Product count is still a decent rough signal, since an account paying for all three is often closer to saturated. Rather than using a strict product adoption method, we rely on the framing in how to evaluate an account's revenue growth potential to determine if there's actually expansion potential.

Churn saves

An at-risk account follows the risk mitigation and churn prevention playbook, same as always. Flag early with the Churn Risk tag, dig into the why, and run the save.

When both a TAM and a CSM are on the account, they co-own the save. Both are responsible, and neither should assume the other is handling it.

An account going at risk is also not a reason to add a TAM. Churn saves are generally not a legitimate TAM opportunity. Risk on a CSM-only account stays with the CSM unless a genuine expansion opportunity qualifies through the normal path.

Competitive renewal

Accounts owned only by a CSM can benefit from TAM overlay where we know a competitor is being evaluated ahead of renewal time. CSMs should be having renewal conversations early (3 months out from the renewal date) so that we can get a TAM involved and compete hard to win the renewal.

Trying to layer in a TAM to a competitive situation 30 days from a renewal isn't enough time to meaningfully impact the competitive evaluation.

Below $20k

Accounts below $20k don't get a CSM or TAM. The coverage map covers who (or what) handles them, including Growth TAM coverage and automation.

---

Account ownership in Customer Analytics

Customer Analytics is the source of truth for account ownership. Billing and Salesforce get owner changes from Customer Analytics. The sync goes in one direction only: Customer Analytics to billing to Salesforce. A change shows in Salesforce in 5-10 minutes.

Assigned is not the same as owned

You are considered assigned to the account in Customer Analytics when you are assigned to the correct field (account executive, csm, etc) and relevant tags are applied to the account.

Only accounts assigned to you count toward quota and commission.

Automated assignments are temporary

The Salesforce round robin and the lead-gateway assign accounts automatically (see task assignment logic). This assignment also shows in Customer Analytics, but it makes you a temporary owner only. If you disqualify the task or unassign yourself in Salesforce, Customer Analytics removes you from the account.

A human assignment in Customer Analytics stays. If a person assigned you in Customer Analytics and you unassign yourself in Salesforce, Customer Analytics makes you the owner again in approximately 5 minutes. To come off the account, unassign yourself in Customer Analytics and remove any relevant tags.

Do not change the owner in Salesforce. For an account that Customer Analytics controls, Customer Analytics writes over the Salesforce owner. An account without a PostHog organization is not in Customer Analytics, so you can manage it in Salesforce. If the account gets a PostHog organization later, the Salesforce owner becomes the owner in Customer Analytics.

Technical Account Managers

Technical Account Executives

Ownership history

The system.account_relationships table keeps the history of all account relationships. Each row is one person in one role on one account:

Use this table to find who owned an account at a given date.

---

TAM book balance

TAM book size is set by ARR under management. Account count follows from that. This mirrors how CSM books are balanced, by shape as well as total.

Beyond total size, a balanced book also needs:

If your book is outside these bounds at quarter start, work with your team lead to rebalance.

CSM book balance

CSM books target around $2.5M ARR and are balanced by account size as well as total ARR. Book targets are covered in how the Customer Success team works.

If your book is outside the current target at quarter start, work with your team lead to rebalance it.

Adding a TAM to an account

There is no CSM to TAM handoff anymore, because the CSM never leaves. Instead, when someone spots a growth opportunity on a CSM-covered account, they flag it for a TAM.

Anyone can flag: the CSM, a TAE, support, or automated alerts. The flag routes to a TAM in the right region for qualification.

To flag an account, add the tam overlay needed tag to it in Customer Analytics. TAM team leads check accounts with this tag and assign them to a TAM. Before you tag an account, use the growth potential framework to check that there is a real expansion opportunity. Add a Customer Analytics note that tells the TAM what you saw.

The receiving TAM qualifies the opportunity using the growth potential framework. If it holds up, they join the account as the overlay, open the opp, and intro themselves to the customer with the CSM's help. If it doesn't, they document why in Customer Analytics and the account stays CSM-only. A documented "no" is still useful. It stops the next person re-litigating the same idea in 3 months.

We track coverage in Customer Analytics with the CSM account relationship for the base layer and the TAM assigned for the TAM overlay. An account can have both.

When to request an overlay

Every $20k+ account has a CSM, so every customer has someone who knows them. On a CSM account, a TAM's job is selling expansion nobody on the customer's side is driving yet, like a new team, a new budget, or replacing a competitor. The TAM stays while there's more of that to work.

An overlay isn't extra coverage. If an account needs more hands, ask your team lead first, then bring in another CSM, an FDE, or exec support.

An account's size doesn't add a TAM on its own. Top 40 accounts and TAE handovers have their own rules.

Who's pushing decides who works it.

CSMs can and should push too. Request a TAM when the push needs more than you can give alongside your retention work, usually because it's stalled on a person or a budget rather than on the product. If it's unclear which side an opportunity sits on, flag it and let the TAM decide.

A quick litmus test to assess whether you can carry it yourself: can the people you already work with turn this on? If yes, keep going. If it has to go up the chain or across to another team, consider a TAM.

Flagging is part of the CSM role: a short note with the context. Whether it becomes an overlay is the TAM's call, and they own it.

Request a TAM overlay when a significant expansion opportunity is qualified, and we're the ones pushing it. It's a meaningful expansion rather than a small add-on, and your retention work on the account doesn't leave enough room to drive it. It's your call: if scoped extra help on expansion is in the customer's interest, request a TAM to push it over the finish line.

What counts as a qualified expansion opportunity? If all of the below are true:

When not to request an overlay

A competitive renewal is a separate call the CSM makes and doesn't need these criteria. However, it's a narrower engagement where the TAM is there to help win the renewal, not to work several expansion opportunities over the long term.

Before you tag the account

Do what you can first. Then have an answer for: what would a TAM take on that I can't? Show what you've done and where you've hit the limit of what you can take on alongside your retention work.

If all of the above checks out, then add the tam overlay needed tag in Customer Analytics and add a note with the context the TAM needs to qualify the opportunity.

TAM team leads answer a request within two weeks: a TAM assigned, a no with the reason, or when a TAM will have room. The assigned TAM then qualifies the opportunity using the growth potential framework, and either joins or documents in Customer Analytics why not.

Here's what your note in Customer Analytics could look like. This isn't a hard requirement - use it as a concrete way to sense check your request.

Title: TAM overlay request [YYYY-MM-DD]
Account: [account]

Why a TAM:
[ ] We're pushing this, not the customer: what we'd have to do (find budget, reach a new team, get an exec to care)

The opportunity (this is what the overlay is measured on):
- [product] — use case — who'd own it

If known:
Estimated new ARR, and how you got the number
Pain: what problem this solves for them
Economic buyer: who controls the budget
Champion: who's pushing for it internally
Competition: what they use today, incl. doing nothing

What I've tried: pitches, calls, links

The opportunity is qualified (check all):
[ ] Real use case and someone who'd own it
[ ] Someone on the customer's side is interested: pitched, current tool known, no explicit rejection from the customer
[ ] If stalled, the stall is on a person, not a missing feature
Next step: what the TAM should do first
Capacity

There's no fixed number of TAMs or overlay accounts per CSM. The work comes in bursts and varies by account: number of active users, how often they engage with us, and ARR all shape the load.

TAM books are planned with room for mid-quarter requests, so a qualified request shouldn't have to wait for the next quarter's allocation. If no TAM has room, the request can sit CSM-only until one does, and the team lead says when that will be. Keep working the opportunities in the meantime.

When the TAM joins, it might be useful to tell the customer what they're there for (for example, "joining to help explore error tracking with your platform team"), so it reads as an addition with a clear purpose, not a salesy fishing trip. See kicking off the overlay for guidance on kicking off an overlay.

What good looks like

This section covers overlays a CSM requests. Accounts where the TAM was there before the CSM aren't measured here.

The number of overlays isn't the goal. Each quarter, we look at two things:

  1. Is each overlay doing its job? Of the overlays started, how many turned the opportunity named in the request note into closed-won expansion. Only that opportunity counts, so the overlay is judged on what it set out to do.
  2. What happens without an overlay? Track the requests that were declined or had to wait, and what happened to their requested overlay opportunities. There won't be many, and TAMs will naturally take the strongest ones first, so the two possible results don't mean the same thing:

Either way, it doesn't prove anything on its own, but it's a useful signal for the quarterly reviews.

We count from Q1 2027, and only overlays a CSM requested. Accounts that already had a TAM before then are left out.

The request note is the record, since the tam overlay needed tag comes off once a TAM is assigned. At the end of each quarter, TAM and CSM team leads review the requests together: which were taken or declined and why, what closed, and what happened to the ones declined. TAM team leads then share it in public in Slack. We change these criteria based on what that shows.

---

Removing a TAM from an account

A TAM stays on an account through expansion until it's fully saturated, not just until the first opportunity closes. As long as there's a realistic next play to work (another cross-sell, a new team to land, an annual conversion), the TAM keeps the account and works it. They come off once expansion is genuinely exhausted. In journey terms, the account moves to Steady state and the overlay is removed. The CSM stays, so the customer keeps their point of contact throughout.

A TAM being willing to release an account is itself a decent signal the upside is gone. TAMs are paid on their book, so they don't give up real opportunities lightly. But treat it as a signal and sanity check it. Team leads should verify before agreeing. Team leads should post in public for visibility and approval before removing

Removing a TAM is usually a good outcome, and typically means a healthy, expanded customer. Inventing an opportunity to justify staying on is worse than coming off cleanly.

TAM removals generally happen at the end of the quarter. Accounts can be added to a book at any time, but plan removals for quarter end so books stay stable and handovers get done properly rather than rushed mid-quarter.

Keeping the context with the CSM

The CSM stays on, so nothing about the customer relationship changes from their side. But the TAM knows things the CSM doesn't, and that context has to land somewhere before they leave:

If the same account gets a qualified opportunity later, it goes back through the normal flag and qualification path. The handover note is what lets the next TAM (maybe you) pick it up fast.

What is NOT a valid reason to come off an account

Low engagement or an account being difficult is not a reason to come off. That's the job. Specifically:

If an account is struggling on these dimensions, that's a signal to invest more. The saturation checks require evidence that the opportunity is gone; an account being hard to work is not the same as the opportunity being gone.

---

Doing the allocation

Each quarter, TAM and CSM team leads review coverage and rebalance books. TAM allocation requires Ben's approval; CSM allocation requires team lead approval. Accounts can still be added during the quarter when a handover or qualified growth opportunity requires it.

TAM allocation

A TAM is added on top of CSM coverage where an opportunity qualifies. At the start of each quarter, TAM team leads, with Ben's approval, review:

  1. Accounts still tagged tam overlay needed that are waiting for a TAM with room. New requests don't wait for this review: they get an answer within two weeks (see before you tag the account)
  2. TAM books outside the $1.5M-$2M ARR band to identify which accounts to rebalance
  3. Accounts where the TAM should be removed because expansion is exhausted

Once the decision is settled, the team lead updates the tags and assigns the specific TAM in Customer Analytics. When the TAM is assigned, remove the tam overlay needed tag.

To request CSM coverage, add:

CSM allocation

Every $20k+ account should have a CSM. At the start of each quarter, CSM team leads will review:

  1. The Uncovered customer backlog canvas to find accounts without a CSM
  2. Accounts tagged csm overlay needed or csm handover needed that need a CSM assigned
  3. CSM books outside the current target to identify which accounts should be rebalanced

For accounts with no previous owner, use PostHog GeoIP data to identify the account's primary region. The relevant team lead then assigns the CSM in Customer Analytics. Once the CSM is assigned, a workflow removes the tags automatically.

Once a day an automation runs which adds a region tag to the account to assist in routing to the correct team.

To request TAM coverage for an account with a qualified growth opportunity, add the tam overlay needed tag in Customer Analytics.

Mid-quarter TAM changes

Account removals should only happen at the end of the quarter so that quota can be calculated correctly. However, accounts can be added to your book at any time if you're confident there's growth potential.

If you're assigned an account with a previous owner, work with them on a proper handover. If the customer isn't in a healthy state (usage and engagement-wise), push back and ask the previous owner to get them to a good state first.

New accounts with no previous owner come with a 3 month grace period – if they churn in that initial period, they won't count against your quota. Don't ask for the TAM field to be set until you're confident there's growth potential.

---

Top 40 account management

Our highest-spend customers (~Top 40 by ARR) get special consideration. Adding or removing a TAM on a Top 40 account is decided directly by Ben and team leads rather than the standard Team Lead process. The bar for change is higher here. Sometimes a TAM stays on a saturated account because the relationship is strong and there's long-term strategic value.

---

Handing over customers

To help the new owner hit the ground running, we should make sure the customer is in a good state and a warm introduction happens.

If the account is at $20k+ in usage-based ARR or on a non-legacy Enterprise plan, the TAE handoff always goes to a CSM. Signing a prepaid or annual contract doesn't trigger the handoff by itself: the account needs to be onboarded and consuming at the $20k threshold. The handover typically happens around 3 months after the initial credit purchase, or 12 months after the initial credit pre-purchase if the TAE retains the account against a specific opportunity (see the journey page ownership rules). If a qualified expansion opportunity exists at handover, a TAM is added at the same time. If usage is still under the threshold at the 3 month mark, the TAE hands the renewal opportunity over to the relevant CSM team lead to work the renewal and monitor the account. The team lead is responsible for ensuring the renewal is managed by a CSM as per the renewal handbook guidelines. The team lead is not responsible for support or proactive adoption work. Once the account reaches $20k+ in usage-base ARR, it will be queued for a CSM's book.

TAM add and removal aren't handoffs, since the CSM stays throughout. See Adding a TAM and Removing a TAM above.

For accounts who will be landing at $100k+ a year or have high expansion potential after the initial deal, we should involve a TAM early in the process to ensure a smooth transition. See the section further down this page on how this works.

For handover to take place there should be an Account Plan (saved as a note on the account in Customer Analytics) and the customer should have been onboarded properly to the products they are currently paying for.

All open invoices should also have been paid before handing over. It makes sense to use existing relationships to chase payments, rather than the new owner's first action needing to be chasing payments/suspending access for non-payment.

For TAE accounts being handed over to a CSM, add the csm handover needed tag in PostHog Customer Analytics and flag it with the relevant CSM team lead. There's no need to wait for the end of the quarter. The team lead will review the plan and current state of the customer, then assign a new owner with Simon's approval.

Account Plan

Every account being handed over should have an up-to-date Account Plan saved as a note in Customer Analytics. The existing owner should ensure that this is current and schedule a handover call to walk through it with the new owner. Feel free to push back and ask for it as the new owner if this doesn't happen! Ask your team lead or Simon for help with this if you're not getting the information you need from the previous owner.

Product Onboarding

Before handing over a customer, the existing owner needs to ensure that the customer is onboarded properly to the products they are paying for. We should first ensure that they are only paying for what they need to as detailed in the health checks section of the handbook and then ensure the following steps have been completed, depending on the products they are paying for:

This is an initial pass at what good onboarding looks like for each product. We will refine this checklist as we learn what works.

General principles
Product analytics
Session replay
Feature flags
Data warehouse
Error Tracking

---

Account handover checklist

Every account handover should include a 15-30 minute call between the outgoing and incoming owner. This checklist helps you prep for that call and make sure nothing falls through the cracks.

When to use this

Before the handover call

The incoming TAM should prepare by reviewing the following in Customer Analytics and SFDC before the call, so the handover conversation can focus on context that isn't in the data.

Self-serve research (do this first)

Prepare questions based on gaps in the data. The handover call should focus on things you can't learn from Customer Analytics.

Handover call agenda

This isn't an exhaustive list and not every item needs to be covered every time. Use your judgment based on what's relevant to the account.

1. Relationships & people

This is the most valuable part of the handover – relationship context doesn't live in any tool.

2. Commercial context
3. Technical & product state
4. Risks & opportunities

After the handover call

Immediate actions (within 1 week)

Tips for a good handover

Unassign yourself in Customer Analytics

Once the handover is complete, the outgoing owner should unassign themselves from the account in Customer Analytics. This keeps Customer Analytics accurate about who is actually on the account.

---

Receiving an account as a CSM

CSMs receive every $20k+ account, whether from a TAE at close or when a TAM comes off. Accounts arriving from a TAM should generally be in a steady state: using the products they need, engaged, no major unresolved issues. It's worth looking beyond the surface to make sure that's actually the case. These aren't a rigid checklist. They're things to dig into that can surface problems which are otherwise easy to miss.

Billing and commercial

Product adoption

Engagement

Account documentation

Lower priority

Worth being aware of, but less likely to be blockers:

Pushing back

If you're seeing multiple flags — declining usage, no engagement, concentrated users, missing account plan — push back. An account with several of these signals isn't in steady state and probably needs more work from the previous owner before it's ready for CSM. Talk to Dana if you're unsure whether to accept an account.

---

High potential customers

For TAE-led customers who will be landing at $100k+ a year or have high expansion potential into new product areas, we should introduce a TAM earlier on than normal.

The prime time for this is when the technical win is confirmed - the TAM should be introduced to the customer by the TAE in an evaluation or POC wrap-up call when we know that the customer has selected PostHog.

The introduction is purely for relationship building and continuity purposes so that the TAM can hit the ground running with the customer after the initial credit pre-purchase is signed. It's still on the TAE to work with the customer on the deal, and as such only the TAE will be recognized on the initial deal for commission purposes. After the initial deal is closed won the TAM will take over the account in their book of business.

The TAE and TAM should use their overlapping time to work with the customer on a documented onboarding plan per the above guidance.

Canonical URL: https://posthog.com/handbook/growth/sales/account-allocation

GitHub source: contents/handbook/growth/sales/account-allocation.md

Content hash: e02cafd93a490d0e

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