Product Success Metrics and KPIs: How to Define, Track, and Report Them

Product success metrics are quantifiable measurements that show whether a product is meeting its business and user goals, typically across revenue, engagement, retention, and customer satisfaction. They turn a vague question like "is this product working?" into concrete numbers a product manager can act on. To measure product success, pair a leading indicator (a signal of what is about to happen, such as activation rate) with a lagging indicator (confirmation of what already happened, such as MRR), and tie both to one overarching goal, the North Star Metric.

Without agreed metrics, success is a matter of opinion. Ask three people on your team to define it and you will get three different answers. A SaaS or software business is more black and white than that. Some product success metrics are broadly agreed upon, and others are worth adding for your specific business model.

This guide covers how to define product success, which KPIs to track, and how to analyze them, including for a potential future exit through acquisition. For each metric you will find the formula or measurement method, examples from companies like Spotify, Slack, and Airbnb, and a step-by-step framework for choosing the right KPIs for your SaaS product. You will also find the AARRR Pirate Metrics framework, North Star Metric examples, and the vanity metrics to avoid.

These metrics matter for two reasons. They are decision-making points that lead the company to better product decisions. They also help product managers win executive approval for product investments more easily.

Four Types of Product Success Metrics

Product success metrics fall into a few types. Some predict the business or financial performance of a specific product. Others measure user engagement, keep user attention high, or show how content users are with the product. The sections below cover each type with examples and formulas.

Why Tracking the Wrong Metrics Hides Business Health

Metrics are not equal, and data does not equal data. Do not track the wrong stuff.

We see it over and over again. Businesses get extremely excited about showing us their metrics. "Look at this number!" "Check out this graph!"

Then you ask how the business is doing, and the answer is something like: "Well, we are not profitable, and if we do not raise another substantial round in the next six months, we are going out of business." The chart went up. The business did not.

How Do You Define Success Metrics for a Product?

Product goals usually align directly with business goals, and there are many possible business goals. Work backwards: state the business goal, work out what has to be true to reach it, then pick the product metrics that show progress toward it.

Here is a hypothetical SaaS example of how a business goal shapes a product goal and its metrics:

• Business Goal: Get acquired for $50M+ by 2027
• How to Reach Business Goal:
  • Expected multiple of 6.5x revenue
  • ARR needs to hit $7.7M (meaning MRR needs to hit $640,000)
• Product Goal to Reach Business Goal: Get as many users as possible as fast as possible and keep them as users.
  • Product Metric 1: MRR and ARR moving towards $7.7M
  • Product Metric 2: CAC < ARPU (for every customer you acquire, you make more revenue from them than it costs to acquire them)
  • Product Metric 3: CLTV is at least 7x CAC (if you spend $200 to acquire a user, they bring in a lifetime value of at least $1,400)

These goals and metrics would look very different for a founder whose business goal is: "Build a lifestyle business where the business profits more than $250,000 per year and I can work fewer than 15 hours per week."

Whatever the goal, a complete set of success metrics has the same shape: one North Star Metric, two or three leading indicators, and one or two lagging revenue metrics. For a broader view of how goals, roadmaps, and metrics fit together, see our guide to SaaS product management best practices.

Product Success Metrics Examples: Revenue, Marketing, and Satisfaction KPIs

The examples below are grouped by what they tell you about the product. For each metric you get a definition, why it matters, how to calculate it, and how to track it.

Revenue Product Metrics: MRR, ARPU, and CLTV

MRR (Monthly Recurring Revenue)

What is it? Monthly Recurring Revenue (MRR) is the predictable, consistent revenue generated from your subscription customers each month.

Why is it an important product metric? MRR shows the stability and growth potential of your business. It reflects the health of your subscription model and your ability to retain customers over time.

How do you calculate it? Add up the recurring revenue from all active subscriptions within a given month.

How do you track it? Use dedicated financial tools or a subscription management platform that monitors changes in recurring revenue over time.

ARPU (Average Revenue Per User)

