Before you chase 37%
SaaS Activation Rate: write the tripwire before you chase 37%
A slide that prints “activation is 37%” without naming the cohort, the aha event, or the window is asking you to trust a number that lives on three different formulas. Activation rate asks a smaller, honester question: of the signup cohort you named, how many reached the first-value event you named, inside a window you wrote down first? Hitting or missing that bar is a decision signal. It is not a forecast that you will succeed, and not a license to copy another product’s “activation %.”
Last updated: November 10, 2026
Direct answer
What is SaaS activation rate — and why write the tripwire first?
Activation rate is the percentage of a named new-user cohort that reaches a named first-value / aha event inside a named window. It answers “of the signup cohort we named, how many experienced the value event we named,” not “will we succeed” and not “should our number match Userpilot’s 37.5%.” Write the tripwire before you look: “for cohort C on milestone M (product-specific aha) within window W as-of date D, activation must stay ≥ X% (or we fix the path to first value / stop paid acquisition for that segment / change the milestone if it was vanity before scaling).” Hitting or missing it is a decision signal — not a prediction of success. Userpilot’s 2025 B2B sample averages 37.5% (median 37.04%, n=62), but industry bands run from FinTech 5% to AI & ML 54.8% — definition + industry dwarf a single “good” number. Separately, Amplitude’s 2025 analysis treats ~7% day-7 return as top-quartile early activation (a return-retention proxy, not the same formula).
Key takeaways
What to remember
- Always name the cohort, the milestone event, the window (or day-7 return if that is the proxy), and the as-of date. Never board-slide a bare “% activation.” Userpilot: user activation is the moment the user experiences the value of the product for the first time; activation rate is the percentage of new users who complete a specific action that demonstrates initial value.
- Userpilot’s 37.5% average is a myth of normal. Same 2025 B2B activation subsample (n=62; broader report 547 SaaS companies): median 37.04%. Industry bands on that dashboard: AI & ML 54.8%; CRM & Sales 42.6%; MarTech 24%; Healthcare 23.8%; HR 8.3%; FinTech & Insurance 5%. Pasting 37% onto a FinTech book, or panicking a 24% MarTech sitting, is how a sample average becomes a costume.
- Definition mismatch dwarfs a single “good” number. Userpilot’s aha-event % is not Amplitude’s day-7 return (7% of the original cohort returning on day seven → top 25% for activation performance in their 2025 Product Benchmark Report of 2,600+ companies). OpenView 2022, via Amplitude’s Amplify write-up: only 20–30% of new users reach activation at standout PLG companies. Never mix the three into one “good activation is X%” slide.
- Always report activation next to the milestone definition + window + (when available) time-to-value. Same Userpilot 62-company activation dashboard: average Time-to-Value 1 day, 12 hours, 23 min as the primary TTV cite. The same TTV card also lists 1 day, 1 hour, 54 min as a second average — both labeled averages on the page; this page does not invent which is a median. Related, different metrics on the same report: onboarding checklist completion average 19.2% / median 10.1% (n=188); core feature adoption average 24.5% / median 16.5% (n=181). Do not relabel checklist completion as activation.
- Write the tripwire before you measure: named aha (experienced value, not “opened email” / bare login unless login is the value) + named cohort + window (or day-7 return, labeled) + threshold matched to industry and to the definition you actually use + named action if missed. Use Userpilot industry bands as orientation only. Use Amplitude’s 7% only when you are measuring day-7 return. A Yibud score is not activation rate and not a success prediction. Pre-product, do not “optimize activation” by starving discovery.
Why it matters
Why 37% is the wrong first number
Founders treat “industry activation is 37%” as a target, then copy another product’s aha event because a blog said Userpilot’s average is the bar. The same report’s industry spread — and two other definitions sitting nearby — is the warning: the average is a midpoint across products that do not share a milestone, and the formula you chose moves the sitting more than a slogan will.
The 37% average is a myth of normal
Userpilot 2025 B2B activation subsample: average 37.5%, median 37.04%, n=62. Industry on that dashboard runs from FinTech & Insurance 5% to AI & ML 54.8%. CRM & Sales sits at 42.6%; MarTech 24%; Healthcare 23.8%; HR 8.3%. Chasing 37% is how you panic a healthy FinTech path, or lower an AI sitting after the close, because a sample average looked like a law.
Three formulas, three sittings — never one “good %”
Userpilot counts new users who complete a specific initial-value action. Amplitude’s 7% rule counts the share of the original cohort that return on day seven — a return-retention proxy they still call activation performance. OpenView 2022, as Amplitude summarizes it, reports 20–30% of new users reaching activation at standout PLG companies, with Poyar defining activation as solving the problem that brought the user (the aha), and metrics differing by product. Mixing those into “good activation is 40%” is a slide, not a tripwire.
A % with no named event, window, or cohort is vanity
“Activation is 41%” without saying who, which action, and by when cannot change a decision. It fails the same vanity test as a waitlist trophy. Write the sitting before you look, or you are decorating a dashboard.
Three definitions
Userpilot aha-event %, Amplitude day-7 return, OpenView standout PLG 20–30%
These fields are the instrument. If the milestone, the window, or the cohort is fuzzy, the percentage is a slide, not a tripwire. Label which definition you are using before you compare a number to anyone else’s.
Userpilot — first experience of value, then a specific action
Userpilot, SaaS Product Metrics Benchmark Report 2025: user activation is the moment the user experiences the value of the product for the first time. Activation rate measures the percentage of new users who complete a specific action that demonstrates the initial value of your product. First-party anonymized Userpilot Analytics; 547 SaaS companies across the broader report; this activation sitting is 62 B2B SaaS companies. Page dated/modified 12 September 2025.
Amplitude — day-7 return, labeled as a different proxy
Michele Morales / Amplitude, “The 7% retention rule explained” (30 September 2025), analyzing the 2025 Product Benchmark Report of over 2,600 companies: the share of the original cohort that return on day seven. Hitting 7% puts a product in the top 25% for activation performance. This is not the same as “completed aha event rate.” If you use it, say “day-7 return” on the dated page. Do not relabel it as Userpilot’s action-completion rate.
OpenView / Poyar — aha as solving the problem that brought the user
Noorisingh Saini / Amplitude, summarizing OpenView Partners Blake Bartlett and Kyle Poyar (1 August 2022; Amplify session + OpenView 2022 Product Benchmarks): Poyar frames product activation as solving the problem that brought the user to the product — they get to their aha moment — and says these activation metrics differ by product. OpenView 2022: only 20–30% of new users reach activation at standout PLG companies. Onboarding benchmark framing on that page: reduce time to value as indicated by activation rates. This page uses that 20–30% standout-PLG line and the aha definition. It does not import visitor→signup charts or free-to-paid OpenView numbers.
Always name cohort, milestone, window, as-of date
A usable sitting names who (the new-user cohort), what (the product-specific aha — experienced value, not “viewed dashboard” unless that is the value), by when (a window, or day-7 return if you are using Amplitude’s proxy), and as-of which date. If you only have a day-7 return, say so. If you only have an aha-event %, say so. Never report a bare “% activation.”
Userpilot 2025
Overall 37.5% — and why the industry table is the real sitting
Userpilot, SaaS Product Metrics Benchmark Report 2025. First-party anonymized Userpilot Analytics. Broader report: 547 SaaS companies. Activation subsample: 62 B2B SaaS. Average activation rate 37.5%; median 37.04%. The industry rows below are why “we are at 37%” is almost never a true sentence for your product.
| Industry | Activation rate | How to read it |
|---|---|---|
| AI & ML | 54.8% | Highest band on this dashboard. Not a target for FinTech. |
| CRM & Sales | 42.6% | Above the 37.5% sample average — still not a universal “good.” |
| MarTech | 24% | Below the sample average. Do not panic-copy an AI sitting. |
| Healthcare | 23.8% | Same report, same definition, different industry. |
| HR | 8.3% | Low on this dashboard. Complexity and aha definition both matter. |
| FinTech & Insurance | 5% | Lowest band here. 37% is the wrong costume. |
n=62 B2B SaaS on Userpilot’s Activation Dashboard. Average 37.5%; median 37.04%. Same dashboard, primary TTV cite: average Time-to-Value 1 day, 12 hours, 23 min. The TTV card also lists 1 day, 1 hour, 54 min as a second average — both appear as averages on the source page; this page does not invent a median. Use the industry row as orientation, not as a law. This page does not extract PLG vs SLG activation percentages from image-only charts, and it omits the Fairmarkit “25% activation lift → 34% MRR” claim (second-hand on that page, not independently verified here).
Related, different metrics — do not confuse them with activation
Same Userpilot report, clearly different metrics: onboarding checklist completion average 19.2% / median 10.1% (n=188). Core feature adoption average 24.5% / median 16.5% (n=181). A finished checklist is not an aha. Core-feature adoption in a later window is not first-value completion. Do not average them into a homemade “activation score.”
A different proxy
Amplitude’s 7% day-7 return rule — not an aha-event %
Michele Morales / Amplitude, 30 September 2025. Analysis of the 2025 Product Benchmark Report across over 2,600 companies. This sitting is the share of the original cohort that return on day seven. Label it that way. Do not drop it next to Userpilot’s 37.5% in one unlabeled sentence.
7% day-7 return → top 25% for activation performance
If 7% of the original cohort return on day seven, Amplitude’s analysis puts the product in the top 25% for activation performance. That 7% is a return-retention proxy. It is not “37% of new users completed the aha event.”
Early activation and three-month retention travel together
69% of top day-seven performers were also top three-month performers. Amplitude’s framing: for half of products analyzed, over 98% of new users are no longer active at the two-week mark. Use that as a warning about first-week value, not as a reason to relabel day-7 return as Userpilot’s action rate.
Enterprise gap — 12.4% vs 2.1%
Enterprise: the top 10% achieve 12.4% day-seven retention; the median sits at 2.1% — Amplitude’s nearly six-times gap. Day-14 activation rate for 90th-percentile products is about 9%. Even the top of that sample loses most users inside two weeks. None of these numbers are aha-event completion rates.
Optional: sector three-month retention — labeled, not an activation target
Same Amplitude post, 90th-percentile three-month retention vignettes: financial services 19.5%; travel & hospitality 25.6%; B2B technology 15.6%. These are retention outcomes months later, not activation-rate targets. Do not paste 19.5% onto a day-7 aha sitting.
This page skips SafetyCulture / Super.com / WeMoney case-study lift percentages. The benchmarks above are enough for a tripwire. If you measure day-7 return, the 7% top-quartile line is the Amplitude bar — and you still write your own floor before you look.
Standout PLG, a third sitting
OpenView 2022: 20–30% reach activation at standout PLG companies
Noorisingh Saini / Amplitude, 1 August 2022, writing up Blake Bartlett and Kyle Poyar at Amplify, summarizing OpenView’s 2022 Product Benchmarks. A third definition set. Do not flatten it into Userpilot’s 37.5% or Amplitude’s 7%.
Poyar’s aha — solving the problem that brought the user
Poyar: product activation really just means you are solving the problem that brought the user to the product in the first place — they get to their aha moment. These activation metrics differ for every product, depending on what the product does. That is the reason a copied “activation event” from a famous PLG company is usually the wrong milestone.
20–30% at standout PLG — not a universal 40%
OpenView 2022 Product Benchmarks, as Amplitude reports them: only 20–30% of new users reach activation at standout PLG companies. The same write-up frames onboarding as reducing time to value as indicated by activation rates. A 25% aha-event sitting on a standout-PLG definition can be inside that band and still be the wrong bar for a Userpilot-style industry comparison, or for a day-7 return proxy.
This page does not import OpenView visitor→signup percentages, free-to-paid chart numbers, or “80% higher revenue multipliers.” Those are easy to mislabel here. Stick to the activation 20–30% standout-PLG line and the aha definition.
How to run it
How to run an activation tripwire without faking scale
This is Yibud’s suggested sequence, not a Userpilot or Amplitude mandate. Honor the tripwire you wrote before the first cohort report. If you cannot name the decision the number would change, you are building a slide.
- 1
Write the tripwire before you look
Named aha milestone — experienced value, not “opened email” or a bare login unless login is the value. Named new-user cohort. Window, or day-7 return if you are using Amplitude’s proxy (label it). Threshold matched to industry/complexity (Userpilot industry bands as orientation only) and to the definition you actually use (Amplitude 7% only when measuring day-7 return). Named action if missed: fix the path to first value, stop paid acquisition for that segment, redefine a vanity milestone, or improve time-to-value before scaling signups. Date the page. Do not rewrite the bar after the close.
- 2
Lock numerator, denominator, and the definition
New users in the named cohort are the denominator. Users who reached the named aha inside the named window are the numerator — unless you are measuring day-7 return, in which case the numerator is users who returned on day seven. Say which. An “activation” that silently swaps visitors for signups, or a day-7 return relabeled as aha-event %, is a different metric. Write the definitions before the first report.
- 3
Always sit the rate next to the milestone, the window, and TTV
Never board-slide a bare %. Userpilot’s same 62-company dashboard reports TTV beside activation (primary average 1 day, 12 hours, 23 min; second listed average 1 day, 1 hour, 54 min). A 40% aha-event rate with a 30-day TTV is a different machine from a 40% rate with a same-day aha. Put both on the dated page.
- 4
Match the bar to the definition and the industry — do not chase 37%
Use Userpilot’s industry row as orientation for an aha-event % (FinTech 5% is not AI 54.8%). Use Amplitude’s 7% only for day-7 return. Use OpenView’s 20–30% only when you mean standout-PLG aha completion as they framed it. Do not average the three into a homemade “good activation is 40%.”
- 5
Honor the action. If you are pre-product, use a different instrument.
If the window closes and you missed the bar you wrote, do the thing you named. Do not switch the milestone after the miss so the slide recovers. No signups and no named aha yet? Do not “optimize activation.” Use interviews, a willingness-to-pay test, a smoke test, or kill criteria first. A Yibud score is not activation rate.
What you leave with
The activation tripwire (copy this)
If the sitting produced a percentage and no dated action, you did not finish. Fill the brackets. Leave nothing as “activation is 37% so we are normal.”
The fill-in contract
Product: [name]. Cohort C: [ICP / segment / channel], written before the first report. Milestone M: [the product-specific aha — experienced value, not “opened email” / “viewed dashboard” unless that is the value]. As-of date D: [ ]. Window W: [e.g. 7 days / 14 days / first session] — or day-7 return if using Amplitude’s proxy; label which definition. Hypothesis this number can falsify: [new users on this path reach first value, so we can scale signups / keep this onboarding]. Signups n: [ ]. Reached M inside W: [ ]. Activation: [ ]%. TTV to M (if we have it): [median / p75]. Threshold: [e.g. aha-event % oriented to Userpilot’s industry band for our category — FinTech 5% / HR 8.3% / Healthcare 23.8% / MarTech 24% / CRM 42.6% / AI 54.8% as orientation, not law; or ≥7% day-7 return only if we are measuring return; not the 37.5% sample average; not a homemade 40%]. Action if we miss: [fix path to first value / stop paid acquisition for this segment / redefine vanity milestone / improve TTV before scaling signups]. Action if we clear: [keep going / next vintage on the same definitions]. A Yibud score does not fire this line.
Userpilot industry bands and Amplitude’s 7% are orientation, not a law, and not permission to skip the named milestone. Rewrite the threshold before you measure if you have a reason. Do not rewrite it after.
Example tripwire (Yibud’s suggested template, not a law)
If, for self-serve cohort C as of 1 March, the share that complete “first report generated for a real dataset” within 7 days is below 20% when we close that vintage → we do not 3× paid acquisition in Q3; we fix the path to first value and we do not relabel “viewed dashboard” as the aha just to chase Userpilot’s 37.5%. Report TTV to that milestone in the next column. Do not paste Amplitude’s 7% day-7 return onto this aha-event sitting. Do not paste OpenView’s 20–30% standout-PLG line onto a FinTech book without saying which definition we used.
A 22% aha-event rate on a MarTech-like path is still one vintage. A Yibud report score does not fire this tripwire. If you have no signups and no named aha yet, this template is the wrong first instrument.
The fork
When to use an activation tripwire — and when not to
Activation rate is the wrong first instrument when there is no signup cohort and no named aha yet. It is the right instrument when users can already reach a first-value event and you are about to scale acquisition, copy another product’s “37%,” or treat a dashboard checkbox as value.
Use it when you have signups and a named aha
You can name the cohort, the milestone, the window, and which definition you are using. You are about to 3× signup ads, copy a famous PLG aha event, or tell yourself “activation is 37% so we are normal.” That is when a dated tripwire earns its keep. Always sit the rate next to the milestone and TTV. Optional: run Time to Value, trial-to-paid, or kill criteria as separate sittings — do not average them into a homemade “product score.”
Do not start here when you are pre-product or still discovering
No signups? No named aha? There is no honest activation rate. Do not invent a forecast 37%. Still testing whether anyone has the problem, will pay, or would be very disappointed? Use interviews, a willingness-to-pay test, a landing smoke test, the Ellis PMF survey, or kill / pivot / critical-assumption contracts first. Once you have signups and a named aha event, write the activation tripwire for that cohort + milestone + window. Do not starve discovery to decorate an activation slide. A Yibud score is not activation rate.
Not the same page
Activation rate vs Time to Value, trial-to-paid, vanity metrics, and the neighbors
Several Yibud pages sit next to this one. Mixing them up turns a clock, a later payment, a habit curve, or a waitlist into “activation is 37%, so scale.”
Time to Value — the clock, not the rate
That page asks how long until a named first outcome. This page asks how many of a named new-user cohort reached it inside a named window. A 12-hour median TTV does not tell you activation is 40%. A 40% activation rate does not tell you when aha happened. Slow TTV can starve activation. They are still different instruments. This page does not copy Bessemer/Gainsight TTV vignettes.
Time to Value for startups →Trial-to-paid — later monetization, not aha completion
That page asks how many of a named free cohort paid inside a named window. This page asks how many experienced first value. A 5% free-to-paid does not tell you activation is 30%. A 30% aha-event rate does not tell you they paid. Do not borrow ChartMogul’s 8% median or GOOD / GREAT bands onto this page.
SaaS trial-to-paid conversion →Retention curves — habit after the gate
That page plots whether a cohort still does the core action at day N. Activation is the gate into that retained cohort. A flatten at week 4 does not tell you first-week aha-event %. A 30% activation rate does not tell you the line held. Report them on their own pages.
Retention curves for startups →Vanity metrics — hygiene class; activation fails when the sitting is undefined
That page is the sorting hat: hits, cumulative sign-ups, and waitlist size feel like progress. An activation % with no named event, no window, no cohort, and no tripwire is vanity in a nicer font. “Viewed dashboard” as the aha is the same class unless that view is the value.
Vanity metrics for startups →NPS — sentiment, not first-value completion
That page is how willing users say they are to recommend you. It is not the share who reached a named aha. A 50 NPS does not tell you activation is 30%. A 30% activation rate does not tell you they would recommend you.
NPS for early-stage startups →Discovery and decision contracts — earlier instruments
Willingness to pay, smoke-test sample size, the Ellis PMF survey, kill criteria, pivot criteria, and critical-assumption validation write money evidence, landing interest, disappointment, Stop, rewrite-one-dimension, or the one claim that would kill the idea. Activation is later, and only after signups and a named aha exist. Use those pages first when you are still pre-product.
Where Yibud fits
Neither activation rate nor a Yibud score predicts success
Yibud is a free, no-signup startup idea validator. One-line idea plus five questions. Scores come from a deterministic rule engine, not from a language model guessing success. Optional AI text, when it is used, only polishes prose. It does not invent the number. A Startup MRI report can name a weak acquisition or onboarding assumption, then a Day-7 Continue / Refine / Re-test / Stop signal. The score is a flashlight on the weakest assumption to test next — not activation rate, not Userpilot’s 37.5%, not a forecast. Activation work sits next to that assumption: write the cohort + milestone + window floor, do not hope a famous PLG aha means your cohort will experience value. If you already have a report, start with the named assumption, not the overall score. Then run the cohort yourself. The method on this page stands alone if you never open the analyzer.
Analyze my idea →Common mistakes
What usually wastes an activation week
Chasing 37% across industries
Userpilot 2025: average 37.5%, median 37.04%, n=62. Industry: AI & ML 54.8% down to FinTech & Insurance 5%. Treating 37% as “normal” is how you panic an 8% HR sitting that may match complexity, or celebrate a 40% FinTech sitting that is far above that industry’s 5% band for the wrong reason — a vanity milestone.
Mixing day-7 return with aha-event %
Amplitude’s 7% is the share of the original cohort that return on day seven (top 25% in a 2,600+ company analysis). Userpilot’s 37.5% is new users completing a specific initial-value action. OpenView’s 20–30% is standout-PLG aha completion. Putting them in one unlabeled sentence is how a return-retention proxy becomes “we are below 37%.” Label the definition.
Vanity milestones — “viewed dashboard,” “opened email,” bare login
Userpilot: activation is first experience of product value; the rate is completing a specific action that demonstrates that value. Poyar: solving the problem that brought the user. A tooltip click, an email open, or a login that does not correlate with later retention is a vanity stop. If the named outcome would not show up as value, you named the wrong milestone.
Reporting a % without a window
A 7-day aha-event rate, a 14-day rate, and Amplitude’s day-7 return are all usable. A bare “activation is 41%” is not. Name the window — or say you are measuring day-7 return — on the dated page. Userpilot’s TTV (primary average 1 day, 12 hours, 23 min) belongs in the next column when you have it.
Optimizing activation while starving discovery
Pre-product, there is no honest activation rate. Narrowing interviews, skipping a willingness-to-pay test, or killing a smoke test so the “activation” slide looks busy is how you decorate a dashboard and miss the problem. Write discovery tripwires first. Write this one once signups and a named aha exist.
Claiming activation ≥ X proves product-market fit
Clearing a pre-written cohort + milestone + window floor means that vintage cleared a gate you wrote. It does not prove PMF, does not prove you will succeed, and is not a Yibud GO. Ellis’s very-disappointed question, a retention-curve flatten, and willingness to pay are different sittings. Keep them on their own pages.
Sources
Where these ideas come from
- Userpilot, “SaaS Product Metrics” Benchmark Report 2025 — Used for the user-activation and activation-rate definitions; average 37.5% / median 37.04% (n=62 B2B SaaS); broader report 547 SaaS companies; industry AI & ML 54.8% / CRM & Sales 42.6% / MarTech 24% / Healthcare 23.8% / HR 8.3% / FinTech & Insurance 5%; primary TTV average 1 day, 12 hours, 23 min and the second listed TTV average 1 day, 1 hour, 54 min on the same card; optional related metrics onboarding checklist completion 19.2% / 10.1% (n=188) and core feature adoption 24.5% / 16.5% (n=181). First-party anonymized Userpilot Analytics; page dated/modified 12 September 2025. Omits Fairmarkit 25%→34% MRR and image-only PLG vs SLG activation percentages.
- Amplitude / Michele Morales, “The 7% retention rule explained,” 30 September 2025 — Used for the day-7 return definition; 7% of the original cohort returning on day seven → top 25% for activation performance; 69% of top day-seven performers also top three-month performers; enterprise top 10% 12.4% vs median 2.1% (~6×); day-14 activation rate for 90th-percentile products ≈ 9%; for half of products analyzed, over 98% of new users no longer active at the two-week mark; optional 90th-percentile three-month retention vignettes financial services 19.5% / travel & hospitality 25.6% / B2B technology 15.6% (retention outcomes, not activation-rate targets). 2025 Product Benchmark Report analysis of over 2,600 companies. Omits SafetyCulture / Super.com / WeMoney case-study lift percentages.
- Amplitude / Noorisingh Saini, “How to Benchmark Product-led Growth with OpenView Partners Blake Bartlett and Kyle Poyar,” 1 August 2022 — Used for Poyar’s activation = solving the problem that brought the user (aha; metrics differ by product); OpenView 2022 Product Benchmarks: only 20–30% of new users reach activation at standout PLG companies; onboarding framed as reducing time to value as indicated by activation rates. Omits visitor→signup percentages, free-to-paid OpenView chart numbers, and “80% higher revenue multipliers.”
In one paragraph
Summary you can quote
Activation rate is the share of a named new-user cohort that reaches a named first-value / aha event inside a named window. It answers how many experienced the value event you named — not whether you will succeed. Write cohort + milestone + window + threshold + named action before you look. Userpilot 2025 (62 B2B SaaS; broader report 547): average 37.5%, median 37.04%; industry AI & ML 54.8% / CRM 42.6% / MarTech 24% / Healthcare 23.8% / HR 8.3% / FinTech 5%; primary TTV average 1 day, 12 hours, 23 min. Amplitude 2025 (2,600+ companies): 7% day-7 return = top 25%; 69% of those top day-seven performers were also top three-month; enterprise 12.4% vs 2.1%; day-14 p90 ≈ 9%. OpenView 2022 via Amplitude: 20–30% of new users reach activation at standout PLG companies. Those three sittings are not the same formula. Always report the % next to the milestone and the window. Matching the floor is a decision signal. Neither activation rate nor a Yibud score predicts success.
FAQ
Questions founders actually ask
What is SaaS activation rate / user activation rate?
The percentage of a named new-user cohort that reaches a named first-value / aha event inside a named window. Userpilot: user activation is the moment the user experiences the value of the product for the first time; the rate is the percentage of new users who complete a specific action that demonstrates that initial value. Always name cohort, milestone, window, and as-of date. It is a first-value tripwire, not a success score. Write the bar before you measure.
What is a good SaaS activation rate?
This page does not publish a universal “good activation is 40%.” Userpilot 2025: average 37.5%, median 37.04% (n=62), with industry from FinTech 5% to AI & ML 54.8%. Amplitude 2025: 7% day-7 return = top 25% — a return-retention proxy, not an aha-event %. OpenView 2022: 20–30% of new users reach activation at standout PLG companies. Write your own tripwire for your cohort + milestone + window, matched to the definition you use. Matching a band is not PMF and not a forecast.
How is this different from Time to Value and from trial-to-paid conversion?
Time to Value is the clock to a named first outcome. Activation rate is the share of a named cohort who reach it inside a named window. Trial-to-paid is later monetization of a free cohort. A 12-hour TTV does not tell you activation is 40%. A 5% free-to-paid does not tell you they hit aha. Keep the instruments on separate pages. This page does not copy Bessemer/Gainsight TTV numbers or ChartMogul conversion bands.
Should I use Amplitude’s 7% as my activation target?
Only if you are measuring day-7 return — the share of the original cohort that come back on day seven — and you wrote that definition first. Amplitude: 7% puts you in the top 25% of a 2,600+ company analysis; 69% of top day-seven performers were also top three-month. It is not Userpilot’s aha-event %, and it is not OpenView’s 20–30% standout-PLG line. Do not chase 7% on an action-completion sitting, and do not chase 37.5% on a return sitting.
Is a Yibud score the same as activation rate? Does hitting 37% predict success?
No and no. Yibud scores come from a deterministic rule engine on your idea inputs. They point at the weakest assumption to test next. They are not activation rate, not a 37.5% average, and not a forecast. Neither a Userpilot industry band, an Amplitude day-7 sitting, an OpenView 20–30% line, nor a Yibud report score predicts success. You do not need an account to use this page.
Write the activation tripwire before you chase 37%
Yibud scores weak assumptions with a deterministic engine. You write cohort, milestone, window, threshold, and action while you are still honest — then a vintage of activation is a tripwire, not a 37% slide with no aha underneath.
Generate a Yibud report →