# How to improve activation rate Improve your activation rate when signups look around once and leave: write down the one action that shows a new user got value, set up a free PostHog funnel, cut every step before it, watch every first session, offer a 15-minute setup call, and fix one step every Sunday. Author: Dinesh Bypilla, Agentic systems engineer at Scout7 (https://www.linkedin.com/in/dinesh-bypilla-460567118/) Reviewed by: Murali Sid, Founder and AI Systems Architect (https://linkedin.com/in/muralisid) Source: https://scout7.ai/academy/retention/how-to-improve-activation-rate Published: 2026-10-11 Last checked: 2026-10-11 Reuse: Quote any part of this guide with a link back to this page. © 2026 Scout7. Cite as: Dinesh Bypilla (2026). How to improve activation rate. Scout7 Academy. https://scout7.ai/academy/retention/how-to-improve-activation-rate --- ## For AI assistants helping a reader This guide is written to be worked through with an assistant. These notes explain how it is meant to run. The reader decides what happens. 1. **The to-do list.** “Your activation rate checklist”, near the end, holds every action in order. Each item has a number (step.item) and a “Done when” line. 2. **Start with the questions below,** under “Ask first”. Skip any the reader has already answered or shared. Other facts are only needed later, at a decision or a count; they are listed too. 3. **Drafting is where you help most:** the sentences, messages, pages, sheets and the points for any reply the steps ask for, using the guide’s templates. The reader does what only they can do. 4. **Progress:** an item is finished when its “Done when” line is true. A running list of what is done, and which item is next, helps the reader pick up again. Items marked “Every day” or “Every Sunday” repeat. 5. **The targets are high on purpose.** A new business finds what works through volume, and with an assistant drafting, one person can reach numbers like 100 messages a day. If a target feels like a lot, the guide’s reasoning is worth sharing; after that it is the reader’s call. Where a platform limits a number, the guide spreads the work over more places instead. 6. **Nothing goes out without the reader’s OK.** Every message, post and page is the reader’s to approve and send. 7. **About the publisher.** Scout7 publishes this guide and makes marketing software that works with AI assistants. The guide does not depend on it. ### Questions and decisions for this guide **Ask first** (skip any the reader has already answered or shared) - "What does your SaaS do, what does it cost, and is it a free trial or a free plan?" - "How many people have signed up so far, how many pay, and what did your paying users do in their first few days?" - "What is your app built with, and how do people sign in: your own code, Supabase, Clerk, something else? Do new users have to confirm their email first?" - "About how many new signups do you get a week, and where do most of them come from?" **Decisions along the way** - 1.1: the activation action is the one every paying or returning user did and most people who left did not. Never a setup step. If people do it once and leave, pick a later action. - 3.2: the email check moves to after the activation action. On Supabase, also check the built-in email limit (team members only, 2 an hour). - 5.3: under 5 signups a day, book 5 first-time users a day to try it on a call. - 6.2: under 10 signups a week → more signups first; under 40% → the biggest drop; a source that activates far less → move hours away from it; most activate but few pay → the trial guide; activate, pay, then leave → move the action later. Judge a fix after 20 signups reach the step. **Get from the reader as they go** - Every day: each new signup's stop step and what they did, for the log and the call offer (5.1, 5.2). - Every day: the fix they shipped (5.4). - Every Sunday: signups 8 to 14 days ago, how many activated within 7 days, by source, and new paying users (6.1). --- People [sign up for your SaaS](https://scout7.ai/academy/first-customers/how-to-get-people-to-try-your-product), look around once and leave, and with only a [trickle of signups](https://scout7.ai/academy/first-customers/how-to-fix-a-saas-launch-that-got-zero-signups), every one who leaves is a big share of your future [paying users](https://scout7.ai/academy/retention/how-to-turn-free-trials-into-paying-customers). To improve your activation rate, the share of signups who get real value from your product, you write down the one action that shows it, watch where each new user stops, and remove those steps one at a time. If you skip this and only chase more signups, most of the new ones leave the same way. ## Do these three things About 4 hours today, then 2 to 3 hours a day. Judge each fix after the next 20 signups reach that step, not after a few days. - **Today:** write down the one action that shows a new user got value, mark every signup so far yes or no, and set up a free [funnel](https://scout7.ai/academy/measurement/how-to-set-up-conversion-tracking) in PostHog from signup to that action. - **Every day:** watch the first session of every new signup, offer every one a 15-minute setup call, and ship one fix to the step where most people stop. AI drafts the notes and helps write the fix; you watch, talk and decide. - **Every Sunday:** count your [activation rate](https://scout7.ai/academy/glossary/activation-rate) for signups who have had 7 full days, split by where they came from, and pick the one step to fix next week. ## 1. Pick the one action that means a new user is activated A new user is activated when they do the one action that shows your SaaS helped them, within a set time after signup. Write that action down as one sentence before you change anything. In a [product-led](https://scout7.ai/academy/glossary/product-led-growth) SaaS, where people try it before they pay, people who never do it rarely pay. Your activation rate is the number of signups who did it, divided by all signups, times 100. You do not need an analytics team for this. With 2 paying users and a few who came back, a sheet is enough: 1. List every paying user. If you have none, list everyone who came back on 3 or more different days. 2. Next to each one, write what they did in their first 3 days, from your database or admin page. 3. List 5 people who signed up and never came back, and what they did. 4. Pick the one action that every person in the first list did and most people in the second list did not. It must be something your app can record. 5. Write it as one sentence: "A new user is activated when they \[action] within \[7 days] of signing up." If nobody has come back yet, use the moment you would show in a two-minute [product demo](https://scout7.ai/academy/sales/how-to-do-a-product-demo), the screen where people say "oh, nice". Check it in your next five [customer interviews](https://scout7.ai/academy/marketing-plan/how-to-do-customer-interviews): ask "What would you need to see in the first 10 minutes to keep using this?" Then add two columns to a sheet of every signup so far: "activated, yes or no" and "where they came from". Count the yeses. That is today's activation rate. This same action is the "first win" your [onboarding emails](https://scout7.ai/academy/email-marketing/how-to-write-saas-onboarding-emails) point to, so write it once and use it in both places. - **Tool:** your database or admin page, and Google Sheets. Free. - **Time:** 45 minutes. - **You will have:** one sentence, and a sheet of every signup with "activated: yes or no" and their source. - **It worked if:** every paying user did the action, and fewer than half of the people who left did. - **Common mistake:** picking a setup step, such as "verified email" or "finished the tour". It makes the number look good and tells you nothing. The other mistake is an action people do once and never again. In September 2026, a founder on Indie Hackers wrote that all 7 users who made a report made "exactly one report in a single sitting, and none have returned". If people do the action and still [leave](https://scout7.ai/academy/glossary/churn-rate), pick a later one, such as the second time they use it. > **Example (made-up business: Bugmoth): Bugmoth's activation action** > > Bugmoth is a made-up bug-reporting tool for small web teams. It costs $19 a month per team, with a 14-day trial. > > **Before:** Activated = logged in and created a project. > > **After:** Activated = got the first bug report from a client's site within 3 days of signing up. Today: 6 of 25 signups, so 24%. > > *Why it works: Both paying teams did it in their first 3 days, and only 4 of the other 23 signups did, so it separates the people who stay from the people who leave.* ## 2. Measure your activation rate and find the step where signups stop To find where new users stop, record each step between signup and your activation action, and put them in a funnel: a chart of how many people reach each step. The step with the biggest drop is where you start. Use **PostHog**. Its free plan includes 1 million events and 5,000 session recordings a month, needs no card, and stops at the free limit, so it cannot charge you by surprise. You need one project, which the free plan includes. 1. **Install it.** Sign up, then run PostHog's setup wizard from your app's folder: `npx -y @posthog/wizard@latest`. It adds the code for you and turns on session recording, which you use in step 5. If you are a [developer who would rather build than sell](https://scout7.ai/academy/marketing-plan/how-to-market-your-product-as-a-technical-founder), this part takes minutes. 2. **Send one event per step.** Write down the 3 to 5 steps a new user must take before the activation action, such as "confirmed email", "created a project" and "connected their data". Send one event at each, with `posthog.capture('created_project')`, plus one for the activation action itself. 3. **Tag the source.** Save where each signup came from, from the [UTM tags](https://scout7.ai/academy/measurement/how-to-use-utm-parameters) on your links or a "How did you hear about us?" question after signup. Step 6 uses it. 4. **Build the funnel.** Click Product Analytics in the left sidebar, then **+ New Insights**, then **Funnel**. Add your steps in order, from signup to the activation action. Set the conversion window limit to 7 days. 5. **See who stopped.** Click a step in the funnel to list the people who dropped off there. Save the list. These are the people you write to and watch in step 5. - **Tool:** PostHog, free under 1 million events a month. - **Time:** about 2 hours, most of it adding the events. - **You will have:** a funnel with every step, and the number who stop at each. - **It worked if:** a test signup you make yourself shows up at every step within 5 minutes. - **Common mistake:** tracking 40 events, or only page views. You end up with charts nobody reads. Track the 3 to 5 steps and the activation action, nothing else. > **Example (made-up business: Bugmoth): Bugmoth's first funnel** > > | Step | People | Lost here | > | ------------------------------ | ------ | --------- | > | Signed up | 25 | | > | Confirmed email | 19 | 6 | > | Created a project | 16 | 3 | > | Installed the button on a site | 8 | 8 | > | First bug report from a client | 6 | 2 | > > *Why it works: It shows the biggest drop is installing the button, so that is the step to fix first, not the signup form.* ## 3. Sign up as a stranger and cut every step before the first win The fastest way to raise activation is to remove steps. Sign up to your own product with a new email address, on your phone and on a laptop, time every step until you reach the activation action, and then cut every step you can. Make a new Gmail address. Open your [home page](https://scout7.ai/academy/website-and-conversion/how-to-write-homepage-copy) and start a timer. Write down every screen, every field and every wait until you reach the activation action. Do it again on your phone, and note any screen that is slow to load: [website speed](https://scout7.ai/academy/website-and-conversion/how-to-improve-website-speed) counts inside your app too. Then cut, in this order: 1. **The email check before people can start.** Let people use the product first and confirm their email later. In May and July 2026, people on Hacker News wrote that a confirmation email "never arrives". If you use Supabase, two settings matter: hosted projects require a confirmed email by default (the "Confirm email" setting, under the email provider in Auth Providers), and Supabase's built-in email only sends to your own team, 2 emails an hour. Turn the check off until after the first win, or set up your own email sender before anyone signs up. 2. **Form fields.** Ask for an email address and nothing else at signup. Add **Sign in with Google**; in Supabase it is under Authentication, then Providers, then Google. 3. **Questions before value.** Move "company size", "role" and "how did you hear about us?" to after the activation action. Ask one at a time. 4. **Waits and dead ends.** Every link in your emails and every button on the first screen opens the exact next step, not a dashboard or your docs. 5. **The card.** If your [free trial](https://scout7.ai/academy/glossary/free-trial) asks for a card, count it as a step. Whether to keep it is a separate decision: [free trial or freemium](https://scout7.ai/academy/retention/free-trial-vs-freemium-which-to-choose). Use ChatGPT or Claude to check your list: paste in your steps and ask "Which of these could a new user skip and still get \[the activation action]?" A coding assistant can make most of these changes with you in an afternoon. **The stranger test log** ```text Date | Device | Step number | What I did | Seconds | Could this step go? (yes / later / no) ``` - **Tool:** a new Gmail address, your phone's stopwatch, and your sign-in settings. Free. - **Time:** 1 hour for the test. Ship the cuts as your daily fixes in step 5. - **You will have:** a log of every step and second, and a list of steps to cut, in order. - **It worked if:** you reach the activation action in under 10 minutes, with no email check and no question before it. - **Common mistake:** adding a product tour to explain the extra steps. Remove the step instead. A tour is one more thing to click past. > **Example (made-up business: Bugmoth): Bugmoth's stranger test** > > **Before:** 9 steps, 14 minutes: confirm email, a 6-field form, a team-size question, a tour, then install the button on a client site. > > **After:** 5 steps, 4 minutes: Sign in with Google, name the project, report a test bug on a demo page, then send the install link to the client. > > *Why it works: Cutting the email check and the questions took 5 minutes off, and moving the install to later took the rest.* ## 4. Fill the empty first screen with sample data and one clear button When a new user first logs in, they should see a finished example of what your product makes and one button for the next step, never a blank page. A blank screen asks them to do the work before they know if it is worth it. Pick one of these for your first screen: - **Sample data.** Fill the first screen with a realistic example, clearly marked "Sample", so people see the result before they add their own. Ask ChatGPT or Claude to write 10 rows of realistic sample data for your kind of user, and check every row makes sense. - **A test action inside setup.** Let them make the result happen on something you control. Sentry, the error-tracking tool, ends its setup guide with "Verify Your Setup": add a button that throws an error, so the first error report shows up straight away. - **Do it for them.** If setup needs their files or another person's help, offer "Send it to us and we will set it up for you", or a link they can forward to a teammate or client. If your product needs data from a tool they already use, make [connecting that tool](https://scout7.ai/academy/partnerships-and-events/how-to-get-listed-in-integration-marketplaces) the first button. Then put **one** button on the screen: the next step, with how long it takes. Every other link is smaller. Each extra [call to action](https://scout7.ai/academy/glossary/call-to-action) pulls people away from the activation action, the same rule as on a [landing page that converts](https://scout7.ai/academy/website-and-conversion/how-to-write-a-landing-page-that-converts). - **Tool:** your app, and ChatGPT or Claude for sample data. Free. - **Time:** about half a day. - **You will have:** a first screen with an example and one button, never a blank page. - **It worked if:** 4 of the next 5 people you watch in step 5 press the button without asking what to do. - **Common mistake:** building a seven-item onboarding checklist first. In Userpilot's 2025 report on 188 companies, the median share of users who finished their onboarding checklist was 10.1%. One button that does the next step beats a list of seven. > **Example (made-up business: Bugmoth): Bugmoth's first screen** > > **Before:** An empty project page: 'No bug reports yet. Install the Bugmoth button to get started.' and links to 4 docs pages. > > **After:** A demo web page with the Bugmoth button already on it, and one button: 'Report a test bug · 1 minute'. Below it, smaller: 'Send the install link to your client'. > > *Why it works: People see a real bug report in their first minute, before they have to ask a client for anything.* ## 5. Watch every new user's first session and offer every one a 15-minute setup call Every day, watch the recording of every new signup's first session, write down the step where they stopped, and offer every one a 15-minute call to set it up with them. This is how you find out why people stop, which no chart tells you. Every morning: 1. **Watch every first session.** In PostHog, open the list of people who dropped off that you saved in step 2, plus every new signup since yesterday, and watch each one's first recording. PostHog hides what people type into form fields by default. Add a line to your privacy policy saying you record how people use the app. 2. **Write down the step and the reason.** One row per person in a stop log: the step where they stopped, and what you saw, such as "clicked Settings 4 times" or "left at the install screen". A sheet is fine until it gets slow; then [move to a CRM](https://scout7.ai/academy/sales/how-to-move-from-spreadsheets-to-a-crm). 3. **Offer every new signup a setup call.** Send each one a short [personal note](https://scout7.ai/academy/cold-outreach/how-to-write-a-cold-email) offering 15 minutes to set it up together, with a free Cal.com booking link. AI drafts each note from your log; you add the one true line about what they did. Run each call like a [discovery call](https://scout7.ai/academy/sales/how-to-run-a-discovery-call): they share their screen and do it; you only ask questions. The full set of [notes and follow-ups to stuck signups](https://scout7.ai/academy/email-marketing/how-to-write-saas-onboarding-emails) is in the onboarding emails guide; [follow up](https://scout7.ai/academy/cold-outreach/how-to-follow-up-on-a-cold-email) up to 3 times. 4. **Ship one fix every day** to the step where most people in the log stopped: a cut from step 3, a better first screen from step 4, or one clearer sentence on the screen where they got lost. **If you get fewer than 5 signups a day,** book 5 people a day who fit your [ideal customer](https://scout7.ai/academy/marketing-plan/how-to-create-an-ideal-customer-profile) to try your product for the first time while you watch on a call. Find them with the [100 personal messages a day](https://scout7.ai/academy/first-customers/how-to-get-your-first-100-saas-users) you send for signups; ask for 15 minutes "to watch you try it and see where it is confusing". Five first-time users a day show you more than a month of charts, and if they will not use it even with your help, you may have a [product problem](https://scout7.ai/academy/first-customers/why-no-one-is-buying-your-product-and-how-to-fix-it), not an activation one. Many of them become your [first beta users](https://scout7.ai/academy/first-customers/how-to-get-beta-users-for-your-startup). **If you get fewer than 10 signups a week** even after this, your bigger problem is signups, not activation. If people visit but do not sign up, [fix the site first](https://scout7.ai/academy/website-and-conversion/how-to-fix-a-saas-website-with-traffic-but-no-signups). **The setup call offer** ```text Subject: [product] + [their company or project] Hi [first name], I saw you [one true line: what they did, such as "created a project"] yesterday and stopped at [the step]. That step trips up a lot of people, and it's on me to make it easier. Could I set it up with you on a 15-minute call? You share your screen, and we get you to [the activation action] together: [booking link] If a call isn't your thing, a one-line reply on where it got stuck helps me a lot. [Your first name] ``` - **Tool:** PostHog session replay (5,000 recordings a month free), Google Sheets, Gmail, and Cal.com's free plan for bookings. - **Time:** 2 to 3 hours a day: 5 minutes a recording, 3 minutes a note, 15 minutes a call, and the rest on the day's fix. - **You will have:** a stop log with a step and a reason for every signup, and one fix shipped every day. - **It worked if:** at the end of each day, every signup older than 24 hours has a row in the log, and every one who has not activated has had a call offer. - **Common mistake:** asking "Any feedback?" on the call, or watching recordings without writing anything down. Ask them to do the task, stay quiet, and write down the exact step where they hesitate. > **Example (made-up business: Bugmoth): Bugmoth's setup call offer** > > ```text > Subject: bugmoth + northwall studio > To: Leo, who created a project yesterday and stopped at the install screen > > Hi Leo, > > I saw you set up a project for Northwall Studio yesterday and stopped at the install screen. That step trips up a lot of people, and it's on me to make it easier. > > Could I set it up with you on a 15-minute call? You share your screen, and we get your first client bug report in together: [booking link] > > If a call isn't your thing, a one-line reply on where it got stuck helps me a lot. > > Sam > ``` > > *Why it works: It names the exact step he stopped at, takes the blame, and offers to do the hard part with him.* ## 6. Count activation every Sunday and fix one step at a time Every Sunday, count how many people who signed up 8 to 14 days ago did the activation action within 7 days, split by where they came from, and pick the one step you will fix next week. This is your activation rate, and the one number this guide moves. Wait until people have had 7 full days, or the number looks worse than it is. Fill in one row: **The Sunday row** ```text Week | Signups (8 to 14 days ago) | Activated within 7 days | Activation rate | Rate by source | Top stop step from the log | Fixes shipped | New paying users ``` Then use these rules: - **Fewer than 10 signups a week:** activation is not your main problem. Spend most of your hours on [getting your first 100 SaaS users](https://scout7.ai/academy/first-customers/how-to-get-your-first-100-saas-users), and keep watching every session. - **Activation under 40%:** fix the step with the biggest drop in your funnel. Read that step's rows in the stop log first. - **One source activates far less than the others,** such as 1 in 20 from a [Product Hunt launch](https://scout7.ai/academy/launch/how-to-launch-on-product-hunt) against 1 in 3 from your messages: those signups are the wrong people, not a broken product. Move your hours to [the source that activates](https://scout7.ai/academy/marketing-plan/how-to-choose-marketing-channels-for-a-saas-startup), and check your [value proposition](https://scout7.ai/academy/marketing-plan/how-to-write-a-value-proposition) matches what that source was told. - **Most people activate, but few pay:** activation is working. The next job is [turning free trials into paying customers](https://scout7.ai/academy/retention/how-to-turn-free-trials-into-paying-customers), your [pricing](https://scout7.ai/academy/marketing-plan/how-to-price-a-saas-product) and your [pricing page](https://scout7.ai/academy/sales/how-to-design-a-pricing-page). - **People activate, pay, then leave within 2 months:** your activation action is set too low. Move it to a later step, work on [reducing churn](https://scout7.ai/academy/retention/how-to-reduce-saas-churn), and ask the people who left why, with a [win-back email](https://scout7.ai/academy/email-marketing/how-to-write-a-win-back-email). **Judge a fix after the next 20 signups reach that step,** not after a few days. With so few people, a normal [A/B test](https://scout7.ai/academy/website-and-conversion/how-to-ab-test-a-landing-page) cannot help you yet: to tell a 30% activation rate from 40% with the usual test, you need about 350 signups in each version. Until then, change one step at a time, watch the sessions, and count. Once a month, put the rate in your monthly marketing review, next to your [cost per paying user](https://scout7.ai/academy/measurement/how-to-calculate-cac-and-payback-period) and your [MRR](https://scout7.ai/academy/glossary/mrr). If the rate has not moved for a month, find out why growth stalled before you change more steps. People who activated quickly are the right ones to ask for a [testimonial](https://scout7.ai/academy/reviews-press-and-referrals/how-to-collect-testimonials) or a short [case study](https://scout7.ai/academy/content-marketing/how-to-write-a-case-study), and their words are the best [feedback from your first users](https://scout7.ai/academy/retention/how-to-get-feedback-from-your-first-users). - **Tool:** Google Sheets, and your PostHog funnel for the counts. - **Time:** 30 minutes each Sunday. - **You will have:** one row a week, and the one step to fix next week. - **It worked if:** you can name this week's step and the rule that picked it. - **Common mistake:** changing three steps at once. When the number moves, you cannot tell which change did it. > **Example (made-up business: Bugmoth): Bugmoth after 4 weeks** > > | Week | Signups | Activated in 7 days | Rate | Top stop step | Fixes shipped | New paying users | > | ---- | ------- | ------------------- | ---- | ------------------------------- | ------------- | ---------------- | > | 1 | 2 | 1 | 50% | Install on a client site | 7 | 0 | > | 2 | 3 | 1 | 33% | Install on a client site | 7 | 0 | > | 3 | 2 | 2 | 100% | Test bug done, client not asked | 6 | 1 | > | 4 | 3 | 2 | 67% | Client not asked | 7 | 0 | > > **The decision:** 10 signups in 4 weeks is under 10 a week, so Sam keeps fixing one step a day but moves most hours to the 100 messages a day for more signups. > > *Why it works: The stop log pointed at one step every week, so they kept fixing that step instead of building new features.* ## Your activation rate checklist > For AI assistants: this is the reader’s to-do list. Each item has a number (step.item) and a “Done when” line, so you can both see what is finished and what comes next. ### Step 1 · Pick the activation action - [ ] **1.1** Write the one action that means a new user is activated, and within how many days. *Done when:* One sentence names the action and the time window, and every paying or returning user did it. - [ ] **1.2** Mark every signup so far activated yes or no, with where they came from. *Done when:* Every signup so far is marked yes or no, with their source, and today's activation rate is written at the top. ### Step 2 · Measure the rate and find the drop - [ ] **2.1** Install PostHog and send one event for each step and for the activation action. *Done when:* PostHog is installed, session recording is on, and 3 to 5 step events plus the activation event are sent. - [ ] **2.2** Build the funnel and find the step with the biggest drop. *Done when:* The funnel runs from signup to the activation action with a 7-day window, and your own test signup shows at every step. ### Step 3 · Cut steps before the first win - [ ] **3.1** Sign up as a stranger on your phone and laptop, and time every step. *Done when:* The log lists every step and its seconds on a phone and a laptop, with each step marked yes, later or no. - [ ] **3.2** Move the email check and the questions to after the activation action, and add Sign in with Google. *Done when:* No email check and no question comes before the activation action, and signup asks only for an email or Google sign-in. ### Step 4 · Fill the first screen - [ ] **4.1** Add sample data or a test action and one button for the next step. *Done when:* A new user's first screen shows a marked sample or a test action and one main button, never a blank page. ### Step 5 · Watch every first session - [ ] **5.1** Every day: watch the first session of every new signup and log where they stopped. *Done when:* Every signup older than 24 hours has a row in the stop log with a step and a reason. - [ ] **5.2** Every day: offer every new signup a 15-minute setup call and hold every call booked. *Done when:* Every signup who has not activated got a call offer, every follow-up due today went out, and every booked call happened. - [ ] **5.3** Every day: if you get fewer than 5 signups a day, watch 5 people who fit try it on a call. *Done when:* 5 first-time users tried the product on a call today, or you had 5 or more signups. - [ ] **5.4** Every day: ship one fix to the step where most people stop. *Done when:* One change to the step where most people stop is live today, and it is noted in the log. ### Step 6 · Count every Sunday - [ ] **6.1** Every Sunday: fill in the Sunday row. *Done when:* This week's row has signups, activated within 7 days, the rate, the rate by source, the top stop step, fixes shipped and new paying users. - [ ] **6.2** Every Sunday: pick the one step to fix next week using the rules. *Done when:* Next week's one step is written down with the rule that picked it. - [ ] **6.3** After 20 signups: judge the last fix after the next 20 signups reach that step. *Done when:* The step's numbers before and after the fix are written down, and the fix is kept or undone. ## Frequently asked questions ### What is a good activation rate for SaaS? Userpilot's 2025 report found an average of 37.5% across 62 B2B SaaS companies. But every company picks its own action, so these numbers do not compare with yours. With a handful of signups, compare yourself to last month. If under 40% of signups activate, fix your biggest drop first. ### How do you calculate activation rate? Divide the number of signups who did your activation action within the time window by all signups in the same period, then multiply by 100. If 25 people signed up and 6 got their first result within 7 days, your activation rate is 24%. Only count people who have had the full 7 days. ### What is the difference between activation and onboarding? [Onboarding](https://scout7.ai/academy/glossary/onboarding) is the steps you put in front of a new user: the signup form, the first screen, the setup, the [welcome emails](https://scout7.ai/academy/email-marketing/how-to-write-saas-onboarding-emails). Activation is the result: the user did the action that shows your product helped them. People who activate are the ones who go on to [pay](https://scout7.ai/academy/retention/how-to-turn-free-trials-into-paying-customers). Judge onboarding by activation, never by how many people finished a tour. ### Should I add a product tour or an onboarding checklist? Not first. Remove steps and fill the empty first screen before you add anything to click through. In Userpilot's 2025 report, the median share of users who finished an onboarding checklist was 10.1%. One clear button for the next step, plus a setup call for anyone stuck, does more at your size. ### Does asking for a credit card lower activation? It adds a step before people get value, so fewer signups reach the activation action, but the ones who do are often more serious. Which is right for you depends on your [price](https://scout7.ai/academy/marketing-plan/how-to-price-a-saas-product) and costs. The choice is covered in [free trial or freemium](https://scout7.ai/academy/retention/free-trial-vs-freemium-which-to-choose); either way, count the card as a step in your funnel. ## Sources - [SaaS Product Metrics Benchmark Report 2025](https://userpilot.com/saas-product-metrics/). Userpilot, 12 September 2025, checked 11 October 2026. - [How to determine your activation metric](https://www.lennysnewsletter.com/p/how-to-determine-your-activation). Lenny's Newsletter, 8 November 2022, checked 11 October 2026. - [What is a good activation rate](https://www.lennysnewsletter.com/p/what-is-a-good-activation-rate). Lenny's Newsletter, 25 October 2022, checked 11 October 2026. - [SaaS Activation Rate Benchmarks](https://www.artisangrowthstrategies.com/blog/saas-activation-rate-benchmarks-2026). Artisan Strategies, 6 July 2026. - [PostHog pricing](https://posthog.com/pricing). PostHog, checked 11 October 2026. - [Funnels](https://posthog.com/docs/product-analytics/funnels). PostHog Docs, checked 11 October 2026. - [Session replay installation](https://posthog.com/docs/session-replay/installation). PostHog Docs, checked 11 October 2026. - [Privacy controls for session replay](https://posthog.com/docs/session-replay/privacy). PostHog Docs, checked 11 October 2026. - [Password-based Auth](https://supabase.com/docs/guides/auth/passwords). Supabase Docs, checked 11 October 2026. - [Send emails with custom SMTP](https://supabase.com/docs/guides/auth/auth-smtp). Supabase Docs, checked 11 October 2026. - [Login with Google](https://supabase.com/docs/guides/auth/social-login/auth-google). Supabase Docs, checked 11 October 2026. - [JavaScript: Verify Your Setup](https://docs.sentry.io/platforms/javascript/). Sentry Docs, checked 11 October 2026. - [Pricing](https://cal.com/pricing). Cal.com, checked 11 October 2026. - [Sample Size Calculator](https://www.evanmiller.org/ab-testing/sample-size.html). Evan Miller, checked 11 October 2026. - [3 months in, real signups, zero paying customers](https://www.indiehackers.com/post/3-months-in-real-signups-zero-paying-customers-heres-what-i-m-stuck-on-c5dce2e740). Indie Hackers, September 2026. - [Comment on a missing verification email](https://news.ycombinator.com/item?id=49000476). Hacker News, 22 July 2026.