If you run a product-led growth strategy, the metrics that matter most are not signups, page views, or MQL volume. According to Appcues' guide to measuring PLG success, those figures "feel productive but don't tell you whether your product is actually driving growth." What matter instead are behavioral signals that connect what users do inside your product to the revenue outcomes your business depends on. The practical answer for SaaS leaders: organize your metrics around the Product-Led Growth Flywheel — Activation, Adoption, Adoration, Advocation — and start by measuring two foundational Activation metrics, Time-to-Value (TTV) and Activation Rate. This guide shows you how to define and calculate both, and how to use the flywheel to find where your user journey is underperforming.

The PLG Flywheel Framework: A Holistic View

ProductLed's definitive guide for SaaS businesses, authored by Eric Keating, recommends using the Product-Led Growth Flywheel — Activation, Adoption, Adoration, Advocation — to map metrics to each stage of the user lifecycle. Activation focuses on getting users to an "Aha!" moment, with Time-to-Value as the metric to track and continually reduce. Adoption asks what healthy usage looks like, benchmarked against the behaviors of regular value-getting users, such as logins, features used, and breadth of usage. Adoration and Advocation capture satisfaction and the willingness of existing users to recommend the product, driving growth through your installed base rather than your sales team.

The framework's value is diagnostic, not decorative. Appcues describes it as "the navigational spine of your PLG measurement system," noting that it prevents teams from measuring in silos: product teams tend to own activation and engagement metrics, growth teams own acquisition and conversion, and finance owns unit economics — but in a PLG model, all of these connect, and changes at one stage ripple through the rest. When you read a metric, you should always know which flywheel stage it belongs to and which downstream stage it feeds.

ProductLed also cautions against metric sprawl. There is no universal "best" PLG KPI; it depends on what matters most for your company's performance. Their guidance is to create a short list of three to five KPIs aligned with your goals, and to assign a specific owner — typically a growth team member — rather than passing responsibility around.

Activation Stage: Defining the 'Aha!' Moment

Before you can calculate anything, you must define the "Aha!" moment: a specific user action or event that signifies the user has experienced the product's core value. This is where most measurement efforts go wrong. Userpilot's guide to TTV, written by James Mitchinson, identifies the most common mistake: "treating the first value event as a label rather than a measurement specification." Calling it "first report generated" is a label; specifying the exact event, its properties, and the conditions under which it counts is a measurement specification.

Be equally careful not to confuse activity with value. FullSession's Roman Mohren is blunt about what first value is not: "It's not logging in. It's not finishing the onboarding checklist. It's the specific outcome that proves the product works: sharing the first workflow for a project management tool, or generating the first report that changes a decision for an analytics platform." Your users don't care about your features; they care about their outcomes, and TTV is the distance between those two things.

How do you validate that your candidate event is genuinely the first value event rather than a plausible guess? Userpilot recommends validation through cohort retention analysis: compare retention of users who completed the event against those who did not. If the event truly marks first value, the cohorts should diverge visibly. Only after this validation should you treat the event as the endpoint of your Activation measurements.