saas-metrics-coach
$
npx mdskill add alirezarezvani/claude-skills/saas-metrics-coachAnalyzes SaaS financial health using key metrics and benchmarks
- Evaluates business performance using ARR, MRR, churn, LTV, CAC, and NRR
- Uses scripts like metrics_calculator.py and benchmarks from references/benchmarks.md
- Calculates ratios, growth rates, and payback periods to assess unit economics
- Delivers plain-English insights and prioritized recommendations for improvement
SKILL.md
.github/skills/saas-metrics-coachView on GitHub ↗
--- name: saas-metrics-coach description: 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. license: MIT metadata: version: 1.0.0 author: Abbas Mir category: finance updated: 2026-03-08 --- # 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.
More from alirezarezvani/claude-skills
- a11y-auditAccessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
- ab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
- ad-creativeWhen the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
- adversarial-reviewerAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
- aeoAnswer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
- agent-designerUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
- agent-protocolInter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
- agent-workflow-designerDesign production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
- agenthubMulti-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
- agile-product-ownerAgile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.