What is it? Average Revenue Per User (ARPU) is the average revenue generated by each customer. It shows the value each customer brings to your business.

Why is it an important product metric? ARPU shows the revenue potential of your customer base and identifies the segments that contribute the most revenue.

How do you calculate it? Divide total revenue by the total number of customers within a specific time frame.

How do you track it? Aggregate revenue data and customer counts on a regular cadence and watch how the ratio moves over time.

CLTV (Customer Lifetime Value)

What is it? Customer Lifetime Value (CLTV) predicts the total value a customer will bring to your business over the course of the relationship.

Why is it an important product metric? CLTV shows the long-term impact of customer relationships and informs decisions about acquisition and retention strategy.

How do you calculate it? Multiply average purchase value by purchase frequency by customer lifespan.

How do you track it? Analyze customer behavior and purchase patterns over time, and refine the calculation as the data matures.

Product Marketing Metrics: Website Traffic, Bounce Rate, CPL, and CAC

Product marketing metrics show whether the top of the funnel is working and what each lead and customer costs to acquire. For a deeper look at this group, see our guide to product marketing KPIs.

Website Traffic

What is it? Website traffic is the number of visitors who access your website within a specific time frame.

Why is it an important product metric? Traffic reflects the reach and visibility of your brand and shows how effective your online presence and marketing efforts are.

How do you calculate it? Tools like Google Analytics count unique visitors over time.

How do you track it? Use website analytics tools to monitor and visualize traffic trends so you can make informed decisions.

Bounce Rate

What is it? Bounce rate is the percentage of visitors who leave your website after viewing only one page.

Why is it an important product metric? Bounce rate flags potential problems with website usability and content engagement, guiding improvements to the user experience.

How do you calculate it? Divide the number of single-page visits by the total number of visits.

How do you track it? Monitor bounce rate in your web analytics tool and check how website changes affect engagement.

CPL (Cost Per Lead)

What is it? Cost Per Lead (CPL) is the average cost of acquiring a single lead through your marketing efforts.

Why is it an important product metric? CPL measures the efficiency of lead generation campaigns and guides budget allocation and campaign optimization.

How do you calculate it? Divide the total cost of a marketing campaign by the number of leads it generated.

How do you track it? Record campaign costs and leads generated so you can compare CPL across marketing initiatives.

CMQL (Cost per Marketing Qualified Lead)

What is it? Cost per Marketing Qualified Lead (CMQL) is the cost of acquiring leads that meet specific marketing criteria indicating potential to convert.

Why is it an important product metric? CMQL shows how well your lead targeting and segmentation work, so the leads you acquire have higher conversion potential.

How do you calculate it? Divide the total cost of a campaign by the number of leads that meet your marketing qualification criteria.

How do you track it? Monitor campaign results and lead quality, and refine your acquisition strategy accordingly.

CSQL (Cost per Sales Qualified Lead)

What is it? Cost per Sales Qualified Lead (CSQL) is the cost of acquiring leads that meet sales-specific criteria indicating a higher likelihood of conversion.

Why is it an important product metric? CSQL aligns marketing efforts with sales objectives, so the leads passed to sales are more likely to close.

How do you calculate it? Divide the total campaign cost by the number of leads that meet your sales qualification criteria.

How do you track it? Regularly review how well marketing and sales criteria line up, and refine the qualification process.

CAC (Customer Acquisition Cost)

What is it? Customer Acquisition Cost (CAC) is the average cost of acquiring a new customer, including all marketing and sales expenses.

Why is it an important product metric? CAC shows how efficient your acquisition strategy is, which helps you manage costs and optimize the sales funnel.

How do you calculate it? Divide the total cost of marketing and sales activities by the number of new customers acquired.

How do you track it? Continuously monitor acquisition costs and check how changes in channels or campaigns move your CAC.

Product Customer Satisfaction Metrics: NPS and DAU/MAU

NPS (Net Promoter Score)

What is it? Net Promoter Score (NPS) measures customer loyalty by asking how likely customers are to recommend your product or service to others.

