Free self-assessment · 7 competencies · 6 minutes

CS Leadership Competency Assessment

Most CS leaders were promoted because they were great CSMs. Those skills don't cover the board or a team of twenty, so rate yourself on the seven competencies the bigger job needs and get a 90-day plan for your two weakest.

Pick what fits today. A 1 or 2 means the Emerging list sounds most like you, and 5 means you could teach the Mastery list to someone else. Be honest.

No sign-up, and your answers stay in this browser unless you send them to me.

    Competency 1 of 7 Strategic business acumen

    Knowing SaaS unit economics and how CS decisions move growth and valuation.

    Emerging 1-2

    • Reports CSAT and NPS without tying them to revenue
    • Can't explain how CS affects valuation or growth targets
    • Makes budget requests without a business case
    • Can't connect GRR and NRR to what the board cares about

    Proficient 3-4

    • Talks about CS results in revenue terms, like ARR retained and expansion ARR
    • Builds ROI cases for headcount and tool requests
    • Ties CS initiatives to company OKRs
    • Can show executives what a few points of NRR do to valuation

    Mastery 5

    • Models how CS changes the growth curve and the valuation multiple
    • Talks CAC payback and LTV to CAC fluently with the CFO and investors
    • Teaches the executive team and board about retention economics
    • Makes calls that change company direction, such as which segment to focus on

    Where are you today?

    Why this matters

    CS leaders who can't talk ARR and NRR with the CFO struggle to get resources. The ones who can? Hard to replace.

    Competency 2 of 7 Customer lifecycle orchestration

    Designing journeys, segments, health scores and triggers that produce consistent outcomes.

    Emerging 1-2

    • Engagement is reactive, with no standard journey or playbooks
    • Segments don't exist or don't change how the team engages
    • The health score is missing, or nobody trusts it
    • Handoffs between teams are inconsistent

    Proficient 3-4

    • A defined lifecycle with clear phases from onboarding to expansion
    • Segmentation drives where resources go
    • A working health score built on a focused set of signals
    • Playbooks for common scenarios, like low usage or an executive change

    Mastery 5

    • Automated triggers plus well-timed human touchpoints across the lifecycle
    • A health score validated against past churn, with signals months ahead
    • Finds lifecycle gaps through cohort analysis, such as a usage drop in months four to seven
    • The team covers far more customers than the industry average

    Where are you today?

    Why this matters

    Ad hoc customer management breaks somewhere between 50 and 100 customers, and a designed lifecycle lets your team cover far more accounts without adding headcount at the same pace.

    Competency 3 of 7 Data-driven decision making

    Using cohort analysis and leading indicators to predict outcomes and set strategy.

    Emerging 1-2

    • Decides on gut feel or the loudest complaint
    • Reviews churn numbers rarely, with no leading indicators
    • Can't forecast renewals more than 30 days out
    • Can't show the impact of initiatives with data

    Proficient 3-4

    • Tracks leading indicators like health trends and usage
    • Forecasts renewals and churn accurately 60 to 90 days out
    • Uses cohort analysis to test ideas
    • Shows before-and-after data for major initiatives

    Mastery 5

    • Builds predictive models for churn risk and expansion
    • Finance trusts the CS forecast for board reporting
    • Spots trends months before they're obvious
    • Uses data to change decisions in Product and Sales

    Where are you today?

    Why this matters

    This is the most common skill gap in CS teams, and leaders who run on anecdotes see risk later than everyone else.

    Competency 4 of 7 Revenue leadership

    Finding and closing expansion revenue, and running renewals on purpose.

    Emerging 1-2

    • Expansion happens by accident
    • No way to spot or qualify expansion-ready accounts
    • Renewal work starts close to the renewal date
    • No expansion quotas or pipeline visibility

    Proficient 3-4

    • Expansion playbooks with clear qualification criteria
    • Renewals start early, with a risk review and a value check
    • Expansion pipeline tracked in the CRM and reviewed regularly
    • Expansion quotas tied to compensation

    Mastery 5

    • Expansion is a real share of new ARR
    • Predictive signals flag expansion-ready accounts early
    • Renewal forecasts are accurate, and renewals are uneventful
    • Joint account planning and shared incentives with Sales

    Where are you today?

    Why this matters

    Companies above 120 percent NRR grow with far less pressure on Sales than companies stuck at 100 to 110, because their existing customers do part of the work that new logos would otherwise have to do.

    Competency 5 of 7 Organizational design and execution

    Building the structure, roles, handoffs and pay plans that let a CS team scale.

    Emerging 1-2

    • The org structure is inherited or ad hoc, with fuzzy roles
    • Customers fall through the cracks at handoffs
    • No coverage model, or one that doesn't fit customer needs
    • Pay isn't tied to outcomes

    Proficient 3-4

    • Clear roles, each with success metrics and a career path
    • A coverage model built on segments
    • Handoffs with named owners and written success criteria
    • Can draw the next stage's org chart and say when to hire each role

    Mastery 5

    • An org design that has scaled through several growth stages
    • Pay plans drive the right behavior with few side effects
    • Resources shift between segments based on retention data
    • Has developed a successor from inside the team

    Where are you today?

    Why this matters

    Broken handoffs and fuzzy roles churn customers faster than any competitor ever will.

    Competency 6 of 7 Cross-functional influence

    Earning credibility with Product, Sales, Marketing and Finance, and influencing without authority.

    Emerging 1-2

    • Other executives don't ask for your input
    • Product rarely prioritizes what customers need
    • CS keeps cleaning up after unrealistic sales promises
    • CS priorities rarely show up in company OKRs

    Proficient 3-4

    • Executives sometimes ask for your view on customer-facing decisions
    • Product listens because you bring data and customer evidence
    • Works with Sales leadership on handoff quality
    • Resolves most cross-functional conflicts constructively

    Mastery 5

    • Peers bring you in before decisions get made
    • Shared OKRs and joint accountability with other functions
    • Retention data changes what Product builds
    • Finance asks for your input on pricing and packaging

    Where are you today?

    Why this matters

    CS can't succeed in a silo, so leaders who move other functions multiply their impact, and the rest end up as order-takers.

    Competency 7 of 7 Team development and culture

    Hiring well, coaching, growing future leaders and building a team people want to join.

    Emerging 1-2

    • Hiring is hit or miss
    • No development plans or growth paths
    • Little time for coaching because of firefighting
    • No backup for key people

    Proficient 3-4

    • Structured hiring, and most hires work out
    • Every person has a development plan
    • Regular one-on-one coaching and feedback
    • Building a bench of senior CSMs and team leads

    Mastery 5

    • Hires raise the bar, and referrals are a main source
    • People name you as one of the most important leaders in their career
    • Promotes from within and has a ready successor
    • Has developed people who went on to lead CS elsewhere

    Where are you today?

    Why this matters

    Leaders who develop people can scale, and the ones who can't become the bottleneck for everything.

    About this tool

    This is the CS Leadership Competency Framework from my old resource library, rebuilt so it scores itself, and it draws on leadership research and 25 years of building CS teams.

    See all the Free Tools