Skills RevOps
Revenue at risk
The number gets built the same way almost every time: take every account with an open complaint or escalation, sum their annual revenue, present the total.
npx rulebase-skills install cx-revenue-at-riskWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “how much revenue is at risk”
- “what are these support failures costing us”
- “revenue behind our open escalations”
How it works
The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.
Exposure and risk are different quantities
If you do not have a defensible probability, report exposure and call it exposure. "£4.2m of ARR sits on accounts with an unresolved escalation" is a true, useful, defensible sentence. "£4.2m of ARR is at risk" is not the same claim, and the difference is the whole credibility of the analysis.
Getting a probability that survives scrutiny
The only honest source is your own history: among accounts that had this signal, what share subsequently churned or downgraded, compared with otherwise-similar accounts that did not?
Contract timing dominates
The same exposure carries very different near-term risk depending on when the customer can actually leave: Inside the renewal or notice window, Mid-term on a multi-year contract, Monthly or usage-based.
Do not double count
Four ways the number gets inflated by construction.
What you cannot claim
You cannot claim support caused the churn. Accounts that escalate differ from accounts that do not in ways you have not controlled for, and the customer who left after a bad support experience may have left anyway. The uplift calculation narrows this; it does not close it.
The version of this that actually gets acted on
A total is a headline. What changes a decision is the ranked list of specific failures, each with the accounts behind it and the exposure it carries: Rank by exposure × uplift × imminence, not by exposure alone.
Related skills
Free and open source, and vendor-neutral — it reads the conversations from whichever helpdesk you already run. Browse all 149 skills · connect your helpdesk over MCP · source on GitHub
