Revenue range is one of the cleanest firmographic signals a sales team can score on. Companies at 50 million in revenue behave differently than companies at 5 million, and their buying cycles, deal sizes, and decision timelines diverge enough that the same scoring model should not treat both the same way. This guide walks you through the full build: enriching leads with revenue data, defining the revenue buckets that match your sales motion, assigning score weights per bucket, routing scored leads to the right segment and SDR, and reviewing the scoring model monthly against actual conversion data so it stays predictive instead of becoming a vanity metric.
Time: 90 minutes
Scoring on revenue only works when the revenue field is populated and reasonably accurate. Before you build any rules, pull a sample of 500 leads from the last 90 days and audit the revenue field. Count how many are populated versus blank, how many look suspicious (one-dollar revenue, placeholder values like 999999), and how many match a trusted external source for a sample of 50 you spot-check. Teams typically find that 20 to 40 percent of leads have missing or unreliable revenue data, which breaks any scoring rule that depends on it. Fix the data problem before the scoring problem. Options include turning on auto-enrichment from a third-party source, requiring the field during form submission (with defaults for unknown), or running a one-time backfill against a data vendor. Scoring on bad data produces worse routing than scoring on nothing, because the model gives false confidence to decisions that would otherwise require human review.
Revenue buckets should match how your sales organization is actually structured. If you have an SMB team, a mid-market team, and an enterprise team, the bucket boundaries should match the account definitions those teams work. A common structure is: SMB under 10 million, mid-market 10 to 100 million, enterprise over 100 million. Your business might use different cutoffs based on average deal size, product fit, or go-to-market strategy. Pick cutoffs that reflect real differences in buyer behavior, not round numbers that look clean on a slide. If deals at 20 million behave the same as deals at 80 million, your mid-market bucket is fine; if 20 million deals convert in 30 days and 80 million deals convert in 180 days, you probably need two mid-market buckets. The number of buckets should stay between three and five. Fewer than three loses meaningful signal; more than five turns the model into a complexity trap nobody maintains.
Each revenue bucket gets a base firmographic score. The weight should reflect which segment produces the best outcome for your business right now, not which segment sounds most prestigious. Walk the historical data: which bucket has the highest win rate, which has the highest deal size, which has the shortest cycle, which has the lowest churn. A bucket that lands on top across those four dimensions deserves the highest score. A common pattern looks like: enterprise 40 points, mid-market 30 points, SMB 20 points, under-10-employees 5 points. Those numbers are illustrative; use your own data. Avoid the temptation to score only the top bucket and ignore the others. Scoring every bucket means every lead gets a comparable number, which keeps the routing model simple. Store the base scores in a config table the scoring engine reads, not hardcoded in a workflow, because quarterly tuning should not require engineering help.
Firmographic scoring on revenue alone will route leads but not prioritize them within a bucket. Layer behavioral and intent signals on top: website visits in the last 14 days, pricing page views, specific content downloads, demo requests, email engagement, third-party intent signals from G2 or similar. Each behavior gets its own point weight, and the total lead score becomes the sum of firmographic plus behavioral plus intent. The composite score tells you both who to route to (based on segment) and what order to work them in (based on total score). Keep behavioral weights proportional to firmographic weights. A single pricing page view should not outweigh the entire revenue bucket signal, because behavior without firmographic fit is low-value traffic. A pricing page view combined with an enterprise revenue bucket is a strong signal; a pricing page view from a 2-employee company is noise. The combination matters more than either signal alone.
Scoring without routing is a report that nobody acts on. Build routing rules that read the composite score and the revenue bucket, then assign the lead to the right queue, pod, or named owner. Common patterns: enterprise bucket plus composite over 70 routes to a named enterprise AE within four business hours; mid-market bucket plus composite over 50 routes to the mid-market SDR pod with same-day SLA; SMB bucket plus composite over 30 routes to the SMB queue with 24-hour SLA; everything else sits in a nurture bucket owned by marketing. The routing rules live in the CRM workflow engine and fire on lead creation or score change. Store the routing table in the same config layer as the scores so changes are coordinated. Avoid routing based on score alone without considering the bucket, because a 60-point SMB lead and a 60-point enterprise lead are not the same opportunity and should not go to the same pod.
No enrichment source has 100 percent coverage. Some leads will come in without a revenue estimate, and the scoring model needs an explicit path for them. Options: route them to a human triage queue, assign a default bucket based on other signals (employee count, industry, email domain), or hold them in a nurture state until enrichment completes asynchronously. Pick one path per lead source. For form submissions, synchronous enrichment at submission is best because the lead gets a routing decision inside the first few minutes. For imported lists, batch enrichment overnight before routing. For partner referrals, treat the referrer's own classification as authoritative and skip enrichment. Also handle the opposite edge case: leads with very high reported revenue (public companies, Fortune 500) that are actually subsidiary business units with different buying authority. For these, add a secondary rule that checks for parent-company signals and routes to the enterprise team only when the signals align.
A scoring model is only worth what it predicts. Instrument three numbers from day one: lead-to-opportunity conversion by bucket, lead-to-opportunity conversion by composite score band, and win rate by bucket. If the model is working, higher composite scores should produce higher conversion, and higher revenue buckets should produce higher win rates. If the data shows no correlation, the model is noise. Build the measurement into a dashboard that updates daily and gets reviewed weekly by marketing and sales ops together. Look for drift. A model that worked last quarter can break this quarter because the lead sources changed, the enrichment data vendor updated their methodology, or your sales motion shifted into new segments. Drift is normal; the dashboard surfaces it before the pipeline suffers. Also measure routing SLA attainment per bucket; if the enterprise 4-hour SLA is being missed consistently, the routing table is wrong or the capacity is understaffed.
Monthly tuning is where most scoring programs either stay sharp or quietly decay. Pull the last 30 days of leads, overlay actual outcomes (opportunity created, won, lost), and recalculate what the ideal weights would have been. Compare the ideal weights to the current weights and adjust where the gap is material. Small gaps (within 5 points) stay unchanged to avoid overfitting; larger gaps trigger a weight update. Also prune signals that lost predictive power. A behavior that correlated with conversion six months ago might not today because buyer habits shifted, or because the signal became too common (every lead downloads the pricing PDF now). Pruning matters as much as adding; a scoring model with 30 signals is harder to maintain than one with 10 well-chosen signals. Document every change in a changelog so the model has version history and the team can trace why a bucket's score moved three months ago.
Routing by revenue bucket will produce edge cases: a company that enriches at 10.5 million dollars straddles the SMB and mid-market boundary; a Fortune 500 subsidiary looks like enterprise by parent revenue but behaves like SMB by local budget authority; a startup that just raised funding shows last year's revenue of under a million but is clearly moving upmarket. Each edge case triggers a dispute between pods about who owns the lead. Pre-empt the disputes with written tie-break rules: boundary-straddling leads default down (10.5 million routes to SMB, not mid-market, because overclaiming a lead is a bigger pod-level incentive problem than underclaiming); subsidiaries route to the pod that owns the parent unless the subsidiary has independent buying authority; freshly funded startups route by target segment, not current revenue. Review disputes monthly in a 30-minute meeting with marketing ops and sales leadership. Capture every resolution in the tie-break doc so the same dispute does not recur quarter after quarter.
Scoring is not just a lead-level signal; it should flow forward through the CRM lifecycle. When a lead converts to a contact and opportunity, carry the revenue bucket, composite score at conversion, and score trajectory onto the opportunity record. The data drives downstream analysis: do opportunities that converted from high-scored leads win at a higher rate, do they close faster, do they expand more. Also feed the data backward to marketing: which campaigns produced the highest-scoring leads, which content correlated with mid-market versus enterprise bucket conversion, which ad channels delivered the best firmographic fit. The feedback loop is what makes revenue-range scoring a strategic lever rather than a routing utility. Strkr's pipeline and marketing attribution views natively tie lead scores to opportunity outcomes to campaign source, so the loop runs without manual stitching. Teams that keep the loop closed tune marketing targeting and sales focus together, instead of in parallel conversations that never converge.
Lead scoring by revenue range assigns a numerical score to each lead based on which revenue bucket their company falls into (SMB, mid-market, enterprise). The score helps route leads to the right sales segment, prioritize work within a segment, and feed clean data back to marketing on which campaigns produce the best firmographic fit.
Three to five. Fewer loses meaningful signal between buyer segments; more creates a complexity trap nobody maintains. The right number for your business matches how your sales teams are already structured: typically SMB, mid-market, and enterprise, with occasional sub-splits inside mid-market or enterprise if deal shape differs materially.
Third-party enrichment is the most reliable source. Vendors like ZoomInfo, Clearbit, and Apollo return revenue estimates with reasonable accuracy, and Strkr's native integrations with these providers populate the field at lead creation. Self-reported revenue from form submissions is unreliable and should be a tie-breaker, not a source of truth.
Build an explicit fallback path. Options include routing to a human triage queue, assigning a default bucket based on other signals (employee count, industry, email domain), or holding the lead in a nurture state until async enrichment completes. Pick one path per lead source and document it, because leads with missing data otherwise drop into a black hole.
Monthly for weight adjustments against actual conversion data; quarterly for structural changes like bucket boundary moves or signal additions. Weekly tuning overfits to noise. Annual tuning lets the model drift so far from current reality that it loses credibility with sales. Monthly is the right cadence for most teams.
Yes. Firmographic scoring on revenue alone will route leads but not prioritize them within a bucket. Layering behavioral signals (pageviews, downloads, email engagement) and intent signals (third-party intent data) on top produces a composite that both routes and prioritizes. Keep behavioral weights proportional so no single behavior outweighs the firmographic fit.
Strkr pairs native enrichment with configurable scoring tables, routing rules, and attribution dashboards. Build revenue-bucket scoring once and tune the weights without engineering help.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
