Create a cold email campaign for [OFFER] aimed at [TARGET PROSPECTS]. My goal is [CAMPAIGN GOAL]. Use only the supplied prospect research and offer facts. Do not invent mutual connections, personal details, customer results, product capabilities, or urgency. Offer and proof: [OFFER DETAILS AND PROOF] Prospect list and research: [PROSPECT DATA] Sender and relationship context: [SENDER CONTEXT] Constraints: [EMAIL CONSTRAINTS] Call-to-action options: [CTA OPTIONS] Ask up to 3 clarifying questions only if a required input is missing. Otherwise, produce: 1. A campaign brief defining the recipient's likely job-to-be-done, the specific trigger or problem the research supports, the message angle, and the conversion event. Separate verified facts from reasonable hypotheses. 2. A 3-email sequence: initial email, follow-up 1, and close-the-loop email. Each email must have two subject-line options, 70–120 words for the initial email and 45–90 words for follow-ups. Use a distinct first line based only on the prospect research, one concise value proposition, one proof point relevant to the claimed problem, and one low-friction CTA with a specific ask. 3. A personalization matrix showing which research field changes which sentence, plus a safe fallback line when that field is blank. 4. A send plan with sensible spacing, stop rules for replies/unsubscribes, and one A/B test that changes only one variable. Before answering, self-check that every personalization claim appears in the research supplied and that each email asks for one concrete next action, not a meeting by default. Keep the tone professional and plain; do not use false familiarity or pressure tactics.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [OFFER] | Describe the product or service and the outcome it can credibly help achieve. | A SOC 2 evidence-collection tool that connects to common cloud systems and reduces manual audit preparation. |
| [TARGET PROSPECTS] | Describe the role, company type, size, and geography of the people you want to reach. | Security leaders at US SaaS companies with 100–500 employees preparing for their first SOC 2 audit. |
| [CAMPAIGN GOAL] | State the measurable desired outcome, such as a discovery call, trial, or referral. | Book a 15-minute audit-readiness fit check. |
| [OFFER DETAILS AND PROOF] | Provide accurate product facts, relevant customer evidence, pricing context, and limits. | Connects AWS, GitHub, and Okta; one customer reduced evidence collection from six weeks to three, documented case study available. |
| [PROSPECT DATA] | Paste a small prospect table with names, companies, roles, and verified research notes. | Maya Chen, VP Security, Altitude Labs; careers page lists enterprise expansion. Jordan Wells, CTO, PilotDesk; posted about hiring a compliance manager. |
| [SENDER CONTEXT] | State who is sending the email and any genuine relationship, referral, or prior interaction. | Daniel Ruiz, founder at Auditline; no prior relationship or mutual contacts. |
| [EMAIL CONSTRAINTS] | Give deliverability, compliance, brand, length, or prohibited-language requirements. | US CAN-SPAM compliant, no attachments, plain text, no claims of guaranteed compliance. |
| [CTA OPTIONS] | List the next steps you can genuinely offer, such as a 15-minute fit check or a relevant resource. | 15-minute fit check, send the evidence checklist, or ask who owns SOC 2 preparation. |
How to use
- Paste the prompt with a small table of verified research notes rather than links alone.
- Read every opening line against the source note; remove anything that sounds inferred but is presented as fact.
- Send the sequence only after confirming the proof point applies to the prospect’s situation and the CTA is available.
- Follow up with: “Rewrite email 1 for this prospect using only these two verified notes: [NOTES].”
Variations
Account-based outreach
Use this for a coordinated campaign to several stakeholders at one target account.
Plan account-based outreach to [ACCOUNT] for [OFFER]. Stakeholders and verified research: [STAKEHOLDER TABLE]. Account objective or trigger: [ACCOUNT CONTEXT]. Produce a role-specific message angle for each stakeholder, a 3-touch sequence with no duplicated wording, and a contact order that avoids creating internal confusion. Use only provided facts; do not invent relationships or priorities. Each email should make one appropriate CTA from [CTA]. Flag conflicting assumptions between stakeholders. Ask up to 3 questions only if required information is missing.
LinkedIn follow-up
Use this after a prospect accepts a connection request or engages with a post.
Write a LinkedIn follow-up message for [PROSPECT] after [INTERACTION]. My offer is [OFFER], and these are verified relevance notes: [RESEARCH]. Produce two versions under 450 characters: one that starts a conversation and one that offers [RESOURCE OR CTA]. Mention the interaction only as described, without implying familiarity. Do not pitch multiple benefits or ask for a meeting unless the interaction warrants it. Flag any claim unsupported by my notes. Ask up to 3 questions only if a required input is missing.
Re-engagement email
Use this for prospects who did not reply or went quiet after an earlier conversation.
Write a re-engagement email to [PROSPECT] about [OFFER]. Prior outreach or conversation: [PRIOR CONTEXT]. New, verified reason to reconnect: [NEW REASON]. Offer proof: [PROOF]. Create a subject line and an email of 70–110 words that acknowledges the prior context without guilt or pressure, explains why the new reason may matter, and asks one clear next step: [CTA]. Do not pretend there is an update if there is not one. Flag unsupported claims and ask up to 3 questions only if a required input is missing.
Tips
- Personalize on a business signal that changes the relevance of your offer, such as an announced expansion or a new compliance hire, not a generic compliment.
- Keep the first email to one problem, one credible proof point, and one next step; a catalog of features gives the reader nothing to decide.
- Use an opt-out process and stop automated contact when someone replies, declines, or unsubscribes; legal requirements vary by location.
- Test subject lines or CTAs separately from message angle so a result tells you what actually changed.
FAQ
How much personalization is enough for a cold email?
One verified observation tied to a relevant problem is usually enough. More is useful only when it adds evidence rather than making the email feel surveillant.
Should every cold email ask for a meeting?
No. A small information request, a checklist, or confirmation of the right owner can be a more credible first CTA when relevance is uncertain.
Can AI research prospects for me?
It can organize research you provide, but verify each fact at the source before sending. Do not use unverified AI-generated personal details in outreach.