Anton Chisliuk · AI Marketing Ops
Anton Chisliuk
AI Marketing Ops

Sales Operations

Lead Scoring Worksheets + Free Calculator (Download)

Build a reliable lead scoring model in under an hour. Download free worksheets and a spreadsheet calculator, then plug the model into HubSpot, Salesforce, or your CRM.

12 min readWritten by: Anton ChisliukMiddle of funnel

You don’t need a six-week workshop to qualify leads. You need a clear scoring model, a simple calculator to stress-test it, and a clean handoff to sales. This guide ships all three: free lead scoring worksheets, a ready-to-use calculator, and a practical implementation plan for HubSpot, Salesforce, and spreadsheets.

Lead scoring’s real job: faster, cleaner handoffs to sales

Lead scoring is not about points; it’s about decisions. Who should sales talk to now, who needs more nurturing, and who should be filtered out entirely? When it works, sales gets a short and defensible list of people to call, while marketing stops burning budget on the wrong audience.

Good scoring compresses time-to-first-conversation. It communicates “why” a lead is worth attention (ICP fit + intent), not just that they exist in your CRM. Done right, it also reduces political bickering. Instead of sales saying “marketing sends junk,” you can show the attributes and behaviors that drove qualification.

We’ve seen this effect firsthand. For example, in B2B SaaS, tightening scoring and routing contributed to outcomes like 0→80K organic visits/month and 0→2K inbound leads/month for Cleverence, with a 16% lead-to-purchase rate on qualified demand. If you want a quick read on how rigorous execution compounds, see the Cleverence case study.

What’s inside the free pack: worksheets and calculator

This pack gives you a ready-made framework and a spreadsheet calculator so you can design and pressure-test your model in under an hour. You’ll also find a mapping worksheet to translate your model into CRM properties and workflows.

Components included:

  • Fit vs. Intent Worksheet: Define ICP attributes (industry, company size, tech stack, role) and intent signals (pageviews, assets, demo requests). Includes defaults.
  • Negative & Disqualifier List: Countries, roles, competitors, and behaviors to subtract or exclude.
  • Scoring Calculator (Spreadsheet): Weighted scoring with an adjustable scale (0–100 by default), decay, and scenario testing.
  • Lifecycle Mapping Sheet: Translate scores to MQL/SQL/SAL thresholds and SLAs.
  • HubSpot/Salesforce Field Map: Properties, workflows, and routing logic templates.

Use the worksheets to define “fit” and “intent,” then drop those weights into the calculator. Run a few real leads through it to see whether high-value contacts actually surface at the top. Iterate until your model matches sales reality.

Lead scoring framework: fit, intent, recency, and disqualification

Your model should be simple enough to audit, but detailed enough to reflect buying signals. Start with four pillars: Fit, Intent, Recency, and Disqualification.

Fit measures whether the person and company match your ICP. Don’t overcomplicate. Keep it to five to seven high-signal attributes that correlate with win rate. If your best customers are 50–250 FTE logistics firms on Microsoft stack, weight those heavier than generic firmographics.

Intent captures behavior. Not all clicks are equal. A demo request or pricing page visit means far more than a single blog view. Use ladders: low-intent (newsletter signup), medium-intent (comparison guide download), high-intent (demo/pricing/implementation pages, return visits).

Recency matters. Someone who did five high-intent actions yesterday is hotter than someone who did ten last quarter. Introduce decay so scores drift down over time if there’s no activity. It’s honest and keeps sales focused.

Disqualification saves everyone time. If you can’t or won’t sell to a geography, competitor domain, or student email, subtract hard or set a “disqualified” flag. Negative scoring is a kindness to sales capacity.

Default scoring blueprint you can start with

These are starting points. Replace with your data as soon as you see patterns.

  • Fit (max 50 points)
    • Industry match: +10
    • Company size within ICP: +10
    • Tech stack match (e.g., uses HubSpot, Azure): +10
    • Role seniority (Director+): +10
    • Buying center (RevOps/IT/Finance when relevant): +10
  • Intent (max 40 points)
    • Demo request/contact sales: +30
    • Pricing page view (unique): +15
    • Product docs/case study (2+ pages): +10
    • Engaged email click on product offer: +10
  • Recency & frequency (max 20 points)
    • Actions in last 7 days: +10
    • 3+ high-intent events in 14 days: +10
  • Negative/Disqualifiers
    • Competitor domain: -100 (auto disqualify)
    • Student/free email for enterprise offer: -20
    • Out-of-ICP geography: -20
    • Role mismatch (Intern, Student): -10

