agentleFS
samuelcastrosamuelcastro/startup-skills/customer-success/SKILL.md

customer-success

Skill1 starsChanged 5 months agoMITView on GitHub

Guide founders through customer success strategy including onboarding, support processes, churn prevention, and satisfaction measurement. Use when a founder says "help me design an onboarding flow for new customers", "how do I reduce churn?", "create an NPS survey for my product", "build a customer health scoring system", "help me set up a support ticketing process", "how to improve my customer satisfaction?", "QBR template", "customer success playbook", or asks about retention, customer experience, or building a CS team.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

22 rules. 0 are common, 12 are distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask: "Where are you in your customer success journey?"

    line 22
  2. Very specific:

    Stop customers before they leave.

    line 116
  3. Distinctive:

    When customers churn, learn why:

    line 176
  4. Very specific:

    Create using docx skill:

    line 426
  5. Distinctive:

    Follow-up sequences by segment

    line 449
  6. Distinctive:

    No defined activation moment (unclear success)

    line 477
  7. Distinctive:

    No measurement (can't improve what you don't track)

    line 480
  8. Distinctive:

    Not segmenting churn (treating all churn the same)

    line 484
  9. Distinctive:

    No exit interviews (missing root causes)

    line 485
  10. Distinctive:

    No follow-up on responses (especially detractors)

    line 490
  11. Distinctive:

    Not acting on scores (dashboard without action)

    line 496
  12. Distinctive:

    No SLAs defined (inconsistent experience)

    line 501
  13. Distinctive:

    No escalation path (tickets stuck in limbo)

    line 502
  14. Distinctive:

    Not connecting support to product (missing feedback loop)

    line 503
  15. Very specific:

    Use product skill for feature prioritization from CS feedback

    line 508
  16. Very specific:

    Use growth-analytics skill for retention metrics and cohort analysis

    line 509
  17. Very specific:

    Use sales skill for handoff process from sales to CS

    line 510
  18. Very specific:

    Use operations skill for CS team OKRs and hiring

    line 511
  19. Very specific:

    Use business-model skill for LTV/CAC and expansion revenue

    line 512
  20. Very specific:

    Use docx skill for process documentation and playbooks

    line 513
  21. Very specific:

    Use xlsx skill for health scorecards and metrics tracking

    line 514
  22. Very specific:

    Use pptx skill for QBR decks

    line 515

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Customer Success

Guide founders from reactive support to proactive customer success—from first customers through building a scalable CS organization.

Reference Files

  • references/onboarding.md — Onboarding flows, email sequences, activation checklists
  • references/churn-prevention.md — Churn analysis frameworks, intervention playbooks, exit surveys
  • references/nps-csat.md — NPS/CSAT survey templates, follow-up workflows, benchmarks
  • references/health-scoring.md — Health score models, risk indicators, early warning systems
  • references/support-processes.md — Support ticketing, escalation paths, QBR templates

Workflow

1. Diagnose Stage & Need

Ask: "Where are you in your customer success journey?"

StageSignalsFocus
Early-stage (1-100 customers)Founder handles support, no formal processes→ Lightweight onboarding, manual health checks
Growth (100-500 customers)Can't personally know every customer→ Systematize onboarding, implement health scoring
Scale (500+ customers)Building CS team, need playbooks→ Full CS org, automation, QBRs

Primary Need Identification:

NeedSignalsNext Step
Onboarding"Customers don't activate", "time to value is long"→ Step 2: Onboarding
Churn"Customers leaving", "high churn rate", "why are we losing customers?"→ Step 3: Churn Prevention
Satisfaction"Need NPS", "measure satisfaction", "customer feedback"→ Step 4: NPS & CSAT
Health Scoring"Predict at-risk customers", "proactive CS"→ Step 5: Health Scoring
Support"Support process", "ticketing", "QBRs"→ Step 6: Support & QBRs

2. Onboarding

Transform new customers into successful, activated users. See references/onboarding.md for complete templates.

Onboarding Framework

The Goal: Deliver first value as fast as possible.

Signup → First Value Moment → Habit Formation → Expansion
         (Time-to-value)       (Stickiness)      (Growth)

Define Your Activation Moment:

Business TypeTypical ActivationWhy
B2B SaaSFirst workflow completedCore value realized
Collaboration toolTeam member invitedNetwork effect
AnalyticsFirst report generatedInsight delivered
MarketplaceFirst transactionBoth sides connected

Onboarding Stages

