Draft a sales follow-up that matches the actual conversation

A follow-up should make the next step easy to understand. It should not add a feature, delivery date, or discount merely to sound persuasive.

Prepare the input

Provide the call notes, approved offer facts, intended recipient role, and the action you want the reader to take. Mark tentative ideas. Remove private information that the draft does not need.

Run the workflow

First extract agreements and open questions. Then draft the message using that list. Ask for a separate commitment check so you can inspect promises before sending. This workflow prepares text; it does not send email.

Prompt to copy

Notes: [notes]. Approved facts: [facts].
First list confirmed agreements, tentative options, and open questions.
Draft a short follow-up with one clear next action.
Do not add pricing, dates, features, or guarantees absent from the sources.
After the draft, list each commitment and its supporting note.
Do not send or update a CRM.

Review a worked example

Illustrative note: “We will check whether the calendar can connect.” The draft can promise an assessment, not a completed integration. “We can launch next week” would change the agreement. Verify the recipient, attachments, factual claims, and requested next step.

Read the message as the recipient: is it clear what you are asking them to confirm? A vague “let us know your thoughts” may hide an unresolved requirement. Keep one primary request and state why it matters. Remove any implication that silence counts as approval unless that rule has actually been agreed.

Use it again

Save the structure, not customer-specific facts. Add actual feedback to the next brief. For a personal workflow see Bot; for email or CRM actions discuss the connection scope.