Dual Scoring That Actually Books Meetings: Fit + Intent, With a Stop-Sending Rule

Most teams do “scoring” the way they do New Year’s resolutions. They talk about it. They build a spreadsheet. Nothing changes. Pipeline stays sad.

Dual scoring fixes that, but only if you ship the part everyone avoids: rules that change actions. Who gets emailed. When. With what message. And when to stop sending.

This guide shows exactly how to build fit and intent scoring, then wire it into outbound with a hard stop-sending rule.

TL;DR

• Fit = “Should we ever sell to this account?” (firmographics, technographics, ICP match, constraints)
• Intent = “Is now the right time?” (site behavior, job changes, installs, ads + email engagement)
• Dual scoring = two numbers, one decision: prioritize, personalize, pause, or stop
• Stop-sending rule protects deliverability and brand. Google’s bulk sender guidance is explicit about spam rate thresholds and unsubscribe requirements. Ignore it and your domain pays the tax. (Google Email sender guidelines FAQ)

---

1) Define “fit and intent scoring” in one sentence

Fit and intent scoring is a two-part model that ranks accounts by:

1. ICP fit (how likely they are to succeed with your product), and
2. Buying intent (how likely they are to buy right now).

Most teams mash this into one “lead score” and wonder why the top “A+ leads” never reply.

Don’t.

Fit and intent are different forces. Treat them separately so your outbound can do different things:

• High fit + low intent = light touch, value-first, longer window.
• Low fit + high intent = tempting, but usually a time sink.
• High fit + high intent = all gas. Senior rep. Fast follow-up. Meeting priority.

---

2) Build your fit model (ICP) before you touch intent

Intent without fit is how you end up chasing random companies that read an article once.

Step 2.1 - Pick 6-10 fit inputs that actually matter

Use inputs you can explain to a rep in 15 seconds. If you need a data scientist, you already lost.

Fit inputs (good defaults):

• Firmographics
  • Industry
  • Employee range
  • Revenue range (optional, often messy)
  • Geography (if you have constraints)
• Technographics
  • Tools you integrate with
  • Tools you replace
  • “Stack smell” (signals they run modern GTM or the opposite)
• Structural constraints
  • Security/compliance requirements you cannot meet
  • Segment exclusions (education, gov, etc.)
• Triggers (fit-adjacent)
  • Recently funded
  • New exec hire (sales, marketing, revops)
  • Hiring velocity in relevant teams

If you want an ICP builder that doesn’t rot in a doc, start here: Chronic ICP Builder

Step 2.2 - Set your “hard no” fit filters first

Scoring comes after gating.

Examples of hard no:

• Under 10 employees (no budget, no process)
• Regulated segment you cannot serve
• Competitor tech that blocks your product entirely

Hard no means: score = 0, never enroll.

Step 2.3 - Assign fit points (keep it boring)

Start with a 0-100 fit score. You can get fancy later. Later never comes, so ship boring now.

Simple fit weighting (example):

• Industry match: 0-25
• Company size band: 0-25
• Tech stack match: 0-25
• Trigger strength: 0-15
• Geo/constraints match: 0-10

Your weights should reflect your real close rates. If you do not know them, set weights based on operator judgment and plan to recalibrate monthly.

Need clean inputs? Fit scoring collapses without enrichment. Chronic Lead Enrichment

---

3) Build your intent model (timing) from signals you can actually capture

Intent is not “they exist.” Intent is behavior, change, or motion.

Also, intent is noisy. One signal lies. Multiple signals converge.

Gartner calls third-party intent fundamental for improving effectiveness, but stresses combining multiple signals to find real buying activity. (Gartner: Combine Multiple Intent Signals)

Step 3.1 - Choose intent inputs by category

Category A: Website behavior (first-party)

• Pricing page view
• Integration docs view
• Competitor comparison page view
• Multiple visits within 7 days
• Time on page thresholds (use carefully)

Category B: Org changes (trigger intent)

• New VP Sales / RevOps / Marketing Ops
• Promotions (manager to director, director to VP)
• Team hiring spree (SDR hiring, AE hiring, RevOps hiring)

Category C: Tech installs (technographic intent)

• New tool installed that correlates with your use case
• Tool churn (they removed a competitor)
• New data provider, sales engagement platform, CRM migration

Category D: Paid + content engagement

• Retargeting ad clicks from target accounts
• Webinar signup from ICP accounts
• High-intent content: “migration,” “security,” “pricing,” “RFP template”

Category E: Email engagement (treat as weak intent)

• Reply > click > open. In that order.
• Multiple clicks on specific assets
• Forwarding signals (rare, but gold)
• Negative signals: spam complaints, repeated no engagement

