Help me prepare a high-quality first outreach message for this prospect. Work from the information I supply and do not claim I visited a page, saw a post, know a business priority, or found a result unless it appears in my notes. If research is unavailable or uncertain, say so rather than fabricating personalization. Inputs: [MY OFFER] [IDEAL CUSTOMER AND USE CASE] [PROSPECT PROFILE] [PROSPECT SIGNALS] [PROOF AND CONSTRAINTS]
[DESIRED NEXT STEP] First, assess fit in a short table: likely operational problem, evidence from the prospect, relevant capability in my offer, and confidence level. Distinguish a direct signal from an inference. Reject weak hooks such as a generic company compliment, a job-title-only observation, or a vague claim that companies “often struggle” with something. Then produce: 1. A 75-110 word email with a specific subject line, a first sentence grounded in the strongest signal, one concise value hypothesis, one relevant proof point only if supported, and a low-friction [DESIRED NEXT STEP]. 2. A 280-character LinkedIn connection note that does not pitch aggressively. 3. A 60-90 word follow-up for 4-6 business days later that adds a useful angle without pretending the prospect read the first message. 4. A call-prep brief with three discovery questions that test the hypothesis rather than assume it is true. Do not use false urgency, “I noticed” without a real observation, generic flattery, or made-up mutual connections. Do not promise results that my proof does not support. Before answering, self-check that every personalization line is traceable to [PROSPECT SIGNALS] and that the call to action asks for one concrete action. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [MY OFFER] | Describe what you sell, who delivers it, and the specific problem it can solve. | We provide invoice-capture software that sends approved bills to QuickBooks Online for midsize construction firms. |
| [IDEAL CUSTOMER AND USE CASE] | Define the type of customer and the use case where your offer has the strongest fit. | Construction finance teams processing 300+ vendor invoices monthly across multiple job sites. |
| [PROSPECT PROFILE] | Provide the prospect’s name, role, company, industry, and any relevant company context. | Dana Ruiz, Controller at Northline Builders, a 140-person commercial contractor in Phoenix. |
| [PROSPECT SIGNALS] | List verified public signals such as a job post, initiative, quote, product change, or event. | Northline posted an accounts-payable specialist role mentioning invoice coding, job-cost allocation, and QuickBooks Online. |
| [PROOF AND CONSTRAINTS] | List approved case-study facts, boundaries on claims, and anything you must not mention. | Approved proof: one customer reduced manual invoice entry time by 22%. Do not claim integrations beyond QuickBooks Online. |
| [DESIRED NEXT STEP] | State the exact meeting, reply, resource review, or other action you want the prospect to take. | A 15-minute call next week to compare their current invoice workflow. |
How to use
- Collect a real trigger before drafting, such as a relevant job listing, stated initiative, product launch, or verified operational change.
- Paste the source wording or a precise note so the outreach can distinguish observation from inference.
- Use the fit table to discard prospects where the connection is weak before sending anything.
- Follow up with: “Give me three alternative first lines that use only the verified signal and do not mention my product.”
Variations
Account plan
Use this for a larger account with several likely stakeholders.
Build a prospecting account plan for [TARGET COMPANY] using [COMPANY SIGNALS], [MY OFFER], and [APPROVED PROOF]. Identify 3-5 likely stakeholder roles, the problem each may care about, a role-specific hypothesis, and a credible entry point. Separate observed facts from inferences. Then draft an outreach sequence for [PRIMARY CONTACT] with one 100-word email and one follow-up. Do not invent initiatives, reporting lines, budget, or tool usage. Flag research gaps and ask up to 3 questions only if required inputs are missing.
Cold call opener
Use this when you need a permission-based opening for a first call.
Write a 30-second cold-call opener for [PROSPECT ROLE] at [COMPANY] about [MY OFFER], based only on [VERIFIED SIGNAL]. Include a permission question, a one-sentence reason for the call, a problem hypothesis, and two branching responses for “not interested” and “we already have a tool.” Use [APPROVED PROOF] only if relevant. Do not imply prior contact or claim savings without evidence. End with one clear next step.
Re-engagement email
Use this for a prospect who previously evaluated you or went quiet.
Draft a re-engagement email to [PROSPECT] based on [PRIOR CONVERSATION OR TIMELINE], [CURRENT OFFER], and [NEW VERIFIED REASON TO REACH OUT]. Write 90-120 words with a direct acknowledgment of the prior context, one new relevant point, and [NEXT STEP]. Do not pretend the timing is urgent unless the notes establish it, and do not repeat a rejected pitch. Flag any unverified assumption before writing.
Tips
- A job post is a signal of a workflow or capability need, not proof that the decision-maker owns the initiative or has budget.
- Personalize around a business consequence the prospect can confirm, then use discovery questions to test it.
- One relevant proof point is stronger than a paragraph of customer logos or unsupported performance claims.
- A first message should make it easy to decline or redirect; a forced calendar link is often too much for a cold contact.
FAQ
How much prospect research should I include in a cold email?
Usually one specific, relevant observation is enough. More detail can read as surveillance unless it clearly helps the prospect understand the reason for contact.
Can AI find prospecting leads for me?
It can organize supplied research and suggest fit hypotheses. Verify source facts and contact data before acting on them.
What makes a good next step?
Ask for one small, explicit action, such as a 15-minute workflow comparison or permission to send a relevant example.