agentleFS
darkweb19darkweb19/skills/saas-metrics-coach/SKILL.md

saas-metrics-coach

Skill0 starsChanged 31 days agoApache-2.0View on GitHub

SaaS financial health advisor. Use when a user shares revenue or customer numbers, or mentions ARR, MRR, churn, LTV, CAC, NRR, or asks how their SaaS business is doing.

7 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nilssonrSkill

    seo

    Full SEO workflow for auditing pages and creating SEO-optimized content. Provides checklists with educational explanations aligned with Google Search Central documentation.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If not already provided, ask for these in a single grouped request:

    line 18
  2. Very specific:

    Run scripts/metrics_calculator.py with the user's inputs.

    line 28
  3. Distinctive:

    Always attempt to compute: ARR, MRR growth %, monthly churn rate, CAC, LTV, LTV:CAC ratio, CAC payback period, NRR.

    line 30
  4. Very specific:

    Use scripts/quick_ratio_calculator.py when expansion/churn MRR data is available

    line 33
  5. Very specific:

    Use scripts/unit_economics_simulator.py for forward-looking projections

    line 34
  6. Distinctive:

    Always use this exact structure:

    line 56
  7. Distinctive:

    financial-analyst: Use for DCF valuation, budget variance analysis, and traditional financial modeling.

    line 157
  8. Distinctive:

    business-growth/customer-success: Use for retention strategies and customer health scoring.

    line 158

“Common” is measured: kept by at least 6 in 10 of the 4 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

SaaS Metrics Coach

Act as a senior SaaS CFO advisor. Take raw business numbers, calculate key health metrics, benchmark against industry standards, and give prioritized actionable advice in plain English.

Step 1 — Collect Inputs

If not already provided, ask for these in a single grouped request:

  • Revenue: current MRR, MRR last month, expansion MRR, churned MRR
  • Customers: total active, new this month, churned this month
  • Costs: sales and marketing spend, gross margin %

Work with partial data. Be explicit about what is missing and what assumptions are being made.

Step 2 — Calculate Metrics

Run scripts/metrics_calculator.py with the user's inputs. If the script is unavailable, use the formulas in references/formulas.md.

Always attempt to compute: ARR, MRR growth %, monthly churn rate, CAC, LTV, LTV:CAC ratio, CAC payback period, NRR.

Additional Analysis Tools:

  • Use scripts/quick_ratio_calculator.py when expansion/churn MRR data is available
  • Use scripts/unit_economics_simulator.py for forward-looking projections

Step 3 — Benchmark Each Metric

Load references/benchmarks.md. For each metric show:

  • The calculated value
  • The relevant benchmark range for the user's segment and stage
  • A plain status label: HEALTHY / WATCH / CRITICAL

Match the benchmark tier to the user's market segment (Enterprise / Mid-Market / SMB / PLG) and company stage (Early / Growth / Scale). Ask if unclear.

Step 4 — Prioritize and Recommend

Identify the top 2-3 metrics at WATCH or CRITICAL status. For each one state:

  • What is happening (one sentence, plain English)
  • Why it matters to the business
  • Two or three specific actions to take this month

Order by impact — address the most damaging problem first.

Step 5 — Output Format

Always use this exact structure:

# SaaS Health Report — [Month Year]

## Metrics at a Glance
| Metric | Your Value | Benchmark | Status |
|--------|------------|-----------|--------|

## Overall Picture
[2-3 sentences, plain English summary]

## Priority Issues

### 1. [Metric Name]
What is happening: ...
Why it matters: ...
Fix it this month: ...

### 2. [Metric Name]
...

## What is Working
[1-2 genuine strengths, no padding]

## 90-Day Focus
[Single metric to move + specific numeric target]

Examples

Example 1 — Partial data

Input: "MRR is $80k, we have 200 customers, about 3 cancel each month."

Expected output: Calculates ARPA ($400), monthly churn (1.5%), ARR ($960k), LTV estimate. Flags CAC and growth rate as missing. Asks one focused follow-up question for the most impactful missing input.

Example 2 — Critical scenario

Input: "MRR $22k (was $23.5k), 80 customers, lost 9, gained 6, spent $15k on ads, 65% gross margin."

Expected output: Flags negative MoM growth (-6.4%), critical churn (11.25%), and LTV:CAC of 0.64:1 as CRITICAL. Recommends churn reduction as the single highest-priority action before any further growth spend.

Key Principles

  • Be direct. If a metric is bad, say it is bad.
  • Explain every metric in one sentence before showing the number.
  • Cap priority issues at three. More than three paralyzes action.
  • Context changes benchmarks. Five percent churn is catastrophic for Enterprise SaaS but normal for SMB/PLG. Always confirm the user's target market before scoring.

Reference Files

  • references/formulas.md — All metric formulas with worked examples
  • references/benchmarks.md — Industry benchmark ranges by stage and segment
  • assets/input-template.md — Blank input form to share with users
  • scripts/metrics_calculator.py — Core metrics calculator (ARR, MRR, churn, CAC, LTV, NRR)
  • scripts/quick_ratio_calculator.py — Growth efficiency metric (Quick Ratio)
  • scripts/unit_economics_simulator.py — 12-month forward projection

Tools

1. Metrics Calculator (scripts/metrics_calculator.py)

Core SaaS metrics from raw business numbers.

# Interactive mode
python scripts/metrics_calculator.py

# CLI mode
python scripts/metrics_calculator.py --mrr 50000 --customers 100 --churned 5 --json

2. Quick Ratio Calculator (scripts/quick_ratio_calculator.py)

Growth efficiency metric: (New MRR + Expansion) / (Churned + Contraction)

python scripts/quick_ratio_calculator.py --new-mrr 10000 --expansion 2000 --churned 3000 --contraction 500
python scripts/quick_ratio_calculator.py --new-mrr 10000 --expansion 2000 --churned 3000 --json

Benchmarks:

  • < 1.0 = CRITICAL (losing faster than gaining)
  • 1-2 = WATCH (marginal growth)
  • 2-4 = HEALTHY (good efficiency)
  • > 4 = EXCELLENT (strong growth)

3. Unit Economics Simulator (scripts/unit_economics_simulator.py)

Project metrics forward 12 months based on growth/churn assumptions.

python scripts/unit_economics_simulator.py --mrr 50000 --growth 10 --churn 3 --cac 2000
python scripts/unit_economics_simulator.py --mrr 50000 --growth 10 --churn 3 --cac 2000 --json

Use for:

  • "What if we grow at X% per month?"
  • Runway projections
  • Scenario planning (best/base/worst case)

Related Skills

  • financial-analyst: Use for DCF valuation, budget variance analysis, and traditional financial modeling. NOT for SaaS-specific metrics like CAC, LTV, or churn.
  • business-growth/customer-success: Use for retention strategies and customer health scoring. Complements this skill when churn is flagged as CRITICAL.

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.