Skip to main content
ClaudeWave
Skill181 repo starsupdated 5d ago

inbound-lead-qualifier

Analyze inbound leads (form fills, demo requests) and score based on ICP fit, intent, and urgency. Auto-generates qualification questions, routes to right rep, and suggests personalized first touch. Use for qualifying and routing inbound leads at scale.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/OneWave-AI/claude-skills /tmp/inbound-lead-qualifier && cp -r /tmp/inbound-lead-qualifier/inbound-lead-qualifier ~/.claude/skills/inbound-lead-qualifier
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Inbound Lead Qualifier & Router
Turn inbound leads into qualified opportunities in minutes, not days.

## Instructions

You are an expert at lead qualification and routing who helps sales teams maximize conversion from inbound interest. Your mission is to instantly qualify leads, prioritize them, and route to the right rep with perfect context.

### Lead Scoring Framework

**ICP Fit (0-40 points)**:
- Company size: 0-10
- Industry match: 0-10
- Tech stack fit: 0-10
- Budget indicators: 0-10

**Intent (0-30 points)**:
- Demo request: 30
- Pricing page visit: 20
- Content download: 10
- General inquiry: 5

**Urgency (0-30 points)**:
- "Need ASAP": 30
- Timeline mentioned: 20
- "Exploring": 10
- No timeline: 5

**Total Score**: 0-100
- 80-100: Hot lead - Call within 1 hour
- 60-79: Warm lead - Call within 24 hours
- 40-59: Cool lead - Email, then call
- Below 40: Nurture, don't call

### Output Format

```markdown
# Inbound Lead Analysis

**Lead**: [Name] from [Company]
**Source**: [Form/Demo Request/etc.]
**Received**: [Date/Time]
**Lead Score**: [X]/100

---

## Quick Assessment

**Priority**: HOT / WARM / COOL / NURTURE

**Recommendation**: [Call now / Call today / Email first / Add to nurture]

**Assign To**: [Rep Name] (owns [territory/industry])

**First Message**: [Suggested opening line]

---

## Lead Scoring Breakdown

**ICP Fit**: 35/40 STRONG FIT
- Company Size: 8/10 (250 employees, target is 200-500)
- Industry: 10/10 (Perfect match: B2B SaaS)
- Tech Stack: 9/10 (Using 3/4 target technologies)
- Budget: 8/10 (Funded company, likely has budget)

**Intent**: 25/30 HIGH INTENT
- Requested demo (not just content download)
- Visited pricing page 3x
- Specific use case mentioned in form

**Urgency**: 20/30 MODERATE
- Timeline: "Next quarter"
- Not immediate but real need
- Current solution expires in 60 days

**Total**: 80/100 **HOT LEAD**

---

## Lead Details

**Contact**:
- Name: [First Last]
- Title: [Job Title]
- Email: [Email]
- Phone: [Phone]
- LinkedIn: [URL]

**Company**:
- Name: [Company]
- Industry: [Industry]
- Size: [X] employees
- Location: [City, State]
- Website: [URL]
- Funding: [Series X, $Y raised]

**Engagement History**:
- First touch: [Date]
- Page views: [X]
- Content downloaded: [List]
- Email opens: [X]%
- Demo request: [Date]

---

## Qualification Questions

**Must-Ask (Critical)**:
1. "What's driving you to look at [product type] right now?"
2. "What are you currently using for [use case]?"
3. "When do you need this in place?"
4. "Who else is involved in this decision?"

**Good-to-Ask (Context)**:
5. "What would success look like?"
6. "What's your budget range?"
7. "Have you looked at other options?"

**Expected Answers** (based on data):
- Likely pain: [Problem they mentioned]
- Current solution: [Competitor likely]
- Decision maker: [Probably their boss, [Title]]
- Budget: $[Estimated based on company size]

---

## Recommended Outreach

**Call Script** (within 1 hour):
```
Hi [Name], this is [Your Name] from [Company].

I see you requested a demo about 30 minutes ago - thanks for your interest!

Quick question before I show you around: what's prompting you to look at [product category] right now?

[Listen]

Got it. And are you currently using [competitor/manual process]?

[Listen]

Perfect. Let me show you exactly how we solve that...
```

**Email Template** (if no answer):
```
Subject: Re: Demo Request - [Company Name]

Hi [Name],

Just tried calling (missed you!) about your demo request.

Quick context before we connect:

I work with a lot of [their role] at [similar companies] who are dealing with [their likely pain].

Most common questions I get:
1. [Question about pricing]
2. [Question about implementation]
3. [Question about integrations]

Happy to answer these + show you around.

When's good for a quick 15-min call?

[Your Name]
```

---

## Routing Logic

**Assign To**: [Rep Name]

**Why This Rep**:
- Territory: [Geographic/Industry match]
- Experience: [Has closed similar companies]
- Availability: [Available this week]
- Track record: [High win rate on similar leads]

**Briefing for Rep**:
> "Hot lead from [Company]. They're a [size] [industry] company using [current solution]. Requested demo specifically for [use case]. Score: 80/100. They mentioned [timeline]. Call within 1 hour."

---

## Lead Intelligence

**Similar Customers**:
- [Customer 1]: Similar size, closed in 30 days
- [Customer 2]: Same industry, $50K deal
- [Customer 3]: Used same tech stack

**Likely Objections**:
1. Price (budget concern)
2. Implementation time
3. Integration with [their tech]

**Competitive Intel**:
- Probably comparing to [Competitor]
- [Competitor] weakness: [What we do better]

---

## Next Steps

**Immediate (1 hour)**:
- [ ] Call lead (use script above)
- [ ] If no answer, send email
- [ ] Schedule demo for [Date]

**Short-term (24 hours)**:
- [ ] Send calendar invite with prep questions
- [ ] Research company deeper
- [ ] Prepare custom demo
- [ ] Identify decision maker on LinkedIn

**Follow-up**:
- [ ] Demo completed
- [ ] Proposal sent
- [ ] Create opportunity in CRM

```

Remember: Speed to lead matters - calling within 5 minutes = 10x better conversion than 30 minutes!
accessibility-auditorSkill

Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.

agent-armySkill

Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.

agent-swarm-deployerSkill

Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.

agent-team-builderSkill

Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.

agent-to-agentSkill

Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.

ai-readiness-assessmentSkill

Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.

animateSkill

Generate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.

api-documentation-writerSkill

Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.