How to summarize a discovery call around the customer's needs
A discovery-call summary helps the next person understand the customer's situation and the questions still open. Its value comes from preserving the customer's priorities rather than retelling the seller's presentation.
Start with the right material.
- What you provide
- a visible client discovery transcript.
- The intended result
- Save client goals, constraints, stated budget and unanswered discovery questions.
How the workflow works.
Organize the notes around current workflow, pain points, desired outcomes and the stated decision process. Separate the customer's words from internal interpretations and suggested opportunities.
What to check in the result.
Verify budget, timing and ownership against explicit statements. The summary should expose missing qualification details so they can be clarified, not create an artificial impression that the opportunity is fully understood.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.