StageGoalTimeframeKey Actions
WelcomeSet expectationsDay 0Welcome email, account setup
SetupConfigure productDay 1-3Core settings, integrations
ActivationReach first valueDay 3-7Guided workflow, first success
EngagementBuild habitDay 7-30Feature education, check-ins
ExpansionDeepen usageDay 30+Advanced features, team growth

Stage-Appropriate Onboarding

Early-Stage (Manual, High-Touch):

  • Personal welcome call for every customer
  • White-glove setup assistance
  • Direct founder/CEO communication
  • Learn what customers actually need

Growth (Hybrid):

  • Self-serve for SMB, high-touch for enterprise
  • Automated email sequences with personal check-ins
  • In-app guidance (tooltips, checklists)
  • Segment by customer size/value

Scale (Automated with Exceptions):

  • Fully automated self-serve onboarding
  • Tech-touch for most, high-touch for strategic accounts
  • CSM assignment based on ARR threshold
  • Onboarding metrics dashboard

Onboarding Email Sequence

EmailTimingPurposeKey Elements
WelcomeImmediatelyConfirm, set expectationsLogin link, what's next, support contact
Quick WinDay 1Drive first actionOne specific task to complete
Setup HelpDay 3Remove frictionCommon setup issues, FAQ link
Activation PushDay 5Drive to value moment"Here's what successful users do first"
Check-inDay 7Personal touch"How's it going? Questions?"
Feature IntroDay 14Deepen engagementOne underused feature
Success StoryDay 21Social proofCustomer similar to them
ExpansionDay 30Grow usageTeam features, advanced use cases

Onboarding Metrics

MetricFormulaTarget
Time to First ValueDays from signup to activation<7 days (SaaS)
Activation RateUsers reaching activation / Total signups>60%
Onboarding CompletionUsers completing all steps / Total signups>80%
Day 7 RetentionActive day 7 / Total signups>40% (B2B)

3. Churn Prevention

Stop customers before they leave. See references/churn-prevention.md for intervention playbooks.

Understanding Churn

Types of Churn:

TypeCausePrevention
VoluntaryCustomer decides to leaveValue delivery, engagement
InvoluntaryPayment failureDunning emails, payment recovery
DowngradeReduced spendDemonstrate value, right-size plans

Churn Timing Patterns:

WhenLikely CauseIntervention
First 30 daysPoor onboarding, no value foundActivation focus, onboarding calls
At renewalDidn't see ROIQBR before renewal, value recap
After price increasePrice/value mismatchCommunicate value, offer options
After champion leavesRelationship-dependentMulti-thread contacts

Churn Analysis Framework

Step 1: Calculate Churn Rate

Monthly Logo Churn = Customers lost / Customers at start of month
Monthly Revenue Churn = MRR lost / MRR at start of month
Net Revenue Retention = (MRR at end + expansion - churn) / MRR at start

Step 2: Segment Churn

Analyze churn by:

  • Customer segment (SMB/Mid/Enterprise)
  • Tenure (first 90 days vs. established)
  • Acquisition channel
  • Plan type
  • Use case / vertical

Step 3: Identify Patterns

QuestionWhat It Reveals
When do they churn?Onboarding vs. renewal problem
Who churns?Segment fit issues
What predicts churn?Leading indicators
Why do they say they're leaving?Root cause

Churn Intervention Playbook

Risk LevelIndicatorsActionOwner
CriticalCancellation request, angry ticketSame-day call, escalateCS Leader
HighUsage dropped >50%, no login 14+ daysOutreach within 24hCSM
MediumUsage declining, support tickets upAutomated + personal touchCSM/Automated
LowMinor engagement dipAutomated nurtureAutomated

Exit Survey

When customers churn, learn why:

Exit Survey Questions:

  1. What was your primary reason for canceling? (Required, single select)
    • Found a better alternative
    • Too expensive
    • Missing features we needed
    • Didn't use it enough
    • Poor customer support
    • Company/budget changes
    • Other
  2. What could we have done differently? (Optional, open text)
  3. Would you consider us again in the future? (Required, Yes/No/Maybe)
  4. How likely are you to recommend us to others? (NPS scale)

4. NPS & CSAT

Measure and improve customer satisfaction. See references/nps-csat.md for survey templates.

NPS (Net Promoter Score)

The Question:

"On a scale of 0-10, how likely are you to recommend [Product] to a friend or colleague?"

