%20scilla.studio.svg)
If you only remember one thing from this page, make it this: a B2B SaaS company with healthy fundamentals in 2026 tends to land around Day-7 retention of 40 to 60%, an LTV:CAC ratio of 3:1 to 5:1, CAC payback inside 12 months for self-serve (longer for enterprise), and a K-factor of 0.1 to 0.3. Virality is weak in B2B, and that's normal. Those are the load-bearing numbers. Everything else is either a leading indicator of one of them or a vanity metric in disguise.
But here's the thing this whole page is built around, and the thing most "ultimate benchmark guides" quietly get wrong: benchmarks give you context, not targets. They tell you whether your number is weird, not whether it's good. A 3:1 LTV:CAC can mean you're efficient, or it can mean you're starving growth to look efficient. A 25% Day-90 retention can be excellent for a deliberate, low-frequency workflow tool and alarming for a daily-use product. The number only means something next to your business model, your sales motion, and the other numbers around it.
So this is the pillar. Below, each metric gets a short, honest summary of where the B2B band sits and why, plus a link to the deep-dive when you want the full treatment. Read it top to bottom for a mental model, or jump to the metric that's keeping you up at night.
A note on scope: this page is B2B SaaS throughout. Consumer apps follow completely different mechanics (faster acquisition, far steeper retention decay, higher virality), and lumping them together is how people end up panicking over a "low" number that's actually fine. The consumer side lives in its own pillar: Consumer app benchmarks 2026.
A benchmark is the industry's rough distribution for a metric. It answers one question well, "is my number unusual?", and zero others. It does not answer "is my number good?", because "good" depends on things a benchmark can't see: whether you're self-serve or enterprise, freemium or paid-trial, daily-use or quarterly-use, two months post-launch or eight years in.
The honest way to use the numbers below:
That's it. Use them to ask better questions, not to grade yourself.
Retention is the percentage of users who come back after their first use, measured at a fixed point in time (Day 1, Day 7, Day 90). It's the closest thing to a single readout of whether your product actually delivers value, because nobody comes back to something that doesn't.
Look at retention before you look at CAC efficiency. Why? Because acquisition efficiency built on top of weak retention is a leak you're paying to fill. If users don't stick, a great CAC just means you're acquiring churn faster.
| Metric | B2B SaaS benchmark (avg) | What it signals |
|---|---|---|
| Day-1 retention | 50 to 70% | Most activated users return at least once; a low number points at onboarding or value-clarity problems. |
| Day-7 retention | 40 to 60% | Early habit formation / workflow relevance. The first real "did this stick?" checkpoint. |
| Day-14 retention | 35 to 55% | The curve should be flattening by now; a steep drop here signals a weak core loop. |
| Day-90 retention | 25 to 35% | Long-term value. Below 20% is a red flag for B2B. |
Sources: Pendo Product Benchmarks, Amplitude, Mixpanel, Userpilot.
Here's the part most guides skip: the shape of the curve matters more than any single point. A retention curve that drops and then flattens into a stable plateau means you have a group of people who found durable value; that flattening is the visual signature of product-market fit. A curve that keeps sliding toward zero means you don't, no matter how pretty Day 1 looks. Two products can share an identical Day-7 number and have completely different futures depending on whether the line levels off or keeps falling.
And measure it the same way every time. "Retention" can mean came-back-on-exactly-Day-7 (n-day), came-back-anytime-that-week (bracketed), or used-a-core-feature (unbounded). They're not interchangeable, and comparing your bracketed number to someone's n-day benchmark is how you scare yourself for no reason.
→ Full treatment, including how to read the curve and the three definitions, is in Retention rate benchmarks. For why the flattening specifically signals fit, see What is product-market fit.
LTV:CAC is the ratio of the lifetime value of a customer to what it cost to acquire them. It's the one-line answer to "do the unit economics work?"
Formula: LTV:CAC = (average revenue per customer × gross margin × average customer lifetime) ÷ fully-loaded customer acquisition cost. A 3:1 ratio means every $1 of acquisition spend returns $3 of lifetime gross profit.
| Metric | B2B SaaS benchmark | Comment |
|---|---|---|
| LTV:CAC | 3:1 to 5:1 | ~3:1 is the minimum healthy baseline. Below 2:1 is structurally risky. Above 5:1 often means you're under-investing in growth. |
Sources: Bessemer State of the Cloud, OpenView SaaS Benchmarks, a16z, Wall Street Prep.
Now the opinionated bit. In my honest, experience-earned opinion, a suspiciously high LTV:CAC is one of the most under-discussed signals in SaaS. Most people see 7:1 and feel great. But if the market is there and your economics are that good, why aren't you spending more to capture it? A very high ratio frequently means there's profitable growth sitting on the table that you're choosing not to buy (and yes, that means your "great" ratio might be a warning sign rather than a trophy). 3:1 to 5:1 is the band where you're efficient and actually pressing on the accelerator.
The other trap: LTV:CAC says nothing about when the cash comes back. A 5:1 ratio where it takes two years to recoup CAC can sink a company that's growing fast and running out of runway. Which is exactly why you never read this metric alone; you read it next to payback.
→ Full worked examples, margin treatment, and the over-investment trap: LTV:CAC ratio explained.
CAC payback period is how many months of gross profit from a customer it takes to recoup the cost of acquiring them. LTV:CAC tells you if the economics work; payback tells you when, and "when" is what determines whether you survive long enough to enjoy the "if."
Formula: CAC payback (months) = CAC ÷ (monthly revenue per customer × gross margin).
Worked example: a CAC of $6,000, a customer paying $500/month at 80% gross margin, gives $6,000 ÷ ($500 × 0.80) = $6,000 ÷ $400 = 15 months to recoup. Comfortably fine for an enterprise motion; a warning sign for self-serve.
| Motion | CAC payback benchmark | Comment |
|---|---|---|
| SMB / self-serve | 6 to 12 months | Under 12 months is considered strong. |
| Enterprise sales | 12 to 24 months | Longer payback is acceptable only with very high retention and expansion to back it up. |
Sources: OpenView, KeyBanc SaaS Survey.
The motion is the whole story here. A 20-month payback isn't automatically bad. For enterprise deals with multi-year contracts and strong net revenue retention, it can be perfectly healthy. The same 20 months for a self-serve product that churns at 4% a month is a slow-motion bankruptcy. This is the clearest example on the page of why a benchmark without context is useless: the same number is fine in one column and fatal in the other.
Pair it with retention every time. Long payback is only survivable when customers stick around well past the payback point and ideally expand. Short retention plus long payback is the combination that quietly kills otherwise promising companies.
→ The motion-by-motion breakdown and how expansion changes the math, is in CAC payback period explained.
K-factor (the viral coefficient) is how many additional users each new user generates through the product itself: sharing, inviting, collaborating, leaving branded artifacts in the wild. K = 1.0 means each user brings exactly one more, and growth becomes self-sustaining.
Formula (generalized): K = (viral outputs per user) × (signups per output).
| Metric | B2B SaaS benchmark | Comment |
|---|---|---|
| K-factor | 0.1 to 0.3 | B2B virality is usually weak. Above 0.3 is unusually strong unless the product has genuine built-in collaboration loops. |
Sources: Reforge, Andrew Chen.
Let me set expectations honestly: if you're B2B and your K-factor is 0.2, you are completely normal. The products that beat the band (the Slacks, Figmas, Looms) have collaboration baked into the core job, where using the product necessarily exposes a colleague. If your product is used heads-down by one person, no growth-hack bolt-on is going to manufacture a 0.6. Don't chase a number the product's nature won't support.
Here's the interesting part most K-factor discussions miss: cycle time matters as much as the coefficient. A K of 0.5 that takes 45 days to complete one loop is slower-growing than a K of 0.3 that cycles every 14 days. The combined picture is monthly growth rate ≈ K ÷ cycle time in months. Halving your cycle time has the same effect as doubling K, and it's often far more achievable. Strong retention helps here too: a daily-active user gives you ~30 chances a month to generate a viral output; a monthly user gives you one.
→ The full framework (multiple loops, cycle time, worked examples from Loom and Notion) is in Understanding K-factor in product growth.
Activation is the share of new users who reach the moment where the product's core value clicks: completing onboarding, then hitting the "aha" action that predicts they'll stick. It's the bridge between acquisition and retention: weak activation caps your retention before the user ever forms a habit.
Unlike the retention and LTV:CAC bands above, these activation ranges are directional estimates rather than sourced benchmarks, because activation is defined so differently from product to product that no clean industry distribution exists. Treat them as a rough sanity-check, not a target.
| Metric | B2B SaaS directional estimate (not a sourced benchmark) | What it measures |
|---|---|---|
| Day-1 onboarding completion | 55 to 75% (estimate) | Share of new users who finish initial setup/onboarding. |
| Day-7 activation rate | 25 to 40% (estimate) | Share who reach the core-value / "aha" action within the first week. |
These ranges are directional estimates informed by Lenny's Newsletter on activation rate, Userpilot Product Metrics, and OpenView PLG Benchmarks, none of which publish a single agreed B2B activation band. Define and measure activation against your own aha moment.
The thing to internalize: activation is the cheapest retention lever you have. Fixing why 60% of signups never reach first value is almost always higher-ROI than re-acquiring to replace the ones who churned out the back. And "activation" has to be defined as your aha moment: the specific action that, in your data, separates the users who stay from the ones who vanish. Borrowing someone else's definition gives you a number that looks fine and predicts nothing.
→ Activation sits inside the broader fit picture; the deep-dive on what "reaching value" really means lives in What is product-market fit.
There's no single tidy "good growth rate" benchmark, and anyone who hands you one without asking your stage and motion is selling something. Growth rate is an output of the metrics above; it's what retention, activation, unit economics, and any viral loops produce when you run them forward. Chase the rate directly and you get the classic leaky-bucket failure: pour acquisition into a product people don't keep, watch the topline rise, then watch it collapse when the cohorts churn.
The way the benchmark tool models it is the way to think about it: growth is a cohort simulation with two pools. A stable base of long-tenured users who already survived the funnel and now churn slowly, plus new cohorts each month that retain at your M1 rate and graduate into the base if they survive. The two levers are monthly retention (what fraction of each new cohort survives) and K-factor (how many new users each user brings). Sustainable growth is what happens when surviving new cohorts plus any viral additions outrun the slow churn of the mature base. It compounds quietly, which is exactly why durable retention beats a flashy acquisition spike every time.
So don't benchmark your growth rate in isolation. Benchmark the inputs (retention, activation, payback, K), and let the rate be the scoreboard.
Your North Star metric is the single number that best captures the value your product delivers to customers: the thing that, if it goes up the right way, means the business is genuinely healthier, not just busier. You don't compare it against the industry the way you do a benchmark; you choose it yourself so your whole team optimizes for real value instead of vanity.
There's deliberately no benchmark band here, and that's the point. A good North Star is product-specific: messages sent, weekly active workspaces, documents collaborated on, jobs completed. The benchmarks on this page are the supporting cast: the diagnostic inputs that tell you whether your North Star is moving for durable reasons (retention, efficient acquisition) or fragile ones (a discount, a launch spike, a vanity count that doesn't map to value).
The test for a North Star: if it grows, do customers genuinely get more value and does the business get healthier? If you can answer yes to both, you've found it. If growth in the metric can happen while customers are getting less value, it's a vanity metric wearing a North Star costume.
| Metric | B2B SaaS band | One-line read |
|---|---|---|
| Day-1 retention | 50 to 70% | Did activated users come back at all? |
| Day-7 retention | 40 to 60% | First real "did it stick?" checkpoint. |
| Day-90 retention | 25 to 35% | Long-term value; the curve should have plateaued. |
| LTV:CAC | 3:1 to 5:1 | Economics work, but >5:1 can mean under-investing. |
| CAC payback | 6 to 12 mo (self-serve) / 12 to 24 mo (enterprise) | When the cash comes back; read against retention. |
| K-factor | 0.1 to 0.3 | Weak B2B virality is normal; cycle time matters as much. |
| Day-1 onboarding completion | 55 to 75% (directional estimate) | Did new users finish setup? |
| Day-7 activation | 25 to 40% (directional estimate) | Did they reach core value? |
Full sources: Bessemer, OpenView, KeyBanc, a16z, Wall Street Prep, Pendo, Amplitude, Mixpanel, Userpilot, Reforge, Andrew Chen, Lenny's Newsletter.
Reading benchmarks is one thing; seeing your own product charted against them is where the questions get sharp. The free benchmark tool plots your retention curve, K-factor, and unit economics against the B2B SaaS band (and the Consumer band, if you want the contrast) in a couple of minutes, with no signup gauntlet and no sales call. It won't tell you if your numbers are "good." It'll show you which ones are unusual, so you know which question to chase next.
→ Run your numbers at benchmark.scilla.studio
What are the most important B2B SaaS growth metrics in 2026? Retention (Day-1, Day-7, Day-90), LTV:CAC ratio, CAC payback period, K-factor, and activation rate. Retention is the one to read first, because efficient acquisition on top of weak retention is a paid leak. Growth rate and your North Star are outputs of these, not standalone targets.
What is a good retention rate for B2B SaaS? Roughly Day-1 50 to 70%, Day-7 40 to 60%, and Day-90 25 to 35% on average (Pendo, Amplitude). But the shape matters more than any point: a curve that flattens into a stable plateau signals durable value (and product-market fit); one that keeps sliding toward zero doesn't, however strong Day 1 looks.
What is a good LTV:CAC ratio for B2B SaaS? 3:1 to 5:1 (Bessemer, OpenView, a16z). Below 2:1 is structurally risky. Above 5:1 often means you're under-investing in growth: efficient, but leaving profitable acquisition on the table. Always read it alongside CAC payback, which tells you when the cash returns.
What is a good CAC payback period for B2B SaaS? 6 to 12 months for SMB/self-serve and 12 to 24 months for enterprise (OpenView, KeyBanc). Longer payback is only healthy when backed by strong retention and expansion; short retention plus long payback is the combination that quietly kills companies.
Is a low K-factor bad for a B2B product? No. B2B virality typically sits at 0.1 to 0.3 (Reforge, Andrew Chen), and a 0.2 is completely normal. Only products with collaboration baked into the core job beat the band. And cycle time matters as much as the coefficient: a smaller K that loops faster can out-grow a larger K that loops slowly.
Should I compare my B2B numbers to consumer app benchmarks? No. B2B and consumer follow different growth mechanics: consumer acquisition is faster, retention decays far more steeply, and virality runs higher. Comparing across them is how you panic over a "low" number that's actually healthy. See Consumer app benchmarks 2026 for that side.
