Dual Scoring That Works in 2026: Fit + Intent + Capacity (With a Simple Formula)

Most lead scoring fails for one dumb reason: it produces a number, then nobody acts on it fast enough. Fit and intent without capacity is just a leaderboard.

TL;DR

• Build a fit intent scoring model with two scores, not one: Fit (0-100) + Intent (0-100).
• Add the missing third score: Capacity (0-100), which reflects how fast your team can realistically work the lead.
• Use one simple formula to turn all three into a single priority score.
• Route in minutes, not days. Speed matters. InsideSales research has hammered this for years: contacting quickly massively increases connect and qualification odds. (InsideSales lead follow-up)
• Run a weekly tuning loop. Keep it boring. Keep it accurate.

What “dual scoring” actually means in 2026

Dual scoring means:

• Fit score: “Should we sell to them?”
• Intent score: “Should we sell to them now?”

In 2026, teams that stop here still lose. Because the hottest accounts sit unworked while reps “get to them later.”

So the model that works is Fit + Intent + Capacity:

• Capacity score: “Can we actually work this right now, at the speed required?”

HubSpot’s newer scoring tooling even formalizes fit vs engagement in separate criteria, plus combined scores. The split is normal now. The execution is still rare. (HubSpot lead scoring tool, Build lead scores)

Define the three scores (clean definitions)

Fit score (0-100)

How closely the account and persona match your ICP.

Fit inputs usually come from:

• Firmographics (size, industry, geography)
• Technographics (tools they run, data stack, cloud)
• Role and seniority (the person who can buy, or the person who creates urgency)

Intent score (0-100)

How strongly the account is signaling active demand.

Intent inputs can be:

• First-party: your website activity, email engagement, demo requests, product usage for PLG
• Second-party: partner referrals, co-marketing lists, marketplace co-sell signals
• Third-party: review sites and intent networks (G2, Gartner Digital Markets, Bombora, etc.)

Intent data has a real definition in the market: it’s buyer behavior used to predict purchase likelihood. Gartner Digital Markets positions intent as behavior from its properties that identifies accounts “with the highest intent to purchase.” (Gartner Digital Markets B2B Intent Data)

Capacity score (0-100)

A real-time measure of whether the lead will get action within your SLA.

Capacity inputs include:

• Rep availability (open tasks, meetings today, PTO)
• Segment ownership (who can work it)
• Response SLA (can you hit it today, or will it rot)
• Queue health (backlog size, aging)

Capacity is not “nice to have.” Speed to lead is still a conversion multiplier. InsideSales has long published that successful contact rates spike when you respond in the first minutes. (InsideSales lead follow-up)

The simple formula (use this, stop debating it)

You want a single number for routing and priority. Use this:

Priority Score (0-100) = 0.45 * Fit + 0.45 * Intent + 0.10 * Capacity

Why this works:

• Fit and intent carry the outcome.
• Capacity is the tie-breaker that prevents “hottest lead dies in the queue.”

If your motion is inbound-heavy, shift intent up:

• Inbound motion default: 0.35 Fit / 0.55 Intent / 0.10 Capacity

If your motion is outbound-heavy, shift fit up:

• Outbound motion default: 0.55 Fit / 0.35 Intent / 0.10 Capacity

You can implement this in a spreadsheet, a CRM formula field, or directly inside Chronic’s scoring logic.

Chronic’s native model starts with dual fit + intent scoring, then prioritizes with capacity-aware routing so high intent does not sit idle. That is the difference between “smart scoring” and booked meetings. (Chronic AI Lead Scoring)

Step-by-step: build your fit intent scoring model

Step 1: lock the ICP inputs (or your scoring is cosplay)

You need an ICP that shows up in data. Not a vibe.

Start with 3 inputs max:

1. Company size band (employees or revenue)
2. Industry (or 2-3 verticals you actually win)
3. Triggering stack (one technographic that matters)

If you do not have clean ICP fields, fix that first. Chronic’s ICP Builder exists for this exact problem. (ICP Builder)

Step 2: Fit scoring rubric (0-100)

Build fit as three buckets:

• Firmographics: 50 points
• Technographics: 25 points
• Role/persona: 25 points

Here’s a plug-and-play rubric.

Firmographics (0-50)

• Employee band matches ICP: +20
• Industry matches ICP: +15
• Geography matches selling coverage: +5
• Funding/growth profile matches motion: +5
• Negative fit (student, agency, consultant, competitor): -25 to -50

Technographics (0-25)

• Uses required system (example: Salesforce if you sell a Salesforce app): +15
• Uses complementary tool (example: HubSpot + outreach tooling if you sell deliverability): +5
• Uses “anti-fit” stack (example: locked into your direct competitor on a long contract): -10 to -25

Role and seniority (0-25)

• Buyer role (VP Sales, RevOps, Demand Gen lead, etc.): +15
• Seniority (Director+): +5
• Functional adjacency (SDR manager if you need sales leadership): +3
• Generic title match only (no function clarity): +0