Why is it an important product metric? NPS reveals customer satisfaction and loyalty and guides efforts to improve the customer experience.

How do you calculate it? Subtract the percentage of detractors (unlikely to recommend) from the percentage of promoters (likely to recommend).

How do you track it? Collect NPS through surveys and track the score over time to see whether customer sentiment improves. AnnounceKit has NPS software you can implement easily.

Daily Active User (DAU) / Monthly Active User (MAU) Ratio

What is it? The DAU/MAU ratio compares daily active users to monthly active users, which shows how frequently users engage with your product.

Why is it an important product metric? The ratio reflects engagement patterns and shows how consistently users interact with the product.

Engaged users also give you more chances to reach them. When you launch a new feature (perhaps one that requires an additional investment, and therefore lifts CLTV), you can announce it through a release notes tool so users actually see the new features and releases.

How do you calculate it? Count unique users in a day (DAU) and unique users in a month (MAU). Divide DAU by MAU and multiply by 100.

How do you track it? Monitor DAU and MAU regularly and use the ratio to spot changes in engagement behavior.

Why One Healthy Metric Is Not Enough

Say you have an excellent CAC (Customer Acquisition Cost). But people are not actually engaging with your product.

In that case you do not have a sustainable business, even though one product success metric looks really healthy. Metrics are important, but they are not the end-all-be-all. There is a bigger story to tell, and the frameworks below help you tell it.

Frameworks for Choosing Product Success Metrics: AARRR, RARRA, and the North Star Metric

Picking individual metrics in isolation is one of the most common mistakes in product management. Without a guiding framework, teams track dozens of numbers that move independently of each other. The result is a dashboard that looks impressive but does not answer the only question that matters: is the product growing in a healthy way? Three frameworks have become the practical standard for organizing product success metrics into a coherent system.

AARRR (Pirate Metrics) Framework

AARRR was coined by Dave McClure and nicknamed "Pirate Metrics" because of how it sounds. It groups product KPIs into five stages of the customer lifecycle: Acquisition, Activation, Retention, Referral, and Revenue. Each stage has its own primary metric.

Acquisition tracks how users find your product (visits, signups, traffic source quality). Activation measures whether new users reach a meaningful first experience (activation rate, time to value). Retention shows whether users come back (DAU/MAU ratio, weekly active users).

Referral captures whether users invite others (viral coefficient, NPS). Revenue closes the loop with MRR, ARPU, and CLTV. The power of AARRR is that it forces you to track the funnel end to end rather than fixating on a single number.

RARRA Framework

RARRA is a re-ordering of AARRR proposed by Thomas Petit and Gabor Papp for modern PLG and mobile SaaS products, where acquiring users is expensive and the bottleneck has moved to keeping them. The order becomes Retention, Activation, Referral, Revenue, Acquisition. Retention sits at the top because an unretained user is a leaky bucket that no marketing budget can fill. If your product has strong product-market fit but weak ad ROAS, RARRA is the better lens. If you are still searching for product-market fit, AARRR is more useful because it surfaces where the funnel breaks earliest.

The North Star Metric (NSM)

The North Star Metric is the single number that best captures the value your product delivers to users. Unlike AARRR, which is a multi-metric framework, the NSM is a forcing function: every team aligns around moving one number, and every other KPI feeds into it as an input metric. Well-known examples make the idea concrete. Spotify uses "minutes listened", Airbnb uses "nights booked", Slack uses "messages sent within a team", and Facebook used "monthly active users" in its early growth years. A good North Star Metric is a leading indicator of revenue, reflects real user value rather than engagement for its own sake, and is sensitive enough to move with product changes.

Activation Rate, Time to Value, and Feature Adoption: The PLG Metrics

The shift to product-led growth has pushed three metrics from the activation stage of AARRR into the spotlight. They are arguably the most important early-funnel signals for any modern SaaS product, because they predict retention long before churn shows up.

Activation Rate

