Product Management Metrics Glossary: 40+ Definitions for PMs
Complete glossary of product management metrics with definitions, formulas, benchmarks, and links to free calculators
Every metric a PM needs, in one page.
How to Use This Glossary
Five categories: SaaS economics, growth, prioritization, experimentation, execution. Each metric includes a concise definition, the formula you need, a benchmark to aim for, and a red flag to watch out for. Where a free PM Toolkit calculator exists, you will find a direct link.
Bookmark this page. Come back whenever you need a quick refresher before a board meeting, quarterly review, or stakeholder conversation.
The benchmarks below are general industry ranges, not hard rules. They move with company stage, segment, and business model. SaaS churn, NRR, and GRR bands track to the public SaaS benchmark surveys (KeyBanc, OpenView); NPS tiers follow Bain's loyalty research; the PMF threshold is Sean Ellis's 40% survey rule. Treat every number here as directional and check it against your own cohort before quoting it in a board meeting.
SaaS Economics Metrics
These metrics define the financial engine of a subscription business. If you only learn one category, make it this one. SaaS economics metrics tell you whether your business model is sustainable and where to focus investment.
LTV (Customer Lifetime Value)
Definition: The total revenue a business expects to earn from a single customer over the entire duration of their relationship.
Formula: ARPU / Monthly Churn Rate or ARPU x Average Customer Lifespan
Good Benchmark: LTV should be at least 3x your CAC. Top SaaS companies achieve 5x or higher.
Red Flag: LTV below your CAC means you lose money on every customer you acquire.
CAC (Customer Acquisition Cost)
Definition: The total cost of acquiring a new customer, including all sales and marketing expenses divided by the number of new customers gained.
Formula: Total Sales and Marketing Spend / Number of New Customers Acquired
Good Benchmark: LTV:CAC ratio greater than 3:1. Enterprise SaaS often targets 5:1.
Red Flag: Rising CAC without a corresponding rise in LTV signals an unsustainable growth model.
LTV:CAC Ratio
Definition: The ratio comparing the lifetime value of a customer to the cost of acquiring them. This is arguably the single most important unit economics metric.
Formula: LTV / CAC
Good Benchmark: 3:1 to 5:1. Below 3:1 suggests underspending on growth or poor retention. Above 5:1 may mean you are underinvesting in acquisition.
Red Flag: A ratio below 1:1 means you are paying more to acquire customers than they will ever return.
Calculate your LTV:CAC Ratio →
MRR (Monthly Recurring Revenue)
Definition: The predictable, recurring revenue a business earns each month from all active subscriptions.
Formula: Sum of all monthly subscription amounts
Good Benchmark: Healthy SaaS companies grow MRR at 10-20% month-over-month in early stages.
Red Flag: Flat or declining MRR despite active customer acquisition signals a churn problem.
ARR (Annual Recurring Revenue)
Definition: The annualized value of recurring revenue. This is the standard metric for measuring the scale of a SaaS business.
Formula: MRR x 12
Good Benchmark: $1M ARR is often called the first major milestone for SaaS startups.
Red Flag: ARR growing slower than your burn rate means you are running out of runway.
ARPU (Average Revenue Per User)
Definition: The average amount of revenue generated per active user over a given period, typically monthly.
Formula: Total Revenue / Total Active Users
Good Benchmark: Varies widely by segment. Track trends over time rather than comparing across companies.
Red Flag: Declining ARPU often indicates pricing pressure or a shift toward lower-value customer segments.
ARPA (Average Revenue Per Account)
Definition: Similar to ARPU but measured at the account level rather than the individual user level. More common in B2B contexts where a single account may have multiple users.
Formula: Total Revenue / Total Active Accounts
Good Benchmark: Rising ARPA indicates successful upselling and expansion within existing accounts.
Red Flag: ARPA declining while user count grows suggests you are adding seats without capturing additional value.
Churn Rate
Definition: The percentage of customers who cancel or stop using your product within a given time period.
Formula: Customers Lost During Period / Customers at Start of Period x 100
Good Benchmark: Below 5% monthly for SMB SaaS, below 2% monthly for mid-market, below 1% for enterprise.
Red Flag: Monthly churn above 7% means you are replacing nearly your entire customer base every year.
Revenue Churn (MRR Churn)
Definition: The percentage of monthly recurring revenue lost due to cancellations and downgrades in a given period.
Formula: Lost MRR During Period / MRR at Start of Period x 100
Good Benchmark: Below 2% monthly. Best-in-class SaaS companies achieve negative net revenue churn through expansion.
Red Flag: Revenue churn exceeding customer churn means your highest-value customers are leaving.
Calculate your Revenue Churn →
NRR (Net Revenue Retention)
Definition: The percentage of recurring revenue retained from existing customers over a period, including expansion, contraction, and churn. This captures the full picture of how well you grow within your customer base.
Formula: (Starting MRR + Expansion MRR - Contraction MRR - Churned MRR) / Starting MRR x 100
Good Benchmark: Above 110%. Best-in-class SaaS lands around 120%+.
Red Flag: NRR below 100% means your existing customer base is shrinking, forcing you to rely entirely on new sales.
GRR (Gross Revenue Retention)
Definition: The percentage of recurring revenue retained from existing customers excluding expansion. This isolates how well you prevent revenue loss.
Formula: (Starting MRR - Contraction MRR - Churned MRR) / Starting MRR x 100
Good Benchmark: Above 85%. Enterprise SaaS typically achieves 90-95%.
Red Flag: GRR below 80% indicates a serious retention problem that expansion alone cannot fix.
CAC Payback Period
Definition: The number of months it takes to recover the cost of acquiring a customer through their subscription payments.
Formula: CAC / (ARPU x Gross Margin)
Good Benchmark: Under 12 months. Venture-backed companies may tolerate up to 18 months for high-LTV segments.
Red Flag: Payback periods over 24 months create severe cash flow pressure and increase exposure to churn risk.
Calculate your CAC Payback Period →
ROI (Return on Investment)
Definition: The percentage return generated relative to the cost of an investment. Used across product development, marketing campaigns, and strategic initiatives.
Formula: (Gain from Investment - Cost of Investment) / Cost of Investment x 100
Good Benchmark: Positive ROI is the baseline. Strong product investments target 200%+ ROI over 12-18 months.
Red Flag: Negative ROI on recurring initiatives signals a need to pivot or cut investment.
Growth and Engagement Metrics
Growth metrics tell you whether people are finding, using, and sticking with your product. These are the leading indicators that predict future revenue. Strong engagement today means strong retention tomorrow.
DAU (Daily Active Users)
Definition: The number of unique users who engage with your product on a given day. The definition of "active" varies by product and should be tied to a meaningful action, not just a login.
Formula: Count of unique users performing a qualifying action in a single day
Good Benchmark: Absolute numbers depend on market size. Track growth rate and consistency rather than raw count.
Red Flag: DAU declining while MAU stays flat means engagement depth is weakening.
MAU (Monthly Active Users)
Definition: The number of unique users who engage with your product at least once during a 30-day period.
Formula: Count of unique users performing a qualifying action in a 30-day window
Good Benchmark: Consistent month-over-month growth. Compare against your total registered user base to understand activation.
Red Flag: MAU growing slower than sign-ups indicates an activation or onboarding problem.
DAU/MAU Ratio (Stickiness)
Definition: The proportion of monthly active users who use the product on any given day. This measures how essential your product is to daily workflows.
Formula: DAU / MAU
Good Benchmark: Above 20% for SaaS products. Social and communication apps target 50%+.
Red Flag: DAU/MAU below 10% for a tool that should be used daily suggests the product is not habit-forming.
Calculate your DAU/MAU Ratio →
WAU (Weekly Active Users)
Definition: The number of unique users who engage with your product at least once during a 7-day period. Useful for products with weekly usage patterns such as project management or reporting tools.
Formula: Count of unique users performing a qualifying action in a 7-day window
Good Benchmark: WAU/MAU above 40% indicates healthy weekly engagement.
Red Flag: Sharp drops in WAU during specific weeks may indicate reliance on external triggers rather than organic habit.
Conversion Rate
Definition: The percentage of users who complete a desired action out of the total number who had the opportunity. Applied to sign-ups, trials, purchases, upgrades, and more.
Formula: Number of Conversions / Total Visitors or Users x 100
Good Benchmark: 2-5% for website visitors to free trial. 10-25% for free trial to paid. Varies significantly by funnel stage.
Red Flag: Conversion rate declining while traffic grows usually signals a targeting or messaging mismatch.
Calculate your Conversion Rate →
Retention Rate
Definition: The percentage of existing users who continue to use your product over a given time period. The inverse perspective of churn, measured from the users who remain.
Formula: (Users at End of Period - New Users During Period) / Users at Start of Period x 100
Good Benchmark: 35-40% Day-30 retention for mobile apps. 80%+ monthly retention for SaaS.
Red Flag: Retention flattening at a very low percentage means your product lacks a durable core use case.
Calculate your Retention Rate →
N-Day Retention
Definition: The percentage of users who return to your product exactly N days after their first use. Commonly tracked at Day 1, Day 7, Day 14, and Day 30 to map the retention curve.
Formula: Users active on Day N / Users who started on Day 0 x 100
Good Benchmark: Day-1 retention above 40% for consumer apps, above 80% for SaaS. Day-30 above 20% for consumer, above 60% for SaaS.
Red Flag: A steep drop between Day 1 and Day 7 indicates users do not find enough value during onboarding.
Analyze your Retention Curves →
NPS (Net Promoter Score)
Definition: A measure of customer loyalty based on a single question: "How likely are you to recommend this product to a friend or colleague?" Responses on a 0-10 scale classify users as Promoters (9-10), Passives (7-8), or Detractors (0-6).
Formula: % Promoters - % Detractors
Good Benchmark: Above 30 is considered good. Above 50 is excellent. Above 70 is world-class.
Red Flag: Negative NPS means more customers would actively discourage others from using your product.
PMF Score (Product-Market Fit Score)
Definition: A composite score measuring how well a product meets market demand. Often based on the Sean Ellis survey question: "How would you feel if you could no longer use this product?" combined with additional signals.
Formula: Multi-signal weighted score incorporating survey responses, engagement, and retention data
Good Benchmark: Above 65 on a 100-point scale. The classic PMF threshold is 40%+ of users saying they would be "very disappointed" without the product.
Red Flag: PMF score below 40 suggests the product has not yet found its core audience or value proposition.
Activation Rate
Definition: The percentage of new sign-ups who complete a predefined key action that correlates with long-term retention. This is the "aha moment" metric.
Formula: Users completing key action / Total new sign-ups x 100
Good Benchmark: 25-40% for self-serve SaaS products. The specific action must be validated through retention cohort analysis.
Red Flag: Low activation rate combined with high sign-up volume means your onboarding experience is failing.
Viral Coefficient (K-Factor)
Definition: A measure of how many new users each existing user generates through referrals or sharing. A K-factor above 1 means exponential organic growth.
Formula: Average Invites Sent per User x Invite Conversion Rate
Good Benchmark: Above 0.5 provides meaningful organic growth. Above 1.0 enables true viral growth.
Red Flag: K-factor near zero means growth depends entirely on paid acquisition.
Prioritization Metrics
Prioritization metrics help you decide what to build next. Without a systematic scoring approach, roadmap decisions default to opinion and politics. These frameworks turn subjective debates into structured evaluations.
RICE Score
Definition: A prioritization framework that scores initiatives based on four factors: Reach, Impact, Confidence, and Effort. Developed at Intercom to make prioritization more objective and comparable.
Formula: (Reach x Impact x Confidence) / Effort
Good Benchmark: Use RICE to rank items relative to each other rather than targeting an absolute score. The highest-scoring items should align with strategic goals.
Red Flag: All items scoring similarly suggests your estimates need more granularity, or you are not differentiating enough between high and low confidence.
ICE Score
Definition: A simplified prioritization framework scoring initiatives on Impact, Confidence, and Ease. Faster to apply than RICE, making it suitable for rapid triage.
Formula: (Impact + Confidence + Ease) / 3
Good Benchmark: Use the average to compare items within the same backlog. Recalibrate scales periodically.
Red Flag: Over-reliance on ICE without periodically validating scores against actual outcomes leads to score inflation.
Weighted Score
Definition: A flexible prioritization method where you define custom criteria, assign weights reflecting strategic importance, and score each feature against every criterion.
Formula: Sum of (Weight x Score) for each criterion
Good Benchmark: The framework is as good as the criteria you choose. Align weights with current business priorities.
Red Flag: Too many criteria (more than 7) dilute the differentiation between items and create scoring fatigue.
WSJF (Weighted Shortest Job First)
Definition: A prioritization method from SAFe (Scaled Agile Framework) that divides the cost of delay by the job duration. Items with the highest WSJF are prioritized first.
Formula: Cost of Delay / Job Duration
Good Benchmark: Prioritize items where the cost of delay is high and the job duration is short. These deliver the fastest economic impact.
Red Flag: Ignoring job duration leads to prioritizing large, high-value items that block the pipeline for months.
Opportunity Score
Definition: A framework based on Outcome-Driven Innovation (ODI) that identifies underserved customer needs by comparing how important a job is versus how satisfied customers are with current solutions.
Formula: Importance + (Importance - Satisfaction)
Good Benchmark: Scores above 12 (on a 1-10 scale for each factor) indicate strong opportunities.
Red Flag: Building features where satisfaction already matches importance means you are over-serving a need.
Impact/Effort Matrix
Definition: A 2x2 grid that plots features or initiatives by their expected impact (high/low) against the effort required (high/low). The four quadrants are Quick Wins, Big Bets, Fill-Ins, and Money Pits.
Formula: Visual placement based on estimated impact and effort scores.
Good Benchmark: Prioritize Quick Wins (high impact, low effort) first. Invest strategically in Big Bets (high impact, high effort).
Red Flag: Spending time on Money Pits (low impact, high effort) is a resource trap.
Build your Impact/Effort Matrix →
Kano Categories
Definition: A model that classifies product features into five categories based on how they affect customer satisfaction: Must-be (expected basics), One-dimensional (more is better), Attractive (delightful surprises), Indifferent (no impact), and Reverse (causes dissatisfaction).
Formula: Classification through paired functional/dysfunctional survey questions and a lookup table.
Good Benchmark: Ensure all Must-be features are solid before investing in Attractive features.
Red Flag: Treating Indifferent features as high priority wastes resources on things customers do not care about.
Experimentation Metrics
Experimentation metrics ensure your product decisions are backed by statistical evidence, not gut feeling. Understanding these concepts is the difference between running valid experiments and fooling yourself with noisy data.
Statistical Significance
Definition: A measure of whether an observed difference between experiment variants is likely real or simply due to random chance. Typically assessed using a p-value threshold.
Formula: Determined through a hypothesis test. A result is statistically significant if p-value < 0.05 (the conventional threshold).
Good Benchmark: Use a significance level (alpha) of 0.05 for most product experiments. High-stakes decisions may warrant 0.01.
Red Flag: Calling a test "significant" before reaching the required sample size produces unreliable results.
P-Value
Definition: The probability of observing the measured difference (or a more extreme one) assuming the null hypothesis is true. In product experiments, a low p-value suggests the variant genuinely differs from the control.
Formula: Calculated through a statistical test (Z-test, T-test, or Chi-squared) based on sample sizes and observed rates.
Good Benchmark: Below 0.05 is the standard threshold. Below 0.01 provides stronger evidence.
Red Flag: A p-value of 0.04 does not mean there is a 96% chance your variant is better. It means there is a 4% chance of seeing this result if there were truly no difference.
Confidence Interval
Definition: A range of values within which the true effect of a change is likely to fall, given a specified confidence level (usually 95%).
Formula: Observed Effect +/- Margin of Error, where margin of error depends on sample size and variance.
Good Benchmark: A 95% confidence interval that does not cross zero indicates a statistically significant effect.
Red Flag: Very wide confidence intervals mean your sample size is too small to draw meaningful conclusions.
Sample Size
Definition: The number of observations (users, sessions, transactions) required to detect a statistically meaningful difference between experiment variants with adequate power.
Formula: Depends on baseline conversion rate, minimum detectable effect, significance level, and power. Calculated using standard formulas or online tools.
Good Benchmark: Calculate before launching any experiment. Never decide sample size after looking at results.
Red Flag: Running experiments with insufficient sample size leads to both false positives and missed real effects.
Calculate Required Sample Size →
MDE (Minimum Detectable Effect)
Definition: The smallest difference between control and variant that your experiment is designed to reliably detect. Smaller MDEs require larger sample sizes.
Formula: Determined during pre-test planning based on baseline rate, desired power, and significance level.
Good Benchmark: 5-10% relative MDE is practical for most product experiments. 1-2% MDE requires very large traffic.
Red Flag: Setting an MDE that is too large means you might miss meaningful improvements. Setting it too small means tests run for months.
Power (Statistical Power)
Definition: The probability that your experiment will correctly detect a true effect when one exists. Power is the complement of a Type II error (false negative).
Formula: 1 - Beta, where Beta is the probability of a false negative.
Good Benchmark: 80% power is the standard minimum. Critical experiments should target 90%.
Red Flag: Running underpowered experiments means you will frequently fail to detect real improvements, leading to the false conclusion that nothing works.
Lift
Definition: The percentage difference in a key metric between the variant and the control in an experiment.
Formula: (Variant Metric - Control Metric) / Control Metric x 100
Good Benchmark: Depends entirely on context. A 5% lift in conversion rate on a high-traffic page can be worth millions.
Red Flag: Celebrating lift without confirming statistical significance is a common and costly mistake.
Execution Metrics
Execution metrics measure how efficiently your team delivers value. They bridge the gap between strategy (what to build) and delivery (how fast you ship). These metrics also include market sizing, which is fundamental to strategic planning.
Sprint Velocity
Definition: The number of story points (or other units of work) a team completes in a single sprint. Used for forecasting capacity and planning future iterations.
Formula: Total Story Points Completed in a Sprint
Good Benchmark: Velocity should stabilize over 4-6 sprints. Consistent velocity (low variance) matters more than high velocity.
Red Flag: Velocity that swings wildly from sprint to sprint makes planning unreliable and often indicates unclear scope or unstable team composition.
Cycle Time
Definition: The elapsed time from when work actively begins on a task to when it is completed and delivered. This measures execution speed within your development process.
Formula: Completion Timestamp - Work Start Timestamp
Good Benchmark: 2-5 days for standard features. Under 1 day for bug fixes. Track the median, not the mean.
Red Flag: Cycle time increasing over successive sprints often indicates growing technical debt or process bottlenecks.
Lead Time
Definition: The total elapsed time from when a request is made (ticket created, feature requested) to when the work is delivered to the customer. Lead time includes waiting time plus cycle time.
Formula: Delivery Timestamp - Request Timestamp
Good Benchmark: Under 2 weeks for most feature requests. The gap between lead time and cycle time reveals queuing inefficiencies.
Red Flag: Lead time that is 5x or more longer than cycle time means work sits in queues far longer than it takes to complete.
Story Points
Definition: A relative unit of measure used in agile development to estimate the size, complexity, and risk of a user story or task. Story points are not hours; they represent relative effort compared to a baseline story.
Formula: Assigned through team estimation (planning poker, T-shirt sizing, or similar techniques).
Good Benchmark: The specific scale matters less than consistency. Most teams use a Fibonacci-like sequence (1, 2, 3, 5, 8, 13).
Red Flag: Using story points to measure individual developer productivity undermines their purpose and erodes team trust.
TAM (Total Addressable Market)
Definition: The total revenue opportunity available if a product achieved 100% market share. This is the theoretical maximum, representing the full demand for the type of product or service.
Formula: Total number of potential customers x Annual revenue per customer (top-down) or built up from segment-level analysis (bottom-up).
Good Benchmark: TAM should be large enough to justify the investment. Venture-backed startups typically target TAMs of $1B+.
Red Flag: A TAM that is too small limits growth ceiling. A TAM that is unrealistically large suggests sloppy analysis.
SAM (Serviceable Addressable Market)
Definition: The portion of the TAM that your product can realistically serve given its features, geography, distribution model, and current capabilities.
Formula: TAM x Percentage reachable with your business model
Good Benchmark: SAM is typically 20-50% of TAM for focused products. Define your filters clearly: geography, segment, use case.
Red Flag: SAM that equals TAM suggests you have not thought critically about product-market constraints.
SOM (Serviceable Obtainable Market)
Definition: The portion of the SAM that you can realistically capture in the near term, given your current resources, competitive position, and go-to-market strategy.
Formula: SAM x Realistic capture percentage
Good Benchmark: SOM is typically 1-10% of SAM for startups in year one. Mature companies may capture 20-40% of SAM.
Red Flag: SOM projections above 25% of SAM without clear competitive advantages are almost always overestimates.
Putting It All Together
Metrics do not exist in isolation. They form a connected system:
- Lowering churn increases LTV, which improves your LTV:CAC ratio and shortens CAC payback
- Improving activation drives better retention, which compounds into higher DAU/MAU and NPS
- Faster cycle time means more experiments per quarter. More experiments means more winners.
- Better prioritization (RICE, ICE, Weighted) focuses effort on high-impact work, improving ROI
Start with the metrics most relevant to your current role and product stage. Learn the formulas. Use the calculators. Over time, build an intuition for how these numbers connect and influence one another. Most of the work is understanding how a change in one metric ripples into the others.
Quick Reference Table
| Metric | Category | Key Formula | Good Benchmark |
|---|---|---|---|
| LTV | SaaS Economics | ARPU / Churn Rate | 3x+ CAC |
| CAC | SaaS Economics | Sales and Marketing / New Customers | LTV:CAC > 3:1 |
| MRR | SaaS Economics | Sum of monthly subscriptions | 10-20% MoM growth |
| Churn Rate | SaaS Economics | Lost Customers / Starting Customers | Less than 5% monthly |
| NRR | SaaS Economics | Revenue retained including expansion | Above 110% |
| DAU/MAU | Growth | DAU / MAU | Above 20% |
| Conversion Rate | Growth | Conversions / Visitors | 2-5% top of funnel |
| NPS | Growth | % Promoters - % Detractors | Above 30 |
| RICE | Prioritization | (R x I x C) / E | Relative ranking |
| Sample Size | Experimentation | Pre-test calculation | Plan before testing |
| Velocity | Execution | Story Points per Sprint | Stable variance |
| TAM | Execution | Total market revenue opportunity | Large enough to justify investment |