lead-scoring-model
/lead-scoring-model
Use this skill when you need a lead scoring model that sales trusts: inbound leads pile up unworked, marketing and sales argue about MQL quality, or reps chase the wrong leads first. Designs a two-axis model (fit and engagement) from your won and lost data, sets point values and decay, defines the handoff threshold and the SLA, and includes the test that proves the model works. Produces a documented scoring model ready to configure in any CRM or marketing system.
- Author
- prosyo-ai ↗
- Repository
- gtm-skill ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill when you need a lead scoring model that sales trusts: inbound leads pile up unworked, marketing and sales argue about MQL quality, or reps chase the wrong leads first. Designs a two-axis model (fit and engagement) from your won and lost data, sets point values and decay, defines the handoff threshold and the SLA, and includes the test that proves the model works. Produces a documented scoring model ready to configure in any CRM or marketing system.
Original author description
Use this skill when you need a lead scoring model that sales trusts: inbound leads pile up unworked, marketing and sales argue about MQL quality, or reps chase the wrong leads first. Designs a two-axis model (fit and engagement) from your won and lost data, sets point values and decay, defines the handoff threshold and the SLA, and includes the test that proves the model works. Produces a documented scoring model ready to configure in any CRM or marketing system.
How it works
- Inputs
- The play
- What good looks like
- Rules
- Example prompts
SKILL.md preview
---
name: lead-scoring-model
description: "Use this skill when you need a lead scoring model that sales trusts: inbound leads pile up unworked, marketing and sales argue about MQL quality, or reps chase the wrong leads first. Designs a two-axis model (fit and engagement) from your won and lost data, sets point values and decay, defines the handoff threshold and the SLA, and includes the test that proves the model works. Produces a documented scoring model ready to configure in any CRM or marketing system."
license: MIT
metadata:
title: Lead scoring model
category: prospecting
tags: "RevOps, Marketing, Demand Gen, Sales Leaders"
author: prosyo
version: "1.0.0"
keywords: "lead scoring model, b2b lead scoring template, mql scoring, claude lead scoring skill, predictive lead score"
inputs: "Won and lost leads with attributes, Engagement data, Sales capacity"
outputs: "Fit and engagement scoring tables, Handoff threshold, SLA, Validation report"
---
Use this when the question is "which leads should sales call first?". It produces a scoring model with point tables, a threshold and a validation test, documented well enough that anyone can configure it.
## Inputs
- 6 to 12 months of leads with outcome: became an opportunity, won, or went nowhere.
- Firmographic and role data on each lead.
- Engagement events: form fills, page visits, email replies, event attendance, product sign-ups.
- Sales capacity: how many leads a week the team can work properly.
## The play
### 1. Two axes, never one
- **Fit** (who they are): role, company size, industry, region, stack. Changes rarely.
- **Engagement** (what they did): actions, weighted by intent, decaying over time.
A single blended number lets a student who downloads ten ebooks outrank a VP who visited pricing once.
### 2. Derive points from data
For each attribute and action, compare the opportunity rate of leads that have it with the base rate. Points roughly follow the lift: an action with 4x the base opportunity rate earns about twice the points of one with 2x. Read [references/scoring-tables.md](references/scoring-tables.md) for starter tables and the lift method.
### 3. Add negative scores and decay
Subtract for students, competitors, personal emails, job seekers and unsubscribes. Halve engagement points every 30 days so old activity does not keep a lead hot.
### 4. Set the threshold from capacity
Choose the fit and engagement cut-offs that send sales roughly the number of leads they can work within the SLA. A threshold that produces 300 leads a week for a team that can work 80 trains reps to ignore scores.
### 5. Define the handoff
- High fit + high engagement: route to sales, first touch within 1 business hour (inbound) or same day.
- High fit + low engagement: targeted outbound or nurture.
- Low fit + high engagement: self-serve path or marketing nurture.
- Low fit + low engagement: no action.
High-intent actions such as a demo request or pricing contact bypass scoring entirely.
### 6. Validate before launch
Backtest on last quarter: the top 20% of scored leads should hold at least 50% of the opportunities. Then review monthly.
## What good looks like
- Sales can explain any score from the point table in 30 seconds.
- The top-scored decile converts to opportunity at 3x or more the average.
- Demo requests never wait for a score.
- The common mistake is guessing points in a meeting ("a webinar feels like 10 points") instead of deriving them from outcomes.
## Rules
- MUST keep fit and engagement as separate scores.
- MUST include decay and negative scoring.
- MUST backtest before going live.
- NEVER route a direct demo or pricing request through scoring delays.
## Example prompts
- "Build a lead scoring model from this export of 4,000 leads with outcomes."
- "Our MQLs convert at 3%. Redesign the scoring so sales trusts it."
- "Set a threshold that sends my 5 reps about 60 leads a week."
Files in this package (2)
- SKILL.md 4 KB
- references/scoring-tables.md 2 KB
Versions
The database has no other skills named lead-scoring-model.
Database snapshot: 13.11.2026 · package version aeead1d7d1bb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100lead-scoring-model-builder
Builds a lead scoring model from your own won and lost leads, turning traits and actions into points, fitting decay and picking the MQL threshold from a backtest. Also audits an existing model and builds PQL scores. Use when asked to build, fix or audit lead scoring or set an MQL threshold. - 100lead-scoring
Design, validate, and recalibrate a lead scoring model - fit and engagement signals, weighting, negative scoring and exclusions, decay, MQL/PQL threshold and tier setting, backtesting against closed-won/closed-lost outcomes, and governance; also diagnoses an existing broken… - 100lead-handoff-sla
Use when the user wants to check whether the marketing-to-sales lead handoff works: MQLs followed up within the SLA, sales accepting what marketing sends, and the MQL threshold in the right place. Also use when the user mentions lead response time, speed to lead, MQL SLA, SLA… - 100lead-handoff-designer
Designs the marketing to sales lead handoff from your CRM lead export, setting MQL vs SQL rules, lead routing, a response time SLA, rejected lead recycling and no-show steps. Use to define MQL and SQL, write a sales SLA or fix speed to lead. Not for scoring (use lead-scoring-model-builder). - 87sales-marketing-sla
AUTO-TRIGGER: Apply this skill when the user wants to build, fix, or document the agreement between sales and marketing around lead quality, lead handoff, and follow-up expectations. Trigger phrases include: "MQL definition," "sales-marketing SLA," "lead handoff," "sales isn't… - 95lead-scoring
Set up and automate lead scoring for HubSpot and other CRMs. Use when a user wants to score leads, define MQL/SQL criteria, build scoring matrices, configure lifecycle stages, implement engagement scoring, or automate lead qualification. Instruction-only skill with scoring…