Fit score guardrails

• Cap at 100.
• If you apply negative fit, apply it hard. Weak disqualification wastes time.

To populate these fields at scale, you need enrichment that is consistent. Chronic does enrichment as a default step, not a separate tool you duct-tape in. (Lead Enrichment)

Step 3: Intent scoring rubric (0-100) using signals you already have

Most teams already have enough intent signals. They just do not score them.

Use two dimensions:

• Depth (how strong is the action)
• Recency/velocity (how recent and how many)

First-party intent (0-70)

Assign points by action strength.

High intent (buying actions)

• Demo request / contact sales: +40
• Pricing page visit (2+ times in 7 days): +20
• Integration docs visit: +15
• Case study view in their vertical: +10

Medium intent (evaluation actions)

• Webinar attendance live: +10
• Product tour completion: +10
• Reply to outbound email with real question: +15

Low intent (awareness actions)

• Blog view: +2
• Careers page: +1 (yes, it matters, but not like you think)

Add recency multipliers:

• In last 3 days: x1.3
• In last 7 days: x1.1
• Older than 14 days: x0.7

Product intent for PLG (0-70, replaces some web intent)

If you run PLG, product usage is intent. That is literally what a PQL is: someone who experienced value through usage and behavior. (TechTarget PQL definition)

Example PQL scoring:

• Hit “Aha” moment (your key activation event): +30
• Invited 2+ teammates: +15
• Connected integration: +15
• Usage on 3 distinct days in 7 days: +10

Third-party intent (0-30)

Optional. Useful. Not magical.

Examples:

• G2 Buyer Intent surges and category activity: +10 to +25 depending on intensity and stage. (G2 Buyer Intent documentation)
• Gartner Digital Markets intent activity in your category: +10 to +25. (Gartner Digital Markets B2B Intent Data)

Rule: Third-party intent never outweighs first-party buying actions. It’s additive, not authoritative.

Step 4: Add capacity-based routing (the piece everyone ignores)

If you want meetings, you need two things:

• The right lead
• At the right time
• Worked fast enough

Capacity scoring turns that into rules.

Capacity score rubric (0-100)

Score capacity at the rep or queue level.

• Rep has < 15 open tasks and < 6 meetings today: +30
• Rep is currently “on inbound” rotation: +25
• Lead is in correct territory and segment: +15
• SLA can be met inside 2 hours: +20
• Rep is on PTO or at meeting cap: -50
• Queue backlog has > 50 unworked leads: -30

If you do not have dynamic rep context, do capacity at the queue level:

• Queue backlog age < 24 hours: +30
• Backlog age 24-72 hours: +10
• Backlog age > 72 hours: -20

This is not academic. Routing and SLAs are the difference between scoring that looks good and scoring that produces pipeline. Even Salesforce ops folks frame scoring as useless without routing and action. (Salesforce lead management best practices)

Weighting examples: SMB vs mid-market (use-case ready)

SMB motion (volume, speed, lower ACV)

Your model should reward intent more than fit. SMB buyers move fast. Your team should too.

Recommended weights:

• Fit 35%
• Intent 55%
• Capacity 10%

Example thresholds:

• Priority Score 75+: instant call + email in 5 minutes
• 60-74: enroll in sequence, call within 24 hours
• < 60: nurture or low-touch outbound

Mid-market motion (higher ACV, more stakeholders)

Fit matters more. Wrong fit burns cycles across SDR, AE, and solutions.

Recommended weights:

• Fit 50%
• Intent 40%
• Capacity 10%

Example thresholds:

• Priority Score 80+: route to named SDR with 2-hour SLA
• 65-79: route to SDR pool, 24-hour SLA
• < 65: outbound later or marketing nurture

Tie-break rules (when two leads score the same)

Ties happen. Do not let reps choose based on vibes.

Use these tie-breakers in order:

1. Intent recency (last 72 hours wins)
2. Buying action type (demo request beats pricing visit)
3. Persona authority (economic buyer beats influencer)
4. Account expansion potential (existing customer expansion beats new logo, if your comp plan rewards it)
5. Capacity reality (if no rep can work it today, route to an “autonomous touch” queue)

That last one matters because “we’ll do it tomorrow” is sales fiction.

Implementation: the minimum viable stack (no mystery AI product required)

You can build this with:

• Spreadsheet + weekly upload
• CRM fields + workflow routing
• A lightweight rules engine

What you need in the CRM:

• Fit score field (0-100)
• Intent score field (0-100)
• Capacity score field (0-100)
• Priority score formula field
• Priority band field (A, B, C)
• Routing rule based on band + segment + capacity

If your current CRM setup needs five tools to do this, congrats, you bought a hobby. Chronic runs this end-to-end, including scoring, enrichment, sequencing, and pipeline tracking. (Sales Pipeline, AI Email Writer)

The score bands and the action map (this is where it turns into meetings)