Google’s bulk sender rules make it clear that complaint rate matters and one-click unsubscribe is not optional for bulk. That means your stop-sending rule is not “nice.” It’s survival. (Google Email sender guidelines FAQ)

---

4) The lightweight dual scoring table you can copy today

Here’s a simple model that works without a PhD.

Example: Fit score (0-100)

Example: Intent score (0-100)

Two important notes:

• Intent decays. Website intent from 90 days ago is basically a ghost. Put time windows on points.
• Replies override scoring. A human response beats your model every time.

---

5) Turn dual scoring into actions (the part that books meetings)

Scoring that doesn’t change routing is analytics cosplay.

You need a ruleset for:

• sequence enrollment
• message type
• channel choice
• follow-up priority
• when to stop sending

Step 5.1 - Create 4 segments using fit + intent thresholds

Keep thresholds simple.

Recommended starting thresholds:

• Fit: High = 70+
• Intent: High = 60+

That gives you four boxes:

1. High fit + high intent (HFHI)
2. High fit + low intent (HFLI)
3. Low fit + high intent (LFHI)
4. Low fit + low intent (LFLI)

Step 5.2 - Sequence enrollment rules (simple and ruthless)

HFHI: enroll immediately

• Start sequence within 5 minutes of signal (if possible)
• Assign to top-performing rep or meeting-setter
• Use the most specific message version (trigger-based)
• Add a call task if your motion uses phone

HFLI: enroll in a slower, value-first sequence

• Longer spacing
• Lower personalization cost
• More educational angle
• Goal: create engagement signals, not “book a meeting tomorrow”

LFHI: conditional enroll

• Enroll only if intent signal is strong and recent (example: demo request, pricing view + docs view)
• Otherwise, route to marketing nurture or ignore
• This box is where teams waste SDR hours chasing mirages

LFLI: never enroll

• Keep in a watchlist
• Re-score weekly
• Don’t burn your domain on deadwood

If you want this operational inside one system, Chronic runs dual scoring and prioritization here: Chronic AI Lead Scoring

---

6) Message rules: what you say changes with fit and intent

HFHI messaging: mirror the signal, ask for the meeting

You earned the right to be direct.

Structure:

1. Call out the signal (without being creepy)
2. Tie it to a likely priority
3. Give a tight meeting ask with a clear outcome

Example:

• “Saw your team is hiring SDRs and ramping outbound.”
• “That usually means lists, deliverability, and routing get messy fast.”
• “Worth a 12-minute call to map your scoring and stop-sending rules so reps only touch the accounts that can buy this month?”

HFLI messaging: teach, then trigger

No fake urgency. That’s how you get spam clicks.

Structure:

1. Call out fit (industry + role)
2. Offer a useful pattern
3. Ask a low-friction question

Example:

• “Most Series B SaaS teams hit the same wall: volume dies, targeting gets sloppy.”
• “We run fit and intent scoring with a stop-sending rule so outbound doesn’t torch the domain.”
• “Who owns scoring and routing today, RevOps or SDR leadership?”

Want better personalization patterns that don’t read like “nice post”? Use this: Personalization That Wins in 2026

---

7) The stop-sending rule (non-negotiable)

Teams love to “always follow up.”

Mailbox providers love to punish them for it.

Google’s guidance explicitly calls out spam rate thresholds (0.3% is a line in the sand) and requires one-click unsubscribe for bulk senders. (Google Email sender guidelines FAQ)

So your stop-sending rule needs two layers:

1. Contact-level stops (respect the individual)
2. Domain-level stops (protect deliverability)

Step 7.1 - Contact-level stop rules

Stop sending immediately when any of these happen:

• Unsubscribe
• Spam complaint
• “Not interested” (explicit)
• “Remove me”
• “We already use X” and you are not competing for displacement
• They ask to stop
• They bounce (hard bounce)
• They say “wrong person” AND they do not provide referral AND you cannot reliably route

Also stop after no engagement beyond a defined cap:

• Example: 6 touches across 21 days with zero clicks, zero replies
  Move to a 60-90 day recycle, then re-enter only if new intent appears.

Step 7.2 - Domain-level stop rules (protect the whole operation)

These stops pause campaigns when deliverability risk spikes:

• Spam complaint rate approaching provider thresholds (watch Gmail Postmaster if you have volume)
• Sudden bounce spikes (list quality issue)
• Open rates collapse across mailboxes (reputation hit or filtering)

If you do not have a weekly deliverability SOP, fix that before you crank volume. Use: Cold Email Deliverability Ops in 2026

Dry truth: the stop-sending rule is how you keep sending next month.

---

8) Reply handling and meeting booking priority (your routing rules)

Scoring decides who enters. Replies decide everything next.

Step 8.1 - Reply classification rules

Every reply becomes one of these:

