How Do Leading SaaS Companies Measure Onboarding Success?

Every figure below comes from a 10-Q, 10-K, 8-K exhibit or investor release dated February to September 2026. They are retention outcomes: how much revenue from last year's customers is still there today. A good onboarding program produces them twelve months later; they are not how the program is measured while it runs.

The metric names differ (net revenue retention, net dollar retention, net ARR expansion) and so do the definitions behind them, so the rows are not directly comparable. Several companies segment the rate: monday.com reports 115% for customers over $50K ARR against 109% overall. And Cloudflare states the purpose plainly in its 10-Q: "Our dollar-based net retention rate is a key way we measure our performance in these areas." Retention is the scoreboard. Onboarding is measured somewhere else.

For a fair target at your size and contract value, use the churn benchmarks page, not this table. The definition and maths of net revenue retention are on their own page.

The measurements underneath those rates are product events with a time window, chosen because the company checked which behaviours its retained customers shared. The table lists only what the companies have described themselves, in a blog post, documentation, a filing or a first-person interview with a named employee.

Two patterns run through the table. The activation event is always a count of a core action inside a window: 2,000 messages, a conversation threshold in three months, a Zap that ran within 24 hours, a video viewed within a week. Nobody uses "logged in" or "completed onboarding". And setup is kept separate from activation: Intercom's Day Zero milestones are configuration steps that predict retention; its Activation milestone is usage.

One caution on kind: HubSpot's onboarding model is in its 10-K and its retention rates are on earnings calls, but the blog article recommending time to value is guidance for HubSpot's readers, not a disclosure of its own onboarding metric.

Three published datasets put numbers on onboarding-level measurement. Know the methodology before you quote one in a deck.

• OpenView's 2022 Product Benchmarks (450+ product-led founders and CEOs): "87% of standout PLG companies identify and track activation". A statement about who measures, not what the rate is.
• Kyle Poyar of OpenView, on Amplitude's blog, put the rate itself at only 20 to 30% of new users reaching activation at standout PLG companies. Activation is a minority outcome even at the best-run product-led businesses.
• Mixpanel's 2024 Benchmarks Report (7,700+ customers): "In 2023, the average week one retention rate across industries fell from 50% to 28%." User-level, across consumer and B2B products, so use it as a shape (steep first-week drop-off), not as a B2B account target.
• Pendo's onboarding e-book: "The average time to value for companies of all sizes is 1.5 days" and "average one-month user retention is 38%." No methodology is given, so treat both as a vendor benchmark; 1.5 days describes self-serve user activation, not a B2B implementation with an integration and a training plan.

None of these should be your target. They tell you activation is worth tracking, a minority of users reach it, and the first week decides most of the curve. Your target comes from your own retained cohort, which is the method below.

If you are starting from nothing, this is the default: the structure the companies above use, reduced to four numbers a two-person onboarding team can pull from a product database, a billing export and a spreadsheet.

The rule that holds the stack together: each layer must predict the next. If activated accounts churn at the same rate as non-activated ones, the activation event is wrong. Check the pairs quarterly and change the definition, not the target.

The companies in the second table did not guess their event. Intercom compared retention for customers that reached Day Zero against customers that did not; Slack's 2,000 messages came with a retention figure attached. The method is the same for a 40-customer startup; only the sample size changes.

1. 1

   List five candidate behaviours

   Each a core action a user takes on real data, countable from product events. Include the one your product team already believes in and two smaller ones. Exclude logins, page views and checklist completion; those measure presence, not value.

2. 2

   Pull two cohorts from the last four quarters

   Accounts still paying at 12 months, and accounts that churned inside 12 months. One row per account with the signature date. Thirty per cohort is enough to see a gap; ten is enough to see a direction.

3. 3

   Score each account on each candidate at day 14 and day 30

   Did the account perform the behaviour at least N times by the cut-off? Try N at 1, 3 and 10. This is the Intercom method: retention for those that reached the milestone against those that did not.

4. 4

   Keep the smallest behaviour with the largest retention gap

   If "three reports approved by day 30" separates renewed from churned accounts as well as "twenty reports", the smaller one is your event: more accounts can hit it and the team can act sooner. Slack's threshold is high because messages are cheap; yours will usually be a single digit.

5. 5

   Write the definition as a query, with the window

   One sentence an engineer can implement: "account has 3 or more expense reports approved by 3 or more distinct submitters within 30 days of signature". The window matters as much as the count; a milestone with no deadline cannot be missed, so it cannot warn anyone.

6. 6

   Pair it with a time-to-value definition

   Activation says the customer is using the product; it does not say the product did the job. Define the first value moment separately, using the tests in time to value and why completed onboardings churn, and report both.

7. 7

   Re-run the comparison every quarter

   Product changes, pricing changes and a new segment all move the event. When the retention gap between activated and non-activated accounts narrows, the definition has drifted. Fix the definition first; the tactics for moving more accounts across it are in improving product adoption during initial use.

A dashboard that reads well while renewals still surprise you is measuring one of four wrong things: completion instead of value, an average instead of a distribution, the buyer's satisfaction instead of the end user's, or a milestone the customer never asked for. Completion at 90%, kickoff-to-go-live at 28 days and CSAT at 4.6 can all be true of an account that never reached first value.

• It measures the vendor's work. Completion rate, sessions delivered and days to go-live are dated by your calendar. No company in the second table names a completion rate; every event they name is something the customer's users did.
• The activation event was chosen by conviction, not by comparison. A product team's favourite feature is not the behaviour retained customers share. Run the cohort comparison above before defending the number.
• It has no window. A milestone that can be hit in month nine is a usage metric, not an onboarding metric. Intercom, Zapier and Loom all attach one: three months, 24 hours, one week.
• It stops at activation. Activated is a threshold of use; value is a business result in the customer's own data. The account that activated and never reached value is the one the thread below describes.

The fix in each case is a definition change, not a new tool: replace completion with a customer-side event chosen from the cohort comparison, put a window on it, and add the time-to-value layer above it. If the account has already gone quiet, the re-engagement playbook covers that.

The board and the onboarding team want different numbers, and one dashboard serves neither. The public companies answer this by structure: the filings carry the retention outcome, the product and growth teams carry the milestones. Copy the split.

A decision rule on build versus buy: if you can pull the activation event and the first value event from your product data today, build the stack in a spreadsheet this month and revisit tooling when the weekly pull becomes painful. If you cannot pull either event, the gap is instrumentation, and no onboarding tool fixes that.

GainTrace connects billing, CRM and product usage and dates each of the four layers per account: the setup milestone, the activation event you define, the first value moment and the renewal outcome. Product signals show which accounts passed each layer and which are past the window, and revenue analytics reports gross and net retention by signing cohort beside those layers, so the chain from onboarding to retention is one view rather than a quarterly reconstruction.