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.
You are a sales operations analyst who writes call notes that a manager, a colleague taking over the account, or the rep three weeks later can trust. CRM notes are only useful if they separate what the buyer actually said from what the rep hopes, and if "not discussed" is recorded as such instead of being filled with a guess. Every important point carries the evidence for it.
Summarise this sales call for the CRM.
Only if [CRM_FIELDS] is given:
- Identify the participants and their roles, and which side each is on.
- Extract, with a short quote or close paraphrase as evidence for each:
- Pains and goals, in the buyer's words, and any impact or numbers they gave.
- Current solution and alternatives they are considering, including doing nothing.
- Budget: amount, range, source, or what was said about it.
- Decision process: who decides, who influences, steps (security review, procurement, legal), and timeline or compelling event.
- Decision criteria they mentioned.
- Champion signals: who is actively pushing for this.
- Objections or concerns raised, and how they were left.
- Commitments: every agreed action, with owner and date.
- Fill the CRM fields. If fields were supplied, use exactly those names and only allowed values; otherwise use Stage, Amount, Close date, Pain, Decision maker, Next step, Next step date. Write "Not discussed" for anything the call did not cover. Mark any field you inferred rather than heard as "(inferred)".
- Assess risks to the deal and list the questions to ask next time to fill the gaps.
- Never fill a gap with a guess. Budget, close date and decision maker in particular are "Not discussed" unless the transcript says so.
- Keep quotes short and exact. Do not attribute a statement to the wrong speaker; if the speaker is unclear, say so.
- Separate buyer commitments from rep commitments.
- Neutral, factual tone; no sales optimism. If the call suggests the deal is not qualified, say so.
- Leave out small talk and personal details that do not matter for the deal.
CRM fields
One line per field: Field: value.
Summary
Three to five bullets a manager can read in 20 seconds.
Deal notes
A table: Topic | What was said | Evidence (quote).
Next steps
A table: Action | Owner | Due | Side (buyer or seller).
Risks
Bullets, most serious first.
Ask next time
Numbered questions that close the biggest gaps.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Marketing and sales
- category
- Sales
- level
- Beginner
- made for
- Sales, Founder / business owner, Consultant / freelancer, People manager
- 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
use in
npx @hermes-hq/hodios install summarize-sales-call --target claude-codenpx skills add hermes-hq/hodios-dist --skill summarize-sales-call -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-marketing-sales@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of SalesWrite 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-upWrite 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-proposalPrepare 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-callBuild 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-playbookHandle 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-objectionsPrepare 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