Create a first-touch sales outreach package for [PROSPECT AND COMPANY]. I sell [OFFER], which helps with [PROBLEM WE SOLVE]. Use only these verified prospect facts and sources: [PROSPECT RESEARCH]. My proof points I am authorized to use are [APPROVED PROOF]. The intended channel and call to action are [CHANNEL AND CTA]. First, separate facts about the prospect from hypotheses about their priorities. If the research does not support a relevant reason to contact them, say so and suggest what to research next; do not invent personalization, mutual connections, metrics, or company initiatives. Produce: 1. A prospect brief: role, likely relevant priority, trigger or evidence, and one open question. 2. Two outreach drafts in the specified channel, 80–120 words for email or 300 characters for LinkedIn. Each must have a different angle. 3. Three subject lines for email, each under 50 characters. 4. A 30-second call opener and three discovery questions tied to the stated problem. Each draft must lead with a specific, verifiable observation; connect that observation to one plausible business consequence; then make one low-friction CTA. Do not stack product features, use vague praise, claim a result without a source, or ask for 30 minutes by default. Use a short, concrete meeting ask such as a 15-minute comparison only when it fits the CTA. Before answering, check that every personalization line traces to supplied research and that the CTA asks for exactly one next action. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROSPECT AND COMPANY] | Enter the buyer’s name, role, company, and any relevant account context. | Maya Chen, Director of RevOps at Northline Logistics, a 230-person freight brokerage |
| [OFFER] | Enter the product or service you are selling in plain language. | a revenue intelligence tool that identifies stalled opportunities and missing follow-up tasks |
| [PROBLEM WE SOLVE] | Enter the business problem and the audience affected by it. | sales teams lose forecast accuracy when deal activity is recorded inconsistently across CRM and email |
| [PROSPECT RESEARCH] | Enter verified facts from public sources, conversations, account notes, or approved research. | Northline posted a RevOps analyst role mentioning Salesforce hygiene and forecast reporting. Maya shared a post about reducing manual pipeline reviews last month. |
| [APPROVED PROOF] | Enter only customer results, case studies, capabilities, and claims you are allowed to make. | A published case study says Bayline Freight Services reduced weekly pipeline-review preparation by 6 hours after rollout. We integrate with Salesforce and Microsoft 365. |
| [CHANNEL AND CTA] | Enter the outreach channel and the specific next action you want, such as a 15-minute fit check. | Email; ask whether she is open to a 15-minute comparison of their current review workflow. |
How to use
- Collect two or three verifiable account facts and paste their source context, not just a company description.
- Paste only approved product claims and customer evidence; remove results you cannot substantiate.
- Check each opening line against the research notes and remove any inference presented as fact.
- Follow up with: “Rewrite draft two for a skeptical RevOps leader who has likely seen similar tools, without adding new claims.”
Variations
Account plan
Use this before a multithreaded campaign into a strategic account.
Build a prospecting account plan for [ACCOUNT] using this verified research: [RESEARCH]. We sell [OFFER] and can substantiate [PROOF]. Identify 4–6 likely stakeholder roles, the specific issue each may own, a credible entry point, and the information still needed. Return a table plus a 30-day sequence of research and outreach actions. Do not name individuals who are not in the research or state hypotheses as facts. Check that every outreach angle maps to a stakeholder’s plausible responsibility.
Breakup email
Use this after a short outreach sequence has received no reply.
Write three respectful breakup emails to [PROSPECT] about [OFFER]. The prior messages covered [PREVIOUS ANGLES], and this is the only verified context: [RESEARCH]. Keep each under 80 words. One should offer a useful resource, one should ask for routing guidance, and one should close the loop cleanly. Include one subject line per version. Do not imply they ignored me personally or create urgency. Check that no email repeats an unsupported personalization claim.
Call research
Use this before a scheduled discovery call and need a focused question plan.
Prepare a discovery-call brief for [PROSPECT AND COMPANY]. The meeting purpose is [MEETING GOAL], and verified context is [RESEARCH]. Our relevant capabilities and limitations are [OFFER DETAILS]. Return a 20-minute agenda, five open questions ordered from current process to impact to evaluation criteria, two hypotheses labeled as hypotheses, and a concise close. Do not make product claims outside the supplied details. Check that each question could change what we recommend next.
Tips
- A job posting, earnings statement, product release, or stated initiative is stronger personalization than a generic compliment about the company.
- Keep the first message to one problem and one outcome; multiple pain points make the email read like a product catalog.
- Use customer proof only when the customer’s situation and metric are approved for external use.
- If research only supports a weak connection, research further instead of manufacturing relevance with AI.
FAQ
How much prospect research is enough for a first email?
Usually one relevant trigger, one role-specific implication, and one approved proof point are enough. More facts are useful only if they change the outreach angle.
Can AI find prospect facts for me?
It can summarize material you provide, but verify current facts from reliable sources before using them in outreach.
Should a first prospecting email include a demo link?
Only if the recipient can get value without a meeting. A focused question or small fit-check request often creates less friction.