A reusable buyer email template
Write a follow-up your buyer can put to work.
A useful sales follow-up should travel well. The person who receives it may need to share it with a budget owner, a technical reviewer, or a team that will do the work.
Those readers were not on your call. They need enough context to make a decision without asking your contact to rebuild the case.
Write for that next reader.
Build the case ↓Start with the decision they need to make.
Before drafting, ask your contact who needs to weigh in and what that person needs to decide.
The answer might be permission to run a test. It might be agreement on a requirement, a budget choice, or approval to buy. Name the actual decision. A broad request for thoughts leaves the next step unclear.
Our sales follow-up decision map helps you choose whether to send, wait, or close the loop. This template helps when there is a useful message to send.
Give them a case they can stand behind.
Include these parts:
Decision needed → Buyer’s goal → Evidence and gaps → Options and tradeoffs → Owner and next step
Use the buyer’s words for the goal. Show which facts are confirmed and which claims still need testing. If you describe the cost of waiting, confirm it with the buyer first.
Include the work the purchase would create: budget, staff time, dependencies, and any open risks. A contact should be able to share your note without having to explain away a missing cost or an unsupported claim.
Copy this template and fill it in together.
Replace the brackets with confirmed details. Mark unknowns as unknown. Remove a field only when it does not affect the decision.
Subject: Decision needed: [specific choice] for [buyer’s goal] [Name / team], We need to decide [specific choice]. This supports [goal the buyer has confirmed]. What we know: [Relevant finding, source, and date. Include any limit that changes how the finding should be read.] What we still need to check: [Assumption or unanswered question, who will check it, and when.] Options: - [Proposed option]: [expected benefit], requiring [budget and team effort]. Main risk or dependency: [detail]. - [Alternative, including keeping the current approach]: [benefit and tradeoff]. My recommendation is [option], because [reason supported above]. Next step: Can [owner] [approve, choose, validate, or resolve something specific] by [agreed date, if there is one]? If approved, [owner] will [next action]. We will review [success criteria] at [agreed point] before deciding whether to continue.
The recommendation belongs to the person sending the note. Let them change it. Do not make your buyer sound more certain than they are.
Keep the decision and main reason in the email. Link to supporting detail when it would make the message hard to scan.
Let the buyer correct the case before it travels.
Send the draft to your contact first:
Does this reflect your case? What would you change before sharing it with the people who need to decide?
Ask whether the proposed recipient is the right person. Check what can be shared. An internal concern or draft number may not belong in a wider email.
A request for corrections gives your contact a chance to make the case their own. It also gives you a chance to catch a claim they would not defend.
Ask for the work, then choose the format.
If one person can validate a requirement by email, ask them to do that. If several people need to resolve a tradeoff together, propose a meeting. Say what it will settle and who needs to attend.
A meeting request could read:
Could the budget owner and rollout lead review the two options together? The decision is whether the expected benefit justifies the cost and staff time. I’ll send the comparison first.
Use a deadline when it reflects a real decision date. Do not turn your own sales deadline into the buyer’s urgency.
Check what the message helped resolve.
After the note is shared, ask what happened. Did someone confirm a requirement, reject an assumption, choose an option, or approve the next step?
Record what remains open and who owns it. A decision to pause can be useful progress too.
Before you send, ask yourself: Could my contact forward this without repairing the facts or explaining the context?