agentleFS
sp1esp1e/claude-skills/business-metrics-calculator/SKILL.md

business-metrics-calculator

Skill1 starsChanged 34 days agoMITView on GitHub

Standard business metric calculation with industry benchmarks. Use when calculating SaaS metrics (MRR, churn, LTV, CAC), e-commerce KPIs, or product analytics metrics with proper definitions.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Business Metrics Calculator

When to use

  • Preparing a board or investor deck and need accurately defined metrics
  • The team disagrees on how a key metric (e.g., churn) should be calculated
  • Benchmarking performance against industry standards
  • Building a metrics report for a new business or new metric set
  • Validating that existing metric calculations match the standard definition

Process

  1. Identify the business model and period — confirm the model type (SaaS subscription, e-commerce, marketplace, product/app) and the calculation period (month, quarter, trailing 12M). Model type determines which metrics apply. See references/metric_definitions.md.
  2. Load and validate the underlying data — check for expected row counts, missing values, and plausible date ranges. A metrics report is only as good as the data feeding it.
  3. Calculate primary metrics — for SaaS: MRR, ARR, new MRR, churned MRR, expansion MRR, customer churn rate, revenue churn rate. For e-commerce: GMV, AOV, conversion rate, ROAS. Use scripts/saas_metrics.py or adapt for other models.
  4. Calculate unit economics — LTV (simple average and cohort-based), CAC, LTV:CAC ratio, payback period, and quick ratio. Document which assumptions were used for LTV lifetime.
  5. Compare to benchmarks — grade each metric against the industry benchmark thresholds in references/metric_definitions.md (good / average / poor). Flag anything outside the acceptable range.
  6. Produce the metrics report — assemble results into assets/metrics_report_template.md with trend charts, benchmark comparison, and 3–5 key insights. Document any definition choices that differ from industry standard.

Inputs the skill needs

  • Subscription or transaction data with at minimum: customer ID, date, value, status
  • Marketing spend data (for CAC calculation)
  • Monthly targets or goals (for vs-target comparisons)
  • The agreed-upon metric definitions (or default to industry standard)
  • Time period and any segmentation required (by plan, region, cohort)

Output

  • scripts/saas_metrics.py — calculates standard SaaS metrics from a subscriptions CSV; includes MRR waterfall, churn, LTV/CAC
  • references/metric_definitions.md — canonical definitions and benchmark thresholds by model type
  • assets/metrics_report_template.md — structured report: revenue metrics, customer metrics, unit economics, benchmark comparison, insights

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.