Activation Rate is the percentage of new users who reach a defined "aha moment" within their first session or first few days. The exact moment varies by product. For Slack it was sending 2,000 team messages, for Dropbox it was uploading a file to a folder, and for Facebook it was adding 7 friends in 10 days.

Formula: Activation Rate = (Users who hit the activation event ÷ Total new signups) × 100. A healthy SaaS activation rate sits between 25% and 40% depending on category. Below 20% almost always means the onboarding flow is broken.

Time to Value (TTV) and Time to First Value (TTFV)

Time to Value is the elapsed time between signup and the moment a user first experiences the core benefit of the product. Time to First Value (TTFV) applies the same idea to the very first meaningful action: the smallest possible win that proves the product works. Measurement: median or 75th-percentile minutes or hours from the signup timestamp to the first activation event timestamp. Lowering TTV is the single highest-leverage onboarding investment most teams can make. Every minute removed from time to first value typically lifts week-1 retention by 1 to 3 percentage points.

Feature Adoption Rate

Feature Adoption Rate is the percentage of active users who use a specific feature within a defined time window. It tells you whether the features you ship actually move the needle or sit unused in the UI. Formula: Feature Adoption Rate = (Monthly active users of feature X ÷ Total monthly active users) × 100.

Pair feature adoption with release notes and changelog announcements to close the loop on launches. If a feature lifts adoption above 30% within 30 days of launch and lifts retention as a downstream effect, it is a genuine win. AnnounceKit's release notes and in-app announcements help you tie launch communication to feature adoption metrics, and our guide on how to announce new features to drive product adoption covers the communication side in detail. See also the feature adoption and user education use case.

Churn Rate and Retention Rate: Formulas and Benchmarks

Churn and retention are the same coin viewed from opposite sides, and they are the two metrics most directly tied to long-term SaaS revenue. A product can post stellar acquisition numbers and still die quietly if churn compounds in the background. That is why every serious product team tracks both at multiple cadences.

Customer Churn Rate

Customer Churn Rate is the percentage of customers who cancel or stop using the product over a given period. Formula: Customer Churn Rate = (Customers lost during period ÷ Customers at start of period) × 100. Healthy SaaS churn benchmarks vary by segment. SMB SaaS typically sees 3 to 5% monthly churn, mid-market 1 to 2%, and enterprise under 1% (often measured annually instead). Track gross churn (raw cancellations) alongside net churn (which subtracts upgrades and expansion revenue from the same cohort) to get a true picture of revenue health.

Retention Rate

Retention Rate is the percentage of users from a starting cohort who are still active at the end of a defined period. Formula: Retention Rate = (Users active at end of period ÷ Users at start of period) × 100. The most useful version is the cohort retention curve, which plots day-1, day-7, day-30, and day-90 retention for each weekly or monthly signup cohort. A curve that flattens, rather than one that keeps declining, is the signature of strong product-market fit. It shows the product has a stable base of users who keep coming back instead of a churning treadmill.

New Product Success Metrics: What to Track in the First 90 Days

Launching a new product or major feature creates a different measurement problem than running an established product. There are no historical baselines yet, the user base is small, and early data is noisy. The metrics below are designed for the first 30 to 90 days after launch, when teams need to decide whether to double down or pivot.

Launch-specific metrics to track:

• Sign-up velocity: daily new signups in the first 30 days, compared against the next-best comparable launch in your portfolio.
• Day-1 activation rate: percentage of new signups who hit the activation event on the day they sign up, a strong leading indicator of overall fit.
• Week-1 retention: percentage of week-0 signups who return in week 1; under 20% almost always means the offer or onboarding misses.
• Feature engagement breadth: average number of distinct features used per user in the first session, which tells you whether the launch communicated the value clearly.
• Qualitative NPS / first-session sentiment: a one-question post-onboarding survey (0 to 10) gathered automatically inside the product.
• Channel attribution split: share of activations coming from product-led signals (release notes, in-app announcements) versus paid acquisition.

