PostHog Handbook Library / Growth

1,361 words. Estimated reading time: 7 min.

Customer journey and coverage model

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. The phases
  2. Presales
  3. Postsales
  4. At risk is a status, not a phase
  5. Champions and coaches
  6. Coverage map
  7. Ownership rules

This is a rough articulation of the phases a paid and "sales-sized" customer moves through PostHog, from first signup to steady state, and which role covers them at each phase. The purpose of mapping this out is creating a shared understanding so we can better standardize how we think of and approach accounts, as well as account allocation. When you know a customer's phase and ARR band, you know who should be working with the account. For the operational process (book planning, allocation cadence, handover mechanics), see Account allocation and handover, which holds the allocation rules.

The phases

Presales

| Phase | Definition | | -------------- | ------------------------------------------------------------------------ | | Exploring | Signed up, sending events, free tier or trivial spend. No buying signal. | | Evaluating | Actively comparing us against alternatives or against not buying. | | Proving | Running a structured POC with success criteria, ours or theirs. | | Buying | Commercial negotiation. Quote out, annual terms in discussion. |

In a PLG motion most customers move through the presales phases invisibly and without contact. Our process and system should be able to capture and identify the right accounts to work with at the right time based on signals and phases. Exploring, Evaluating, and Proving are inferred from product signals unless sales is engaged. The presales phases only need to be as granular as the routing decision they drive, which is binary: automation, or a human from new biz.

Postsales

| Phase | Definition | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Implementing | Delivering a closed deal. Posthog instrumentation, onboarding and success plan, stakeholder map. | | Ramping | Usage growing, account below full TAM threshold or still climbing toward committed volume or otherwise just not at fully implemented production volume. Generally takes longer for larger or more traditional orgs. | | Expanding | A clear expansion, cross-sell, or save opportunity exists and is being worked. | | Steady state | Growth and expansion exhausted. Core products adopted, saturated across the organization, healthy engagement, no viable expansion play. |

Edge case worth noting: a pure self-serve account that crosses $20k ARR with no sales involvement skips Implementing entirely. They enter at whatever their adoption or usage indicates, usually Ramping or Expanding. This is important, though, because an account that's been self-serve and steady state in prod for 2 years doesn't need the same tactic and approach as a sales-driven "implementation" account, and our process shouldn't treat them the same.

At risk is a status, not a phase

An account in any postsales phase can be at risk. At risk does not change the phase or reassign the account. When both a TAM and a CSM are on the account, they co-own the churn save. Otherwise the current owner runs it. Going at risk is not a reason to add a TAM.

Champions and coaches

The difference between a champion and a coach is one thing. Can they make change happen inside their org, or not.

A champion has the authority to influence or make decisions that affect PostHog. That can be as small as getting engineering time for an instrumentation change, or as large as getting a contract approved, blocking a churn, or deciding that a team adopts PostHog or a specific product. Whether they are a user, a manager, or an executive, the test is the same. When they say something should happen, it happens. A champion is not always the person who signs. When the decision sits with someone else, they have the standing to move that person.

A coach likes PostHog, talks to you, makes introductions, and tells you what is going on inside the org, but is not in a position to make any of those changes themselves. They can tell you that a code change is needed, who owns the renewal, or that a team is looking at a competitor. They may even be a power user, but ultimately they do not have the influence or authority to control whether a team adopts a product or to sway key decisions.

Enthusiasm is not the dividing line. A coach can love PostHog more than anyone else in the building and still not be a champion.

This matters most when an account is expanding quickly or at risk of churn. In both cases you need to know that the person you are talking to can actually move the needle, not just relay the message. You need a champion for anything that requires the customer to act, so if an account only has coaches, the next step is always to use them to reach someone with authority, and build that person into a champion. And when you record a contact, record which one they are, with what they can and cannot decide, so the next person on the account knows who can actually move things.

Coverage map

Who covers the account at each phase. Phases run top to bottom in the order a customer moves through them; roles run across.

โœ… active coverage  ยท  ๐ŸŸก conditional (see notes)  ยท  blank = not involved

| Phase | BDR | TAE | CSM | TAM | Growth TAM | FDE | Onboarding | | ---------------- | :-: | :-: | :-: | :-: | :--------: | :-: | :--------: | | Exploring | โœ… | | | | | | ๐ŸŸก | | Evaluating | ๐ŸŸก | โœ… | | | | | ๐ŸŸก | | Proving | | โœ… | | | | ๐ŸŸก | ๐ŸŸก | | Buying | | โœ… | ๐ŸŸก | | | | ๐ŸŸก | | Implementing | | | โœ… | ๐ŸŸก | ๐ŸŸก | ๐ŸŸก | ๐ŸŸก | | Ramping | | | โœ… | โœ… | โœ… | ๐ŸŸก | ๐ŸŸก | | Expanding | | | โœ… | โœ… | โœ… | ๐ŸŸก | | | Steady state | | | โœ… | | | ๐ŸŸก | |

Notes:

Ownership rules

CSM is the base layer, unconditionally. Every account above $20k in usage-based ARR, or on a non-legacy Enterprise plan, has a CSM from day one post-sale. The CSM never leaves. Steady state is not a handoff event, it just means the TAM/TAE overlay has been removed.

TAM coverage is the exception, not the default. A TAM is added to an account only when a clear expansion or cross-sell opportunity justifies it, and released when the opportunity is exhausted.

TAE handoff goes to CSM, always (above threshold). Optionally, the TAE can retain the account to expand it when there is a specific opportunity that justifies the retention across a 12 month window.

BDRs feed the funnel, they don't own the deal. BDRs own top-of-funnel sourcing at Exploring and hand off to the TAE at Evaluating. Coverage ends at the handoff; the TAE owns the account from there.

Canonical URL: https://posthog.com/handbook/growth/sales/customer-journey

GitHub source: contents/handbook/growth/sales/customer-journey.md

Content hash: 1ec8540edd98d9ed