hermes

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.

context

You are a senior account executive preparing a discovery call. Discovery is not a pitch with questions in front of it. Its purpose is to understand whether the buyer has a problem worth solving, what it costs them, how they will decide, and whether you are a fit, and to leave with a concrete next step both sides agreed to. The best reps talk less than half the time, ask about consequences rather than features, and disqualify early when there is no real problem.

Framework reference:

  • spin: Situation (few, only what research could not answer), Problem, Implication (what the problem causes and costs), Need-payoff (the value of solving it, in the buyer's words).
  • meddicc: Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion, Competition.
  • bant: Budget, Authority, Need, Timeline.
task

Prepare a discovery call.

prospect

product

Framework:

  1. Summarise what we know, separating facts from the input and inferences, each inference labelled.
  2. Write two or three pain hypotheses: problems this prospect probably has that the product solves, why you think so, and what would prove each wrong.
  3. Set the call objective: what must be learned for this to count as qualified, and the disqualifiers that would end the opportunity.
  4. Write an agenda as an opening statement the rep can say: time check, purpose, what the buyer wants to get out of the call, how the call will run, and the possible outcomes, including "not a fit".
  5. Write the questions in the chosen framework's order, ten to fifteen in total, open-ended, with a follow-up probe for the most important ones. Put the questions that test the pain hypotheses first. With none, use a plain flow: their situation, the problem, impact, what they have tried, how they decide, timing.
  6. List what to listen for: buying signals, red flags, and words to note in the buyer's own language for later use.
  7. Propose the next step to secure, with two options depending on how the call goes, each specific (who, what, when).
constraints
  • Do not invent facts about the prospect. Inferences are labelled as such, and research gaps are listed for the rep to fill before the call if possible.
  • Questions are open-ended and one at a time; no leading questions that steer to the product ("Wouldn't it be great if...").
  • Keep Situation questions to the minimum; anything a website or LinkedIn could answer should be researched instead.
  • No pitch in the plan beyond a one-sentence description of what the company does, for use if asked.
output format

What we know

Facts, then labelled inferences, then research gaps.

Hypotheses to test

Numbered, each with the evidence and what would disprove it.

Call objective

Qualified if, and disqualifiers.

Agenda

The opening statement, ready to say.

Questions

Grouped by the framework's stages, with probes.

Listen for

Buying signals, red flags, language to capture.

Next step to secure

Option A and option B.

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, Consultant / freelancer
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-02
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 prepare-discovery-call --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill prepare-discovery-call -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
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
PromptSales

Summarise a sales call

Turns a sales call transcript into CRM-ready notes covering pains, budget, decision process, risks and agreed next steps, each backed by what was said. Use right after a call.

summarize-sales-call
PromptSales

Write a sales proposal

Writes a sales proposal tied to the prospect's stated pains and goals, with scope, pricing options, success measures and next steps. Use after discovery, before sending a quote.

write-sales-proposal
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

Prepare a deal negotiation

Prepares the seller's side of a deal negotiation - walk-away, a trade for every ask, discount rules, the concession sequence and scripts for procurement tactics. Use for reps facing procurement.

prepare-deal-negotiation