1. Positive (meeting interest)
2. Objection (timing, budget, authority)
3. Not now (future)
4. Not a fit (stop)
5. Wrong person (reroute)
6. OOTO (pause then retry)

Step 8.2 - Priority rules (who gets handled first)

When you run volume, speed becomes a weapon.

Meeting booking priority order:

1. Positive reply from HFHI
2. Positive reply from HFLI
3. Objection from HFHI
4. Positive reply from LFHI
5. Everything else

If your team responds to “maybe later” faster than “yes,” you deserve the quarter you get.

Step 8.3 - Scheduling rules (stop losing meetings to friction)

• Offer 2 specific times, then a calendar link.
• Confirm agenda in one line.
• Auto-create CRM activity and tag the original fit and intent scores for analysis.

If your CRM cannot keep up with the workflow, you end up duct-taping tools. Here’s the consolidation playbook: The 2026 CRM Stack for SMBs

---

9) Operationalize inside outbound (so it runs without hero reps)

Step 9.1 - Set a weekly scoring cadence

• Recompute intent daily if you have signals.
• Recompute fit weekly or monthly (fit shifts slower).
• Review thresholds weekly for the first 4 weeks, then monthly.

Step 9.2 - Track the only metrics that matter

Forget “leads scored.”

Track:

• Meetings booked per 100 enrolled (by segment)
• Reply rate (by segment)
• Positive reply rate (by segment)
• Time-to-first-touch after intent spike (HFHI should be minutes, not days)
• Unsubscribe and complaint rates (by segment and by sequence)

Forrester reports that 86% of B2B purchases stall and 81% of buyers are dissatisfied with the provider they choose. Translation: buyers are overwhelmed and picky. Relevance wins. (Forrester press release, Dec 4 2024)

Step 9.3 - Recalibrate weights using booked meetings, not vibes

Every 30 days:

• Pull booked meetings by segment.
• Identify which fit inputs correlate with bookings.
• Identify which intent inputs correlate with replies and bookings.
• Reduce points for “vanity intent” (random blog visits, opens).
• Increase points for “commitment intent” (pricing, docs, demo, stakeholder activity).

---

10) Where Chronic fits (if you want this to run end-to-end)

You can build this with a stack of tools and a RevOps wizard.

Or you can run it the way it should run: autonomous and tied to actions.

Chronic:

• Defines ICP and routing with ICP Builder
• Enriches accounts with Lead Enrichment
• Scores with dual fit + intent via AI Lead Scoring
• Writes sequences with AI Email Writer
• Runs follow-up and routing inside your Sales Pipeline

Competitors exist for pieces of the workflow:

• Apollo runs data + engagement, but you still stitch logic and governance. (Chronic vs Apollo)
• HubSpot runs CRM and sequences, but dual scoring logic often turns into custom property soup. (Chronic vs HubSpot)
• Salesforce runs anything if you pay enough and hire admins to babysit it. (Chronic vs Salesforce)

Chronic runs the whole motion till the meeting is booked. Pipeline on autopilot.

---

FAQ

What’s the difference between fit scoring and intent scoring?

Fit scoring measures whether an account matches your ICP and can succeed with what you sell. Intent scoring measures whether that account shows signs of active buying motion right now. Fit stays stable. Intent spikes and decays.

What’s a good starting threshold for “high fit” and “high intent”?

Start with High fit = 70+ and High intent = 60+ on a 0-100 scale. Then recalibrate after 30 days using booked meetings per segment. Keep thresholds stable long enough to learn.

Which intent signals matter most for outbound?

Strongest signals are the ones closest to purchase: pricing page views, integration/docs views, demo requests, and org changes in buying roles. Email opens are weak. Replies are king.

How do I implement a stop-sending rule without killing pipeline?

You stop sending to people who do not engage and people who explicitly opt out. That improves deliverability, which increases total inbox placement. More inbox placement means more replies from the right accounts. You replace “more follow-ups” with “better targeting and timing.”

How often should we update the scoring model?

Recompute intent daily if signals change quickly. Recompute fit weekly or monthly. Recalibrate weights monthly for the first quarter, then quarterly once stable.

What’s the biggest mistake teams make with fit and intent scoring?

They score leads but do not change actions. No routing. No sequence differences. No priority rules. No stop-sending rule. They end up with a pretty dashboard and the same outbound behavior that wasn’t working last month.

---

Build it this week. Then enforce it.

1. Ship a basic fit model (0-100) with 6-10 inputs.
2. Ship a basic intent model (0-100) with time windows.
3. Create the four-box routing (HFHI, HFLI, LFHI, LFLI).
4. Enforce enrollment rules and reply priority.
5. Enforce the stop-sending rule like your domain depends on it, because it does.
6. Recalibrate monthly using booked meetings, not feelings.