810-110

The XaaS Economy Shift

Traditional on-premises sales focused on a single transaction. XaaS flips the model: customers subscribe, consume, and can churn at any renewal. This changes how the vendor earns revenue and how the customer evaluates success.

The Customer Lifecycle: Land - Adopt - Expand - Renew

The CSM orchestrates the customer journey across four repeating phases. Each phase has distinct goals, activities, and success metrics.

• Land - Onboarding kickoff, success plan creation, goal alignment, provisioning, first-value timing.
• Adopt - Drive active usage, remove adoption barriers, measure engagement, run QBRs, track health score.
• Expand - Identify new use cases, upsell additional capacity, cross-sell adjacent products, widen stakeholder map.
• Renew - Protect recurring revenue, surface risks early, secure multi-year commitments, forecast to finance.

CSM vs CSE vs TAM vs Sales

Cisco distinguishes several customer-facing roles. Knowing who owns what is essential.

The Success Plan

A success plan is the living document that captures the customer's business objectives, the outcomes they expect, the measurable success criteria, and the action plan to get there. It is co-authored with the customer and reviewed at every major touchpoint.

• Business objectives (strategic goals in the customer's language)
• Desired outcomes (what does success look like?)
• Success criteria / KPIs (quantifiable, time-bound)
• Stakeholder map (economic buyer, champion, users)
• Barriers and mitigations
• Use-case roadmap and adoption milestones
• Governance cadence (weekly ops, monthly steerco, QBR)

Core CSM Competencies

• Business acumen - translate technology into business value
• Outcome orientation - obsess over measurable results, not features
• Relationship management - earn trust at multiple levels
• Data literacy - read telemetry, health score, usage trends
• Change management - guide the customer organization through adoption

Key Stakeholder Archetypes

The RACI Matrix

RACI is the classic tool for clarifying ownership on any workstream: Responsible (does the work), Accountable (single owner, signs off), Consulted (expert input), Informed (kept in the loop).

Task                         | Exec Sponsor | Champion | CSM  | Tech Owner | End User
Approve success plan         |      A       |    R     |  C   |     I      |    I
Configure platform           |      I       |    I     |  C   |     R/A    |    I
Run end-user training        |      I       |    C     |  A   |     C      |    R
Quarterly Business Review    |      A       |    R     |  R   |     C      |    I
Renewal decision             |      A       |    R     |  C   |     C      |    I
Escalation path              |      A       |    C     |  R   |     C      |    I

QBR vs EBR

Both are governance touchpoints, but they serve very different audiences.

• QBR (Quarterly Business Review) - Operational. Attended by champion, technical owner, CSM. Focus on adoption KPIs, open risks, next-quarter plan, use-case delivery. Typically 60-90 minutes.
• EBR (Executive Business Review) - Strategic. Attended by executive sponsors and economic buyer. Focus on outcome attainment, ROI story, industry benchmarks, strategic roadmap, multi-year value. Typically 45-60 minutes, senior-to-senior.

Influence Mapping

Beyond the org chart, CSMs must understand the political reality. Plot each stakeholder on two axes: Influence (how much sway they have on the renewal decision) and Support (how favorable they are to your solution).

• High influence + high support = Champions. Invest, equip with wins, amplify.
• High influence + low support = Blockers. Priority to neutralize with data, peer proof, executive alignment.
• Low influence + high support = Advocates. Nurture, develop into champions.
• Low influence + low support = Noise. Monitor, do not over-invest.

Stakeholder Engagement Cadence

The Adoption Baseline

Before you can measure progress you must measure the starting point. The adoption baseline captures:

• Number of licensed users vs active users
• Feature breadth (which modules are turned on?)
• Feature depth (are users getting past the basics?)
• Integration footprint (connected systems, data volumes)
• Process maturity (ad-hoc, standardized, optimized)

The Adoption Gap

The adoption gap is the difference between the customer's entitled value (what they are paying for) and their realized value (what they are actually getting). Closing that gap is the CSM's primary job.

Entitlement       [==============================] 100%
Deployed          [======================        ] 70%
Active usage      [============                  ] 40%
Realized outcomes [========                      ] 25%
                  ^
                  Adoption gap = 75% of paid value unrealized

Categories of Adoption Barriers

Adoption Metrics That Matter

• DAU / MAU - Daily Active Users over Monthly Active Users. A ratio above 0.3 generally indicates a sticky product.
• License utilization - Active users / entitled licenses. Under 60% signals a shelfware risk.
• Feature adoption breadth - Number of features used out of total available.
• Time to First Value (TTFV) - Days from contract signature to first measurable outcome.
• Health score - Composite index combining usage, support, sentiment, and financial signals.

Anatomy of a Health Score

Health Score = (Product Usage  * 0.35)
             + (Support Signals * 0.15)
             + (Engagement      * 0.20)
             + (Sentiment / NPS * 0.15)
             + (Financial       * 0.15)

Bands:  Green  >= 80   At target, expansion-ready
        Yellow 60-79   Watch list, CSM action required
        Red    < 60    At risk, escalation + save plan

Adoption Playbook (by lifecycle stage)

• Onboarding (0-90d) - Kickoff, success plan, admin training, TTFV milestone, 30/60/90 day check-ins.
• Ramp (90-180d) - Use-case launch, broader user training, first QBR, close top 3 barriers.
• Steady state (180-360d) - Feature expansion, champions program, second use case, benchmark the customer.
• Pre-renewal (T-120d) - Value-realization review, EBR, multi-year proposal, risk mitigation.

Value Drivers

Every customer ultimately buys for one of four reasons. Naming the primary driver shapes the entire success plan.

ROI, TCO, Payback

CSMs must be fluent in financial language without pretending to be CFOs.

• ROI (Return on Investment) = (Net benefit / Cost of investment) x 100. Percentage return over a period.
• TCO (Total Cost of Ownership) = All direct + indirect costs over the useful life (licenses, infra, staff, training, risk).
• Payback period = Months needed for cumulative benefit to equal cumulative cost.
• NPV (Net Present Value) = Sum of discounted future cash flows minus initial investment.

Example ROI calculation
-----------------------
Annual subscription cost  : $  240,000
Hours saved per week      :       320
Loaded hourly rate        : $    55
Annual labor savings      : $  915,200 (320 * 52 * 55)
Net annual benefit        : $  675,200
ROI                       :      281%
Payback period            :      ~4 months

Outcome-Based Roadmap

Traditional roadmaps list features. An outcome-based roadmap lists outcomes and the features that enable them. This keeps every conversation anchored in business value.

Outcome                        Target      Owner       Due        Status
-------------------------------------------------------------------------------
Reduce ticket volume -25%      Q2 baseline  IT Ops      Q3 end     On track
Increase CSAT to 4.6           +0.4 pts     Support     Q4 mid     At risk
Launch new digital channel     Go-live      Product     Q3 start   On track
Retire legacy platform         EOL          Arch        Q4 end     Behind

Success Criteria: SMART and Measurable

Success criteria must be written so that anyone can tell, without interpretation, whether they were met.

• Specific - what exactly will change?
• Measurable - how will we quantify it?
• Achievable - realistic given resources?
• Relevant - ties to a business driver?
• Time-bound - by when?

Weak: "Improve customer support." Strong: "Reduce first-response time from 4 hours to 30 minutes across tier-1 tickets by Q3, measured in the support platform report."

Telling the Value Story

At every EBR and renewal cycle the CSM should be able to tell the value story in three slides:

1. What we committed to - the outcomes and success criteria from the original success plan.
2. What we delivered - quantified results, ideally with before/after data and peer benchmarks.
3. What is next - the outcome-based roadmap for the next period, including expansion opportunities.

Case Studies & Advocacy

A realized value story is a reusable asset. Package wins into case studies, reference calls, or conference talks. Benefits are bilateral: the customer gets visibility for their team, and the vendor earns proof points for other accounts.

Core Retention Metrics

NRR = (Starting ARR + Expansion - Downgrades - Churn) / Starting ARR
GRR = (Starting ARR - Downgrades - Churn) / Starting ARR

Example: Starting $1M, expansion $250k, downgrades $50k, churn $100k
NRR = (1,000 + 250 - 50 - 100) / 1,000 = 110%
GRR = (1,000 - 50 - 100) / 1,000         =  85%

Upsell vs Cross-Sell

• Upsell - More of the same: additional users, higher tier, more capacity, longer term.
• Cross-sell - A different product or adjacent capability that extends the relationship.
• Expansion - Umbrella term for any net-new recurring revenue from an existing account.

The Renewal Playbook

A renewal is won or lost long before the PO is cut. Cisco's recommended motion starts 180 days before the contract end date.

Indicators of a Healthy Renewal

• Documented outcomes achieved from the current period
• Health score green for at least the last two quarters
• Multiple engaged stakeholders, including exec sponsor
• Active champion with a personal stake in success
• Expansion conversation started and quantified
• No material unresolved escalation

Red Flags at Renewal

• Champion departure with no successor identified
• Sudden drop in active usage or support activity
• Competitive displacement rumors
• Procurement involved before CSM has closed the value story
• "We need to cut budget by X%" without outcome conversation
• Executive sponsor unavailable for EBR

Expansion Triggers

CSMs identify expansion signals and hand them off (or co-sell) with the account team.

• License utilization above 85% - upsell capacity
• New department or geography requesting access - scale horizontally
• New use case referenced in QBR - cross-sell adjacent module
• Mergers or acquisitions - expand to new entity
• Customer publicly reports outcome - advocacy + upsell opportunity

Early Warning Signs

The earlier a risk is surfaced, the cheaper it is to fix. CSMs watch for combinations of these signals:

• Declining product usage trend over 30-60 days
• Increase in support ticket volume or severity
• Champion unresponsive or out of cycle meetings
• Key stakeholder departure without backfill
• Negative sentiment in QBR or NPS feedback
• Budget review or procurement freeze
• Competitor POC in flight
• Multiple missed milestones on the success plan

Escalation Playbook

De-escalation Techniques

• Listen first - allow the customer to vent before proposing solutions.
• Acknowledge impact - name the business impact specifically, not generically.
• Own the problem - avoid blame-shifting to product, partners, or the customer.
• Commit to cadence - "I will update you at 17:00 daily until resolved" beats "we will keep you posted."
• Escalate proactively - bring your exec sponsor in before the customer asks.
• Close the loop - document resolution in writing and in the next QBR.

Root Cause Analysis: The 5 Whys

A simple and powerful tool to move beyond symptoms and fix the underlying cause.

Problem: Major outage during peak hours.
Why 1? A configuration change was pushed in production.
Why 2? The change was not tested in staging first.
Why 3? No staging environment exists for this service.
Why 4? The service was inherited from a recent acquisition.
Why 5? No integration plan covered environment parity.

Root cause: Missing integration playbook for acquired services.
Action: Build standardized acquisition readiness checklist.

Case Management Discipline

• Single owner per escalation (usually the CSM, unless purely technical)
• Severity classification aligned to business impact, not just technical severity
• Defined communication SLAs by severity
• Centralized case record accessible to both customer and vendor teams
• Weekly risk review at the CSM team level; red accounts surfaced to leadership
• Post-mortem output fed back into success plan for prevention

Risk-to-Action Matrix

Turning Escalations into Loyalty

Research consistently shows that customers whose escalations are handled well become more loyal than customers who never had an issue. The key is speed, transparency, ownership, and a visible commitment to prevention. The CSM is the person who must orchestrate all four.