Scale the ranges to your motion. Many teams cap at 100. If you have dense data, extend to 200 to give yourself room without cramming everything into a narrow band.

Templates are a start. Your real power comes from tuning the model to your funnel. You’ll do this with three feedback loops: win analysis, qualitative sales input, and volume testing.

Start by analyzing the last 50 wins and 50 losses. Which industries, sizes, roles, and behaviors show up in wins far more than losses? Give those signals more weight. If your closer says “Deals above 200 seats that visit Pricing twice close 30%,” don’t argue - codify it.

Then run volume testing. Push historical contacts through the calculator. Do your top 10% by score look like closed-won accounts? If not, you’re over-weighting weak signals (e.g., generic content views). Rebalance until the top decile aligns with reality.

Finally, force tradeoffs. If everything is important, nothing is. Limit each pillar to a maximum so you don’t crowd out higher signal attributes.

Map scores to lifecycle stages and SLAs

A score without action is trivia. Decide what happens at each threshold and who owns it. Keep it brutally simple so sales can run the playbook without a committee meeting.

Example mapping:

  • 0–49: Nurture (Marketing). Enter a 30–45 day educational sequence, no sales touch unless behavior spikes. Decay aggressively.
  • 50–74: PQL/MQL (Marketing → SDR). Auto-create task for SDR within 24 hours. Two calls + one email within 48 hours. If no connect, drop back to nurture.
  • 75+: SQL (SDR → AE). Immediate connect attempt. If demo booked, move to SAL; otherwise, hold for 5 business days with 5x multi-channel touch plan.

Tune the thresholds to your demand mix. If you’re generating few but high-intent leads, raise the MQL/SQL lines. If you have volume but lower intent, enforce a strict SLA on the mid-tier band and use behavior-based promotions.

Write these SLAs on the worksheet and share them with the team. If the rule is “Pricing page + demo request = immediate call,” you want zero ambiguity in execution.

Implement in HubSpot, Salesforce, and spreadsheets

Use the calculator to finalize weights, then move to your CRM so scoring runs automatically. The pack’s field map shows required properties and recommended workflows for routing and alerts.

HubSpot approach: create a numeric property (e.g., Lead Score) and use the built-in scoring tool for attribute and behavior points. Add workflows to trigger when score crosses thresholds (e.g., enroll in SDR queue, create task, send Slack alert). If you need granular logic (e.g., decay or “seen pricing twice in 14 days”), use custom behavioral events and time-based workflow branches.

Salesforce approach: create a score field and use Flow or a scoring app to manage rules. For behavior, track campaign member statuses and pageview events (via Marketing Cloud, Pardot, or custom tracking) and use a process that increments/decrements scores. Leverage assignment rules and queues for routing once thresholds are met.

No CRM? The spreadsheet calculator still works. Import your contacts, map attributes, and use formulas to compute scores. It’s manual, but it will validate your model before you invest engineering time. Once proven, port the fields and weights into your CRM of choice or get help with CRM and HubSpot implementation.

Automate scoring across channels without adding headcount

Rules are only useful if they stay current. Connect web analytics, email, ads, and product usage so behavior-based points are assigned immediately. You can do this with native tools or lightweight automation platforms.

Web and content: track visits to pricing, docs, competitors vs. you, high-intent blogs, and repeat sessions within 14 days. Assign +5 to +15 for each unique high-intent page and add multipliers when events cluster in a short window.

Ads and email: push campaign member data into your CRM. Differentiate between awareness clicks and product offer clicks. Don’t over-credit ad clicks; prioritize form fills and site engagement that follows.

Product usage: if you have a freemium or trial motion, push events like “invited 3 team members,” “connected integration,” or “exported data.” These are gold for PQLs and should jump scores sharply.

