mcpField
C
customer-health-analyst

customer-health-analyst

github.com/ncklrsData & databases53152 installsUpdated 35w ago
Repository

About customer-health-analyst

customer-health-analyst is a guidance skill for customer success teams building health scoring and predictive analytics. It organizes rules for churn signals, segmentation, reporting, and interventions to turn customer data into action.

Key features

  1. 01Health score design and calibration
  2. 02Leading and lagging indicator analysis
  3. 03Churn prediction and early warnings
  4. 04Customer usage and adoption analytics
  5. 05Risk intervention guidance
  6. 06Cohort analysis and executive reporting

Use cases

  1. 01Designing customer health scoring models
  2. 02Detecting churn risk before renewal
  3. 03Segmenting accounts for interventions
  4. 04Reporting customer health to executives

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ncklrs/startup-os-skills --skill customer-health-analyst

After installing, type/customer-health-analystin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
_sections.md
churn-prediction-modeling.md
cohort-analysis-benchmarking.md
data-enrichment-360.md
executive-reporting-dashboards.md
health-model-validation.md
health-score-design.md
indicators-leading-lagging.md
risk-identification-escalation.md
segmentation-tier-scoring.md
usage-analytics-adoption.md

Details

From the project README

Customer Health Analyst

Expert guidance for customer health scoring, predictive analytics, and data-driven customer success strategies. Transform raw customer data into actionable insights that prevent churn and drive expansion.

Philosophy

Customer health is not a single metric — it's a predictive system:

  1. Measure what matters — Health scores should predict outcomes, not just track activity
  2. Lead, don't lag — Focus on indicators that predict churn before it's too late
  3. Segment for action — Different customers need different interventions
  4. Automate detection — Scale health monitoring across your entire customer base
  5. Close the loop — Analytics without action is just expensive data collection

How This Skill Works

When invoked, apply the guidelines in rules/ organized by:

  • health-* — Health score design, weighting, and calibration
  • indicators-* — Leading vs lagging indicator analysis
  • churn-* — Prediction modeling and early warning systems
  • usage-* — Analytics and adoption metrics
  • risk-* — Identification, escalation, and intervention
  • data-* — Enrichment and customer 360 development
  • cohort-* — Analysis and benchmarking
  • executive-* — Reporting and dashboards
  • segmentation-* — Customer tiers and scoring models

Core Frameworks

The Health Score Hierarchy
┌─────────────────────────────────────────────────────────────────┐
│                    COMPOSITE HEALTH SCORE                       │
│                         (0-100)                                 │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐  ┌──────────┐       │
│  │ PRODUCT  │  │ENGAGEMENT│  │ GROWTH   │  │ SUPPORT  │       │
│  │  USAGE   │  │          │  │ SIGNALS  │  │ HEALTH   │       │
│  │  (35%)   │  │  (25%)   │  │  (20%)   │  │  (20%)   │       │
│  └──────────┘  └──────────┘  └──────────┘  └──────────┘       │
│                                                                 │
├─────────────────────────────────────────────────────────────────┤
│                    COMPONENT METRICS                            │
│                                                                 │
│  Usage:        Engagement:    Growth:        Support:          │
│  - DAU/MAU     - NPS score    - Seat trend   - Ticket volume   │
│  - Features    - CSM meetings - Usage trend  - Resolution time │
│  - Depth       - Email opens  - Expansion    - Sentiment       │
│  - Breadth     - Logins       - Contract     - Escalations     │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘
Leading vs Lagging Indicators
TypeDefinitionExamplesAction Window
LeadingPredict future outcomesUsage decline, engagement drop60-90 days
CoincidentMove with outcomesSupport sentiment, NPS30-60 days
LaggingConfirm after the factChurn, revenue lossToo late
Customer Health States
┌─────────────────────────────────────────────────────────────────┐
│                                                                 │
│  THRIVING ──→ HEALTHY ──→ NEUTRAL ──→ AT-RISK ──→ CRITICAL    │
│    (85+)      (70-84)     (50-69)     (30-49)      (<30)       │
│                                                                 │
│  Expand       Monitor     Engage      Intervene    Escalate    │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘
Health Score Components
ComponentWeightKey MetricsWhy It Matters
Product Usage30-40%DAU/MAU, feature adoption, depthUsage predicts value realization
Engagement20-25%NPS, CSM contact, responsivenessRelationship strength indicator
Growth Signals15-20%Seat expansion, usage trendInvestment signals commitment
Support Health15-20%Ticket volume, sentiment, resolutionFrustration predicts churn
Financial5-10%Payment history, contract lengthFinancial commitment level
Churn Risk Factors
FactorRisk WeightDetection Method
Champion departureCriticalContact tracking, LinkedIn
Usage decline >30%HighProduct analytics
Negative NPS (0-6)HighSurvey responses
Support escalationsHighTicket analysis
Missed renewal meetingHighCSM activity tracking
Contract downgradeVery HighBilling data
Competitor mentionsHighCall transcripts, tickets
Budget review mentionsMediumCSM notes
The Analytics Stack
LayerPurposeTools/Methods
CollectionGather raw dataProduct events, CRM, support
ProcessingClean and transformETL, data pipelines
CalculationCompute scoresScoring algorithms
StorageHistorical trackingData warehouse
VisualizationPresent insightsDashboards, reports
ActionTrigger interventionsAlerting, automation
Key Metrics
MetricFormulaTarget
Health Score AccuracyChurn predicted / Actual churn>70%
Leading Indicator CorrelationCorrelation to outcomes>0.6
Score Distribution% in each health tierBell curve
Intervention Success RateSaved / Intervened>40%
Time to DetectionDays before risk → action<14 days
False Positive RateFalse alerts / Total alerts<20%
Executive Dashboard KPIs
KPIDefinitionBenchmark
Gross Revenue RetentionRetained ARR / Starting ARR85-95%
Net Revenue Retention(Retained + Expansion) / Starting100-130%
Logo RetentionRetained customers / Starting90-95%
Health Score AverageMean across customer base65-75
At-Risk RevenueARR with health <50<15%
Expansion RateCustomers expanded / Total15-30%
Cohort Analysis Framework
Cohort TypeSegments ByUse Case
Time-basedSign-up month/quarterRetention trends
BehavioralFeature usage patternsActivation success
Value-basedARR tierSegment economics
IndustryVerticalProduct-market fit
AcquisitionChannel/sourceMarketing efficiency

Anti-Patterns

  • Vanity health scores — Scores that look good but don't predict outcomes
  • Over-weighted product usage — Ignoring relationship and sentiment signals
  • Lagging indicator focus — Measuring what already happened
  • One-size-fits-all thresholds — Same scores mean different things for different segments
  • Manual-only health tracking — Can't scale without automation
  • Score without action — Calculating risk without intervention playbooks
  • Annual calibration only — Health models need continuous refinement
  • Ignoring data quality — Garbage in, garbage out

Comments

Markdown supported