Customer Success Foundations
Domain focus
Customer Success Foundations tests the vocabulary and operating model of customer success: why the discipline exists, how the CSM role differs from support and sales, and how a success plan connects customer outcomes to action. Expect questions on lifecycle stages, stakeholder roles, outcome versus output, and governance.
Core rules
- Customer success is proactive and outcome-led: the customer achieves stated business outcomes, and the vendor earns retention and expansion. It is not reactive ticket handling.
- The CSM is a trusted advisor and orchestrator. The CSM owns the success plan, adoption and value conversations, health and risk signals, and renewal readiness, while coordinating support, sales, partners, and executives.
- The customer lifecycle runs from onboarding through adoption, value realization, renewal, and expansion. Handoffs between stages need explicit owners and evidence.
- A success plan is a joint, living document: business outcomes, measurable success criteria, stakeholders, actions, dates, and risks. It is not a project plan or a sales proposal.
- Outcome versus output: deploying a product is an output; reducing cost, risk, or time is an outcome. The exam rewards outcome language.
- Stakeholder mapping separates executive sponsor, business owner, technical admin, champion, and blocker. Each needs a different engagement cadence.
- Governance defines cadence, escalation, and decision rights so issues surface before renewal.
Worked example
A customer buys collaboration licenses and says the goal is 'better meetings.' The CSM reframes this as an outcome: reduce average meeting start time by 25% within two quarters and increase active meeting-room usage. The success plan lists the executive sponsor, IT admin, and line-of-business champion; actions include room readiness, user enablement, and adoption reporting; the first review is at 30 days. Reasoning: 'better meetings' is not measurable, so the CSM converts it into a business metric, assigns owners, and defines evidence. License delivery alone would be an output and would not prove value.
Traps
- Treating the CSM as an escalation manager for support tickets.
- Writing a success plan with vendor tasks only and no customer commitments.
- Measuring activity (calls, training sessions) instead of outcomes.
- Assuming the economic buyer is the daily champion.
- Waiting for renewal to discuss value.