Scoring:

  • Promoters (9-10): Loyal enthusiasts who refer others
  • Passives (7-8): Satisfied but vulnerable to competition
  • Detractors (0-6): Unhappy customers who can damage brand

NPS Calculation:

NPS = % Promoters - % Detractors
Range: -100 to +100

NPS Benchmarks:

NPS ScoreRatingContext
70+World-classTop companies (Apple, USAA)
50-69ExcellentStrong customer loyalty
30-49GoodHealthy, room to improve
0-29Needs workMore detractors than ideal
NegativeCriticalUrgent action needed

B2B SaaS NPS Benchmarks:

SegmentMedianTop Quartile
SMB3050+
Mid-market3555+
Enterprise4060+

CSAT (Customer Satisfaction Score)

The Question:

"How satisfied are you with [specific interaction/product]?"

Scale: 1-5 or 1-7

CSAT Calculation:

CSAT = (Satisfied responses / Total responses) × 100
"Satisfied" = top 2 scores (4-5 on 5-point scale)

When to Use Each:

MetricBest ForTiming
NPSOverall relationship, loyaltyQuarterly, after key milestones
CSATSpecific interactionsAfter support ticket, after onboarding
CESEase of experienceAfter specific task completion

NPS Survey Implementation

Timing Strategy:

TriggerRationale
QuarterlyRegular pulse on relationship
Post-onboarding (Day 30)Measure first impression
Post-support resolutionMeasure support quality
Pre-renewal (60 days out)Identify at-risk before too late

Follow-up Questions (by segment):

For Promoters (9-10):

"What do you love most about [Product]?" "Would you be open to leaving a review or being a reference?"

For Passives (7-8):

"What would make you rate us higher?" "What's one thing we could improve?"

For Detractors (0-6):

"We're sorry to hear that. What's the main reason for your score?" "What would it take to improve your experience?"

NPS Follow-up Workflow

SegmentResponse SLAActionOwner
Detractors24 hoursPersonal call, understand issueCSM/CS Leader
Passives48 hoursEmail follow-up, gather feedbackCSM
Promoters1 weekThank you, referral/review askCSM/Marketing

5. Customer Health Scoring

Predict and prevent churn before it happens. See references/health-scoring.md for detailed models.

Health Score Components

Build a composite score from multiple signals:

CategoryWeightSignals
Product Usage40%Login frequency, feature adoption, breadth of use
Engagement25%Support tickets, NPS responses, event attendance
Relationship20%Executive sponsor, champion strength, multi-threading
Financial15%Payment history, contract value, expansion potential

Simple Health Score Model

For Early-Stage (Spreadsheet-Based):

DimensionRed (0 pts)Yellow (1 pt)Green (2 pts)
Login FrequencyNo login 14+ days1-2x/week3+ times/week
Feature AdoptionOnly 1 feature2-3 features4+ features
Support SentimentNegative ticketsNeutralPositive/none
Stakeholder AccessNo responseSingle contactMulti-contact
NPS ScoreDetractorPassivePromoter

Score Interpretation:

  • 8-10: Healthy (Green)
  • 5-7: Needs attention (Yellow)
  • 0-4: At risk (Red)

Stage-Appropriate Health Scoring

Early-Stage (1-100 customers):

  • Manual health check spreadsheet
  • Gut feel + basic usage data
  • Review weekly with founder
  • Focus on learning patterns

Growth (100-500 customers):

  • Simple scoring model in CRM
  • Automated alerts for red accounts
  • Weekly health review meeting
  • Start documenting playbooks

Scale (500+ customers):

  • Automated health scoring platform
  • ML-based churn prediction
  • Real-time dashboards
  • Tiered response playbooks

Acting on Health Scores

HealthActionFrequencyGoal
GreenExpansion focusQuarterly QBRGrow and advocate
YellowEngagement boostBi-weekly check-inReturn to green
RedInterventionImmediateSave or learn

6. Support Processes & QBRs

Build support systems that scale. See references/support-processes.md for templates.

Support Tier Structure

TierHandlesResponse TimeEscalation
Tier 1FAQs, how-to, basic issues<4 hoursCan't resolve in 1 interaction
Tier 2Technical issues, bugs<8 hoursRequires engineering
Tier 3Engineering escalation<24 hoursProduct decisions needed

Support Metrics

MetricDefinitionTarget
First Response TimeTime to first human reply<4 hours (business)
Resolution TimeTime to fully resolve<24 hours (Tier 1)
First Contact Resolution% resolved in one interaction>70%
CSAT (Support)Post-ticket satisfaction>90%
Ticket Volume per CustomerTickets / Active customersDecreasing trend

