Benchmarks Are Context, Not Targets

A product benchmark tells you where you stand relative to other products. Turn a benchmark into a target and you have swapped your product’s real goal for someone else’s median. That is what “we need Day-90 retention of 15% because that’s the top of the B2B range” does.

Teams get burned by trusting one number out of context and steering toward it. Treat a benchmark as a target and you end up optimizing a metric while the business underneath it stalls.

What’s the difference between context and a target?

A benchmark is a directional reference: the typical range a comparable product sees for a metric, used to interpret your own number.

A target is a number you commit to hitting, derived from your own goals, constraints, and customer reality.

The benchmark answers “is this normal?” The target answers “is this what we should aim for?”

Does the number change when you switch from B2B to consumer, from self-serve to enterprise, or from a daily-use tool to a quarterly-use one? Then it is context. Two healthy products can sit at opposite ends of the same range for good reasons.

Why turning a benchmark into a target backfires

1. Benchmarks are averages, and you are not average

Every range you’ll see, ours included, is an industry average across a messy population of products. The KPI benchmark canvas the tool draws on calls them “directional references, not absolute targets” in its first line.

Take K-factor, the viral coefficient: how many new users each user brings before their influence runs out. For B2B SaaS the typical range is 0.1 to 0.3. Anything above 0.3 is unusually strong unless the product has built-in collaboration loops (Reforge, Andrew Chen). For consumer apps it’s 0.3 to 0.7.

A B2B founder reads a consumer growth blog, sees “aim for K above 0.5,” and sets that as the target. The team is now committed to a number that is abnormal for its category.

2. One number in isolation lies

The classic example is LTV:CAC, the ratio of customer lifetime value to acquisition cost.

The healthy range is 3:1 to 5:1. Above 5:1 often means you’re underinvesting in growth (Bessemer State of the Cloud, OpenView SaaS Benchmarks, a16z).

You only catch that by reading LTV:CAC next to CAC payback period, the months of margin it takes to earn back acquisition cost. For SMB/self-serve that’s 6 to 12 months. For enterprise sales it’s 12 to 24 months (OpenView, KeyBanc SaaS Survey).

In a self-serve business, a 5:1 ratio with a 20-month payback is a different situation from a 5:1 ratio with a 7-month payback. (More in LTV:CAC looks great but you’re not growing.)

3. Targets pulled from benchmarks aim at the median, not at health

An industry average is the middle of a distribution that includes struggling products. Steering toward the average can mean steering down from where a strong product sits. It can also mean steering up toward a number your customers’ usage cadence will never support.

Retention makes this concrete. The B2B Day-7 figure most people quote, 40% to 60% (Pendo), is a returning-user rate: the share of already-active users who come back. A consumer app’s Day-7 cohort retention, the share of all installs still active, is 8% to 15%, with many apps below 10% (AppsFlyer, Amplitude).

A consumer team that imports the B2B “40% to 60%” as a target will feel like it is failing at 12%. Yet 12% is good for their category, and the 40% was never the same metric.

The benchmark ranges, and how to read each one

This is the same data the tool uses, laid out as context.

B2B SaaS (averages)

B2B figures are cohort retention (Amplitude for Day 90; Day 1 and Day 7 are estimates). Pendo’s returning-user rates (50 to 70% Day 1, 40 to 60% Day 7, 25 to 35% at 90 days) measure something else and are not comparable.

Consumer apps (averages)

The tool ships activation ranges for onboarding completion and activation. Those numbers don’t yet have per-number sourcing the way retention and unit economics do. Treat activation benchmarks as the loosest context of the lot.

The bottom of the canvas adds two rules. Don’t compare B2B and consumer directly, since they follow different growth mechanics. Look for curve flattening, not just absolute numbers.

A retention number that’s “below benchmark” but has clearly stopped falling is often healthier than one inside the range and still dropping. (More on reading the shape of the curve in retention rate benchmarks and B2B vs consumer growth.)

How should you use a benchmark?

1. Sanity-check, not scoreboard. The first question is always “is this number normal for a product like mine?” Say your B2B Day-90 cohort retention is 2%. Read against the 2.5% to 15.6% range, that means something is wrong upstream, probably onboarding or value clarity. Investigate that before you touch any growth lever.

2. Interpret pairs, not points. Never read LTV:CAC without payback period. Never read K-factor without cycle time. A K of 0.6 with a two-week loop beats a K of 0.8 with a 60-day loop, because growth rate is K divided by cycle time. The K-factor article works that math in full.

3. Set your own target from your own model. Your Day-1 retention target should come from what your activated users need to do to get value, and how often that job recurs. Then use the benchmark to check whether the target is wildly out of line with reality.

A cohort growth model derives a target by connecting retention, new-user inflow, and viral compounding into one forward projection.

See where your numbers land

The hard part is reading benchmark numbers in context without turning them into targets. That is why we built the free benchmark tool.

It charts your retention curve, K-factor, and unit economics against the B2B and consumer ranges side by side. It keeps each number next to its caveat. It shows the shape of your curve rather than a single pass/fail verdict. It takes six minutes, with no signup gymnastics.

Check your numbers against the benchmarks → benchmark.scilla.studio

Sources: Bessemer State of the Cloud, OpenView SaaS Benchmarks, a16z, KeyBanc SaaS Survey, Reforge, Andrew Chen, Pendo Product Benchmarks, Amplitude, Mixpanel, Userpilot, Adjust, AppsFlyer, Statista, Mobile Dev Memo. Benchmark ranges consolidated in the tool’s own KPI canvas and used throughout the benchmark tool.