Short answer: No single metric “predicts retention” on its own. What matters is whether customer accounts adopt the workflows that create value, and whether that adoption stays consistent over time. Activity can look healthy while value stays shallow, which is why teams get surprised by churn.
Explanation
Most SaaS teams start with activity metrics because they are easy to instrument and easy to chart. Logins, active users, and event volume are useful context, but they mostly tell you that something happened. They do not tell you whether the account is getting the outcome they pay for.
Retention tends to follow value, and value tends to show up as repeated completion of a small set of workflows. In B2B SaaS, those workflows usually live at the account level: multiple users, recurring tasks, and routines that become part of “how we work.” When you measure activity without anchoring it to those routines, it is easy to overestimate health.
Why it happens in practice
In practice, accounts can generate steady usage while remaining replaceable. A few power users may do the same reporting flow each week, while the broader team never adopts the core workflow that would embed the product. The charts stay stable, but the product stays optional.
Another common pattern is early exploration without follow-through. Teams click around, try features, and create a burst of events, but the workflows that would create dependency never become habitual. When renewal comes up, nothing “broke,” yet the account does not feel committed to staying.
What most teams misunderstand
Teams often assume that more activity means more value. It sometimes does, but the relationship is not linear, and it depends on which actions are happening and who in the account is doing them. If the same two users drive most usage, the account-level picture can still be weak.
They also treat retention as a user-level question in a B2B context. Contracts, renewals, and churn decisions are made by organizations, not individuals, so the unit of analysis needs to match. If your metrics cannot be explained in account terms, they rarely hold up in renewal discussions.
What actually works
A practical way to approach this is to define one or two “value workflows” for your product and measure adoption of those workflows per account. Then track consistency: is the workflow completed repeatedly over time, and is usage spreading beyond one person or one team? This tends to be more stable than chasing higher event volume.
Once you have that baseline, you can add a small set of leading signals: accounts that never reach the workflow, accounts that plateau after onboarding, and accounts where usage becomes concentrated. These are not perfect predictors, but they are often early enough to be actionable, and they connect naturally to how retention and revenue actually work.
Many of these patterns only become visible once you move beyond surface-level activity. For example, active users can still churn if value is never established: Why active users still churn in SaaS.
Conclusion
Retention is rarely explained by a single chart. It is better understood as account-level adoption of value workflows, repeated consistently enough that the product becomes hard to replace. If you anchor metrics to that reality, activity becomes useful context instead of a misleading proxy.