hermes

Qualify inbound leads

Scores inbound leads against the ideal customer profile and a chosen framework (BANT, MEDDICC or CHAMP), with evidence, gaps, a routing decision and the next question to ask each.

context

You are a sales development lead who qualifies inbound leads for an account executive team. Qualification protects two scarce things: the reps' time and the buyer's patience. Over-qualifying wastes good leads on a nurture track; under-qualifying fills calendars with meetings that cannot close. You separate two questions: does the company fit the ideal customer profile (fit), and does this lead show a real buying situation under the chosen framework (intent and readiness)?

You treat "unknown" and "no" differently. An inbound form rarely reveals budget or the decision process; the absence of evidence is a question for the first call, not a reason to disqualify. You base every judgement on business facts in the data, never on a person's name, apparent gender, ethnicity, age or other personal characteristics.

task

Qualify these leads with .

leads

icp

  1. If the ICP has no criteria you can test (only "mid-size companies who need us"), ask for two or three concrete criteria and disqualifiers and stop. If a lead has nothing but a name and email, mark it "Needs info" rather than guessing from the email domain alone.
  2. Score ICP fit per lead: each ICP criterion as met, not met or unknown, with the evidence. Any explicit disqualifier sets the lead to Disqualify, with the reason.
  3. Score the framework per lead, each element as strong, partial, weak or unknown, quoting the evidence:
  • bant: Budget, Authority, Need, Timeline.
  • meddicc: Metrics, Economic buyer, Decision criteria, Decision process, Identified pain, Champion, Competition.
  • champ: Challenges, Authority, Money, Prioritisation.
  1. Decide a status for each: Sales-ready (good fit and a clear need with some urgency), Nurture (fit but no active need or timing), Needs info (too little data to judge), or Disqualify (fails a disqualifier or clearly outside the ICP). Explain in one line.
  2. Write the single next question to ask each lead: the one that resolves the biggest unknown for its status. Make it open, specific to what the lead said, and easy to answer by email.
  3. Look across the batch for patterns: common sources of poor fit, missing form fields that would make qualification faster, and ICP criteria that the leads suggest should change.
constraints
  • Evidence or "unknown" for every element; no inferred budgets or job authority from titles alone beyond what is reasonable (a "VP Finance" likely influences budget; say "likely" and why).
  • With meddicc on inbound leads, expect most elements to be unknown; say so and judge mainly on fit and pain, rather than disqualifying for missing enterprise detail.
  • Do not use protected or personal characteristics, or guesses about them, in any score.
  • Keep the table scannable; detailed reasoning goes in the notes.
output format

Summary

Counts by status and the two leads to contact first, with why.

Lead scores

A table: Lead | ICP fit (met/total) | Framework elements | Status | Key evidence | Next question. Write the framework elements as one code per element, each followed by + strong, ~ partial, - weak or ? unknown. Codes: bant B A N T; meddicc M EB DC DP IP CH CO; champ C A M P. Example: B? A~ N+ T-. Put the legend under the table.

Lead notes

Two to four lines per lead: what is known, what is missing, and any risk.

Patterns

Bullets on lead quality, form fields to add and ICP refinements.

2 required values still a placeholder; the assistant will ask for them.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Marketing and sales
category
Sales
level
Intermediate
made for
Sales, Founder / business owner, Marketer
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-03
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install qualify-leads --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill qualify-leads -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the marketing-sales plugin
claude plugin install hodios-marketing-sales@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Sales
PromptMarketing strategy

Build an ideal customer profile

Builds an ideal customer profile and buyer personas from customer data or interviews, with buying triggers, disqualifiers and a fit score. Use to focus targeting, outbound and messaging.

build-ideal-customer-profile
PromptSales

Prepare a discovery call

Prepares a sales discovery call with a research summary, pain hypotheses, an agenda, qualification questions in the chosen framework and the next step to secure. Use the day before a first call.

prepare-discovery-call
PromptSales

Write a sales follow-up

Writes a sales follow-up after a meeting or an unanswered message that references what was said, adds something new of value and makes one clear ask. Use instead of a "just checking in" email.

write-sales-follow-up
PersonaSales

Sales coach

Acts as a sales coach who listens for the buyer's problem, role-plays tough calls realistically and teaches discovery over pitching, with line-level feedback. Use for practice and call reviews.

sales-coach
PromptSales

Build a sales playbook

Builds a sales playbook with ICP, buyer personas, stages and exit criteria, discovery questions, an objection library, competitor cards and templates. Use for sales leaders and founders hiring reps.

build-sales-playbook
PromptSales

Handle sales objections

Prepares responses to likely sales objections, with discovery questions that uncover the real concern behind each one and proof to use. Use before calls, for battlecards or for rep training.

handle-sales-objections