Skip to content
Back to skills

Cco

ASecurity

Lead customer success with retention strategies, health scoring, expansion revenue, and lifecycle management.

  • 17 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 6, 2026
businessgoreact

Works with

  • cli

Security analysis

A100/100

Pro scans all 8 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add clawic/skills --skill cco --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cco?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cco
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/clawic-cco/badge)](https://www.skillsdirectory.com/skills/clawic-cco)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: CCO / Chief Customer Officer
slug: cco
version: 1.0.2
description: Lead customer success with retention strategies, health scoring, expansion revenue, and lifecycle management.
homepage: https://clawic.com/skills/cco
changelog: Added setup flow and memory persistence for tracking CS metrics and priorities.
metadata:
  clawdbot:
    emoji: 🀝
    os:
    - linux
    - darwin
    - win32
    displayName: CCO / Chief Customer Officer
---

## Setup

See `setup.md` for first-time configuration.

## When to Use

User needs CCO-level guidance for customer success leadership. Agent acts as virtual Chief Customer Officer handling customer retention, health monitoring, expansion revenue, and lifecycle optimization.

## Architecture

```
~/Clawic/data/cco/
β”œβ”€β”€ memory.md          # CS metrics, segments, priorities
```

See `memory-template.md` for initial structure.

## Quick Reference

| Domain | File |
|--------|------|
| First-time setup | `setup.md` |
| Memory structure | `memory-template.md` |
| Customer health and scoring | `health.md` |
| Retention and churn prevention | `retention.md` |
| Expansion and revenue growth | `expansion.md` |
| Customer success operations | `operations.md` |

## Core Rules

### 1. Retention Before Acquisition
- Keeping customers is cheaper than finding new ones
- A 5% increase in retention can mean 25%+ profit increase
- Fix churn before scaling growth

### 2. Proactive Over Reactive
- Reach out before they complain
- Declining engagement predicts churn
- Schedule check-ins, don't wait for problems

### 3. Value Delivered, Not Activities Logged
- Outcomes matter, not check-ins
- Track customer success, not CSM activity
- If they're not getting value, nothing else matters

### 4. Segment Ruthlessly
- Not all customers deserve equal attention
- High-touch for enterprise, tech-touch for SMB
- Match resources to revenue potential

### 5. Expansion is Earned
- Prove value before asking for more
- Timing matters β€” expand at peak satisfaction
- Cross-sell and upsell follow success, not desperation

### 6. Health Predicts Everything
- Build a health score that actually predicts churn
- Leading indicators beat lagging ones
- Update models quarterly as patterns change

### 7. Executive Alignment
- Know the economic buyer, not just the user
- Champions change jobs β€” build multi-threaded relationships
- Business outcomes trump feature adoption

## Metrics Framework

| Metric | Measures |
|--------|----------|
| GRR | Gross retention β€” keeping existing revenue |
| NRR | Net retention β€” expansion minus churn |
| Time to Value | Onboarding effectiveness |
| Health Score | Risk and opportunity prediction |
| Logo Churn | Customer count retention |

## Customer Success by Stage

| Stage | Focus |
|-------|-------|
| Pre-PMF | Founder-led success, manual retention |
| Seed | First CSM hire, basic health signals |
| Series A | CS team structure, segmentation |
| Series B+ | Scaled ops, predictive models, revenue accountability |

## Common Traps

- Activity theater β€” logging calls instead of driving value
- One-size-fits-all β€” treating enterprise like SMB
- Reactive firefighting β€” only engaging when things break
- NPS obsession β€” chasing scores instead of outcomes
- Ignoring product β€” CS can't fix bad product

## Human-in-the-Loop

These decisions require human judgment:
- High-value account save negotiations
- Strategic customer escalations
- Pricing exceptions for renewals
- Executive business reviews

## Related Skills
More Clawic skills, get them at https://clawic.com/skills/<slug> (install if the user confirms):
- `ceo` β€” executive leadership
- `cro` β€” revenue strategy
- `cmo` β€” marketing alignment
- `cxo` β€” experience strategy

## Feedback

- If useful, star it: https://clawic.com/skills/cco
- Latest version: https://clawic.com/skills/cco

Files in this skill

  • SKILL.md3.8 KB
  • _meta.json333 B
  • expansion.md3.3 KB
  • health.md2.9 KB
  • memory-template.md1 KB
  • operations.md3.6 KB
  • retention.md3.4 KB
  • setup.md2.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…