gtmpodStart

CS to AM: expansion trigger handoff that doesn't kill the relationship

Customer is healthy. CSM sees expansion signal — new use case in adjacent team, hiring spree, exec change. Handoff to AM. If done wrong, customer feels sold-to and the renewal sours. Here's how to do it with the buyer noticing zero seams.

Last reviewed: 2026-05-23

The problem

In B2B SaaS with a separated CSM (retention) and AM (expansion) function, the handoff is when things get awkward.

Customer's renewal is in 4 months. CSM is doing QBR prep. Customer mentions: "yeah, our data team is starting to use the product too, we might need more seats."

CSM Slacks the AM: "expansion opp at $account."

What happens next, badly: - AM emails the buyer directly: "I heard from your CSM you're expanding. Let's set up a call." - Buyer thinks: "wait, my CSM is sales-tagging me?" - Trust shrinks. - AM pushes for upsell quote. Buyer pushes back. Renewal gets harder.

The hidden cost: customer felt watched. CSM relationship — the trust anchor — got monetized. Even if the expansion closes, future NRR suffers.

The fix: a 3-step handoff that keeps CSM as the relationship owner

The principle: customer's primary relationship stays with CSM. AM enters as a specialist, not a replacement.

Step 1: CSM logs the signal, AI scores it

CSM logs the signal in Vitally / Gainsight with structured fields: - Type: new use case, headcount expansion, exec change, etc. - Strength: weak / medium / strong - Customer-stated or inferred - Customer-aware or quiet signal

AI then scores expansion likelihood + ideal motion: - High likelihood + customer-stated → AM-led conversation, CSM intro - High likelihood + inferred → CSM probes more before AM brought in - Medium likelihood + customer-aware → CSM-led nurture, AM in shadow - Weak signal → CSM continues, no AM engagement yet

Step 2: CSM owns the intro

When AM does come in, it's CSM-introduced. Not "I'm passing you to our AM" but "I want to bring in [AM name] who works on growth options across our customer base — totally optional, but they can show what's worked for similar teams."

This framing keeps CSM as primary. AM enters as guest expert.

Step 3: AM never breaks the CSM relationship

AM rule: any direct buyer email or call must be visible to CSM. AM doesn't run side conversations. If buyer asks questions about product or service, AM redirects to CSM. AM only owns the commercial discussion.

The AI workflow

name: expansion-signal-score
trigger: New "expansion signal" record in Vitally/Gainsight

Inputs: - All CSM notes from the last 90 days - Product usage data (which features are being adopted, by which users, in which workspace) - Champion engagement signals (email opens, in-product activity) - Common Room or Slack community signals if applicable

Claude scores the signal + recommends motion + drafts an intro email for CSM to send.

The intro email draft

This is the highest-value AI output. Done badly, it sounds salesy. Done well, it sounds like a teammate connecting two friends.

System prompt:

You are writing a CSM-to-customer intro email bringing in an AM. The tone must be:
- Customer-first. The CSM is doing the customer a favor, not setting up a sale.
- Optional. The customer can decline meeting AM.
- Specific. Reference the actual use case or signal that prompted this.
- Short. Under 100 words.

Banned phrases: "expansion opportunity", "upsell", "discuss your growth", "commercial discussion".

Approved framing: "I want to introduce", "in case it's helpful", "totally optional", "they can share what's worked for teams like yours". ```

Pitfalls

  • **AM bypasses CSM**: org-level policy is needed. AM cannot have direct customer communication without CSM CC.
  • **Customer sees the seam anyway**: even with perfect handoff, sophisticated buyers know what's happening. The fix is to make AM's value real — they should bring specific case studies and pricing flexibility CSM can't.
  • **CSM and AM compensation conflict**: if CSM is on retention quota and AM on expansion quota, the handoff is structurally adversarial. Compensation alignment helps; shared NRR target is best.

Tools

  • **Vitally or Gainsight**: signal logging + workflow trigger
  • **Common Room**: community + product usage signals not in your CRM
  • **Anthropic Claude**: scoring + draft email
  • **Slack**: AM-CSM coordination channel per account

What good looks like

Customers shouldn't notice this handoff happened. They should feel like one team helped them think about growth. NRR > 115% companies all do this well.

Tools referenced

Pod brief, bi-weekly.

AI workflows for SDR, AE, SE, CSM, AM, RevOps. One handoff article + 3 tool picks per issue.

No spam, unsubscribe in one click.