Research workflow

Inbound lead: qualify and route

Looks up the company behind a form submission, scores it against your ideal customer with reasons, routes it to hot, nurture or not a fit, and drafts the right reply for you to approve.

RouterHuman approvalRuns in Claude Code, Codex, ChatGPT

Running it here

Every step runs here with Claude when you're signed in, and in your own agent.

  1. TriggerNew leadStart with {{lead}}, scored against {{icp}} for {{product}}.→ manual
  2. Tool / MCPLook up the companySearch for the company in {{lead}} (use the email domain if the name is vague). Find: what it does, approximate headcount, industry, location, and anything recent (funding, hiring, launches), each with a source URL. Say 'not found' rather than guess.→ web_search
  3. PromptScore against your ideal customerScore the lead in {{lead}} with {{company}} against {{icp}}: for each criterion, met / not met / unknown with one line of evidence. Then an overall score from 1 to 10 and the single biggest reason. Don't count anything you couldn't verify as met.
  4. RouterRoute the leadUsing {{score}}, pick a route.
    • HotScore 7 or more and no deal-breaker. Draft a reply under 120 words that answers their message specifically, mentions one detail from {{company}}, and offers two meeting times as placeholders [time 1] [time 2].
    • NurtureScore 4 to 6, or key facts unknown. Draft a helpful reply under 100 words with one relevant resource as [link] and one question that would settle the unknowns.
    • Not a fitScore under 4 or a deal-breaker. Draft a polite reply under 80 words that says why it isn't a match today, without criticising them, and points to an alternative if one is obvious.
  5. ApprovalApprove the replyShow {{score}} and {{reply}}. Approve, edit the reply, or reject.→ chat
  6. OutputCRM note and replyReturn a CRM note (company facts with sources, score, route, next step) and {{reply}} ready to send from your own email.→ chat

Good for

Founders and small sales teams who get demo requests or contact-form leads and want each one checked against their ideal customer, with a reply drafted for a person to send.

Last reviewed

Install as a skill

The whole workflow as one SKILL.md. Install it in Claude Code, Codex or Copilot and ask your agent to run “Inbound lead: qualify and route”.

Get the inbound-lead-qualify-and-route skill

What each step does

  1. 1. New lead (Trigger)

    Start with {{lead}}, scored against {{icp}} for {{product}}.

  2. 2. Look up the company (Tool / MCP)

    Search for the company in {{lead}} (use the email domain if the name is vague). Find: what it does, approximate headcount, industry, location, and anything recent (funding, hiring, launches), each with a source URL. Say 'not found' rather than guess.

  3. 3. Score against your ideal customer (Prompt)

    Score the lead in {{lead}} with {{company}} against {{icp}}: for each criterion, met / not met / unknown with one line of evidence. Then an overall score from 1 to 10 and the single biggest reason. Don't count anything you couldn't verify as met.

  4. 4. Route the lead (Router)

    Using {{score}}, pick a route.

    • Hot: Score 7 or more and no deal-breaker. Draft a reply under 120 words that answers their message specifically, mentions one detail from {{company}}, and offers two meeting times as placeholders [time 1] [time 2].
    • Nurture: Score 4 to 6, or key facts unknown. Draft a helpful reply under 100 words with one relevant resource as [link] and one question that would settle the unknowns.
    • Not a fit: Score under 4 or a deal-breaker. Draft a polite reply under 80 words that says why it isn't a match today, without criticising them, and points to an alternative if one is obvious.
  5. 5. Approve the reply (Approval)

    Show {{score}} and {{reply}}. Approve, edit the reply, or reject.

  6. 6. CRM note and reply (Output)

    Return a CRM note (company facts with sources, score, route, next step) and {{reply}} ready to send from your own email.

Use it in your own agent

Fill in the inputs

Name, email domain, company and whatever they wrote.

Who buys, company size, industry, the problem you solve, and deal-breakers.

Open in ClaudeOpen in ChatGPT3 inputs use their example until you fill them in.

Save as .claude/skills/inbound-lead-qualify-and-route/SKILL.md for Claude Code, or .agents/skills/inbound-lead-qualify-and-route/SKILL.md for Codex and other Agent Skills tools. Then ask: “run the Inbound lead: qualify and route workflow”.

SKILL.md
---
name: inbound-lead-qualify-and-route
description: "Looks up the company behind a form submission, scores it against your ideal customer with reasons, routes it to hot, nurture or not a fit, and drafts the right reply for you to approve. Use when asked to run the \"Inbound lead: qualify and route\" workflow."
---

# Inbound lead: qualify and route

Looks up the company behind a form submission, scores it against your ideal customer with reasons, routes it to hot, nurture or not a fit, and drafts the right reply for you to approve.

## Inputs

Ask for any of these that the user hasn't given:

- `lead` (e.g. "Name: Priya Shah
Email: priya@northwind-logistics.test
Company: Northwind Logistics
Message: We have 40 dispatchers writing the same customer updates all day. Can your tool help us standardise them?")
- `icp` (e.g. "B2B companies with 20-500 staff, a team of 10+ people writing customer-facing messages, English-speaking. Not a fit: agencies reselling, students, companies under 10 people.")
- `product` (e.g. "Acme Prompts, a shared prompt library for support and ops teams")

## Steps

Run the steps in order. Refer to saved results by name. Don't skip a step that says STOP.

1. **New lead** — Start: Start with {{lead}}, scored against {{icp}} for {{product}}.
2. **Look up the company** — Use web_search: Search for the company in {{lead}} (use the email domain if the name is vague). Find: what it does, approximate headcount, industry, location, and anything recent (funding, hiring, launches), each with a source URL. Say 'not found' rather than guess. Save the result as `company`.
3. **Score against your ideal customer** — Score the lead in {{lead}} with {{company}} against {{icp}}: for each criterion, met / not met / unknown with one line of evidence. Then an overall score from 1 to 10 and the single biggest reason. Don't count anything you couldn't verify as met. Save the result as `score`.
4. **Route the lead** — Using {{score}}, pick a route. Pick one route: Save the result as `reply`.
   - **Hot**: Score 7 or more and no deal-breaker. Draft a reply under 120 words that answers their message specifically, mentions one detail from {{company}}, and offers two meeting times as placeholders [time 1] [time 2].
   - **Nurture**: Score 4 to 6, or key facts unknown. Draft a helpful reply under 100 words with one relevant resource as [link] and one question that would settle the unknowns.
   - **Not a fit**: Score under 4 or a deal-breaker. Draft a polite reply under 80 words that says why it isn't a match today, without criticising them, and points to an alternative if one is obvious.
5. **Approve the reply** — STOP and ask the user to approve before continuing: Show {{score}} and {{reply}}. Approve, edit the reply, or reject.
6. **CRM note and reply** — Finish: Return a CRM note (company facts with sources, score, route, next step) and {{reply}} ready to send from your own email.

## Done when

Every step has run, each approval was given, and you've reported what was produced and where it was saved.

Want different steps? Open it in the workflow builder.