qualification-scorer
Use when scoring leads, qualifying prospects, prioritizing pipeline, deciding which accounts to pursue, or building a lead scoring model. Triggers: 'score this lead', 'qualify this prospect', 'is this a good lead', 'lead scoring', 'prioritize my pipeline', 'qualification framework'.
git clone --depth 1 https://github.com/Othmane-Khadri/gtm-engineer-playbook /tmp/qualification-scorer && cp -r /tmp/qualification-scorer/.claude/skills/gtm-playbook/qualification-scorer ~/.claude/skills/qualification-scorerSKILL.md
# Qualification Scorer Score and qualify leads using a multi-axis framework. Takes a lead or list of leads, evaluates them on four axes (Fit, Timing, Access, Intent), classifies them into tiers, and produces actionable next steps for each. ## Tools Used - **Read** — load `docs/icp.md`, `docs/signals/*.md`, `docs/accounts/*.md`, CSV files - **Write** — output scored results to `docs/pipeline/scored-leads.md` - **Glob** — discover existing docs that can enrich scoring ## Steps ### Step 1: Context Loading Check for existing files that inform scoring. Run these searches: ``` Glob: docs/icp.md Glob: docs/signals/*.md Glob: docs/accounts/*.md ``` - If `docs/icp.md` exists, read it and extract ICP criteria (company size, industry, stage, budget range). Use these criteria to auto-score the Fit axis. - If `docs/signals/*.md` files exist, read them and extract known trigger events, intent data, and timing indicators. Use these to inform Timing and Intent scoring. - If `docs/accounts/*.md` files exist, read them and cross-reference any leads against known account briefs for enrichment. - If NONE of these files exist, ask the user: > I don't see an ICP definition at `docs/icp.md`. Before I can score leads accurately, I need to understand your ideal customer. Tell me: > 1. What company size do you target? (employee count or revenue range) > 2. What industries or verticals? > 3. What company stage? (seed, Series A, growth, enterprise) > 4. What budget range per month are you selling into? Store the user's answers as the working ICP definition for this scoring session. ### Step 2: Lead Input Ask the user how they want to provide leads: > How would you like to provide the leads to score? > > **A.** Paste a list (company name, contact name, title — one per line) > **B.** Single lead deep-dive (I'll ask you detailed questions about one prospect) > **C.** Give me a CSV file path to read Handle each input mode: - **Option A (list):** Parse the pasted text. Extract company name, contact name, and title for each row. Tolerate messy formatting (comma-separated, tab-separated, or line-by-line). - **Option B (single lead):** Ask follow-up questions about the lead: company name, contact name and title, company size, industry, any recent events you know of, how you found them, any engagement so far. - **Option C (CSV):** Read the file at the given path. Map columns to company, contact, and title. If column names are ambiguous, show the header row and ask the user to confirm the mapping. ### Step 3: Scoring Framework For each lead, evaluate four axes. Score each axis 1 through 5. #### Fit (1-5) — Does this company match the ICP? | Score | Criteria | |-------|----------| | 5 | Perfect match: right size, industry, stage, and budget | | 4 | Strong match: 3 of 4 ICP criteria match | | 3 | Partial match: 2 of 4 ICP criteria match | | 2 | Weak match: 1 criterion matches | | 1 | No match: wrong segment entirely | If `docs/icp.md` was loaded, auto-score Fit by comparing the lead's known attributes against the ICP criteria. If information is missing, default to 3 and flag it for user review. #### Timing (1-5) — Is now the right moment? | Score | Criteria | |-------|----------| | 5 | Active buying event: demo requested, RFP published, contract with competitor ending | | 4 | Strong trigger: just raised funding, new CXO hired, hiring spree in relevant roles | | 3 | Moderate trigger: product launch, market shift, expansion announcement | | 2 | Weak trigger: general growth, no urgency indicators | | 1 | No trigger: stable company, no change signals detected | If `docs/signals/*.md` files were loaded, cross-reference leads against known signals to auto-score. Otherwise, default to 2 and flag for user input. #### Access (1-5) — Can you reach the decision maker? | Score | Criteria | |-------|----------| | 5 | Warm introduction available: mutual connection, past relationship, shared investor | | 4 | Second-degree connection: shared community, alumni network, conference overlap | | 3 | Cold but reachable: email address known, LinkedIn profile open, active on social media | | 2 | Cold and gated: no email found, LinkedIn restricted, requires research | | 1 | Unreachable: no contact info, heavy gatekeeper, not present on social platforms | IMPORTANT: Do NOT auto-score Access. Default to 2 for all leads and explicitly ask the user to review. The user almost always knows more about their access than any data source can reveal. #### Intent (1-5) — How much buying intent is visible? | Score | Criteria | |-------|----------| | 5 | Explicit intent: requested a demo, responded to outreach, asked for pricing | | 4 | High intent: reviewing competitors, published a pain point, attended your webinar | | 3 | Moderate intent: hiring for a related role, engaging with your content | | 2 | Low intent: company matches ICP but no engagement yet | | 1 | No intent: no visible interest or engagement signals | If signal files were loaded, use them to inform Intent scoring. Otherwise, default to 2 and flag for user review. ### Step 4: Composite Scoring Calculate the composite score and assign a tier for each lead. **Score** = Fit + Timing + Access + Intent (maximum 20) **Tier Classification:** | Score Range | Tier | Recommended Action | |-------------|------|-------------------| | 17-20 | HOT | Reach out within 24 hours. Top priority. Personalize heavily. | | 13-16 | WARM | Add to active outreach sequence. Nurture with value-first touchpoints. | | 9-12 | COLD | Monitor for trigger events. Build relationship passively. Revisit monthly. | | Below 9 | PARK | Add to quarterly review list. Not ready now. Check back in 90 days. | For each lead, generate a one-line recommended action that accounts for their specific score distribution. Examples: - Fit=5, Access=1 -> "Find a warm intro path before reaching out — this is a perfect-fit account stuck behind a cold wall." - Fit=3, Timing=5 -> "Timing is urgent but fit is uncertain. Val
Use when preparing to engage a target account, researching a company before outreach, or building pre-call intelligence. Triggers: 'research this company', 'account brief for [company]', 'company research', 'what do I need to know about [company]', 'pre-outreach research'.
Use when designing an autonomous agent, planning agent architecture, building a scheduled automation, or creating a Claude Code agent workflow. Triggers: 'design an agent', 'build an automation', 'agent architecture', 'automate this workflow', 'create a scheduled agent', 'shell script agent'.
Use when analyzing competitors, creating sales battlecards, building competitive positioning, preparing for competitive deals, or updating competitive intelligence. Triggers: 'battlecard for [competitor]', 'competitive analysis of [competitor]', 'how do we beat [competitor]', 'compare us to [competitor]', 'competitive intel', 'win against [competitor]'.
Use when auditing CRM data quality, finding duplicate records, identifying stale leads, cleaning pipeline data, or improving data hygiene. Triggers: 'clean my CRM', 'audit CRM data', 'find duplicates', 'CRM hygiene', 'data quality check', 'stale leads', 'pipeline cleanup'.
Use when building or refining an Ideal Customer Profile (ICP), defining target personas, mapping buyer psychographics, or discovering where prospects gather online. Triggers: 'build my ICP', 'define target customer', 'who should I sell to', 'refine ICP', 'persona mapping'.
Use when preparing for a sales meeting, discovery call, demo, or customer check-in. Triggers: 'prep me for a meeting with [company]', 'meeting brief for [company]', 'pre-call prep', 'I have a call with [contact] at [company]', 'meeting prep', 'call prep'.
Use when creating outreach sequences, writing cold email campaigns, building multi-channel cadences, designing follow-up flows, or crafting signal-triggered messages. Triggers: 'build an outreach sequence', 'write a cold email sequence', 'create a cadence', 'outreach for [signal]', 'email sequence', 'follow-up sequence', 'multi-channel outreach'.
Use when searching for buying signals, detecting intent data, scoring prospect readiness, or monitoring accounts for trigger events. Triggers: 'scan for signals', 'find buying signals', 'who is ready to buy', 'intent signals', 'signal scoring', 'account signals'.