Renewal Risk Radar

Problem Statement

Account teams receive renewal risk signals from many systems, but the weekly planning view is inconsistent and late. Customer Success wants one governed queue that highlights accounts needing attention before the renewal is already at risk.

Proposed Workflow

• Pull signals from Salesforce, support, and product usage, with permission.
• Turn them into a ranked weekly list of at-risk renewals for account owners.
• Post the list to the account team in Slack so nothing slips.
• Have a manager review what data it reads before it’s built.

Data and Controls

Renewal Risk Radar would read account, renewal, support, and product-usage signals only after the business owner approves the data scope. Account owners see their own book of business, leaders see their teams, and the risk logic is visible enough for teams to challenge a score.

What It Connects To

• Salesforce, for accounts, contract dates, owners, and renewal value.
• Support systems, for open escalations and recent case volume.
• Slack, where the weekly queue and account-owner reminders are posted.

Acceptance Criteria

• Employees can back it with credits until it qualifies.
• A business owner and a sensitivity level are set before any work starts.
• No one sees accounts they’re not allowed to see.
• It can’t read any data until that’s approved.