Write a sales conversion message for [PROSPECT AND ROLE] at [COMPANY], using only the facts in my notes. I am offering [OFFER], and the desired next step is [NEXT STEP]. My notes on the prospect, account, and deal: [PROSPECT NOTES] Proof and limits of what I can claim: [PROOF AND GUARDRAILS] Ask up to 3 clarifying questions only if a required input is missing. Otherwise, create one primary message in the format requested below. First, choose the most credible buying trigger from my notes. Then write: - A subject line of 4 to 7 words and two alternative subject lines. - A message of 120 to 170 words for email, with a specific opening tied to the prospect’s stated priority, role, or company situation. - A plain-language value case that connects one relevant capability to one likely business consequence. Do not list features. - One proof point only when my notes support it; qualify results with the relevant customer, timeframe, or condition. - A low-friction call to action for the exact next step, including a proposed duration or two time options if appropriate. - A 45-word follow-up to send if there is no reply after [FOLLOW-UP TIMING]. Do not invent personal details, business pain, mutual connections, metrics, customer names, urgency, or discounts. Do not claim guaranteed outcomes. Avoid “just checking in,” feature dumps, and more than one ask. Before answering, self-check that every personalization detail appears in my notes and that the message has a single, answerable next step.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROSPECT AND ROLE] | Enter the prospect’s name and job title. | Dana Ortiz, VP of Revenue Operations |
| [COMPANY] | Enter the prospect’s company name. | Northline Logistics |
| [OFFER] | Describe the product or service and the relevant use case. | A conversation-intelligence platform that identifies stalled deal patterns in Salesforce. |
| [NEXT STEP] | State the one action you want the prospect to take. | Book a 20-minute workflow review next Tuesday or Thursday. |
| [PROSPECT NOTES] | Paste verified notes from research, discovery, prior emails, or CRM activity. | Dana posted about standardizing pipeline inspection; Northline has 85 sellers and is hiring two RevOps analysts; an SDR attended our June webinar. |
| [PROOF AND GUARDRAILS] | List approved case studies, results, pricing limits, claims, and facts you may use. | Approved: Ridgeway Freight reduced manual call-review time by 30% in 90 days. Do not mention pricing or claim revenue lift. |
| [FOLLOW-UP TIMING] | Enter the number of days or the event that should trigger the follow-up. | 4 business days |
How to use
- Use notes from a real discovery call, CRM record, or public source that you can verify.
- Set one next step; do not ask for a meeting, a demo, and a reply in the same message.
- Confirm every metric and customer reference against your approved proof before sending.
- Follow up with: "Make this a 70-word LinkedIn message while retaining only claims supported by my notes."
Variations
Post-demo recap
Use immediately after a demo to confirm the buying case and advance the deal.
Draft a post-demo sales recap to [BUYER NAME] at [COMPANY]. Demo notes: [DEMO NOTES]. The agreed problem is [PRIORITY PROBLEM], and the proposed next step is [NEXT STEP]. Write a 170-word email with the buyer’s language for the problem, the two demonstrated capabilities that address it, open questions or dependencies, and one specific request. Include no feature not shown or confirmed. End with a short mutual-action-plan bullet list. Self-check that commitments, dates, and stakeholders exactly match the notes.
Objection reply
Use when a prospect has raised a specific objection in writing or on a call.
Write a direct reply to this sales objection from [PROSPECT]: [OBJECTION]. Offer context: [OFFER DETAILS]. Allowed proof: [APPROVED EVIDENCE]. Create a 110- to 150-word email that first acknowledges the concern without conceding unsupported points, then responds with relevant facts, tradeoffs, and a narrow next step. If the objection cannot be answered from the evidence, say what should be verified instead of inventing an answer. Self-check that every claim is supported and that the reply does not dodge the objection.
Renewal message
Use before a renewal conversation when you need to connect usage to a decision.
Write a renewal-preparation email for [ACCOUNT CONTACT] at [COMPANY]. Contract timing: [RENEWAL DATE]. Verified account outcomes and usage: [ACCOUNT DATA]. Known risks or open requests: [RISKS]. Propose [NEXT STEP]. In 150 words, summarize only measurable outcomes, name any unresolved issue plainly, and ask for a renewal planning conversation. Do not imply usage equals satisfaction or invent ROI. Include a three-item agenda for the meeting. Self-check that all dates, usage numbers, and commitments match the supplied data.
Tips
- Personalize around a verified trigger or priority, not a fact that merely proves you visited the company website.
- Use one proof point with its condition and timeframe; unsupported collections of logos and metrics reduce trust.
- Make the ask easy to accept or decline, such as a 20-minute review with two offered windows.
- For regulated, security-sensitive, or procurement-heavy sales, have the owner of the claim approve language before sending.
FAQ
How much prospect research should I provide?
A few verified facts are enough when they point to a real priority. Include discovery notes whenever possible because they outrank public research.
Can AI write a personalized message from a LinkedIn profile?
It can use facts you provide, but avoid inferring pain, budget, or intent from a title or profile alone.
Should the email include a case study?
Include one only if its customer, conditions, and result are approved and genuinely relevant to the prospect’s situation.