Revenue at Risk in HubSpot: What the Number Really Means

Revenue at risk is not every contract renewing this quarter. It is the value attached to renewals where the decision date is near and the follow-up evidence is weak or missing.

A large number on a dashboard feels useful until someone asks which customers make it up. Teams often sum every upcoming renewal, multiply deal amounts by subjective risk percentages, or count the same contract once on the original deal and again on the renewal deal. The result looks precise and is difficult to act on. A useful revenue-at-risk number begins at account level, uses one value source, and keeps the operational reason attached.

Quick answers

What is renewal revenue at risk?: Renewal revenue at risk is the contract value associated with customer accounts that are approaching a renewal decision and do not have enough evidence that the renewal is actively being worked. The trigger should combine timing with missing follow-up, not timing alone.
How do I calculate revenue at risk in HubSpot?: Define the active renewing population, resolve one renewal date and one value per company, apply a clear risk rule, and sum only the accounts that match it. Keep the account list and evidence behind the total so the number can be reconciled and acted on.
Which HubSpot amount should I use?: Use the value closest to the active recurring contract: renewal deal amount, recurring revenue property, active subscription value, or governed company ARR. Choose one precedence rule and do not sum multiple representations of the same contract. If only total contract value exists, label the metric accordingly instead of calling it ARR.
Is revenue at risk the same as a churn forecast?: No. Revenue at risk is an operational exposure measure: value attached to accounts that need attention. A churn forecast estimates expected loss, usually by applying probabilities. One tells the team where to act; the other estimates a financial outcome. Combining them too early hides the accounts behind a weighted total.
How does Renewal Radar calculate value at risk?: Renewal Radar resolves the usable value associated with the company and attaches it to a renewal risk only when the timing and follow-up conditions are met. The amount stays connected to the account and the evidence, rather than existing only as an aggregate dashboard number.

Start with a company-level risk rule

The formula should be simple enough that every account in the total can be explained.

A practical rule is: the account is an active customer, its renewal date falls inside the selected window, and there is no sufficient next step before that date. Supporting evidence can include no upcoming meeting, no recent inbound reply, no open renewal task, or no meaningful renewal-stage movement. The rule can become stricter as the date approaches.

What should not count automatically is every renewal inside 90 days. Upcoming revenue is exposure, not risk. A customer with an accepted renewal meeting next week and an active commercial thread belongs in the renewal forecast. It does not belong in the same intervention queue as a customer nobody has spoken to in three months.

Resolve one value per customer

HubSpot can represent the same commercial value in several places: the original closed-won deal, a renewal deal, line items, company ARR, subscription amounts, or a custom contract record. Summing them without a precedence rule can double or triple the exposure.

Use the source closest to the active term and document the fallback:

Current renewal deal amount when it accurately represents the next term.
Active recurring contract or subscription value.
Governed company ARR or MRR property.
Associated recurring line items, deduplicated to the active term.
Original deal amount as a labelled fallback when no current recurring value exists.

Currency also matters. Do not add EUR, USD, and GBP values into one total without conversion. Keep native-currency totals separate or apply a documented reporting rate outside the account-level risk logic.

Do not hide action behind probability

Multiplying a €100,000 renewal by a 30% risk score produces €30,000 of weighted risk. It also removes the most useful fact: there is a €100,000 customer account that may need a conversation today. Probability weighting is useful later for finance. It is a poor first output for customer success and account management.

Keep two layers separate:

Operational revenue at risk: full customer value attached to accounts that match an explainable action rule.
Expected revenue loss: a forecast model that applies probabilities after the underlying account list is understood.

The first layer tells the team where to work. The second supports planning. One should not replace the other.

A clean calculation workflow

Define active customer accounts and the renewal window.
Resolve one renewal date per company using a documented precedence rule.
Resolve one current contract value per company and preserve its currency.
Apply the risk rule using meetings, inbound replies, tasks, ownership, and renewal-stage evidence.
Exclude accounts with a credible next step already in motion.
Sum the remaining company values by currency, owner, and renewal month.
Keep the company list under every total so the number is always auditable.

The hardest steps are not arithmetic. They are resolving the date, the value, and whether follow-up is real. HubSpot dashboards can sum a field easily. They cannot repair scattered renewal timing or decide whether the account is actually being worked, which is why dashboard-only renewal management breaks down, as covered in HubSpot Renewal Management: Why Dashboards Fail.

What the output should look like

The aggregate is useful for prioritisation: for example, €240,000 across seven accounts inside 60 days. The account rows are what make it operational. Each row should show the company, renewal date, value source, owner, risk evidence, and next action. That lets a leader challenge a false positive, lets RevOps correct bad data, and lets the account owner act without reconstructing the logic.

This is also why one task per real risk is better than a stream of alerts. The amount matters only when it reaches the person who can change the outcome, with enough evidence to trust it.

How Renewal Radar handles this

Renewal Radar by Sighub resolves renewal timing and customer value at company level, then checks whether the account is already under control. When a renewal needs action, the value and evidence stay attached to one self-resolving HubSpot task. Teams can see the total exposure, but they never lose the account-level reason behind it.