---
name: discovery-call-notes
description: >-
  Turns raw discovery-call notes into pains, the current stack, the cost of the
  status quo, and a next step. Use when the user asks to write up a sales call
  or discovery notes.
license: Apache-2.0
metadata:
  category: sales-gtm
  tags: discovery, sales
  added: "2026-11-05"
  featured: false
---

# Discovery call notes

Turn messy call notes into a record the next person can use. Attribute statements to the buyer. Do not upgrade a maybe into a requirement.

## Steps

1. Read the notes and the account name. If it is unclear who said a line, mark the speaker as unknown.
2. List pains in the buyer's words, then the current tool or process they use for that pain.
3. Record the cost of the status quo only when the buyer stated a number, a delay, or a failure. Otherwise write "not stated."
4. Record the next step, the owner, and the date if one was agreed. If none was agreed, write that no next step was set.
5. Validate the notes by removing any pain, budget, or timeline you cannot point to in the raw notes.

## Example

User notes: "Asha said reviews of new skills take a day because nothing is linted. They use a shared doc. No budget discussed. She will send two sample skills on Friday."

Agent: Pain — reviews take a day because skills are not linted (Asha). Current stack — a shared doc. Cost — a day of review time, no money figure stated. Next step — Asha sends two sample skills on Friday. Budget was not discussed.

## Boundaries

Do not invent a champion, a budget, or a close date. Do not store a personal detail that is irrelevant to the deal.