Tie launch metrics to your product release management process. That is what separates teams that learn from each launch from teams that ship and forget. Every launch should produce a written 30-day retrospective with these numbers attached, so the next launch starts smarter than the last. The announcement itself is part of the launch, so it pays to know how to write a new product announcement that drives the activation you plan to measure.

Vanity Metrics to Avoid (and What to Track Instead)

Vanity metrics are numbers that look impressive in slides but do not predict business outcomes or guide decisions. They go up and to the right almost by default, which makes teams feel productive without revealing whether the product actually works. The five most common offenders are:

• Total signups (cumulative): always grows, never shrinks, and says nothing about whether new users actually use the product. Replace with weekly active signups or activated users.
• Total page views: unweighted traffic without conversion context. Replace with conversion rate by page or the traffic-to-activated-user ratio.
• Total downloads (mobile): a download is not a user. Replace with day-1 and day-7 retention from the install cohort.
• Time on site / time on page: can mean engagement or confusion. Replace with task-completion rate or session-to-conversion rate.
• Social media followers: visible but disconnected from product usage. Replace with referral traffic that activates and engagement-to-signup conversion rate.

The litmus test for whether a metric is vanity or actionable is simple: if the metric goes up by 20%, can you point to a specific decision that would change? If yes, it is actionable. If the answer is "we would celebrate," it is vanity.

How Do You Measure Product Success? A 4-Step Framework

Choosing the right product success metrics is not about copying another company's dashboard. It is about translating your product's specific goals into a measurement system. The four-step framework below is what most high-functioning product teams use to set up KPIs from scratch.

1. Set the goal. Write down, in one sentence, what success looks like for your product over the next 12 months. "Hit $5M ARR" is a goal. "Improve engagement" is not, because it is too vague to measure.
2. Identify the user behaviors that signal success. Work backwards from the goal: what do users have to actually do for that goal to be met? If the goal is $5M ARR, the signals are likely "convert from trial to paid", "stay paid for 12+ months", and "expand seats".
3. Pick one North Star Metric and 4 to 6 input KPIs. The NSM should capture the user value most tied to your goal (for example, "weekly active teams"). The input KPIs are the levers that move the NSM (activation rate, week-4 retention, feature adoption rate, NPS, churn rate).
4. Define the reporting cadence and accountability. Each metric needs an owner, a review cadence (weekly for input KPIs, monthly for the NSM and revenue), and a target. Without targets, metrics are just decoration.

Then evaluate the product against three benchmarks: its own historical baseline (is it growing month over month?), its category benchmarks (is it growing faster than typical SaaS in the same segment?), and its goal targets (is it on pace for its OKRs?). A product is on track when retention is flat or improving, MRR is growing faster than churn, and the North Star Metric is moving in the planned direction quarter over quarter.

Treat this as a living system rather than a one-time exercise. Most high-performing teams run one North Star Metric, 4 to 6 input KPIs, and 10 to 20 supporting diagnostic metrics that get reviewed only when something looks off. Review the set quarterly: if a number has not influenced a decision in three months, retire it; if a question keeps coming up that no metric answers, add one. For channel-specific metrics, see product management metrics and KPIs for mobile apps, which goes deeper into the mobile KPI stack.

Conversion Rate: Formula and SaaS Benchmarks

Conversion Rate is the percentage of users who complete a desired action. Most often that means moving from one funnel stage to the next: from free trial to paid subscriber, from visitor to signup, or from onboarding to first activation. It is arguably the most actionable single metric in product management, because every percentage point of improvement compounds directly into revenue without additional acquisition spend.

Formula: Conversion Rate = (Users who completed the action ÷ Total users who had the opportunity) × 100

For SaaS products, trial-to-paid conversion typically ranges from 2% to 5% for freemium models and 15% to 25% for time-limited free trials with active sales involvement. A conversion rate below 2% on a self-serve trial almost always signals a mismatch between the value promised in marketing and the value experienced during onboarding. To diagnose low conversion, pair it with activation rate and time to value. Most conversion problems are really activation problems in disguise.

