What is revenue potential, and how is it different from a lead score?

Revenue potential is an estimate of what an account could be worth to you, built from facts about the company, like seats, sites or spend. A lead score ranks how engaged a person has been with your marketing. Revenue potential tells reps which accounts deserve their time. A lead score only tells them who clicked.

I'll be honest: I've built a lot of lead scores. I sold HubSpot for years, and lead scoring was part of almost every demo. Points for opening an email. Points for a pricing page visit. Minus points for a Gmail address.

Then I watched what reps actually did with them. They ignored them. Not because reps are stubborn, but because the score answered a question nobody on the sales team was asking. Reps don't want to know who clicked. They want to know which accounts are worth a week of their life.

That's what revenue potential answers. It's a number, in dollars or seats or units, that says how big this account could be for you if you won all of it. It's the first thing we build on almost every data project, and it's the reason I stopped saying "lead score" altogether.

Why do lead scores let sales teams down?

Lead scores measure activity, not value. They reward people for clicking, downloading and visiting, so they rank the curious ahead of the qualified. A student downloading every guide can outscore a buyer at your biggest prospect who visited once.

There are three problems with them in practice:

• They score people, not accounts. B2B deals are bought by companies. Five engaged people at a tiny company look better than one quiet executive at a company that could be your largest customer.
• They hide the biggest accounts. At Chaos, a design software company, a signup with one seat and a Gmail address looked like the lowest-value lead in the database. It turned out to be Parsons Corporation, with room for 407 seats.
• Nobody can explain them. When a rep asks "why is this a 72?", the honest answer is usually a pile of points nobody remembers setting up. Reps don't trust a number they can't explain.

The Esko team said it plainly on one of our calls: their CRM had no revenue potential, so reps couldn't prioritize. Everything looked the same size.

How do you calculate revenue potential?

Pick the unit you sell, estimate how many of those units each account could buy, and multiply by what you charge. Revenue potential equals potential units times price per unit. The hard part isn't the math. It's finding the right unit and getting trustworthy data for it.

At Chaos, the unit was seats. Revenue potential was potential seats times EUR 550. We estimated potential seats from company size and the kinds of roles that use their software, then multiplied. That one field let the team rank every account in the database by what it could actually be worth.

The unit changes by business:

• Software: seats, users or locations.
• Manufacturing: plants, production lines or annual volume of the parts you make.
• Logistics: shipping volume, lanes or facilities.
• Professional services: employees, entities or engagements a year.

When you're unsure which unit to use, look at your best customers and ask what made them big. That's usually your unit.

What data do you need to calculate revenue potential?

You need a reliable fact for your unit on every account, plus a way to know how much to trust it. That usually means enrichment from several sources in a waterfall, a confidence score on each field, and a sample checked by hand before you run everything.

On Chaos, we gave every enriched field a confidence score from 1 to 10. Only fields above the bar synced to the CRM. A separate score looked at the whole record and blocked junk records from getting in at all. The client spot-checked 200 to 250 records by hand, because the people who know the customers should be the ones who sign off.

We also ran a 1,000-record sample first. It hit an 80% or better match before we ran the full database of about 174,000 records in batches of 50,000. A sample tells you if the unit is findable, how much the data costs and whether the number feels right to the sales team, before you spend real money.

How do reps use revenue potential day to day?

Reps use revenue potential to decide where to spend time. It sorts their account list, sets tiers, shapes territories and decides which accounts get a person and which get automation. When the number is in the CRM, every list a rep opens is already ranked.

A few ways it shows up:

• Tiers. Tier one, two and three by revenue potential, updated automatically as data changes.
• Territories. Fair territories balance total potential, not just account counts.
• The human lane and the AI lane. One revenue potential number can decide who works an account. High-potential accounts get a rep. The long tail gets an AI agent that only hands an account to a person when it replies or shows a strong signal.
• Expansion. For existing customers, the gap between what they buy now and their potential is your expansion list. Chaos used this to target trials with room to grow into larger accounts.

At Esko, the goal was to add about 25,000 net-new accounts with revenue potential and a product-fit tag, plus contacts with 90% or better valid emails, so reps could start with the right accounts instead of the alphabet.

Can revenue potential and engagement work together?

Yes, and they should. Revenue potential tells you who is worth pursuing. Signals tell you when. The best queue sorts by potential first, then puts accounts with a fresh buying signal, like a new executive, a hiring push or a pricing page visit, at the top of their tier.

That's the difference between a score and a system. A lead score blends value and timing into one number, so you can't tell which one is high. Keeping them separate lets a rep say "this is a big account, and they're moving now," which is the best sentence in sales.

Here's a simple test for your own team. Pull your ten largest customers and look up what your lead score said about each of them before they bought. If most of them were never "hot," your score is measuring the wrong thing. Now ask the same question of a revenue potential number. If your biggest customers would have ranked near the top, you have a number reps can trust.

Engagement still matters. It just stops pretending to be value.

Frequently asked questions

Is revenue potential the same as total addressable market?

No. Total addressable market is the size of the whole market. Revenue potential is calculated account by account, for the companies in your CRM and on your target list. Add up the revenue potential of every account you could sell to and you get a bottom-up view of your market, which is usually more useful than a top-down estimate because each number points to a real company.

Do we need Clay to calculate revenue potential?

No, but you need enrichment from several sources, and Clay is the most flexible tool we know for that. The formula is simple. The work is finding a trustworthy value for your unit on every account and keeping it fresh. Clay runs the waterfall, the AI research and the confidence checks, then writes the result to your CRM so reps see it.

What if we can't find our unit for most accounts?

Use a proxy you can find, like employee count, number of locations or revenue, and test it against your best customers. If the proxy ranks your top customers near the top, it's good enough to start. Run a sample first, show the ranked list to a few senior reps and ask if it matches what they know. Their reaction is the fastest test.

Should we delete our lead score?

Not necessarily. Keep engagement data, but rename and reposition it as a signal of timing, not value. Then sort accounts by revenue potential first and use engagement to decide who to call this week within each tier. Most teams find the old score stops mattering once reps have a number they trust and can explain to their manager.

Sources

• Chaos, waterfall enrichment and revenue potential, 2025 to 2026: revenue potential as potential seats times EUR 550, confidence scores from 1 to 10, the 1,000-record sample at 80% or better match, about 174,000 records run in batches of 50,000, 200 to 250 records spot-checked by the client, and the one-seat Gmail signup that was Parsons Corporation with room for 407 seats. See the Clay enterprise case study.
• Esko data project, September 2026: no revenue potential in the CRM, and the plan for about 25,000 net-new accounts with 90% or better valid emails and a product-fit tag.
• RevOps Shop, Clay for RevOps: how we build revenue potential and self-updating tiers.