If you’re missing glue between tools, route events with Make or n8n and translate them into consistent CRM updates. For help designing always-on workflows, see our approach to marketing automation.

Operator’s note: If you want a single accountable builder instead of a layered agency, Anton Chisliuk · AI Marketing Ops runs the operator model - one senior person ships SEO, paid, outbound, HubSpot, and automation in a 90-day cycle. Transparent economics, month-to-month after initial build. Proof includes B2B SaaS outcomes like 0→80K organic visits/month and 2K inbound leads/month. Learn more on our about page.

Common pitfalls and how to fix them

Too many weak signals: If everything gives +5, nothing stands out. Collapse low-signal items (e.g., “any blog view”) into a single low cap, and push weight into proven high-intent actions.

No negative scoring: You’ll waste sales cycles chasing the wrong regions or roles. Add firm disqualifiers and negative points so SDRs don’t have to guess. This also prevents vanity MQL spikes.

Stale recency: A lead that clicked an email 90 days ago isn’t hot. Set a decay rule (e.g., -10 every 14 days without activity, bottoming at 0) so queues self-clean without manual grooming.

Overfitting single channels: If your model only recognizes demo requests, you’ll miss accounts warming up across multiple product pages and case studies. Reward clusters of actions, not just forms.

Hidden logic: If sales can’t explain why a lead is qualified, trust erodes. Store score breakdowns in properties or the activity timeline so anyone can see the recipe.

Commit to a 90-day improvement window. The first month validates that your thresholds produce a manageable SDR workload. The second month tunes weights based on connect and conversion data. The third month locks in routing and reporting.

Weekly: review top-scorers that didn’t convert. Which signals were misleading? Remove or downgrade them. Also look for surprise wins and upgrade their signals. Keep notes in the worksheet for version control.

Monthly: run a backtest. Take a cohort of leads and simulate scores with your current model. Compare score deciles to down-funnel outcomes (connects, meetings, pipeline). If the top decile isn’t meaningfully better than the middle, you have work to do.

Quarterly: revisit ICP. Markets move. If your win rate is rising in a new segment, reflect that in Fit scoring and content programming.

Reporting that sales actually uses

Don’t bury outcomes in dashboards nobody opens. Give sales sortable, alert-driven views and a small set of reports tied to SLAs and pipeline.

Core artifacts to ship:

  • Hot Leads view: score ≥ SQL threshold, last activity ≤ 7 days, not yet contacted.
  • Reheat view: previously qualified leads that dipped below threshold and recently spiked again.
  • Breakdown panel: Fit vs. Intent contribution and top three behaviors that drove qualification.

Leadership needs three things: MQL→SQL conversion by segment, time-to-first-touch vs. win rate, and pipeline created per 100 qualified leads. If those three trend up, scoring is doing its job.

Example models by motion

SaaS (sales-assisted): Favor pricing, docs, product tours, and multi-user trials. Fit focuses on industry, team size, and tech stack. Negative score for student emails or competitors.

Example highlights:

  • Pricing page visit (unique): +15 (cap 30 if multi-visit)
  • Docs/implementation content (2+ pages): +10
  • Trial activated: +20; invited teammate: +10 each (cap 20)
  • ICP role Director+: +10; ICP industry: +10
  • Decay: -10 every 14 days without activity

Ecommerce (high AOV/B2B): Use account-level scoring. Weight SKU/category page clusters, cart activity, and repeat visits. Fit: company type and order volume potential. Penalize retail-only consumers if you sell wholesale.

Local/Services (healthcare, legal, clinics): Prioritize location match, service-line page views, phone clicks, and form submissions. Negative for out-of-area and non-service keywords.

Build vs. buy: rules, predictive scoring, and CDPs

Rules-based models are enough for most teams. They’re transparent, editable, and easy to connect to routing. If you have data science resources or big volume, predictive scoring can uncover patterns your rules miss - but only if you feed it clean, consistent CRM data.

CDPs and intent data (e.g., third-party intent providers) can boost context, but they’re not a substitute for fundamentals. If your reps don’t call hot leads within hours, no model will save you.

