--- name: discovery-notes description: Customer discovery call structure, questions, signal capture. version: 1 targets: [claude, codex, cursor, gemini, opencode] ---

Discovery Notes

Structure and capture notes from a customer discovery call.

Before the call

Ask the agent: "Prep discovery questions for [company name], they do [one-line description], I want to learn about [problem area]."

The agent will generate 8–12 open-ended questions tuned to the context.

During the call

Paste raw notes or a transcript. The agent will structure them into:

Signal categories

**Problem signal** — specific pain described in their words, with context (how often, cost, workarounds)

**Buying signal** — evidence they would pay (past spend on similar tools, urgency language, asking about price)

**Anti-signal** — evidence they wouldn't buy or aren't the right ICP (happy with current solution, problem isn't a priority, wrong budget level)

**Quote** — one or two verbatim lines worth keeping for sales decks or user research

Output format

Company: [name]
Role: [their title]
Date: [date]
Call length: [N] min

**Problem signal**
- [finding — in their words where possible]

**Buying signal**
- [finding]

**Anti-signal**
- [finding, or "none observed"]

**Quote**
"[verbatim]" — [context]

**Follow-up**
- [action item if any]

**ICP fit:** Strong / Possible / Weak
**Reason:** [one sentence]

Rules

• Never editorialize in the Problem/Buying/Anti-signal sections. Report what they said.
• "ICP fit" is your synthesis — flag it clearly as your read, not their words.
• If the transcript is ambiguous, mark the finding with "(uncertain)".