mcpField
L
lead-qualification

lead-qualification

github.com/gtmagentsMarketing & growth43083 installsUpdated 30w ago
Repository

About lead-qualification

lead-qualification is a skill for marketing, SDR, and RevOps teams to score and route leads consistently. It combines FITS criteria, weighted thresholds, and explainability notes with handoff checklists.

Key features

  1. 01FITS-based lead scoring
  2. 02Weighted score thresholds
  3. 03Scoring rationale notes
  4. 04Lead routing by score
  5. 05SDR-to-AE handoff checklist
  6. 06Inbound and outbound playbooks

Use cases

  1. 01Prioritizing leads before SDR outreach
  2. 02Standardizing marketing-to-sales handoffs
  3. 03Adapting scoring to evolving ICPs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill lead-qualification

After installing, type/lead-qualificationin Claude Code to confirm it loaded.

Details

From the project README

Lead Qualification Skill

When to Use

  • New inbound/outbound leads need scoring before SDR outreach.
  • Marketing > Sales handoff requires consistent acceptance criteria.
  • You must prioritize high-intent signals for limited SDR capacity.
  • RevOps wants transparent scoring logic tied to pipeline stages.

Framework

  1. FITS Model – Firmographics, Intent, Timing, Solution Match as core dimensions.
  2. Scoring Steps – normalize data, apply weights, set thresholds (80+, 60–79, 40–59, <40), and capture explainability notes.
  3. Question Toolkit – pain, authority, budget, timeline prompts to validate scoring inputs.
  4. Routing Logic – map scores to AE handoff, SDR follow-up, nurture, or recycle.
  5. Handoff Checklist – verify CRM data, attach notes/enrichment, include recommended CTA, start AE SLA timer.

Templates

  • Fit scoring sheet (CSV) with weight columns and notes.
  • Intent signal decoder (G2 topics → pains) for faster scoring.
  • Playbooks for inbound vs outbound vs PQL models.
  • Handoff checklist doc for SDRs.

Tips

  • Review weights quarterly with RevOps to match evolving ICP.
  • Keep explainability notes so AEs trust automated scores.
  • Pair scoring with QA sampling to catch bad data feeds early.
  • Share top intent triggers weekly so marketing can reinforce them.

Comments

Markdown supported