Pragmatic path: start with rules, add predictive later. Keep your worksheet as the source of truth so you don’t forget why the machine made a decision.

A quick, practical rollout plan

Day 1–2: Use the worksheets to define ICP fit, intent events, negatives, and thresholds. Build the first draft in the calculator and test with 50 historical leads.

Day 3–5: Implement in CRM. Create score property, workflows, routing, and alerts. Enable auditability (breakout fields or timeline notes).

Week 2: Train SDRs and AEs on the “why” and the SLA playbook. Add dashboards and views. Start the 90-day iteration loop.

Soft CTA: If you want someone to stand up the model, wire your CRM, and automate the workflows without adding internal headcount, this is standard operating work in our builds. We can get you to a working MQL/SQL handoff in weeks, not quarters.

Conclusion

You don’t need a complex system to qualify leads. A defensible score, a firm SLA, and automation that updates in real time will lift conversions and reduce waste. Start with the worksheets here, validate with the calculator, and only then wire it into your CRM. Keep it transparent so sales trusts the number, and revisit weights every quarter.

If you want an outside view and a clear, prioritized build plan across scoring, routing, and dashboards, start with a free Growth Audit. We’ll show you what to keep, what to cut, and what to ship next.

Written by Anton Chisliuk - Leads, sales, content, and systems - one senior operator.

FAQs

- What is lead scoring and why should I bother?

It’s a repeatable way to rank leads by fit and buying intent so sales focuses on the right people, fast. Teams that deploy it well see higher connect rates, more meetings from the same volume, and less friction between marketing and sales.

- Do I really need both “fit” and “intent” in the model?

Yes. Fit (ICP attributes) without intent just tells you who could buy someday. Intent without fit fills pipelines with unqualified interest. The combination is what predicts near-term opportunity.

- How many points should a demo request be worth?

In most B2B motions, 25–35 points is appropriate, with additional boosts for pricing or implementation page views. Calibrate by backtesting against deals that closed to confirm it pushes the lead over your SQL threshold.

- How often should I revisit the scores and thresholds?

Light tuning monthly, deeper review quarterly. Markets shift, content changes, and your SDR tactics evolve. Use a 90-day loop to lock in improvements and avoid endless fiddling.

- Can I do lead scoring without HubSpot or Salesforce?

Yes. Start in a spreadsheet using the calculator from this pack. Once the model aligns with reality, implement it in your CRM so it runs automatically and triggers routing/alerts.

- What’s the difference between rules-based and predictive scoring?

Rules-based uses weights you design - transparent and easy to audit. Predictive uses machine learning to infer weights from historical data. It can work well at scale but requires clean data and still benefits from human oversight.

- How do I get sales to adopt the scoring model?

Make the score explainable (show top factors), set simple SLAs, and prove value early by reviewing a handful of wins and losses together. When reps see it saves time and surfaces real buyers, adoption follows.

- Should I include negative scoring?

Absolutely. Out-of-ICP geographies, competitor domains, or student emails should subtract points or hard-disqualify. This prevents vanity MQLs and focuses reps on real opportunity.

- How do I handle decay?

Apply a time-based decrease (e.g., -10 every 14 days with no activity) and cap the downside at zero. This mirrors reality - interest fades - and prevents sales from chasing stale leads.

- What if my top-scored leads aren’t closing?

Backtest and rebalance. You’re probably over-weighting weak signals (e.g., generic content). Reduce those, raise weights on proven actions (pricing, demo, product docs), and review with sales weekly for 90 days.

Written by

Anton Chisliuk

Founder & Lead Operator · AI Marketing Operator

Anton Chisliuk is a GTM Engineer and Marketing Systems Architect. He built Cleverence's AI-native revenue OS (88 Make blueprints, MCP hub, 0→200K organic, 2.2K leads/mo) and now delivers outsourced GTM Engineering — CRM, automation, SEO, outbound — for growth-stage businesses via aimrktops.com.

About Anton →

Ready to fix this — for real?

Book a free Growth Audit. No sales deck — a 30-minute conversation about your pipeline, stack, and what to ship first.

Lead Scoring Worksheets + Free Calculator (Download)