QBR (Quarterly Business Review)

Purpose: Demonstrate value, align on goals, identify expansion.

QBR Agenda (60 min):

SectionTimeContent
Business Update5 minTheir company news, priorities
Usage & Value15 minMetrics, ROI achieved
Wins & Challenges10 minWhat's working, what's not
Product Roadmap10 minRelevant upcoming features
Goals & Action Plan15 minNext quarter objectives
Expansion Discussion5 minGrowth opportunities

QBR Preparation Checklist:

  • Usage data and trends pulled
  • ROI/value metrics calculated
  • Support ticket summary reviewed
  • Renewal date confirmed
  • Expansion opportunities identified
  • Stakeholder list updated
  • Previous QBR action items reviewed

When to Start QBRs

Customer SegmentQBR FrequencyDelivery
Enterprise ($100K+)QuarterlyIn-person or video
Mid-market ($25-100K)Bi-annuallyVideo call
SMB (<$25K)Annually or trigger-basedEmail summary

7. Building a CS Team

When to Hire First CSM:

  • 50+ customers
  • Founder can't personally manage all relationships
  • Churn is becoming a problem
  • Clear patterns in what makes customers successful

CSM-to-Account Ratios:

SegmentRatioWhy
Enterprise1:10-20High-touch required
Mid-market1:30-50Balanced touch
SMB1:100-200Tech-touch + pooled

First CS Hire Profile:

  • Previous startup experience at similar stage
  • Can build process, not just follow it
  • Strong communication + empathy
  • Comfortable with ambiguity
  • Technical enough to understand product

Deliverables

1. Onboarding Email Sequence

Create using docx skill:

  • 6-8 email sequence with timing
  • Subject lines and body copy
  • Personalization placeholders
  • Success metrics to track

2. Onboarding Checklist

Create using xlsx skill:

  • Step-by-step activation checklist
  • Owner assignments
  • Timeline targets
  • Completion tracking

3. Churn Analysis Framework

Create as markdown:

  • Churn calculation formulas
  • Segmentation dimensions
  • Analysis template
  • Intervention triggers

4. NPS Survey + Workflow

Create using docx skill:

  • Survey questions
  • Follow-up sequences by segment
  • Response SLAs
  • Reporting template

5. Customer Health Scorecard

Create using xlsx skill:

  • Scoring dimensions and weights
  • Red/yellow/green thresholds
  • Account list with scores
  • Action triggers

6. QBR Template

Create using pptx skill:

  • 8-10 slide deck template
  • Agenda and discussion guide
  • Metrics dashboard slide
  • Action plan format

7. Support Process Document

Create using docx skill:

  • Tier definitions and escalation paths
  • Response time SLAs
  • Ticket categorization
  • Metrics and reporting

Anti-Patterns

Onboarding Mistakes:

  • No defined activation moment (unclear success)
  • Same onboarding for all customers (one-size-fits-none)
  • Too many emails too fast (overwhelm)
  • No measurement (can't improve what you don't track)

Churn Prevention Mistakes:

  • Reactive only (waiting for cancellation request)
  • Not segmenting churn (treating all churn the same)
  • No exit interviews (missing root causes)
  • Focusing on save rate, not prevention

NPS Mistakes:

  • Survey fatigue (too frequent)
  • No follow-up on responses (especially detractors)
  • Gaming the score (only surveying happy customers)
  • NPS as only metric (missing context)

Health Score Mistakes:

  • Too complex initially (analysis paralysis)
  • Not acting on scores (dashboard without action)
  • Static thresholds (not updating as you learn)
  • Missing qualitative signals (relationship quality)

Support Mistakes:

  • No SLAs defined (inconsistent experience)
  • No escalation path (tickets stuck in limbo)
  • Not connecting support to product (missing feedback loop)
  • Measuring volume, not quality

Integration with Other Skills

  • Use product skill for feature prioritization from CS feedback
  • Use growth-analytics skill for retention metrics and cohort analysis
  • Use sales skill for handoff process from sales to CS
  • Use operations skill for CS team OKRs and hiring
  • Use business-model skill for LTV/CAC and expansion revenue
  • Use docx skill for process documentation and playbooks
  • Use xlsx skill for health scorecards and metrics tracking
  • Use pptx skill for QBR decks

Adapted from Linas Beliūnas's The One-Person Unicorn founder skill set.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.