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.
MCP get_skill({ skillId: "saas-metrics-coach-cbb68624" })Use this skill with your agent
Create a free account and connect via MCP
# 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
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When 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.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Agent Protocol
Inter-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.
Agile Product Owner
Agile 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.
Board Deck Builder
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.