Renewal risk pulse
Watch usage, support load, and champion movement on every account in its renewal window, so the save starts months before the decision.
Tools
Zendesk, Stripe, Salesforce, 6sense
Outcomes
Every renewal has a current health read • Champion changes noticed the same week • Saves started before the renewal call • No discount offered for lost trust
Documentation
Instruction-ready detail below
A renewal is decided before the renewal conversation begins, because usage fell in the second quarter and the champion left in the first, and neither appeared on anybody's list. This workflow keeps a health read on every account inside its renewal window. It tracks usage against the level the account was bought at, the volume and severity of support tickets, invoices left unpaid, and accounts whose own research activity has dropped or shifted toward a competitor's category. A change in the contacts on the account counts as a signal in its own right, because a departed champion leaves nobody to champion anything. Each account gets a short note naming what changed, when it changed, and the days left on the contract, so the owner has a reason to act rather than a status. Signals that resolve themselves are marked and dropped, keeping the save list to the accounts that need a person this month. A human still decides what the account is worth keeping, whether the issue is commercial or technical, and what to offer.