Sales discovery note standard for evidence a team can reuse
How to capture buyer language, decisions, uncertainty, and next steps without turning discovery notes into a transcript.

sales discovery note standard
Discovery notes should help the next teammate understand the buyer's situation without pretending that every detail is settled. A useful standard preserves the buyer's language, identifies the source of each important claim, and ends with the commitment that moves the conversation forward.
The note is not a performance diary or a compressed transcript. It should answer what the buyer is trying to change, why the issue matters now, how the current approach works, who participates in the decision, and what remains unknown.
Open with the decision context
Record the meeting date, participants, purpose, and stage of the conversation. Then write one sentence explaining the decision the buyer is considering. This frame lets readers distinguish early exploration from a confirmed evaluation with a defined process.
If the seller requested the meeting for a different purpose than the buyer expected, record both. That mismatch can explain shallow answers or a changed next step, and it is more useful than forcing the discussion into the planned discovery template.
Separate words, observations, and inference
Use direct quotations sparingly for language that affects messaging, urgency, or an objection. Label observed facts such as a stated deadline or named stakeholder. Put seller interpretations in a separate field so a reasonable hypothesis does not become inherited truth.
When a buyer cannot answer a question, preserve the unknown. Do not fill the gap from a public profile or another account. A visible unknown tells the next owner what to ask, while an unsupported answer can send a proposal toward the wrong problem.
Describe the current workflow
Capture the trigger, people, tools, handoffs, delay, and consequence of the buyer's present approach. Concrete sequence is more reusable than a broad label such as inefficient. It helps product, sales engineering, and delivery colleagues see where a proposed change must fit.
Include a recent example when the buyer offers one. Note whether it is typical, exceptional, or unclear. One vivid story can explain the problem while still being a poor basis for estimating its frequency across the buyer's organization.
Close with mutual commitments
Write the next action, its owner, and its date. Include any promised document, introduction, security answer, or follow-up question. A generic reminder to check in gives the next owner no way to tell whether the buyer and seller left with the same expectation.
Send a concise recap when appropriate and invite correction. If the buyer changes a material fact, update the working note while preserving the original version. The record should show how understanding improved rather than hiding every earlier assumption.
Review notes for usefulness
Managers can sample notes by asking whether another teammate could prepare the next meeting from the record. Look for repeated missing fields, unsupported conclusions, and commitments without owners. Coach the specific defect rather than demanding longer notes from everyone.
Retire fields that people complete mechanically and add a field only when a recurring handoff failure proves it is needed. A credible short standard earns better adoption than a perfect-looking form that sellers postpone until memory has faded.
Sources
- How to conduct an interview, Digital.gov. Provides a structured interview model with preparation, follow-up questions, and a clear close.
Related GTM guides
Frequently asked questions
Should discovery notes include a full transcript?
No. Keep the source recording or transcript according to policy, then write a usable note that separates buyer statements, observed facts, seller inference, unknowns, and commitments.
Who should correct a discovery note?
The meeting owner maintains the internal record. When a material recap is shared with the buyer, invite correction and update the record without erasing the earlier context.