Customer Success Should Measure Outcomes, Not Logins

When I first stepped into CS leadership, our health reporting had a strange habit. Some of our most strategic customers kept showing up as at-risk because they didn't log in very often, even though they were using our insights to win in their market. Meanwhile, accounts that clicked around every day were marked healthy whether or not they were getting anything out of it.

We were measuring the wrong thing, and it was steering the team toward the wrong accounts.

Activity is easy to count, so we count it

Most CS teams track some version of the same list: daily active users, weekly logins, feature clicks, pageviews. None of those are useless. They just aren't what the customer bought.

Nobody signs a contract because they want to log in more. They sign because they want to hit a number, save time, or look good in front of their boss. When we treat activity as the goal, we end up managing the dashboard instead of the customer, and we get surprised in both directions: "healthy" accounts that churn and "at-risk" accounts that are thrilled.

The question I started asking my team was simple. If this customer only logged in once a month, but we helped them win in their market, would they renew? Almost every time, the answer was yes.

What we changed

We redefined what healthy meant, account by account. Instead of counting logins, we looked for evidence that the customer applied what they learned. Instead of feature clicks, we looked for decisions they made because of us. Instead of relying on NPS alone, we looked for outcomes that mattered to the executive who signed the renewal.

That meant three practical shifts.

Business reviews became about their results. We stopped giving platform tours. Every review started with the customer's original goals, walked through what they'd accomplished, and connected our product to the KPIs their leadership cared about. (I've written separately about why QBRs shouldn't be reporting sessions.) "You logged in 12 times this month" turned into something like "your team used these insights to rework the content plan, and here's what happened to traffic." I've written more about which metrics are worth putting in front of a customer, but the short version is: theirs, not ours.

CSMs asked bigger questions. "What are you being measured on this quarter?" is a better discovery question than any product question. Once CSMs knew the answer, they could tie their work to it, and customers started treating them as advisors instead of support.

The health score followed. We rebuilt it around signals of impact: engagement with the parts of the product that produce business results, wins captured each quarter, and whether we had an executive champion. A customer who logged in less but hit their goals scored healthier than a busy account with nothing to show for it. If you're rebuilding yours, I walk through the mechanics in how to build a health score that actually predicts churn.

What happened

Retention improved across mid-market and enterprise. More customers were willing to be references, which made Sales happy. Product feedback got sharper, because it came from how customers actually used the product to get results rather than which buttons they pressed. Expansion conversations got easier, because we could point to value already delivered.

The part I didn't expect was the effect on the team. CSMs got more confident. When you know your job is to help a customer win, not to chase logins, the work feels a lot more meaningful. And leadership started trusting CS numbers, because those numbers finally described something real.

Where to start

You don't need a new platform to make this shift. Start at onboarding: ask every new customer what success looks like in six months, in their words, and write it down. Build success plans around those goals, and map the journey with those outcomes in mind. Coach CSMs to connect usage to a win in every conversation, not just at the quarterly review. And look hard at what you reward internally. If CSMs get credit for closing tickets and hitting touchpoint counts, that's what you'll get.

Logins are a signal. They're not the story. Once your team starts counting outcomes, the conversations with customers change, and so does the way the rest of the company sees CS. It's the same argument behind treating CS as a revenue function: you have to be able to show what you changed for the customer.

If your team is stuck managing activity and you want to talk it through, reach out. I've been there.