Track conversion rate at every major funnel transition, not just the final purchase event. Visitor-to-signup, signup-to-activated, activated-to-retained, and retained-to-expanded are all conversion moments that compound into each other. Improving visitor-to-signup conversion by 20% while holding all downstream rates constant lifts final revenue by the same 20%.

Revenue Growth Rate: Formula and Benchmarks

Revenue Growth Rate measures how quickly a company's top-line revenue is expanding over a given period, expressed as a percentage. MRR captures the absolute level of recurring revenue and ARPU captures per-user efficiency. Revenue Growth Rate captures velocity: the speed at which the business is getting larger. Investors, acquirers, and boards use it as one of the first screens for business health.

Formula: Revenue Growth Rate = ((Revenue in Period B - Revenue in Period A) ÷ Revenue in Period A) × 100

A widely cited benchmark for early-stage SaaS is the "Triple, Triple, Double, Double, Double" rule: triple ARR in years one and two, then double it in years three, four, and five on the way to $100M ARR. At a more operational level, most growth-stage SaaS products target 15 to 30% month-over-month growth in the early scaling phase, settling toward 8 to 12% monthly growth as the base grows. Always report Revenue Growth Rate alongside net revenue churn. A 20% growth rate with 15% annual churn is much less healthy than a 15% growth rate with 2% annual churn, because net expansion is the more durable engine.

Break Revenue Growth Rate down into its components: new business growth, expansion revenue growth (upsells and seat additions from existing customers), and churned revenue loss. When total growth slows, this decomposition pinpoints whether the problem is acquisition, expansion, or churn. Each requires a different product response.

Customer Effort Score (CES): How to Measure Friction

Customer Effort Score (CES) measures how much effort a customer had to exert to accomplish a specific task with your product, such as completing onboarding, finding a feature, resolving a support issue, or finishing a workflow. Research from Gartner and the Corporate Executive Board found that reducing customer effort is a stronger predictor of loyalty than delighting customers: 94% of customers who report low effort intend to repurchase, while 96% of those who report high effort intend to churn or defect.

Measurement: CES is collected through a single post-interaction survey question: "How easy was it to [complete this task] with [product]?" Responses use a 7-point scale from "Very Difficult" (1) to "Very Easy" (7). CES = average score across all respondents. Higher is better.

CES is especially useful for finding friction in the critical path of your product, the sequence of steps every user must complete to reach core value. A single high-effort step can suppress activation and retention for an entire cohort even when every other metric looks healthy. Common high-effort hotspots include integration setup, data import, permission configuration, and billing workflows. The best teams track CES at the task level (for example, "connect your first integration") rather than only at the account level, which shows exactly where to invest UX resources.

Use CES alongside NPS for a complete customer health picture. NPS captures overall relationship satisfaction, while CES captures moment-to-moment friction. They often diverge: a customer can love your product and still score a specific workflow poorly on CES. That is exactly the signal your product and design teams need.

Stickiness: The DAU/MAU Ratio as a Standalone Metric

Stickiness is the ratio of daily active users (DAU) to monthly active users (MAU), and it is the canonical measure of how habitual product usage has become. A stickiness ratio of 50% means the average user engages on 15 of every 30 days, a strong sign the product is part of their daily workflow. A ratio of 10% means the average user drops in only 3 days per month, which usually indicates an occasional tool rather than one embedded in core workflows.

Formula: Stickiness = (DAU ÷ MAU) × 100

Benchmark targets vary widely by category. Consumer social products (Facebook, Twitter) historically targeted 50%+ stickiness. B2B SaaS products built around daily workflows, such as project management, Slack-style communication, and CRMs used by sales teams, typically see 25 to 50%. Products used weekly rather than daily by design (payroll tools, quarterly review software) should use a WAU/MAU ratio instead. DAU/MAU will systematically understate their engagement and mislead the team.

