Solo Unicorn Club logo

Company Packs

Customer Success Hub

Seven agents scoring health, predicting churn, and driving renewals

B2B SaaS CS teamspost-sale revenue orgsrenewal-focused operators

Why buy

This one sells on retention economics: buyers already know a saved renewal is worth far more than the package price.

// First 7 days

What can be running fast.

01

spot churn sooner

02

Ship a usable package with 14 included files and working structure.

03

Move from purchase to first setup in about 15 min.

// Included files

What is inside the package.

company.yaml
agents/health-scorer.md
agents/churn-predictor.md
agents/outreach-planner.md
agents/ticket-analyzer.md
agents/renewal-tracker.md
agents/feedback-collector.md
agents/cs-manager.md
workflows/health-check.yaml
workflows/renewal-pipeline.yaml
skills/health-scoring.md
skills/churn-signals.md
mcp-servers.json
README.md

Description

What is Customer Success Hub?

Proactive customer success. Health scoring, churn prediction, automated outreach, ticket analysis, renewal tracking, and feedback collection.

solo-unicornclaude-code

Upgrade path

  • 01Start with this package and validate the workflow.
  • 02Add specialized skills or bundles once the core system is stable.
  • 03Use the community to sharpen positioning, demos, and feedback loops.
Previewcompany.yaml
# company.yaml
name: customer-success-hub
version: "1.0"
description: Proactive customer success operations

agents:
  - id: health-scorer
    role: "Score customer health from usage and engagement data"
    skills: [health-scoring, metric-aggregation]
    mcp_servers: [mixpanel, intercom]
    triggers:
      - cron: "0 6 * * *"
        action: daily-health-scores

  - id: churn-predictor
    role: "Predict churn risk and recommend interventions"
    skills: [churn-signals, risk-modeling]
    upstream: [health-scorer]
    output:
      format: json
      destination: churn-alerts/

// Community acceleration

Use the room after the purchase.

Bring your workflow into the Solo Unicorn community for sharper feedback, operator critique, and more visibility once the system is live.

Discuss implementation