The problem with a single revenue-at-risk number

Most CROs at non-SaaS B2B service companies can produce a revenue-at-risk figure when a board member asks for one. Few can defend it under questioning. The number is usually a rollup of accounts flagged “at risk” in the CRM, multiplied by contract value, with no adjustment for whether anyone is actually doing something about it.

That single number conflates two very different questions. How much revenue is exposed right now, based on the signals coming out of delivery, commercial, and satisfaction data? And how much of that exposure will still be there in ninety days, after account teams run their recovery plays? Collapsing both into one line item makes the metric almost useless for planning, because it can’t tell the board whether the exposure is shrinking or just being renamed.

Two numbers, not one: gross and net revenue at risk

The fix is to report revenue at risk the way credit risk teams report loan losses: a gross figure and a net figure, with the gap between them showing the value of the recovery process itself.

Gross revenue at risk

Gross revenue at risk is the total contract value sitting behind accounts whose health score has crossed a risk threshold, before any intervention. It should be calculated from a multi-source account health score that pulls from more than one signal category, not a single satisfaction survey or a sales rep’s gut feel. At minimum it should combine Satisfaction, Engagement, Commercial, Delivery, and Expansion signals, because a logistics account with a clean NPS score can still be bleeding revenue on missed SLAs, and a professional services account with strong delivery metrics can be one procurement change away from a lost renewal.

This number is intentionally alarming. It is the exposure your organization is carrying today, unfiltered by optimism about what account managers might fix.

Net revenue at risk

Net revenue at risk is gross revenue at risk minus the portion already under an active, structured recovery plan with a documented owner and timeline. This is where a CAPA recovery playbook earns its place in the reporting stack: an account only moves from gross to net exposure once a corrective and preventive action plan exists, with root cause identified, actions assigned, and a re-score date set. Without that discipline, “net” becomes just as subjective as the single number you started with, because anyone can claim an account is “being worked.”

Why the gap between the two numbers matters more than either number alone

The size of the gap between gross and net revenue at risk is a better leading indicator of team performance than either figure in isolation. A large, stable gap means recovery playbooks are catching risk early and converting it into managed exposure. A gap that shrinks quarter over quarter, while gross exposure stays flat or grows, means accounts are crossing the risk threshold faster than the team can respond, and it’s usually a coverage or capacity problem, not a data problem.

This matters because retention economics are unforgiving. Bain & Company’s research on customer economics has long shown that a five percent improvement in retention can lift profits by 25 to 95 percent, depending on the industry, because retained accounts carry lower service costs and more predictable revenue than new logos. Harvard Business Review’s research on customer economics makes a related point: the value of a retained customer compounds as the relationship matures, and not all retained revenue is equally profitable — which is exactly why a single revenue-at-risk number, blind to account quality, undersells the stakes of getting the gross-to-net conversion right.

Building the two-number system in practice

Start with signal coverage, not scoring precision

Before refining the scoring model, check whether the account health score actually has enough inputs to trust the gross number. Teams that rely on product-usage-style telemetry, a habit borrowed from SaaS customer success tooling, routinely miss the commercial and delivery signals that drive churn in logistics, IT services, manufacturing, and financial services accounts. A gross revenue-at-risk figure built on one data source is a guess with a decimal point.

McKinsey’s most recent global B2B Pulse research found that inconsistent information and lack of knowledgeable support are now leading causes of supplier switching, and that a large majority of B2B buyers will actively look for a new vendor if performance guarantees aren’t offered. That is a commercial and delivery signal, not a satisfaction survey result, and it needs to be scored as such. See McKinsey’s B2B Pulse findings on how decision-makers are driving growth for the full picture.

Make the recovery step visible in the same system

Gross and net revenue at risk should live in the same record, not in a separate spreadsheet the account team maintains on the side. Stakeholder mapping matters here too: an account can look recovered on a health score while the actual economic buyer has never been part of the save plan. A recovery plan that only reaches the day-to-day contact and never reaches procurement or the executive sponsor rarely holds past the next renewal cycle.

For teams running on Salesforce, the cleanest way to keep gross and net numbers auditable is to push both the health score and the CAPA status onto the Account record itself, through native custom objects rather than a disconnected dashboard. That keeps the number where the account executive and the CRO are already looking, and it keeps the audit trail intact when a board member asks how a specific account moved from gross to net exposure.

Reporting it to the board

Gartner’s CFO research for 2026 found that improving financial forecast accuracy ranks among the top priorities for finance leaders heading into next year, alongside cost optimization. A two-number revenue-at-risk report is one of the more direct ways a CRO can contribute to that forecast accuracy goal: gross exposure feeds the downside case, net exposure feeds the base case, and the gap between them becomes a defensible explanation for why the forecast should be trusted. See Gartner’s 2026 CFO priorities survey for the forecasting context finance leaders are bringing to that conversation.

The reporting cadence should match the QBR calendar, not just the board calendar. If quarterly business reviews are already functioning as a revenue tool rather than a status meeting, the gross and net figures for each strategic account should be part of the review deck, updated with the same account health data the CRO reports upward. That consistency is what turns revenue at risk from a defensive metric into a number the whole revenue organization is accountable to.

Start seeing both numbers

You don’t need a full rollout to find out what your real exposure looks like. The 30-day pilot scores ten of your accounts across all five signal categories for €30 a month, fully refundable and cancel anytime, with setup done for you. If you’d rather explore the platform first, create a free account — no card required — and see how gross and net revenue at risk would look across your own portfolio.