"January would be ideal, if the warehouse move is finished."
In the meeting, the condition is clear. In your notes, it becomes "January start." In the CRM, it becomes an expected close. By the next forecast review, someone is asking why the deal slipped.
AI meeting notes for sales need to preserve the conditions that determine what happens next. You can shorten a conversation considerably while keeping those conditions intact. Lose them, and a concise recap can lead the whole team in the wrong direction.
One meeting, four different kinds of information
Imagine you sell inventory software to a regional distributor. You meet Sofia, the operations director, at her office. Her team needs better stock visibility, but it is also preparing to move warehouses.
She is interested. She can describe the problem clearly. You leave with a next step. Here is what that meeting supports:
| Sofia's words | What you can record | What you still need to learn |
|---|---|---|
| "Last year we spent about $40,000 on a similar project." | A reference to previous spending | Whether this project has an approved budget |
| "January would be ideal, if the warehouse move is finished." | A preferred start tied to the move | When the move is likely to finish |
| "The team won't manage another complicated rollout." | Implementation effort matters to the buyer | Which tasks her team can realistically take on |
| "Send the scope by Thursday. I'll bring it to our next finance meeting." | You send the scope; Sofia takes it to finance | The date of that meeting and what finance needs to decide |
The last line gives you something solid to act on. Prepare the scope by Thursday, and explain the work her team would have to do. You can also ask what finance needs to see. There is enough here for a useful follow-up, even though there is no purchase commitment yet.
The recap has another reader
You were in the room. Your manager, implementation colleague or future account owner may only see a short note. They need enough of the buyer's reasoning to avoid making a promise that the conversation never supported.
"Customer worried about rollout" is a start. "Warehouse move will occupy the operations team; scope needs to show which implementation tasks fall to them" tells a colleague what to do differently.
The same applies to budget. Last year's spending may help you frame a proposal, but it belongs in a different field from an approved amount for this project. Keep the currency, period and source when they affect the interpretation.
When reviewing an AI recap, spend your attention on the statements that could change a proposal or a forecast: money, dates, decision authority and commitments. Check those passages in the transcript, including who spoke. Your suggestion of a January launch should not return as Sofia's promise.
For advice on getting a usable recording in the first place, see AI note-taking for in-person meetings.
Let the buyer correct the record
A follow-up is a chance to discover a misunderstanding before your team builds a plan around it. Continuing the example, you might write:
Sofia, thanks for walking me through the stock visibility problem. I'll send the scope by Thursday, including the work your team would need to do during rollout.
I have January as your preferred start, depending on the warehouse move. When is the finance meeting, and what would help you prepare for it?
The message is short because it concentrates on the next step. It carries the timing condition forward and asks about the missing piece. There is no need to recite every note back to Sofia or turn an exploratory meeting into a declaration of mutual enthusiasm.
If you use an AI assistant to draft the email, give it reviewed notes and a narrow instruction:
Draft a short follow-up from these notes. Include the next steps we agreed to and any conditions attached to them. Ask about the most important missing detail. Flag any sentence in the draft that depends on an assumption I need to check.
Read it before sending. A well-written email can still assign the wrong owner, invent a date or imply that a budget has been approved.
Pick up the deal where the buyer left it
The next conversation may happen a month later, over coffee, after two emails and a conference encounter. You need to know whether the warehouse move is still the obstacle or whether something changed in between.
You can use the Draki app to record a meeting without a bracelet. For days spent moving between customers, the bracelet keeps capture close at hand, with recording you can turn on or off as needed. Draki sends recorded audio through its server to OpenAI over Wi-Fi after your permission. Public Draki does not automatically recognize speakers.
Draki offers a custom MCP connection for AI assistants that support remote MCP. Availability depends on the assistant and your account settings. If you authorize access, your assistant can retrieve the conversation text and context you share. Before meeting Sofia again, you can ask it to find her latest comments about the move, implementation workload and finance review, with the dates attached. That helps you prepare from the most recent discussion while keeping the earlier history available.
The connection is read-only: it retrieves authorized text for you to work with. Your chosen assistant processes that shared text under its own policies. You review the follow-up, send it and update the CRM. The ChatGPT and Claude connection guide explains how to connect an assistant.
A missing finance decision then becomes a question for Sofia, rather than a status silently filled in by the recap. If this is the kind of conversation history you want to keep, join the Draki waitlist.
FAQ
- Can AI take notes during an in-person sales meeting?
- An AI note-taking system can capture and summarize a supported in-person recording. Agree on recording with the participants, check the recording setup and review consequential details against the source before using the notes.
- What should AI sales meeting notes include?
- Include the customer's problem, relevant constraints, budget status, decision process, timing, objections and explicit next steps. Keep seller interpretations separate from customer statements, and preserve conditions attached to commitments.
- Can Draki automatically update my CRM after a meeting?
- Draki's optional MCP connection retrieves conversation text and context you authorize for sharing. It is read-only and cannot write CRM records or send emails. Review the retrieved material, then update your CRM or prepare a message in the tools you use for those tasks.
- How do I use AI to draft a sales follow-up without overstating the meeting?
- Provide verified notes, ask the assistant to preserve conditions and prohibit invented agreements or deadlines. Have it identify unsupported claims before drafting, then review the message yourself before sending.
Written by Darijan Ducic
Draki for iPhone
