Convert revenue ranges to points by assigning higher scores to larger expected contract values, then cap the score so company size does not bury buying intent. A practical model is simple: map each revenue band to a fixed point value, test it against closed-won deals, and adjust monthly. HubSpot is faster for basic scoring. Salesforce is stronger when finance, sales ops, and RevOps need tighter control.
TLDR: Use revenue ranges as one input in lead scoring, not the whole score. For example, a B2B software company might give 5 points to firms under $1 million in revenue, 20 points to firms between $10 million and $50 million, and 35 points to firms above $100 million. In one simple audit, if 62% of closed-won deals came from companies above $25 million in revenue, that band should carry more weight. Still, a small company that visits pricing three times may deserve more attention than a large account with no buying signals.
Why revenue ranges belong in lead scoring
Revenue is a proxy for budget, urgency, and deal size. It is not perfect. Some high-revenue firms are poor-fit buyers. Some smaller firms buy fast and expand later. Still, revenue bands help sales teams avoid wasting time on accounts that cannot afford the product.
The goal is not to create a “rich company equals good lead” rule. The goal is to add structure. Revenue scoring should sit beside firmographic data, intent signals, fit criteria, and sales behavior.
A serious revenue-based score usually includes:
- Company annual revenue, stored as a clean range or numeric value.
- Employee count, used to confirm company size.
- Industry, since revenue meaning changes by sector.
- Product fit, based on use case or tech stack.
- Engagement, such as demo requests, pricing visits, and email replies.
A simple revenue-to-points model
Start with revenue bands that match how your company sells. Do not copy a generic template without checking your own deal data. A startup selling a $99 monthly tool needs different scoring than an enterprise vendor selling six-figure contracts.
| Annual revenue range | Suggested points | Reason |
|---|---|---|
| Under $1M | 0 to 5 | Limited budget unless product is low cost |
| $1M to $10M | 10 | Possible fit for SMB offers |
| $10M to $50M | 20 | Often budget-ready and easier to sell than enterprise |
| $50M to $250M | 30 | Strong fit for mid-market sales |
| $250M+ | 35 to 40 | Large potential value, but longer cycle |
Keep the scale controlled. If your total lead score runs from 0 to 100, revenue should rarely exceed 30% to 40% of the total. Otherwise, a huge company with no interest can outrank a perfect active buyer. That is how reps end up calling cold corporate switchboards while hot leads wait.
HubSpot: easiest for straightforward revenue scoring
HubSpot works well when revenue is stored in a company property such as Annual Revenue or a custom revenue range field. You can create a score property and add positive points when a company falls within a selected band.
A typical HubSpot setup looks like this:
- Create or clean the Annual Revenue company property.
- Standardize values into ranges such as $10M to $50M.
- Create a custom score property, such as Fit Score.
- Add scoring rules for each revenue range.
- Build lists or workflows for MQL handoff.
HubSpot is quick. A RevOps manager can build a basic model in under an hour if the data is clean. The catch is that messy revenue data turns the scoring tool into a cleanup project. “10 million,” “$10M,” “10000000,” and “10-50M” may be treated differently unless the property values are normalized.
HubSpot’s scoring also becomes clumsy when you need layered logic. For example, “give 30 points if revenue is over $50M, but only if the company is in healthcare or finance, and subtract points if the lead is a student.” You can do it, but expect extra properties, lists, and workflows.
Salesforce: better control, more maintenance
Salesforce is stronger for revenue scoring when rules need governance. You can use formula fields, Flow, validation rules, assignment rules, and third-party enrichment. Sales teams also tend to trust Salesforce scores more when they appear directly on Lead, Contact, Account, and Opportunity records.
A common Salesforce method is to create a formula field called Revenue Score. The formula checks annual revenue and returns points. A simplified version might work like this:
- Under $1M: 5 points
- $1M to $10M: 10 points
- $10M to $50M: 20 points
- $50M to $250M: 30 points
- $250M+: 40 points
Then a total score field can combine revenue score, industry score, behavior score, and sales status. Salesforce Flow can update lead status when the total passes a threshold, such as 70 points.
It drives me crazy that small Salesforce scoring changes can take longer than they should. A five-point adjustment may require sandbox testing, deployment, field checks, and stakeholder approval. That discipline is useful in larger teams. It is annoying for small teams that just need to test a new band.
Image not found in postmetaHubSpot vs Salesforce for revenue-based scoring
Choose HubSpot if your scoring model is simple, your marketing team owns qualification, and speed matters. It is especially useful for teams that want fast list building, email automation, and MQL routing.
Choose Salesforce if the revenue score affects territory rules, compensation, enterprise routing, or pipeline reporting. Salesforce gives you deeper control, auditability, and stronger alignment with sales operations.
The trade-off is clear. HubSpot is easier to change. Salesforce is easier to govern. Neither tool fixes bad data by itself.
Other tools worth considering
Revenue scoring often works better when a CRM is paired with data enrichment or predictive scoring tools. These tools can fill missing revenue fields, correct company size, and infer buying potential.
- ZoomInfo: useful for company revenue, employee count, hierarchy, and firmographic enrichment.
- Clearbit: strong for real-time enrichment and routing based on company fit.
- 6sense: useful when account intent and revenue bands need to work together.
- MadKudu: built for predictive scoring and fit models, especially in SaaS.
- Marketo Engage: solid for behavior scoring, though revenue data often comes from CRM sync or enrichment.
- Salesforce Account Engagement: practical for teams already tied to Salesforce campaigns and lead routing.
These tools should not replace business judgment. Predictive scores can look precise while hiding weak inputs. Ask vendors how often revenue fields refresh, where the data comes from, and how missing values are handled.
How to avoid bad scoring decisions
Revenue bands are useful only when tested against real outcomes. Pull the last six to twelve months of closed-won and closed-lost deals. Group them by revenue range. Then check win rate, average contract value, sales cycle length, and no-show rate.
For example, one segment may show a 34% win rate but a small average deal size. Another may show a 12% win rate but three times the contract value. Those groups need different scores and different sales motions.
Follow these rules:
- Cap revenue points so large accounts do not dominate the model.
- Score missing revenue separately instead of treating it as zero.
- Review bands quarterly, especially after pricing or market changes.
- Use negative points for poor-fit industries, students, competitors, or tiny accounts outside your ICP.
- Give sales a visible reason for the score, not just a number.
A practical scoring blueprint
A balanced 100-point model might assign 30 points to revenue, 25 points to industry fit, 25 points to engagement, and 20 points to role or buying authority. This keeps revenue meaningful without making it the whole story.
Set MQL thresholds with care. If the handoff threshold is 70 points, make sure a lead cannot reach it through company revenue alone. Require at least one behavior signal, such as a demo request, pricing page visit, product comparison download, or reply to sales outreach.
The best revenue-based scoring model is boring in the right way. It is clear, tested, and easy to explain. HubSpot can get you there quickly. Salesforce can support stricter operations. Enrichment and predictive tools can improve the inputs. The real work is keeping the model honest after it goes live.