Capture Discovery Call Notes in Fields, Not Free Text

Six fields cover most discovery calls: business problem, current process or tool, decision criteria, decision timeline, stakeholders, and agreed next step. Add estimated budget band only if the team actually uses it in qualification. Every additional required field increases the chance that representatives type filler.

Define each field in plain language and give one example. "Decision criteria" is not self-explanatory. It might mean the technical requirements, the commercial constraints, or the internal approval path. The definition should tell a representative what to write and what to leave out.

Keep the list visible in the note template. A field hidden behind a tab will be skipped.

Memory fades faster than most representatives expect. The details that matter, such as the exact wording of an objection or the name of the system being replaced, are hardest to recover an hour later. Set a capture target of one business hour after the call ends.

If the representative cannot write notes within the hour, the note should record when it was written and whether it came from memory or a transcript.

Make the note part of the call close, not an end-of-week task. Immediate capture takes less total time and produces better detail.

The most dangerous note is the one that blends observation with interpretation. "Buyer is unhappy with the current vendor" might mean the contract is ending, or it might mean the buyer made a joke about a support ticket. The next reader cannot tell.

Use a simple convention. Facts go in the field as observations with a source, such as "Buyer said the renewal is due in March". Inferences go in a separate note or a clearly labelled sentence, such as "Inference: likely evaluating alternatives before renewal". The label costs three words and prevents a guess from becoming a forecast input.

Apply the same rule to stakeholder attitudes. "Champion" is an interpretation, while "asked for the security pack and offered to circulate it" is evidence.

A discovery call without a next step is a conversation, not a sales stage. Record the action, the person who owns it, and the date it is due. If the next step belongs to the buyer, say so and put a follow-up date in the representative's task list.

Avoid vague next steps such as "follow up" or "send info". A useful next step names the artefact and the decision it enables: "Send the integration diagram and ask IT to confirm the ERP version by Thursday". That sentence can be checked, chased, and completed.

When the next step changes, update the field rather than adding another note at the bottom. The current next step should be obvious from the record, not reconstructed from a timeline of edits.

Recording tools make capture easier, but they also create a second data store with its own access and retention questions. Get consent before recording, tell the buyer where the transcript will live, and delete the raw recording when the retention period ends.

The NIST Privacy Framework treats data handling as a risk management concern rather than a compliance checkbox. Discovery recordings often contain personal information about the buyer and their colleagues, so the team should know who can access them, how long they are kept, and how they are removed.

Do not paste a full transcript into the CRM. It buries the usable fields and increases the chance that sensitive details are visible to people who do not need them. Summarise into the fields and keep the transcript in the approved system with a link.

Once a month, pull a sample of discovery calls from each representative and check the six fields. Count a field as complete only when it contains enough detail for another person to act on it. "N/A" is complete only when the buyer genuinely had no answer, and the note should say so.

For the handoff that follows discovery, see the sales meeting handoff checklist. To review a note standard, book a free consultation. The goal is to find the weak field and its cause. If the timeline field is empty across the team, the problem is probably the question, not the discipline.

Pair the sample with a short read-back. Ask a representative who did not attend the call to explain the opportunity from the note alone. If they cannot state the problem, the next step, and the main risk, the note is not complete regardless of how many fields are filled.

The template should fit on one screen and take about six minutes to complete. Start with the problem and the current process, then the criteria and timeline, then the stakeholders, then the next step. Save the narrative for a short context paragraph, not the whole page.

Put the template in the CRM as a guided section rather than a separate document. Representatives will not open a second tool between calls. A six-field form beats a note standard in a shared drive.

Review the template every quarter with the representatives who use it. Remove fields nobody reads and add one only when a downstream team can name the decision it supports.