Your Stickiness Ratio Looks Fine. That's Exactly the Problem.

Someone on your team pulled the stickiness ratio into a slide last week. It was a decent number - Green-ish. Nobody argued with it, and the meeting moved on to the next chart. That's usually how it goes with DAU/MAU. It gets quoted, nodded at, and never actually questioned.

Which is a shame because a stickiness ratio that looks fine can be sitting on top of a product that's slowly falling apart. The number stays calm while the engine underneath it starts to knock.

Let's pull it apart properly...

What the stickiness ratio actually measures

The stickiness ratio is simple maths. Take your average daily active users, divide by your monthly active users, and you get a percentage. If 3,000 people use your product on an average day and 10,000 use it across the month, you're at 30%.

The idea behind it is fair enough. It's a rough read on how often people come back. A high ratio means a big chunk of your monthly users show up most days. A low one means most people drift in once, poke around, and vanish until something drags them back.

So far, so useful. The trouble starts the second you treat that one percentage as a verdict on the whole product. It isn't. It's an average sitting on top of an average, and averages are very good at hiding the things you most need to see.

The benchmark everyone quotes is out of date

Here's where a lot of teams go wrong before they even start.

For years the rule of thumb was 40%. Hit 40% and you were a "sticky" product. Miss it and you weren't. People still quote that number in board decks today. The problem is the ground moved underneath it. Mixpanel's 2026 analysis of over 12,000 companies puts average B2B SaaS stickiness closer to 31%, well below the old 40% standard.

So teams have spent years measuring themselves against a bar that was never realistic for most products. Panic sets in. Roadmaps get yanked around to chase daily usage that the product was never designed to produce.

The 40% thing has done real damage," says Ian Naylor, Founder of SaaSToolkit.ai. "I've watched teams tear up a perfectly good roadmap because their ratio sat at 22%, when 22% was completely normal for what they'd built. Then you look at a different tool and a ratio above 20% is genuinely healthy for most SaaS, with 50%-plus being exceptional. The number isn't the problem. The made-up target next to it is.

Chasing the wrong benchmark is expensive. It burns roadmap. It burns morale.

Why a "good" ratio can still be bad news

Say your ratio is a comfy 35%. Above the average, under the old myth. Feels safe.

Now split it. Your ten most valuable accounts, the ones paying real money, might be the ones whose daily usage is quietly sliding. Meanwhile a swarm of small free users log in every day out of habit and never pay you a cent. Blend those two groups together and the average looks steady. Underneath, your revenue base is drifting toward the door while your cheapest users prop the number up.

That's the core flaw. The ratio treats every active user as identical, and they never are. A daily login from a champion who runs their whole week through your product is worth a hundred times a daily login from someone who opens the app, checks one thing, and leaves.

There's a second trap too. A rising ratio can mean people are stuck, not delighted. If users have to log in every single day just to keep something from breaking, that's friction dressed up as engagement. High stickiness, miserable customers. The number can't tell the difference, so you have to.

Daily active isn't the goal for every product

This is the part the benchmark crowd forgets. Not every product should want daily use.

A payroll tool that people open twice a month isn't broken. A tax product used hard for six weeks a year isn't failing. If your software does its job in a weekly rhythm, then measuring it against a daily-use benchmark is like judging a bus by how fast it corners. Wrong test. Wrong tool.

We ask new customers one question before they obsess over stickiness," says Becky Halls, Strategist at SaaSToolkit.ai. "How often does a happy customer actually need you? For some products the honest answer is once a week, and that's the whole point of the product. If you chase daily logins on top of that, you'll bolt on nagging notifications and streak counters that annoy your best users into leaving. We've seen a team lift their ratio and grow churn at the same time. The dial went up. The business went down.

Read that last bit twice. A better number, a worse business.

The fix isn't to bin the ratio. It's to stop reading it alone. Pair it with a metric that measures value instead of activity, so you're tracking whether people got the thing they came for, not just whether they showed up. That's the difference between a product people rely on and one people can't quite quit.

What to actually watch instead

The stickiness ratio is a smoke alarm, not a diagnosis. It can tell you something might be off. It can't tell you what, or where, or who.

Start by segmenting it. Split the ratio by plan, by cohort, by account size. The blended figure is comfortable and mostly useless. The segmented one shows you the paying accounts fading while the free crowd keeps the average warm. One of those pictures gets you promoted. The other gets you a bad quarter you didn't see coming.

Then tie usage to money. A stickiness number that isn't connected to billing is a vanity stat with good lighting. When you can see that your high-value accounts are the ones logging in less, you've got an actual early warning instead of a shrug. This is exactly where most setups fall down, because product data lives in one tool and revenue lives in another and nobody's holding both at once.

Last, watch depth, not just presence. Track which features people actually keep coming back to, because a login that touches your core workflow is worth far more than a login that bounces off the dashboard and leaves. Frequency tells you they opened the door. Depth tells you they moved in.

Do those three things and the ratio finally earns its slide. On its own it's a mood ring. Segmented, tied to revenue, and paired with depth, it becomes a genuine signal you can run on.

Your stickiness ratio isn't lying to you. It's just answering a much smaller question than the one you're asking it. Go find out who's actually sticky, and whether they're the people paying you. That's the number worth putting on the slide.

FAQ

What is a stickiness ratio? It's the DAU/MAU ratio: your average daily active users divided by your monthly active users, shown as a percentage. It's a rough measure of how often your monthly users come back. A ratio of 30% means the average day sees about a third of your monthly users active.

What is a good stickiness ratio for SaaS? It depends on how often your product is meant to be used, but for most B2B SaaS anything above 20% is healthy and 50%-plus is exceptional. The old 40% "rule" is outdated; recent analysis puts the B2B SaaS average nearer 31%. Weekly-use products will sit lower and that can be completely fine.

How do you calculate the stickiness ratio? Measure your average DAU across a period, then divide it by your MAU for the same period, and multiply by 100. If you average 2,000 daily users against 8,000 monthly users, your ratio is 25%. Track it over time rather than treating a single reading as a score.

Can a high stickiness ratio be a bad thing? Yes. A high ratio can mean users are forced to log in daily to stop something breaking, which is friction, not love. It can also be propped up by low-value free users while your paying accounts quietly fade. Always split the ratio by segment before you celebrate it.

Why shouldn't I chase daily active users? Because plenty of great products are used weekly or monthly by design, and forcing daily use often means adding nags and streaks that irritate your best customers. Match the metric to your product's natural rhythm. If a happy customer only needs you weekly, a lower ratio isn't a failure.

How does SaaSToolkit.ai help me read stickiness properly? It connects product usage and billing from a single snippet, so you can split your stickiness ratio by plan and account value and see which paying customers are fading. Instead of one blended number, you get the ratio tied to revenue and feature depth, which turns it from a vanity stat into an early-warning signal.