How to Build Lead Scoring Rules Based on Revenue Bands: HubSpot vs. Marketo

Build revenue-band scoring as a fit model first, not as a sales wish list. Start by assigning points to company revenue ranges that match your best customers, then subtract points for bands that usually churn, stall, or buy tiny packages. HubSpot supports score properties for contacts and companies, while Marketo Measure and Marketo Engage teams often use fields, Smart Lists, and scoring campaigns to adjust fit scores [source: HubSpot].

TLDR: Use HubSpot if you want a cleaner setup for small or mid-size teams that need visible scoring rules tied to CRM fields. Use Marketo if your revenue bands feed a larger enterprise routing model with product interest, region, account tiers, and lifecycle stages. For example, a SaaS company might add +25 points for accounts with $50M to $250M in annual revenue, +10 for $10M to $50M, and -15 for under $1M. If 38% of closed-won revenue comes from the $50M to $250M band, that band should carry real weight.

Why revenue bands belong in lead scoring

Revenue is not intent. That matters. A company with $500M in revenue may still have no need for your product. Still, revenue is a strong fit signal. It tells you whether the account can afford your offer, match your sales motion, and absorb your pricing without a six-month panic cycle.

Revenue bands work best when they answer one question: Which accounts are worth sales time first?

Common bands include:

• Under $1M: usually early stage, self-serve, or low budget.
• $1M to $10M: small business, possibly founder-led buying.
• $10M to $50M: growing mid-market, often strong for B2B SaaS.
• $50M to $250M: larger mid-market, more budget and process.
• $250M to $1B: enterprise-ready, slower buying cycle.
• $1B+: strategic accounts, often account-based selling.

Start with your closed-won data

Do not copy generic bands from a template. Pull 12 to 24 months of closed-won deals. Sort them by annual company revenue. Then compare revenue bands against:

• Win rate
• Average contract value
• Sales cycle length
• Gross margin
• Retention or churn

This is where scoring gets useful. A $1B account may look exciting, but if it takes 310 days to close and often ends in procurement limbo, it may deserve fewer points than a $75M account that closes in 42 days. Honestly, it feels like teams forget this and then blame the scoring tool.

A simple scoring table may look like this:

• Under $1M: -20 points
• $1M to $10M: +5 points
• $10M to $50M: +15 points
• $50M to $250M: +30 points
• $250M to $1B: +20 points
• $1B+: +10 points

The highest score does not always go to the biggest company. It goes to the band most likely to buy well.

HubSpot: best for clear revenue-band rules

HubSpot is usually easier when your scoring model is straightforward. You can create score properties and add criteria based on company fields such as annual revenue, company size, industry, lifecycle stage, and form activity.

A good HubSpot setup separates fit from engagement. Revenue belongs in fit. Website visits, demo requests, email clicks, and ad interactions belong in engagement. Keep them apart if you can. It makes reporting cleaner.

Example HubSpot rule structure:

• Company annual revenue is between $50M and $250M: add 30 points.
• Company annual revenue is between $10M and $50M: add 15 points.
• Company annual revenue is unknown: add 0 points.
• Company annual revenue is under $1M: subtract 20 points.

Then create a threshold. For instance, a contact becomes an MQL when the total score reaches 60 points, but only if the contact has a work email and belongs to a target industry.

The catch is that HubSpot can get messy when contact and company data do not sync cleanly. A contact may show strong engagement while the company record has missing revenue. Expect to waste time fixing property mapping, duplicate companies, and enrichment gaps. It is not glamorous work, but it saves your sales team from chasing bad fits.

Marketo: better for complex enterprise scoring

Marketo is stronger when scoring rules need more control. Many teams use separate fields for demographic score, behavior score, and person score. Revenue bands can update the demographic score through Smart Campaigns.

A common Marketo pattern looks like this:

1. Create or confirm the Annual Revenue field.
2. Build Smart Lists for each revenue band.
3. Create Smart Campaigns that listen for revenue value changes.
4. Use flow steps to change the demographic score.
5. Trigger lifecycle updates when the combined score passes MQL limits.

For example, a Smart Campaign might say: if Annual Revenue is between 50000000 and 250000000, change demographic score by +30. If revenue later changes to under $1M, another campaign removes the old value and applies the lower one.

That last part is where Marketo needs discipline. If you only add points and never reset them, scores inflate. A lead can carry stale revenue points for months. Build reset campaigns or use calculated fields to prevent score bloat.

HubSpot vs. Marketo: which one handles revenue scoring better?

HubSpot wins on speed. If your revenue scoring model has five to seven bands and a few exclusions, HubSpot is quicker to set up and easier for marketing ops, sales ops, and managers to understand.

Marketo wins on control. If your model has regional exceptions, product lines, multiple scoring fields, account scoring, and strict routing rules, Marketo gives you more room to build. It also gives you more room to break things. That is the annoying tradeoff.

Rules that make revenue-band scoring work

Keep revenue scoring useful with a few firm rules:

• Cap the revenue score. Do not let revenue outweigh all buying signals.
• Score unknown revenue as neutral. Missing data is not always bad fit.
• Use negative points carefully. Penalize clear bad fits, not incomplete records.
• Review bands quarterly. Your best customer profile can shift.
• Compare score to outcomes. If high-scoring leads do not convert, fix the model.

A practical model might give revenue only 25% to 35% of the total fit score. Industry, employee count, region, tech stack, and job title should still matter. If revenue controls everything, sales will get large accounts that look rich but have weak need.

A simple rollout plan

Start with a pilot. Pick one segment, such as North American mid-market software companies. Build five revenue bands. Run the model for 30 days without sending every scored lead to sales. Compare scores against demo requests, SQL creation, and opportunity rate.

If the $50M to $250M band produces twice the SQL rate of other bands, increase its points. If the $1B+ band creates meetings but few opportunities, lower it. Scoring should reflect buyer quality, not ego.

The best version is boring in the right way. HubSpot makes that easier for teams that want clean rules and fast reporting. Marketo suits teams with heavier routing, ABM logic, and scoring governance. Either way, revenue bands should sharpen prioritization, not replace sales judgment.

Latest posts by Editorial Staff (see all)