Why the customer who uses your product the most isn't always the one who renews
High usage doesn't guarantee a renewal: what predicts it is whether the customer reached the outcome that made them buy, not how often they log in.

Cristian Pereyra
Co-founder · Engineering
A customer who logs in every day, has several active users, and never stops generating activity looks, at first glance, like a safe one. It's the most common read in any account review: if they use it a lot, they're happy. Renewal doesn't get decided by how many times someone opened the product this week. It gets decided by whether that customer reached the outcome that made them buy in the first place.
Activity and outcome aren't the same signal
High usage can mean two completely different things, and an activity dashboard doesn't tell them apart. It could be that the customer is getting more and more value out of it and is one step from asking about an upgrade. Or it could be that they're manually compensating for something the product should handle on its own: logging in every day to build a report that should arrive automatically, or repeating a task that looked solved in the demo and still isn't in production. Both situations produce the exact same rising usage graph. The only way to tell them apart is checking whether the promised outcome actually happened.
Gainsight, one of the most widely used customer success platforms, published an analysis back in 2017 of what best predicts renewal within its own customer base, backed by historical data and machine learning. It found that frequent usage does correlate with renewal in its specific case. And it still closed that same piece with a caveat that holds for any product, not just its own: adoption isn't the same as value, and helping the customer get to that value is the real job of an account team.
Adoption isn't the same as value.
What the mistake looks like in practice
Picture two accounts with the exact same usage graph: both saw a 40% jump in product queries last quarter. The first jumped because the customer's team started using it for a second process on top of the original one, and they're now asking about pricing for a bigger plan. The second jumped because something that used to take one click now requires three manual steps, and the team logged in more just to compensate for that friction. An activity dashboard shows the same line going up in both cases. The account manager on the first one will read it correctly. The account manager on the second one will walk into the renewal call convinced everything is fine, and will find out otherwise on the same call where there's nothing left to do about it.
Two accounts, the same quarter
Account A
Started using the product for a second process on top of the original one. Now asking about pricing for a bigger plan.
Account B
Something that used to take one click now requires three manual steps. The team logs in more just to compensate for that friction.
Same graph, same dashboard reading, opposite realities. The difference isn't in the curve: it's in why it went up, and that shows up on no dashboard.
What to ask in your next account review
Instead of opening the meeting with the usage graph, it's worth opening with the question that drove the purchase. If the customer signed up to cut their own response time in half, the question is whether that number dropped, not how many times someone on their team logged in this week. If they signed up to stop losing weekend inquiries, the question is whether that stopped happening. If they signed up so an internal process would stop depending on one person, the question is whether that dependency actually broke. Usage works as context. As an answer, it doesn't hold up.
That question needs to be written down somewhere from day one, not improvised on renewal day. If nobody wrote down, at signing, what outcome the customer expected, there's nothing to compare against six months later, and the renewal conversation turns into a price negotiation instead of an outcome review.
When you find out the account isn't renewing
12-month contract- Only activity gets watched0 months to actSigning · nothing on recordMonth 12 · you find out on the call
Usage was trending up and nobody had anything to check it against. The first signal is the customer saying they aren't renewing, on the same call where there's nothing left to fix.
- The outcome is written down on day one9 months to actSigning · the outcome is on recordMonth 3 · the review already shows it
At three months you compare against what the customer expected, not against the usage graph. If the outcome isn't there, nine months still remain to adjust the service or the expectation.
The contract runs just as long in both cases. The only thing that changes is whether someone wrote down, on signing day, what the outcome would be measured against.
The conversation that avoids the renewal surprise
A commercial team that only looks at activity finds out a customer isn't renewing on the renewal call itself, when it's already too late to fix anything. One that also asks, account by account, whether the outcome was reached has that answer months ahead. That still leaves room to adjust the service or the expectation before the decision is already made on the other side. The difference isn't better dashboards. It's having that conversation, with that specific question, before it becomes urgent.
Sources: Gainsight, "Our Top Indicators of Renewal" (gainsight.com/blog, author Jim Huang, April 5, 2017).

Cristian Pereyra · Co-founder · Engineering, StudioChat
Want agents like these working for your team?
Talk to us now