You spot competitive risk before a renewal by treating a verified competitor touch as a forecast input, not a health-score input. Usage decline, support spikes, and slipping NPS tell you an account is unhappy. They never tell you a competitor is in the room. The one signal that does is a named buyer at a renewal account being worked by a named competitor, confirmed on both sides before it publishes and refreshed daily.
This post is written for the forecast owner, not the CSM. Renewal risk is a number RevOps carries, and the inputs that re-rate that number should be evidence, not inference. The difference decides whether you re-rate a renewal the day a competitor appears or explain it in the post-mortem.
Competitive evaluation before a renewal leaves signals most teams read too late
The conventional renewal-risk signals are real, and every customer success playbook teaches the same set. They are also lagging and proxy-level, which is why teams keep reading them too late.
- Usage decline. Logins, seats, and feature adoption drop over a 30 to 180 day window before the renewal date.
- Support-ticket spikes. Volume or severity climbs, or the tone of tickets shifts from how-to to frustration.
- NPS and CSAT dips. Survey scores fall, or response rates collapse.
- Missed QBRs. The account stops showing up for business reviews, or reschedules them indefinitely.
- Quiet champions. Your executive sponsor goes dark, and replies slow down.
Each of these correlates with churn. None of them names a competitor. A renewal can post every one of these signals because of a budget freeze, a reorg, or a champion leaving, with no competitor anywhere near the account. The forecast needs a signal that resolves the cause, not one that flags the symptom.
Usage and health scores infer churn but never confirm a competitor is in the account
Proxy signals fail at competitive displacement for one reason: they measure your relationship with the account, not the account's relationship with anyone else. A customer can show full usage and a green health score while running an active evaluation of a competitor, because the people logging in every day are rarely the people taking the competitor's call.
The inverse is just as common. A quiet champion has many explanations, and a competitor is only one of them. Health scores were built to rank accounts by sentiment and engagement, and they do that well. They were never built to identify who else is in the room.
A health score tells you an account looks unhappy. It cannot tell you a competitor is the reason.
The missing dimension is identity. A health score is account-level and internal. Competitive displacement is person-level and external: a specific buyer, a specific competitor, a specific contact. Until a signal carries that identity, displacement stays invisible until the renewal slips. For the full comparison of inferred versus confirmed signals, see intent data versus competitor activity.
Renewal risk belongs to the forecast, which makes it a RevOps signal first
Renewal risk usually lives on a customer success health dashboard, separate from the pipeline. That placement is a habit, not a requirement. The renewal is a number in the forecast, RevOps owns the number, and the inputs that move it should sit where the forecast is managed.
RevOps already treats a renewal as one of four states a deal can occupy. A verified competitor touch is a state change in the same way a stalled opportunity is, and it deserves the same treatment in the forecast.
- New business is forming. The account is early, no commitment yet.
- An open opportunity is in play. A deal is live and being worked.
- A closed-lost deal is reopening. A prior loss shows fresh movement.
- A renewal is at risk. An existing account approaches its renewal date, and this is where competitive displacement does its damage.
Detecting displacement is not a sentiment read. It is an event the forecast can ingest: a named buyer at a renewal account is being worked by a named competitor. That event re-rates the renewal. A health-score trend does not. RevOps detects competitive displacement by routing that event into the same workflow that already carries every other forecast change.
Intent data predicts a renewal risk, verified competitor activity proves one
Intent data and verified competitor activity get grouped together because both claim to flag risk early. They are not the same signal, and at a renewal the difference is the whole point. Intent infers from anonymous behavior. Competitor activity confirms a named interaction.
| Property | Renewal intent data | Verified competitor activity |
|---|
| Subject | Account, anonymous | Named buyer, named competitor |
| Resolution | Account-level | Person-level |
| Nature | Probabilistic | Confirmed both sides |
| Confidence | A score you interpret | Publishes only if both sides check out |
| Refresh | Periodic | Daily |
| Use in forecast | A flag to investigate | An event that re-rates the renewal |
Intent predicts. Competitor activity is evidence.
Intent data is useful for prioritization, but it does not name the competitor or the contact, so it cannot move a forecast number on its own. Verified competitor activity carries identity on both sides, confirmed before it publishes and refreshed daily, which is why it can. For the broader framing, see competitor activity in your accounts and the specifics of verified competitor activity.
A verified competitor contact re-rates a renewal the day it appears
The mechanics are simple once the signal carries identity. A named buyer at a renewal account is being worked by a named competitor. The account moves from on-track to contested. The forecast reflects that the day the contact appears, not at the renewal post-mortem.
- The signal lands. A confirmed competitor touch is attached to the account and the contact, checked on both sides before it publishes.
- The renewal re-rates. The forecast category shifts from committed to contested, and the renewal owner is notified.
- The play starts early. The account team works a contested renewal with weeks of runway instead of reacting to a slipped close.
The volume is manageable because the signal is selective. About 3 percent of tracked accounts show competitor activity in a given month, so this is a short, high-signal list to work, not a flood of alerts. A renewal you would otherwise have flagged late on declining logins is now a renewal you re-rated the day the competitor showed up.
The signal is only useful where the renewal forecast is managed, so Deal Intelligence delivers it into the systems RevOps already runs, not into a separate customer success view.
- Salesforce and HubSpot. Custom fields on Account, Contact, and Lead, so a contested renewal is visible in the same record the forecast reads.
- Slack. Alerts routed by territory, segment, and owner, so the right renewal owner sees the touch the day it lands.
- Claude over MCP. A read-only MCP server with tools like renewals_at_risk and competitive_activity, so you can ask the forecast questions in plain language.
- Clay. An enrichment column that adds competitor activity to an existing account list.
- REST and webhooks. Direct integration for custom forecast workflows.
The signal arrives in the CRM, the alert channel, and the enrichment layer where the renewal already lives. See Claude MCP server for the Claude integration and Clay competitor enrichment for the column.