Stickiness is a leading indicator of expansion revenue and a lagging indicator of activation quality. Products with high stickiness see higher NPS, lower churn, and higher upgrade rates, because daily users are both more satisfied and more exposed to upsell opportunities inside the product. If stickiness is low for your category, the root cause is almost always activation. Users who never internalize a daily use case never develop the habit that drives a high DAU/MAU ratio.

KPIs for New Product Development: Time to Market, Defect Density, and Velocity

Most product KPI frameworks focus on user behavior and revenue outcomes, the downstream results of what engineering builds. Product development KPIs measure the health and velocity of the build process itself. They matter because slow, bug-heavy development directly suppresses product-led growth.

If time to market is long, competitors ship faster. If defect density is high, customer satisfaction erodes. If team velocity degrades, roadmap commitments slip. High-performing product organizations track development KPIs alongside user-facing product performance metrics so they can intervene on the input side before output metrics degrade.

Time to Market

Time to Market (TTM) is the elapsed calendar time from the moment a feature enters active development (the first engineering sprint) to the moment it is live in production for all customers. It is the most direct measure of organizational speed.

Formula: TTM = Production release date - Development start date. Benchmarks vary by team size and tech stack. Most high-performing teams at the 25-person stage target 2 to 6 weeks for a significant feature and under 1 week for an iteration or fix. Reducing TTM requires process improvements (smaller batch sizes, faster code review, continuous deployment pipelines) and architectural decisions (modular systems that allow isolated feature releases without system-wide rebuilds).

Defect Density

Defect Density is the number of confirmed software defects per unit of code, typically measured as bugs per 1,000 lines of code (KLOC) or bugs per feature shipped per sprint. It is the primary measure of code quality and test coverage.

Formula: Defect Density = Total defects ÷ Size of the software module (KLOC or feature count). Industry averages run between 1 and 25 defects per KLOC depending on system complexity and domain. Products with robust automated test suites typically see under 5 per KLOC. High defect density correlates directly with more support tickets, lower customer satisfaction, and engineering time diverted from new features to bug fixes, which in turn degrades Time to Market.

Team Velocity

Team Velocity is the average number of story points (or equivalent effort units) a development team completes per sprint. It is a capacity planning metric rather than a performance measurement. The goal is not to maximize velocity for its own sake but to measure it consistently, so sprint commitments and roadmap timelines become predictable.

Formula: Velocity = Total story points completed ÷ Number of sprints (rolling average, typically over 3 to 5 sprints). A healthy velocity trend is stable or slowly growing.

A sudden drop signals blockers (technical debt, team disruption, unclear requirements) that need active intervention. Never use velocity to compare teams. It is an internal calibration tool, not a performance ranking.

Feature Adoption Rate (as a Development KPI)

Feature Adoption Rate closes the loop between the development process and user outcomes. Tracked as a development KPI, it answers whether the features the team shipped last cycle are being used. A team with high velocity and low feature adoption is shipping the wrong things fast. Pair feature adoption rate with a 30-day post-ship review for every significant feature. If adoption is below 15% at day 30, the feature has a UX problem, a discoverability problem, or a product-market fit problem, and each calls for a different response.

The HEART Framework for UX Metrics

The HEART Framework is a structured UX measurement system developed by Google's research team (Kerry Rodden, Hilary Hutchinson, and Xin Fu). It brings the same rigor to user experience measurement that engineering teams apply to system performance. Where AARRR and RARRA measure business funnel health, HEART measures the quality of the experience itself, the signal most closely tied to whether users find the product genuinely valuable rather than merely tolerable.

HEART stands for five dimensions. Happiness is users' subjective satisfaction and attitude toward the product, measured through CSAT, NPS, or CES. Engagement is the depth and frequency of interaction beyond active sessions: features used per session, actions completed, content consumed.

Adoption covers new users acquiring the product and completing first-time use of core features; activation rate is the primary adoption metric. Retention is whether users return over time, measured with cohort retention curves and churn rate. Task Success is whether users accomplish specific in-product tasks efficiently: completion rate, error rate, and time on task per workflow.

