Relationship
| Sign | Where it shows up | First move |
|---|---|---|
| 1. Your champion leaves or changes role | A call, an email bounce, a job change on LinkedIn or a contact database | Reach the new owner within 48 hours (see the champion-left playbook) |
| 2. The executive sponsor goes quiet | Declined meetings, no replies from above director level | Exec-to-exec outreach from your side |
| 3. No conversation in 45 days or more | Calendar, inbox, call recordings | Restart contact with something useful, not a "just checking in" email |
| 4. Meetings get shorter, or get delegated down | Call recordings and attendee lists | Ask what changed in their priorities |
| 5. A new decision maker appears | New names on tickets, invoices or calls | Introduce yourself and re-sell the outcomes |
| 6. A key contact gives a detractor score | NPS or CSAT survey responses | Follow up personally and ask what's behind the score |
Adoption
| Sign | Where it shows up | First move |
|---|---|---|
| 7. Usage drops 15 percentage points or more in 4 weeks (for example, seat utilization from 70% to 55%) | Product analytics, seat reports | Find out which team dropped and why |
| 8. Licenses bought but unused | Seat utilization | Help them put the seats to work before they're cut at renewal |
| 9. A key feature is abandoned | Feature usage | Check whether a workaround or a competitor replaced it |
| 10. Onboarding stalls | Open onboarding tasks, an implementation owner who's away | Re-plan with a named owner on their side |
| 11. A data-export request, or a drop in API or integration use | Support tickets, API logs, integration dashboards | Ask what they need the data for. A bulk export can be the first step of a move to another tool |
Product and support
| Sign | Where it shows up | First move |
|---|---|---|
| 12. Escalated or reopened tickets | Support desk | Get an owner and a date for the fix, and tell the customer |
| 13. A blocker bug open on a renewing account | Issue tracker | Raise it with engineering, with the renewal date attached |
| 14. Frustrated language: "again", "third time", "unacceptable" | Tickets, emails, call transcripts | Call them. Don't reply to frustration with a ticket update |
| 15. Missed SLAs | Support desk | Acknowledge it before they bring it up |
Commercial
| Sign | Where it shows up | First move |
|---|---|---|
| 16. Budget cuts or a procurement review | Calls, emails from finance | Prepare a business case in their numbers |
| 17. A competitor mentioned | Call transcripts, emails | Find out what problem the competitor would solve for them |
| 18. An RFP or security review for a replacement tool | Calls, emails from procurement or IT | Ask the sponsor what problem it's meant to solve, and ask to take part |
| 19. Asked to prove ROI | Calls, QBR requests | Book a value review with data, before the renewal talk |
| 20. Auto-renew turned off, or a downgrade requested | CRM, contract system | Ask the sponsor what prompted it, and treat it as a renewal risk |
| 21. Late payments or invoice disputes | Billing system, emails from finance | Find out whether it's a cash problem or a question about value |
| 22. Layoffs, a reorg, or a merger or acquisition at the customer | News, LinkedIn, calls | Find out who owns the budget and your product after the change |
| 23. Renewal within 90 days and no recent conversation | CRM plus calendar | Book the renewal conversation now |
How to read the signs together
- One serious sign beats several small ones. A lost sponsor matters more than three minor tickets.
- Don't let good areas hide a bad one. Great usage doesn't cancel out a champion who left. Score each area separately and let the weakest one limit the total.
- Silence is a signal. Treat an account you haven't heard from as unknown, not healthy.
- Start with the most ARR and the nearest renewal. When several accounts show signs, rank them by the ARR at stake, then by days to renewal.
- Keep the evidence. Write down the quote, ticket or chart behind each sign, so the next person can check it.
A simple weekly routine
- List every renewal in the next 90 days.
- For each, check the four areas above and note any sign with its evidence.
- Give every account with a serious sign an owner and a next step due this week.
- Review last week's next steps: was each one done, and did it change anything?
Horizon automates this routine. It reads calls, tickets, Jira, email and usage, raises a risk signal with its source when it finds one of these signs, and lists the renewals to act on.
More on this topic: churn, definitions, guides and tools.
Updated November 3, 2026