Part of the Assess phase
Customer Success Maturity Model
The Distilled CS maturity model places your CS organization on a three-stage scale (Crawl, Walk, Run) and shows the priority actions for moving up. It anchors the assessment, the recommended playbooks, and the metrics directory.
The starting point of CS maturity. Every team begins here.
In this stage, CS exists but operates mostly on instinct and firefighting. Customer engagement is inconsistent, metrics are sparse or manually tracked, and most effort goes into reacting to problems rather than preventing them.
Key Characteristics
- No formal customer segmentation. Every customer gets a similar experience
- Health is assessed by gut feel, not data
- No documented playbooks or journey maps
- CSMs are reactive, responding to escalations and complaints
- Metrics limited to basic churn rate, maybe CSAT
- CS reports into Sales or Support, low organizational visibility
Priority Actions
- Define basic customer segmentation (at least 2–3 tiers)
- Implement a simple health score using 3–5 signals
- Document the onboarding process as your first playbook
- Start tracking logo retention and GRR monthly
- Establish a regular cadence for customer touchpoints
- Get CS a seat at the table: establish regular syncs with Sales and Product teams
- Pilot AI call-summarization in your CSM workflow
Typical Profile
Early-stage companies with under $5M ARR, or larger companies that have recently formed a CS function. Team size is usually 1–3 people wearing multiple hats.
The middle stage, where structure starts to take hold.
In this stage, CS has organized its data and customers, established basic processes, but hasn't fully operationalized them at scale. The team is moving from reactive to structured, with defined segments and some playbooks in place.
Key Characteristics
- Customer base is segmented by ARR or tier, engagement models differ by segment
- Basic health scores exist but may be inconsistently maintained
- Some playbooks documented, especially for onboarding and renewal
- CSMs have defined books of business with rough coverage ratios
- Tracking GRR, NRR, and basic adoption metrics
- CS has a seat at the table but isn't yet driving strategic decisions
Priority Actions
- Operationalize health scores: make them systematic, not manual
- Build playbooks for risk mitigation and expansion identification
- Implement QBR/EBR cadence for top-tier accounts
- Define time-to-value metrics by segment
- Start measuring CSM capacity and coverage ratios formally
- Build a CS roadmap aligned with company strategy
- Share customer health data with other teams: create a shared dashboard or Slack channel
- Pilot an AI-driven health score alongside your rule-based one
Typical Profile
Companies with $5M–$20M ARR that have had a CS team for 1–3 years. Team size is 4–10 people with emerging specialization.
The most mature stage in the model. Scaled, predictive, and operationalized.
In this stage, CS is data-driven and predictive. Playbooks govern the customer lifecycle, health scores trigger automated actions, and CS is a recognized revenue contributor. The team operates with discipline and consistency at scale. Continued improvement within Run is the ongoing work: refining predictive models, scaling AI-assisted workflows, and deepening cross-functional influence.
Key Characteristics
- Multi-dimensional health scores with automated alerts and triggers
- Comprehensive playbooks for all lifecycle stages
- Customer journey fully mapped with defined milestones and success criteria
- CS actively identifies and drives expansion opportunities
- Dedicated CS platform in use (Gainsight, ChurnZero, Vitally, etc.)
- CS metrics are part of company-level reporting and board updates
- Formal career paths and development programs for the CS team
- Customer advocacy programs convert satisfied accounts into expansion and referral opportunities
Priority Actions
- Build predictive models for churn and expansion
- Implement digital CS motions for long-tail accounts
- Develop cross-functional alignment frameworks with Product, Sales, and Marketing
- Start exploring CS monetization (paid success plans, premium support)
- Build cohort analysis capabilities for retention forecasting
- Establish CS benchmarking against industry peers
- Formalize CS integration: include CS in product planning and structured sales handoffs, track customer outcomes cross-functionally
- Establish a Responsible AI policy for CS: PII handling, human review requirements, and adoption tracking
- Build customer advocacy and referral programs to convert your healthiest accounts into a measurable expansion and referral channel
Typical Profile
Companies with $20M–$100M+ ARR that have had a CS team for 3+ years. Team size is 11–25 with dedicated CS Ops, possibly CS leadership at VP+ level.
Why a maturity model for customer success
A maturity model gives the CS team a shared frame for what it is ready to do next, instead of arguing about tactics in the abstract. Principles that work at Crawl can misfire at Run. Metrics that matter at Run are noise at Crawl. Naming the stage lets the team match the advice to the reality of the organization.
The three stages above are ordered by capability, not by company size. A lean team at a Series A startup can operate at Run. A hundred-person CS org at a public company can still be stuck at Crawl if the motions are inconsistent. Stage is a description of the operating system, not a badge for the team.
Frequently asked questions
What is the customer success maturity model?
A three-stage model that describes how CS organizations evolve from reactive firefighting to proactive, outcome-driven operations. The stages are Crawl, Walk, and Run. Each names the operating mode of the team, the metrics that matter at that level, and the plays that move the team forward.
How do the three stages differ?
Crawl is reactive and foundational: the team is saving what it can while standardizing onboarding and renewal. Walk is informed and structured: segmentation is real, health scoring exists, QBRs run reliably. Run is proactive and operationalized: leading indicators drive action, expansion is a repeatable motion, and AI-assisted workflows are in practice. Continued improvement within Run is the ongoing discipline.
How do I know which stage I am in?
The Distilled CS assessment scores eight domains and maps your overall score to a stage. If you have not completed it, a quick heuristic: if renewals surprise you, you are at Crawl. If you know which accounts are at risk but react late, you are at Walk. If you catch risk weeks in advance, expansion is a repeatable motion, and predictive models or AI workflows are in use, you are at Run.
How long does it take to move between stages?
Typically nine to eighteen months per transition, depending on company growth rate and how much the CS function is already instrumented. Crawl to Walk is the fastest when the team commits to consistent motions. Walk to Run is the longest because it requires a data layer that most teams underestimate.
Can a CS team skip a stage?
No. Stages are not arbitrary. Each layer depends on the capabilities built in the prior one. A team that skips to Run without Walk-stage segmentation and health scoring ends up running plays on accounts it cannot read. The work compounds.
Is maturity the same across segments?
The stages are, but the expression differs. A Run-stage enterprise team runs multi-stakeholder QBRs with outcome scorecards. A Run-stage SMB team runs automated usage-triggered nudges with human escalation. The principles match; the tooling and cadence shift with segment economics.
What triggers a stage transition?
A combination of outgrowing the current stage playbook (CSMs hit the ceiling of what reactive motion can achieve) and new pressure on the business (board expectations, new segment, scale). The transition guide on the transform page walks through the signals that mark each boundary.
How does this compare to other CS frameworks?
Most published CS frameworks focus on either metric taxonomies or operational checklists. The Distilled CS model connects a maturity stage to specific principles, metrics, and playbooks. It is open-source, vendor-neutral, and designed so the advice changes as the team matures, not just as its size grows.
Ready to execute?
Now that you understand the maturity model, put it into action with stage-specific playbooks.