The framework is designed to run alongside a Goals-Signals-Metrics (GSM) process. For each HEART dimension, first define the goal ("we want users to find the dashboard valuable"), then identify the behavioral signal that shows the goal is being met ("users who view the dashboard weekly"), then select the metric that captures that signal ("weekly dashboard view rate"). This three-step process prevents the common mistake of picking metrics first and retrofitting them to goals.

For SaaS product teams, the most actionable HEART dimensions are usually Adoption, Retention, and Task Success, because they pinpoint specific product interactions that can be improved. Happiness metrics like NPS are useful but slower-moving. Engagement metrics can mislead if the product is designed for efficient in-and-out use rather than deep sessions. Apply HEART selectively: pick the 2 or 3 dimensions most relevant to your current strategic priority and track the rest at lower frequency.

Earned Growth Rate (EGR)

Earned Growth Rate (EGR) was introduced by Fred Reichheld (the creator of NPS) and Bain & Company as a complement to NPS. It measures how much of a company's revenue growth is "earned" through genuinely satisfied customers, meaning returning customers and customers acquired through referrals, versus purchased through advertising and promotional spending. It separates organic, loyalty-driven growth from paid growth, which can mask structural product weaknesses behind an aggressive marketing budget.

Formula: EGR = (Net Revenue Retention Rate + Earned New Customer Revenue Rate) - 100%

Net Revenue Retention (NRR) captures how much of last year's revenue base remained and expanded this year. Earned New Customer Revenue Rate captures the share of new customer revenue that came from referrals or organic word of mouth rather than paid channels. A company with 110% NRR and 30% of new revenue from referrals has an EGR of approximately 40%, meaning nearly half its total growth is compounding from customer satisfaction rather than marketing spend.

EGR is especially valuable for product-led growth companies because it makes the financial case for investing in product experience rather than paid acquisition. If EGR is rising, satisfied customers are becoming your most efficient growth engine. If EGR is flat or falling while total revenue growth looks healthy, you are paying more and more to replace customers who are not recommending you, which is a structurally fragile position. Track EGR quarterly alongside NPS and net revenue churn to see whether your product is building durable loyalty or simply buying growth.

AARRR vs. RARRA vs. North Star Metric: Which Framework Should You Use?

The most widely used product metrics frameworks answer different questions and suit different business stages. Rather than debating which is "best," high-functioning product teams treat them as complementary lenses. The table below summarizes the key differences so you can choose the right starting point for your product's current stage.

Framework	Order of Priority	Best For	Core Question	Primary Risk It Addresses
AARRR (Pirate Metrics)	Acquisition → Activation → Retention → Referral → Revenue	Early-stage products still finding product-market fit; companies where the biggest unknown is where the funnel breaks	Where is the funnel leaking?	Spending on acquisition before the product is ready to retain users
RARRA	Retention → Activation → Referral → Revenue → Acquisition	PLG / mobile SaaS products with proven product-market fit but high acquisition costs; companies where leaky retention is compounding the CAC problem	Are we retaining the users we pay to acquire?	Filling a leaky bucket faster rather than fixing the leak first
North Star Metric	Single metric + input KPIs	Growth-stage and scale-up companies that need cross-team alignment; teams where each function optimizes its own metric at the expense of system-wide health	Is the product delivering its core value at increasing scale?	Local optimization: marketing, product, and engineering each moving different numbers in different directions
HEART	Happiness → Engagement → Adoption → Retention → Task Success	UX-heavy products where the user experience is the primary competitive differentiator; teams running redesigns or major onboarding changes	Are users genuinely satisfied and successful with the product?	Optimizing funnel metrics while silently degrading the user experience

A practical starting point for most SaaS teams: use AARRR to diagnose where the funnel breaks, adopt RARRA as the operating lens once retention is the primary constraint, define a North Star Metric when cross-team alignment becomes the bottleneck, and apply HEART to any major UX investment so you measure the quality of the experience, not just the quantity of the outcomes.