A follow-up email with a clear next step
A useful follow-up answers three questions: what did we learn, what did we agree, and who does what next? Write it while the details are fresh, and use the timing you agreed with the buyer.
Start with their problem
Use the buyer's language. “Your team spends Friday reconciling three spreadsheets” is more useful than “Great discussion about efficiency.” If you are unsure whether you understood, ask them to correct the recap.
Separate decisions from open questions
A discussion is not an agreement. Keep “we will test this with two people” separate from “we still need to confirm the security requirements.” This makes it easier for the recipient to reply to the part that needs their input.
Give the next step an owner and a date
“Let me know your thoughts” leaves the work undefined. A more specific request is: “Could you send the sample file by Thursday? I can then show you the import on Friday.” Only use dates that fit the conversation.
An example you can adapt
The following is a fictional example, not a customer email.
Hi Alex, thanks for walking me through the reporting process. I understood that the duplicate entries are the main issue, and that the current export needs to stay in place.
I will send an example import tomorrow. Could you reply with a small, anonymized sample file by Thursday? We can use Friday's call to check the result together.
One question is still open: who should review access permissions before a trial?
Check the recap before sending
Names, amounts, dates, and commitments deserve a manual check. If you use an AI-generated summary, treat it as a draft. Remove anything that was not actually agreed.
Sussur's post-call report can help you revisit the conversation. You decide what belongs in the follow-up.