Numbers do nothing. Actions book meetings.

Band A: Priority Score 80-100

Goal: contact now.

Actions:

1. Auto-assign to rep with highest capacity score
2. Create task due in 15 minutes
3. Trigger call + email sequence immediately
4. If no rep capacity, route to “autonomous first touch” sequence and escalate when rep frees up

Band B: Priority Score 65-79

Goal: contact today.

Actions:

• Assign within territory
• Start sequence within 2 hours
• Call within same business day

Band C: Priority Score 50-64

Goal: qualify via low-touch.

Actions:

• Email-only sequence
• Light personalization
• Re-score on any new intent event

Band D: Priority Score < 50

Goal: stop wasting time.

Actions:

• Nurture
• Exclude from SDR queue
• Keep for retargeting if relevant

If you want a cleaner way to operationalize this, map scoring to a signal-led cadence so outreach changes based on what the buyer did. Chronic already publishes this exact philosophy. (Signal-led sales cadence, Signal library)

Weekly tuning loop (the part that keeps it from rotting)

A fit intent scoring model is never “done.” It’s either tuned or dead.

Run this every week. Same 30 minutes. Same doc.

1) Pull the scoreboard

For the last 7 days, by band (A/B/C/D):

• Meeting booked rate
• Reply rate
• Connect rate (if calling)
• Time-to-first-touch
• No-show rate

2) Find two failure modes

Look for:

• Band A leads not converting - your intent weights are wrong, or your routing is slow.
• Band C leads converting surprisingly well - you under-scored a signal.

3) Change only 3 things

Examples:

• Increase pricing page weight from 10 to 20
• Add negative fit for agencies
• Add decay for “old intent” older than 14 days
• Raise capacity penalty for reps over meeting cap

4) Recalculate and compare

You want stability. Not chaos.

• If your weekly changes flip 40% of leads between bands, your model is too sensitive.

5) Lock the SLA

Speed is operational. Track it like revenue. If you are not responding fast, capacity must override scoring. This is where most orgs fail and then blame scoring.

For more on the execution jump, not just dashboards, this is the real line: ask systems questions, then do the work automatically. (Ask your CRM vs do the work)

Common pitfalls (so you do not build a pretty spreadsheet nobody trusts)

1. One combined score only

   • You lose explainability.
   • Reps stop trusting it.

2. Too many inputs

   • If your model needs 47 fields, it’s not smart. It’s fragile.

3. No decay

   • Old “intent” becomes a zombie score that clogs your queue.

4. No negative scoring

   • Bad fit needs real penalties.

5. No routing and no SLA

   • Then your “hottest lead” becomes “last week’s missed meeting.”

Where Chronic fits (one line of contrast, then back to results)

Apollo exports lists. HubSpot and Salesforce can score, but you still stitch enrichment, scoring logic, sequences, and routing together. That is why “lead scoring” turns into another tab.

Chronic runs end-to-end, till the meeting is booked: ICP, enrichment, dual scoring, capacity-aware prioritization, and outreach execution. Pipeline on autopilot. (AI Lead Scoring, Lead Enrichment, AI Email Writer, Outbound workflow blueprint)

FAQ

What is a fit intent scoring model?

A fit intent scoring model is a lead or account prioritization system that assigns a Fit score based on ICP match and an Intent score based on buying signals. Many teams also compute a combined priority score for routing and outreach.

Why not just buy an “AI lead scoring” product?

Because you still need to define your ICP, decide which signals matter, and enforce routing SLAs. If the vendor score is a black box, reps do not trust it and ops cannot tune it. Start with rules you can explain, then automate.

What intent signals work best if we do not pay for third-party intent?

First-party signals usually win:

• Demo requests
• Pricing page repeat visits
• Integration docs views
• Product usage events (PQL signals) These are direct evidence of evaluation behavior, not inferred interest.

How do I score capacity if my CRM cannot see rep workload?

Start with a queue-level capacity score:

• Backlog age
• Unworked lead count
• Hours of coverage Then route Band A to the smallest backlog first. It’s crude, but it stops the worst failure: hot leads sitting untouched.

How often should we tune the scoring weights?

Weekly. Small changes. Maximum three edits per week. Scoring models decay because your market and your motion change, not because the math is hard.

What is the fastest way to implement this without engineering?

Use a spreadsheet rubric to generate Fit and Intent scores, import them into CRM fields, then build simple workflow routing by band. If you want it fully autonomous, use a system that handles ICP, enrichment, scoring, and sequencing in one flow. Chronic does that out of the box. (Chronic AI Lead Scoring)

Build it this week, then let it earn the right to get fancy

1. Define Fit inputs (max 3) and score them to 100.
2. Define Intent inputs from signals you already have and score them to 100.
3. Add Capacity scoring so Band A never waits for “when I have time.”
4. Use the formula. Route by band. Enforce SLAs.
5. Tune weekly based on meetings booked, not clicks.