To fix a problem, you first have to measure it correctly. For StaffWise, a subscription-based HR and workforce management platform, revenue stagnation wasn’t caused by poor acquisition, but leakage from failed payments, refunds, and customer churn.
The first step in solving this was to agree on clear, business-aligned definitions for every metric in the analysis.
Key Metrics Mapped for the Analysis
The analysis focuses on:
- Expected Revenue (ARR/MRR)
- Definition: The recurring revenue StaffWise should generate if every active subscription is paid in full.
- Purpose: Establishes the “perfect world” benchmark to compare against.
- Realized Revenue
- Definition: Actual revenue collected after accounting for payment failures, refunds, and downgrades.
- Purpose: Reveals the true health of the billing pipeline.
- Revenue Loss (Gap Analysis)
- Definition: Difference between expected and realized revenue.
- Purpose: Quantifies leakage and prioritizes what to fix first.
- Churn Rate (by Plan and Cycle)
- Definition: % of subscribers canceling or failing to renew within a billing period, segmented by monthly vs. annual plans.
- Purpose: Identifies where customer retention efforts should focus.
- Refund Rate
- Definition: % of collected payments returned to customers.
- Purpose: Flags product or service quality issues driving dissatisfaction.
- Failed Payment Rate
- Definition: % of attempted subscription renewals that do not process successfully.
- Purpose: Highlights technical or card-related friction points.
Designing a Metrics Hierarchy
Each metric rolls up into one question:
How much money is StaffWise leaving on the table, and why?
By structuring metrics this way, every calculation supports actionable decisions:
- Which plan types are bleeding revenue?
- Are refunds a customer-experience issue or a billing policy issue?
- Should the team invest more in churn reduction, payment recovery, or both?