How Do I Improve Product Adoption in the First 30 Days?

Adoption stalls because the first sessions ask the user to learn the product before the product has done anything for them. Every tactic below works by shortening the distance between signup and the first moment the user gets something back. Everything that lengthens that distance (a tour of every feature, a setup wizard with twelve steps, a training call scheduled for next week) costs adoption even when it feels helpful.

The industry that manages adoption is unusually vague about what it is. In the 2,094 sentences from public G2 reviews where buyers of the three most-reviewed customer success platforms describe the problem they bought the tool to solve, the word adoption appears 103 times. The word activation appears zero times. Teams are tracking a thing they have not defined, which is why so many track logins instead.

Intercom's Lynsey Duncan drew the line that helps most: "aha moments are when the user discovers value in your product; activation is when you see value in that user." The metric you want is the second thing, a behaviour you can observe, that correlates with the first.

These are the early-use metrics with a primary source we could read: a founder on the record, a named employee's post, a lecture transcript. Read the pattern rather than the numbers. Each is a behaviour, on the user's own work, reached within days, involving other people more often than not.

Two rows deserve a note. Superhuman's 40% is not an activation metric; it is a product-market-fit survey that Vohra used to decide which users to design onboarding for, and it sits in the table because it is the published number most often confused with one. Twitter's 30 follows reaches us only second-hand, which is why it is hedged. Facebook's two versions (7 in 10, 10 in 14) came from two executives describing the same idea at different times; the exact threshold mattered less to them than the direction.

Each metric in the table is a correlation the company found in its own retention data. Users who reached 2,000 messages stayed; nobody has shown that forcing a team to 2,000 messages makes it stay. Copying Slack's threshold into a procurement tool tells you nothing, and copying the shape (a behaviour on real work, reached in days, that other people see) tells you almost everything.

The Canva row shows why even a company's own number splits. Ho's team found that new users arriving for posters behaved differently from users arriving for social graphics, asked poster users "what type of poster new users are looking for", and moved activation for that segment by 10%. If your product serves two buyer types, expect two metrics. Most B2B products we look at have one metric for the admin and a different one for the invited user, and only the second predicts renewal.

This needs read access to product events and billing, a spreadsheet, and about eight working hours. It does not need a data scientist. The output is one sentence with a number and a day count, and the date that event happened for every account.

1. 1

   Pull two cohorts from the last four quarters

   Accounts that renewed or are still active at day 90 and accounts that cancelled or went dormant before day 90. You need at least 30 in the smaller group; if you do not have that, extend the window or use users instead of accounts.

2. 2

   List eight to twelve candidate behaviours

   Things a user does on their own work in the product: sent a real message, connected a live data source, invited a second person, shared an output, ran a report on last month's data, completed a first transaction in test mode. Exclude anything about your product (tour completed, profile filled, onboarding checklist done).

3. 3

   Score each behaviour for each account in the first 14 days

   One column per behaviour, one row per account: did it happen by day 7, did it happen by day 14, how many times. Pull the dates from product events; if a behaviour cannot be pulled, drop it and log the instrumentation gap.

4. 4

   Compare the day-90 outcome for accounts that did and did not do each behaviour

   For each candidate, retention rate among accounts that did it by day 14 versus accounts that did not. Rank by the gap. Then check reach: what share of all accounts did it by day 14. A behaviour with a huge gap that 4% of accounts reach is a description of your best customers, not a target.

5. 5

   Pick the behaviour with the largest gap that at least a third of accounts already reach

   Write it as one sentence: "An account is activated when [N] users have [done the thing] on real data by day [D]." Include the second-user condition if your product is used by a team; HubSpot's two-or-more-people rule and Amplitude's shared-with-two-others rule both exist because the single-user version did not predict retention.

6. 6

   Test it by intervening, then re-check quarterly

   Take the next cohort, drive them to the behaviour with the cheapest tactic in the next section, and see whether day-90 retention moves. If it does not, you found a symptom of good customers rather than a cause. Either way, re-run steps 1 to 4 every quarter on the newest cohort, because the moment drifts.

Once the moment is named, every tactic is a way of removing one reason a user stops before it. The table pairs each published tactic with the blocker it removes, so you pick by diagnosis rather than by fashion.

Note what is missing from the table: a longer product tour, a bigger welcome sequence, a second training session. None of the sources credits those, and in our experience they are the three things teams reach for first because they are the three things the onboarding team controls without product or engineering.

Pull the activation date and the user list for the stalled cohort before deciding what to send. The pattern in the data tells you which of three problems you have, and each has a different fix.

• The admin reached the moment and nobody else did. Ninety percent of events come from one login. The fix is the second user, not more of the first: an invite with a reason attached (Figma's multiplayer, HubSpot's two-people rule) and a getting-started guide written for the invitee.
• Nobody reached the moment, and the users who logged in spent their time in settings. The path to the moment is behind setup. Re-order the checklist so the value behaviour comes before configuration, and use a template or sample data so the first session produces an output.
• Users reached the moment once and did not repeat it. The behaviour you picked is a symptom, not a habit. Go back to the method above and look for the repeated version (Loom's video with a view, Amplitude's shared learning) rather than the one-off.

That head of customer success, with 1,500 customers and five direct reports, had discovered that doing the work for the customer produces renewals and no adoption. It is the most common shape of the problem in B2B: the vendor reaches the moment on the customer's behalf, so the metric looks fine and the habit never forms. The fix is to stop one step short and let the customer's own user do the last action, on the call if necessary.

The legal-tech team above, onboarding up to 200 single-lawyer customers a week with ten CSMs, is the case for the self-serve tactics in the table. Their remaining problem, silent churn from lack of initial adoption, is the activation metric they had not yet defined: without it, the webinar and the e-learning platform cannot be measured against anything except attendance.

Accounts that pass day 14 without the moment belong on the same weekly list as the risk signals in spotting churn risk early across scattered data. Accounts that reached it and later went quiet are a different problem, covered in the re-engagement playbook. If the onboarding program itself is the gap, the ten components other companies published is the place to start.

GainTrace takes the activation sentence you wrote in the method above and reads it from your product events, so every account has a date it reached the moment, or a count of days without it, beside the signature date. Product signals show which invited users got there and which stopped at setup, and churn prediction weights a cohort that passed day 14 without activation as the risk it is, without waiting for a check-in to go unanswered.