메뉴
Use when defining or reviewing SaaS revenue, growth, retention, engagement, satisfaction, unit economics, or Rule-of-40 metrics.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/peterbamuhigire/chwezi-dev-engine --skill saas-business-metrics명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | saas-business-metrics |
| description | Use when defining or reviewing SaaS revenue, growth, retention, engagement, satisfaction, unit economics, or Rule-of-40 metrics. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
| Input | Required | Use |
|---|---|---|
| Tenant, product, and lifecycle scope | yes | Bound the SaaS decision |
| Current architecture, plans, policies, and constraints | yes | Preserve enforceable behaviour |
| Production data or verified evidence | conditional | Validate thresholds and migrations |
Default to read-only analysis. Change configuration, billing, identity, tenant data, infrastructure, or customer communications only with explicit authority, least-privilege credentials, tenant scope, rollback, and auditable approval. Never expose secrets or cross tenant boundaries.
If production access, policy, telemetry, or authoritative records are unavailable, produce a labelled design or dry-run plan. Do not claim deployment, reconciliation, deletion, delivery, or measured outcomes; list missing evidence and verification.
| Condition | Action | Stop condition |
|---|---|---|
| Tenant isolation, money, identity, or deletion is affected |
| Require approval and rollback evidence |
| Scope or authority is ambiguous |
| Evidence supports a reversible change | Stage, test, and record it | Acceptance checks fail |
| Only partial context is available | Return assumptions and validation | A production claim cannot be verified |
| Category | Artifact | Format | Example |
|---|---|---|---|
| Release evidence | SaaS metrics dashboard | Markdown doc plus dashboard link covering MRR/ARR/ARPU, CAC/LTV/payback, and churn/NRR/GRR | docs/metrics/saas-dashboard-2026-04-16.md |
Based on A Quick Guide to Software as a Service (Indocan Publications, 2022) and Dash (2025) Mastering Software Product Management.
The first principle of SaaS metrics: Measure outcomes, not activities. The number of features shipped, lines of code written, or support tickets closed are activities. MRR growth, churn rate, and NPS are outcomes.
MRR = Sum of all normalised monthly subscription revenue from active customers.
A healthy SaaS business has Expansion MRR > Churned MRR (negative net churn).
ARR = MRR × 12. Used for annual planning, valuations, and investor reporting.
Only include recurring subscription revenue. One-off implementation fees and professional services revenue are excluded from ARR.
ARPU = MRR ÷ Total Active Customers
CAC = Total Sales & Marketing Spend (period) ÷ New Customers Acquired (period)
CAC Payback = CAC ÷ (ARPU × Gross Margin %)
24 months payback is a warning sign — the business is burning cash to grow.
LTV = ARPU × Gross Margin % × Average Customer Lifetime
Average Customer Lifetime (months) = 1 ÷ Monthly Churn Rate
Example: ARPU = UGX 150,000/month; Gross Margin = 70%; Monthly Churn = 2%
LTV:CAC = LTV ÷ CAC
| Ratio | Interpretation |
|---|---|
| < 1:1 | Destroying value — each customer costs more than they will ever generate |
| 1:1 – 3:1 | Marginal — sustainable only if growth is very fast |
| 3:1 | Healthy benchmark for established SaaS |
| > 5:1 | Strong — may indicate underinvestment in growth (room to spend more on acquisition) |
Retention is the most important SaaS metric. Acquisition without retention fills a leaky bucket.
Logo Churn = Customers Lost ÷ Customers at Start of Period
Monthly target: < 2% for B2B SaaS; < 5% for B2C SaaS.
Revenue Churn = MRR Lost from Churned + Contracted Customers ÷ MRR at Start of Period
Revenue churn is more important than logo churn when customers have different-sized contracts.
NRR = (Starting MRR + Expansion MRR − Contraction MRR − Churned MRR) ÷ Starting MRR × 100%
| NRR | Interpretation |
|---|---|
| < 100% | Business shrinks even without losing a single customer |
| 100% | Flat — churn exactly offset by expansion |
| > 100% | Negative churn — existing customers generate more revenue than you lose |
| > 120% | World-class — seen in top enterprise SaaS companies |
GRR = (Starting MRR − Contraction MRR − Churned MRR) ÷ Starting MRR × 100%
GRR excludes expansion revenue. It measures purely how well you retain existing revenue. GRR can never exceed 100%.
Stickiness = Daily Active Users ÷ Monthly Active Users
20%: Good engagement for most B2B tools.
50%: Exceptional — product is used daily by most monthly users (messaging, task management).
Feature Adoption = Users who used feature at least once ÷ Total Active Users
The elapsed time from account creation to the moment a new user experiences the core value of the product. Minimising TTFV is the single most impactful lever for improving early retention.
NPS asks one question: "On a scale of 0–10, how likely are you to recommend [product] to a colleague?"
NPS = % Promoters − % Detractors
| NPS Range | Benchmark |
|---|---|
| < 0 | Poor — more detractors than promoters |
| 0–29 | Average |
| 30–69 | Good |
| ≥ 70 | World-class |
Always follow up NPS with an open-ended "Why did you give that score?" NPS alone tells you what; the open question tells you why.
CSAT asks: "How satisfied were you with [interaction/product]?" on a 1–5 or 1–10 scale. Calculated as % of respondents who gave a positive score (4 or 5 on a 5-point scale).
CSAT is transactional (measures a specific interaction). NPS is relational (measures overall loyalty).
CES asks: "How easy was it to [complete the task]?" on a 1–7 scale.
Low effort = high loyalty. CES is the strongest predictor of customer churn in support contexts. Every time a customer must work hard to use your product, churn probability increases.
Unit economics measure the per-customer profitability of the business model.
Gross Margin % = (Revenue − Cost of Goods Sold) ÷ Revenue × 100%
For SaaS, COGS includes: hosting, third-party APIs, customer support costs directly tied to delivering the service. It does not include sales, marketing, or R&D.
Healthy SaaS Gross Margin: 70–85%. Below 60% indicates a services-heavy model or infrastructure inefficiency.
Contribution Margin = Revenue − Variable Costs (per customer)
Used to evaluate whether adding one more customer increases or decreases profitability.
A single metric used to evaluate the overall health of a SaaS business.
Rule of 40 Score = Revenue Growth Rate % + Profit Margin %
Where Profit Margin is typically measured as EBITDA margin or Free Cash Flow margin.
| Score | Interpretation |
|---|---|
| < 20 | Concern — either growth is slow or the business is burning cash unsustainably |
| 20–40 | Acceptable for early-stage; concerning for mature SaaS |
| ≥ 40 | Healthy — used by investors as a benchmark for SaaS quality |
| > 60 | Exceptional |
Example: 60% revenue growth rate + (−15%) EBITDA margin = 45. Healthy. Example: 10% revenue growth rate + 5% EBITDA margin = 15. Concerning.
The Rule of 40 is an investor heuristic, not an operational target. Use it for external communication and strategic health checks, not for weekly product decisions.
| Term | Definition |
|---|---|
| Bookings | Total contract value signed (including future periods not yet billed) |
| Billings | Cash invoiced to customers in the period |
| Revenue | Cash recognised under accounting rules (deferred for prepaid annual contracts) |
An annual contract signed in December is a Booking and a Billing, but only 1/12 is recognised as Revenue in December.
When a customer pays for a 12-month subscription upfront, the unearned portion sits on the balance sheet as Deferred Revenue. It is a liability (you owe the service), not income. As each month passes, 1/12 is recognised as Revenue.
| Type | Characteristic | Examples |
|---|---|---|
| Lagging | Confirms what happened; cannot be acted on in real time | MRR, ARR, Churn Rate |
| Leading | Predicts future outcomes; actionable now | TTFV, Feature Adoption, Onboarding Completion |
Build your operational dashboard around leading indicators. Report lagging indicators to leadership and investors.
| Vanity Metric | Why It Is Misleading |
|---|---|
| Total registered users | Includes inactive accounts; inflates perceived traction |
| App downloads | Tells you nothing about usage or retention |
| Page views | Traffic without conversion is not a business |
| Features shipped | Output metric; does not measure customer or business outcome |
| Support tickets closed | Closing tickets faster does not mean fewer problems |
If a metric is used as a performance target, it will be gamed. (Goodhart's Law.) Pair every KPI metric with a counter-metric to detect gaming.
Example: Pair "Average ticket close time" with "Customer re-open rate." If close time drops and re-open rate rises, support agents are closing tickets prematurely.
product-strategy-vision (OKR Key Results should be drawn from leading metrics)software-pricing-strategy (MRR and churn data drive pricing decisions)competitive-analysis-pm (win rate and churn by segment are competitive intelligence), lean-ux-validation (metrics design for UX experiments)Every reported metric must fix its grain, denominator, currency, time boundary, source, owner, exclusions, and reconciliation rule before comparison or target-setting.
| Artefact | Consumer | Acceptance condition |
|---|---|---|
| SaaS metric dictionary and operating scorecard | Executive, finance, and growth teams | MRR movements reconcile, cohort and denominator rules are fixed, source systems are named, and each metric has an owner and decision threshold |