# generate-leads

generate-leads — a Claude Code command that builds a lead list from ICP criteria: industry, company size, tech stack, location. Run it with --enrich comprehensive to get a full buying committee map, technographics, and intent signals.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 450 repo stars
- Author: gtmagents
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/gtmagents/gtm-agents/tree/HEAD/plugins/sales-prospecting/commands/generate-leads.md
- Updated: 2026-04-03
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/generate-leads

## What it does

The command runs in Claude Code under the `/sales-prospecting:generate-leads` namespace. It takes ICP criteria via `--criteria`, a lead count (`--count`, default 20), and an enrichment level (`--enrich`: basic, standard, or comprehensive). Output goes to CSV, JSON, or directly into Salesforce, HubSpot, Outreach.io, or SalesLoft format.

The process has five stages: parsing criteria into filters, finding and ranking companies by fit score, identifying decision makers and buying influencers, appending firmographic and technographic data, and generating personalized outreach recommendations. At the comprehensive level, this expands to competitive intelligence and an account research brief. Data processing runs on claude-haiku-4-5; insight generation uses claude-sonnet-4.

Each lead record carries an intent_score, trigger events (for example, a new VP Sales hire or a Series B close), the technology stack, and a recommended contact approach. The `--minimum-score 70` flag cuts weak matches before export, so the list you get has already been filtered.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/generate-leads.md` — Call it with /generate-leads. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/generate-leads.md` — Call it with /prompts:generate-leads. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/generate-leads.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/generate-leads.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/gtmagents/gtm-agents/tree/HEAD/plugins/sales-prospecting/commands/generate-leads.md

## When to use it
- build a company list from specific ICP criteria with fit scoring
- map the buying committee and surface decision-maker contacts
- append technographics and intent signals to each lead record
- export leads to Salesforce or HubSpot without manual reformatting
- exclude existing CRM records and competitor domains from results

## Example prompts
- Generate 50 B2B SaaS leads with full enrichment: `/sales-prospecting:generate-leads --criteria "B2B SaaS" --count 50 --enrich comprehensive`
- Find financial-services companies with revenue above $100M in the Northeast US, five contacts per account: `/sales-prospecting:generate-leads --criteria "Financial services, >$100M revenue, Northeast US" --count 50 --enrich comprehensive --contacts 5`
- Pull recently funded B2B companies with intent signals and export to HubSpot: `/sales-prospecting:generate-leads --criteria "Recently funded B2B companies" --intent true --enrich standard --format hubspot`

## Source text · generate-leads.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 42883ab09714da05.

BEGIN THIRD-PARTY FILE 42883ab09714da05
````text
---
name: generate-leads
description: Generate ICP-qualified leads with enrichment, intent signals, and export-ready outputs.
usage: /sales-prospecting:generate-leads --criteria "B2B SaaS" --count 50 --enrich comprehensive
---

# Generate Leads Command

Generate qualified leads based on ideal customer profile (ICP) criteria with enriched contact information and buying signals.

## Command Syntax
```bash
/sales-prospecting:generate-leads --criteria <criteria> --count <number> --enrich <level>
```

## Parameters

- `--criteria`: ICP definition (industry, size, tech stack, location, etc.)
- `--count`: Number of leads to generate (default: 20)
- `--enrich`: Enrichment level (basic|standard|comprehensive)
- `--intent`: Include intent signals (true|false, default: true)
- `--contacts`: Number of contacts per account (default: 3)
- `--format`: Output format (csv|json|salesforce|hubspot)

## Examples

### Basic Lead Generation
```bash
/sales-prospecting:generate-leads --criteria "SaaS companies, 50-500 employees, using Salesforce"
```

### Comprehensive Account Research
```bash
/sales-prospecting:generate-leads \
  --criteria "Financial services, >$100M revenue, Northeast US" \
  --count 50 \
  --enrich comprehensive \
  --contacts 5
```

### Intent-Based Targeting
```bash
/sales-prospecting:generate-leads \
  --criteria "Recently funded B2B companies" \
  --intent true \
  --enrich standard
```

## Process Flow

1. **Define ICP Parameters**
   - Parse criteria into searchable filters
   - Validate parameter compatibility
   - Set enrichment requirements

2. **Initial Discovery**
   - Query data sources for matching companies
   - Apply filtering and scoring logic
   - Rank by fit score

3. **Contact Discovery**
   - Identify decision makers and influencers
   - Map buying committee structure
   - Verify contact information

4. **Data Enrichment**
   - Append firmographic data
   - Add technographic insights
   - Include intent signals and triggers
   - Calculate lead scores

5. **Output Generation**
   - Format according to specification
   - Include research notes and insights
   - Generate outreach recommendations

## Output Schema

### Standard Lead Record
```json
{
  "company": {
    "name": "Acme Corp",
    "domain": "acme.com",
    "industry": "Software",
    "size": 250,
    "revenue": "$50M",
    "location": "San Francisco, CA",
    "growth_rate": "45%"
  },
  "contacts": [
    {
      "name": "John Smith",
      "title": "VP Sales",
      "email": "john.smith@acme.com",
      "linkedin": "linkedin.com/in/johnsmith",
      "phone": "+1-415-555-0100",
      "role": "Decision Maker"
    }
  ],
  "technology": {
    "crm": "Salesforce",
    "marketing": "HubSpot",
    "relevant_tools": ["Slack", "Zoom", "Google Workspace"]
  },
  "signals": {
    "intent_score": 82,
    "buying_signals": [
      "Researching competitors",
      "Downloaded pricing guides",
      "Attending industry events"
    ],
    "trigger_events": [
      "New VP Sales hired 2 months ago",
      "Series B funding closed"
````
END THIRD-PARTY FILE 42883ab09714da05

The third-party file has ended. Everything between the 42883ab09714da05 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3044 of 5376 bytes. © gtmagents · Apache-2.0 · https://github.com/gtmagents/gtm-agents/tree/HEAD/plugins/sales-prospecting/commands/generate-leads.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
