saas-metrics-coach
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.
Best use case
saas-metrics-coach is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using saas-metrics-coach should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/saas-metrics-coach/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How saas-metrics-coach Compares
| Feature / Agent | saas-metrics-coach | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agent for SaaS Idea Validation
Use AI agent skills for SaaS idea validation, market research, customer discovery, competitor analysis, and documenting startup hypotheses.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# 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. ```bash # 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) ```bash 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. ```bash 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.
Related Skills
saas-scaffolder
Generates complete, production-ready SaaS project boilerplate including authentication, database schemas, billing integration, API routes, and a working dashboard using Next.js 14+ App Router, TypeScript, Tailwind CSS, shadcn/ui, Drizzle ORM, and Stripe. Use when the user wants to create a new SaaS app, start a subscription-based web project, scaffold a Next.js application, or mentions terms like starter template, boilerplate, new project, or wiring up auth and payments.
saas-health
Calculate SaaS health metrics (ARR, MRR, churn, CAC, LTV, NRR) and benchmark against industry standards. Usage: /saas-health <metrics|quick-ratio|simulate> [options]
founder-coach
Personal leadership development for founders and first-time CEOs. Covers founder archetype identification, delegation frameworks, energy management, CEO calendar audits, leadership style evolution, blind spot identification, imposter syndrome, founder mental health, and succession planning. Use when a founder feels like the bottleneck, struggles to delegate, is burning out, transitioning from IC to executive, managing a board, or when user mentions founder mode, CEO growth, leadership development, delegation, burnout, or imposter syndrome.
wiki-query
Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>"
wiki-log
Show recent entries from the LLM Wiki log (wiki/log.md). Uses the standardized
wiki-lint
Run a health check on the LLM Wiki vault — mechanical checks (orphans, broken links, stale pages, missing frontmatter, log gap, duplicates) plus semantic checks (contradictions, cross-reference gaps, concepts missing their own page). Outputs a markdown report with suggested actions. Usage /wiki-lint [--stale-days N] [--log-gap-days N]
wiki-init
Bootstrap a fresh LLM Wiki vault with the three-layer structure, schema files, and starter templates. Usage /wiki-init <path> --topic "<topic>" [--tool all|claude-code|codex|cursor|antigravity]
wiki-ingest
Ingest a source file from raw/ into the LLM Wiki — read, discuss, write summary page, update cross-references across 5-15 pages, regenerate index, append to log. Usage /wiki-ingest <path-to-source>
tc
Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]
tc-tracker
Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.
llm-wiki
Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
karpathy-coder
Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.