CX leader — VP Customer Experience / Head of CS / CCO
"Owns the post-sale number under do-more-with-less — wants users to reach value without growing the team."
Type: Exec / Champion · Function: Customer Experience / Success · Size: mid-market + enterprise Lead with: AI-Native priority, outcomes flavor — AI Onboarding · Motion: land & expand
Aligned to the company AI-Native priority at the strategic level; sell on outcomes (activation, TTV, cost-to-serve) at the working level. Lead AI-Native, land on the number she feels day to day.
Why them
Owns onboarding, adoption, retention (NRR/GRR), and increasingly expansion. The 2026 squeeze is "more customers, same team." TTV is the retention battleground — top quartile gets to value in <5 min, while most products activate only 15–20% of users. Has likely piloted an AI support agent and is wary of the deflection backlash (56% of consumers feel negatively about AI in CX).
Angle — what to say (lead activation/outcomes, NOT deflection)
- Onboarding requires hand-holding to get to value: the Product Agent gets users to first value inside the product — collapsing setup into a prompt — so activation and TTV move without adding headcount. A day-one novice operates with the skill of a five-year power user. Cut onboarding time, reduce the dependency on managed services.
- Support / CS hand-holding is a cost center: knowledge grounding + support handoff — the agent explains in natural language and does the task instead of escalating to a human.
- The intent dividend — Conversational Analytics (early access): Foldspace's analysis of users' conversations with the agent shows exactly where they stall.
- Sell against the product/adoption budget, as "embedded success / in-product adoption pathways" — not a support bot.
Hooks
- "Your best CSMs are doing work your product should do. The agent lends every user their expertise on day one."
- "We engineer champions. We don't wait six months and hope a user watched enough tutorials."
- "Your TTV is the retention battleground. What if onboarding just did itself?"
- "Most products activate 15–20% of users. The agent does the setup for them."
- "Same team, more accounts. Move activation without moving headcount."
Objections → responses
- "We already have Fin / Decagon / Sierra." → Those run in support to cut cost-to-serve. Foldspace runs in the product to drive activation/TTV — different surface, budget, and metric.
- "Isn't this just a support bot?" → No — it executes the core product workflow to get users to value, not answer tickets. (#1 objection to disarm.)
- "Deflection hurts CSAT." → We don't deflect; we get users to the outcome, with a human-readable trace in Conversational Analytics.
- "Will users trust an agent taking real actions?" → Trust Lab (early access) — evals at the interface, golden sets, shadow mode, outcome-matching; validated outputs before they surface, every action bound by the same permissions as a human user.
- "Our domain is too specialized." → The agent embeds your knowledge — product logic, best practices, user context.
Targeting & channels
- Technographics: Gainsight · ChurnZero · Catalyst / Totango · Intercom / Zendesk (incumbent signal)
- Paid: LinkedIn (VP CX / Head of CS / CCO)
- Voices: Nick Mehta · Kristi Faltorusso · ChurnZero / You Mon Tsang · Lincoln Murphy · TSIA
Avoid
"chatbot" · "support bot" · "ticket deflection" · "self-service portal" · "conversational AI" · "answers questions" · "reduce headcount" · "replace CSMs" · "the agent does it vs answers it" (eroded vs Decagon/Sierra)
Two big risks (
icp-d §5, §11): (1) Don't land in a Fin/Decagon/Sierra deflection bake-off — differentiate on surface + goal (in-product, activation), never "we take action." (2) The budget owner is usually Product or the CTO (sometimes Marketing), not CS — Optibus = CTO, EverCommerce = Marketing/CTO/Product. Treat the CX leader as a champion/influencer and line up the Product or CTO economic buyer.
Source: positioning/icp-d-cx-leader.md (full research) · matrix positioning/gtm-messaging-matrix.md · modules core/overview.md.