Record what was actually discussed
Summarise the main topics, requested evidence and open questions. Distinguish a positive reaction from a commitment. Avoid writing a follow-up that assumes agreement on terms that were only mentioned. Confirm the responsible person for each action and a realistic response date. Keep confidential material within the agreed sharing process rather than attaching an entire data room to the first reply.
Make the next step useful
Provide the specific information requested and explain anything still being prepared. If another discussion is proposed, state its purpose. Keep the internal relationship record aligned with the actual status so later team members do not mistake a meeting for a completed funding arrangement. A clear follow-up respects both parties’ time by making it easy to correct misunderstandings before they become embedded in the process.
Put the guide to work
Offer recipients a clear way to correct the meeting summary. A brief invitation to confirm the recorded next steps can surface misunderstandings early. Update the internal relationship record only when the discussion supports the new status, rather than using the follow-up message itself as evidence of agreement.
Hypothetical example
An investor asks for clarification on customer activity and implementation costs. The founder’s follow-up addresses those two topics and lists the remaining evidence being prepared. It does not describe the conversation as an investment agreement simply because the meeting was encouraging.
Make it practical.
Use this checklist as you read. Checks are not stored.Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
