The Opportunity Score: one number for the revenue already sitting in your CRM

An Opportunity Score is a single 0–100 measure of how much recoverable revenue is currently exposed inside a CRM, weighted by how reachable that revenue is. It is not a forecast, a health check or an activity metric. It answers one question that most revenue teams cannot answer on demand: if we did nothing new this quarter, how much money that we have already earned the right to would quietly leave?

The distinction matters. A forecast projects new revenue from deals your team is actively working. An Opportunity Score looks in the opposite direction — at the deals, renewals and relationships that already exist in the CRM and are drifting out of reach without anyone deciding to let them go. In practice that is a much larger pool than most executives expect, because it is nobody's job to notice.

The score is expressed on a 0–100 scale for one reason: comparability. A $340,000 exposure means something very different for a company running a $1.2M pipeline than for one running $40M. Normalising the exposure against the size and shape of the portal lets you compare this month to last month, one business unit to another, and your own performance to a reasonable expectation.

Every CRM already produces more reports than anyone reads. The problem in most revenue organisations is not a shortage of data — it is that the data does not resolve into a decision. A pipeline dashboard shows you 400 open deals. It does not tell you which 22 are quietly dying, which 9 renewals have no owner attached, or which 60 past customers have not been contacted since their last purchase closed.

A single score forces prioritisation in three ways that a dashboard does not:

• It creates a trend line. One number can be tracked month over month and put on a board slide. Twelve charts cannot.
• It survives a leadership meeting. When the score drops eight points, the conversation is about why — which immediately surfaces the underlying findings.
• It exposes ownership gaps. Scores broken down by owner, pipeline or business unit make it obvious where the process is working and where it is not.

The risk with any composite score is that it becomes a number people manage instead of a problem people solve. The defence against that is traceability: the score must always decompose into named records with named owners and a stated reason. If you can click from the score to the exact deal that dragged it down, the number stays honest.

knovaly builds the Opportunity Score from five categories. Each one answers a different question about where revenue leaks, and each is calculated independently before being combined.

The mechanics are deliberately simple, because a score that requires a statistician to explain will not survive contact with an executive team.

1. Each category produces a set of findings, and each finding carries an estimated value derived from the record itself — deal amount, historical order value, or comparable closed value for the same account.
2. Findings are weighted by reachability. A renewal window opening next month weighs more heavily than a relationship dormant for two years, because the probability of recovering it is higher.
3. The weighted exposure is normalised against the size of the revenue base: total open pipeline value plus recent closed-won value, rather than raw record counts.
4. CRM health is applied as a confidence modifier. Low data quality widens the uncertainty band and is reported explicitly rather than being hidden inside the score.
5. The result is inverted onto a 0–100 scale, so a higher score means less exposed revenue and a healthier position.

Every input is versioned. When the calculation changes, historical reports continue to render under the logic and labels they were generated with, so a score from six months ago still means what it meant then. A metric you cannot trust historically is not a metric you can manage against.

Treat the score as a triage tool, not a grade. The bands below reflect what we typically see across connected HubSpot portals.

• 80–100. Strong. Follow-up discipline and renewal ownership are working. Remaining upside is concentrated in win-backs and long-tail dormant relationships.
• 65–79. Healthy with a visible leak. Usually one category dominates — most often renewals, because the motion is happening outside the CRM.
• 45–64. Material exposure. Typically a pipeline that is not being groomed: stale deals accumulate because nothing forces a decision to advance or close them.
• Below 45. Structural. The CRM has stopped reflecting how the business actually sells. Start with ownership and stage definitions before touching individual records.

Always read the score alongside its CRM health figure. A score of 72 in a portal with excellent data quality is a real result. The same 72 in a portal where half the open deals have no amount is an estimate with a wide error bar, and should be treated as a prompt to fix the inputs first.

Scores respond to process changes far more than to data clean-up. In rough order of impact:

1. Give every renewal an owner and a record. Creating a deal for each expected renewal window converts the largest invisible category into managed pipeline in a single step.
2. Introduce a stale-deal rule. Any open deal with no meaningful activity for a defined period gets advanced, re-dated or closed — no fourth option. This single rule reliably moves the score more than any other change.
3. Work the dormant list in batches by owner. Twenty warm relationships per owner per month is sustainable; a list of 900 is ignored.
4. Fix the properties that actually feed the score: deal amount, close date, owner, stage. Deprioritise cosmetic fields that do not change any calculation.
5. Review win-backs quarterly, not weekly. They convert slowly, and weekly review burns credibility with the sales team.

Expect the first month to be the largest single movement, because the initial scan finds years of accumulated drift. After that, month-over-month change of three to six points reflects genuine operating improvement. If your score jumps twenty points in a fortnight, check whether someone bulk-closed stale deals rather than resolving them.

• Bulk-closing stale deals before a review. It improves the number and changes nothing about the revenue.
• Counting system activity as sales activity. A workflow that stamps a property is not a human touching the account, and treating it as one makes dead pipeline look alive.
• Mixing win-backs into the headline. They convert differently and inflate the figure that leadership anchors on.
• Scoring closed deals. Risk categories must be restricted to open pipeline, or the same revenue is counted twice.
• Reporting a score without evidence. If a finding cannot name the record, the owner and the signal, it should not affect the score.

The teams that get the most from an Opportunity Score run it on a fixed rhythm rather than reaching for it when a quarter looks short.

• Monthly: recalculate, review the top findings by value, assign owners with dates.
• Quarterly: review the trend line and the category mix — which leak closed, which one grew.
• Annually: revisit the definitions themselves. Sales cycles change; a dormancy threshold set two years ago may no longer describe how you sell.

The goal is not a perfect score. It is a revenue organisation where nothing worth recovering leaves the building without somebody making a deliberate decision about it.