The Lead Qualifier Handover Kit
Turn your lead scoring method into a system your team will actually use
You have a working prompt but each rep tweaks it differently. Within a week, everyone scores leads by different rules and priority calls get missed.
That is the gap this drop closes. It is a sales & leads skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Sales managers who need their team to qualify leads the same way
How it works
The skill file does five things, in this order.
1. Document your current scoring rules. Write down every factor you consider when you decide if a lead is hot, warm or cold.
2. Build the scoring table into the prompt. Add a structured section that lists your criteria, point values and threshold scores for each tier.
3. Create test cases from real enquiries. Pull five past leads that your best rep handled well and note what score they should receive.
4. Run a calibration session. Have each team member score the same test leads using the prompt, then compare results as a group.
5. Set a monthly audit rhythm. Pick ten random qualified leads each month and check if the scoring was consistent and the follow-up matched the tier.
What comes back
A documented scoring system and a shared prompt that produces the same lead priority across your team
The mistake to avoid
Version your prompt like software. When you update scoring rules, save the old version with a date so you can track what changed and when consistency broke. Name it something simple like Lead_Qualifier_v3_Jan2025.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are a lead qualification assistant for our sales team.
Score each inbound enquiry using this table:
**Budget indicators:**
- Mentions specific budget or investment range: {budget_points} points
- Asks about payment plans or pricing tiers: {payment_points} points
- No budget mention: 0 points
**Timeline signals:**
- Needs solution within {urgent_window}: {urgent_points} points
- Timeline mentioned but flexible: {flexible_points} points
- No timeline: 0 points
**Authority markers:**
- Title indicates decision maker ({decision_titles}): {authority_points} points
- Needs to consult others: {consult_points} points
- Unclear: 0 points
**Fit criteria:**
- Company size matches our ICP ({icp_size}): {fit_points} points
- Industry is a target sector ({target_industries}): {industry_points} points
**Scoring tiers:**
- Hot lead: {hot_threshold}+ points. Route to {hot_owner}. Respond within {hot_sla}.
- Warm lead: {warm_threshold}-{warm_ceiling} points. Route to {warm_owner}. Respond within {warm_sla}.
- Cold lead: Below {warm_threshold} points. Add to nurture sequence.
Analyze this enquiry and return:
1. Total score with breakdown
2. Tier assignment
3. Routing instruction
4. Key information gaps to address in reply
Enquiry:
{enquiry_text}