The CS leader's first 90 days.

Context

Every new CS leadership role is won or lost in the first 90 days. Move too fast and you alienate the team you inherited. Move too slowly and the operating gaps compound. I run the same disciplined framework every time — adapted for the company, not the leader.

Challenge

New CS leaders are usually handed a blend of cultural inheritance, brittle processes, and unreliable signal. The temptation is to fix everything at once. The work is to build trust first, diagnose what's actually broken second, and only then prioritize the changes that compound.

Approach

1. 01

   Days 1–30 · Build trust & listen

   Cross-functional discovery sessions. Shadow customer-facing teams in their real cadence. Experience the product as a customer would. Map the customer journey end-to-end before proposing a single change. Understand before optimizing.

2. 02

   Days 31–60 · Diagnose & connect the dots

   Audit health score logic and data fidelity. Surface forecasting visibility gaps. Pattern-match escalations to identify root causes vs. symptoms. Evaluate the AI and automation footprint — what's leverage, what's noise. Check knowledge and tooling gaps with the team.

3. 03

   Days 61–90 · Prioritize & build the roadmap

   Formalize the operating rhythms that should have always existed: account reviews, renewal cadences, escalation paths. Land 2-3 quick wins that build credibility. Align cross-functional ownership so CS, Sales, and Product are running the same lifecycle. Set the 12-month roadmap with the team, not at the team.

4. 04

   Underneath all three phases · Leadership philosophy

   Human-centered systems — design for people first. Continuous improvement — measure, learn, iterate. Empowered teams — clarity is what enables ownership. The goal: proactive, operationally mature, and deeply human Customer Success.

The Deck

The Leadership Success Framework — the way I think about the first 90 days, slide by slide.