Cold Email

A cold email template should give you a structure to adapt, not a sentence to copy at scale. The existing SOE Knowledge article on writing cold emails focuses on why a message gets a reply. This template has a narrower job: turn that reasoning into a repeatable drafting and review workflow.

Current sales guidance emphasizes researching the recipient, avoiding generic messages, making the reason for contact relevant, keeping the ask clear, and learning from outreach performance over time. HubSpot's current guidance also stresses respecting the recipient's privacy and avoiding one-size-fits-all outreach.

Do not start by filling in the blanks.

First establish:

Recipient: [Name / role] Company: [Company] Why this person: [Why this role is relevant] Observed context: [Specific public fact, business event, role responsibility or problem signal] Problem you believe may exist: [Problem] Evidence for that belief: [Evidence] Relevant value: [What you can actually help with] Smallest reasonable next step: [Reply / permission to send something / short conversation]

If you cannot complete the context without inventing information, stop and research further.

Choose a subject that is accurate, specific and proportionate to the relationship.

Option 1: [Specific topic] Option 2: [Relevant observation] Option 3: [Clear reason for reaching out]

Avoid subject lines that imply a relationship or urgency that does not exist.

Hi [First Name],

I noticed [specific, verifiable context].

The opening should demonstrate why this message was written for this recipient rather than for a generic list.

Good context can come from a recent public announcement, product change, hiring signal, published viewpoint, event, role responsibility or another fact that is genuinely relevant.

Do not manufacture familiarity.

I’m reaching out because [specific reason connected to the context].

Keep this focused on the recipient's situation. Do not immediately turn the email into a biography of the sender.

We help [specific type of company / role] with [specific problem]. In this situation, the useful part would be [specific, credible value].

Use only claims you can substantiate.

If you have a relevant case study, credential or result that you are entitled to disclose, include the smallest useful proof:

[Verified evidence in one sentence.]

If you do not have relevant evidence, do not invent social proof. A plain, accurate explanation is better than a fabricated success story.

Would you be open to [small, specific next step]?

Examples:

• “Would it be useful if I sent the short framework we use for this?”
• “Would you be open to a 15-minute conversation next week?”
• “Is this something your team is currently looking at?”
• “Would a short example be useful?”

The ask should match the amount of trust established by the message.

If this is not a priority right now, no problem.

An easy exit makes the decision explicit and avoids pretending that a stranger owes you a response.

[Name] [Role] [Company] [Relevant link]

Keep the signature useful. Do not turn it into a catalogue of every service you offer.

Copy this structure into your working document:

Subject: [Specific and accurate subject]

Hi [First Name],

I noticed [specific context].

I’m reaching out because [specific reason this matters to them].

We help [relevant audience] with [specific problem]. [One sentence explaining the useful value.]

[Optional verified proof, only if genuinely relevant.]

Would you be open to [small next step]?

If this is not a priority right now, no problem.

Best, [Name] [Role / Company] [Relevant link]

Before sending, verify:

• [ ] I know why this person is relevant.
• [ ] My opening is based on a real fact.
• [ ] The fact is recent enough to be useful.
• [ ] I have not confused a public signal with knowledge of their internal situation.
• [ ] The problem I mention is relevant to their role or context.
• [ ] I explain why I am writing to them specifically.
• [ ] I do not use fake familiarity.
• [ ] I do not use a generic compliment as a substitute for research.
• [ ] I have not invented a customer, result, credential or testimonial.
• [ ] Every factual claim can be supported.
• [ ] The ask is small and clear.
• [ ] The recipient can decline without pressure.
• [ ] The email can be understood quickly.

HubSpot's current cold-email guidance similarly recommends researching the contact, avoiding generic outreach, following up deliberately and respecting prospect privacy.

Personalisation is not the same as inserting data fields.

Avoid:

• [First Name] inserted into an otherwise identical email
• generic congratulations on funding
• generic praise such as “I love what you're building”
• references to information that is irrelevant to the reason for contact
• personal details that feel invasive
• claims about an internal problem that the recipient has not publicly established
• fake “I was referred by...” language

A useful test is:

If the recipient's name and company were replaced, would the email still make sense?

If yes, the message probably needs more contextual work.

Before sending, complete these four sentences:

I am contacting this person because: [Reason]

I believe the relevant problem may be: [Problem]

I know this because: [Evidence]

The useful next step is: [Small ask]

If any answer is speculation disguised as fact, rewrite it.

A follow-up should add a reason to continue the conversation. It should not simply announce that you are following up.

Subject: Re: [Original subject]

Hi [First Name],

One additional thought on [specific context]:

[Useful observation, resource, question or clarification.]

Would [small next step] be useful?

Best, [Name]

Hi [First Name],

I wanted to close the loop on [specific problem].

If [problem] is not a priority right now, no worries. If it is, I can [specific next step].

Best, [Name]

Do not repeat the original pitch with different adjectives.

A cold-email sequence needs a stopping rule.

Stop or pause when:

• the recipient asks not to be contacted;
• the recipient clearly declines;
• the contact is no longer relevant;
• the message was sent to the wrong person;
• continuing would add no useful information;
• your outreach frequency would become intrusive.

For commercial outreach, also follow the applicable privacy, electronic-communications and anti-spam requirements in the relevant jurisdiction. This template does not replace legal advice.

Can the recipient understand why you wrote within the first few lines?

Is there a real connection between the recipient's context and your reason for writing?

Can you support every factual claim?

Have you removed unnecessary company history, feature lists and exaggerated outcomes?

Is the requested action clear and proportionate?

Can the recipient say no without being pressured?

Have you verified names, roles, company facts, links and any claims about recent events?

A cold-email template should become better through evidence.

Track at least:

Do not treat open rate or reply rate as a universal benchmark. Performance varies by audience, list quality, offer, channel, sender reputation, timing and measurement method. Use your own cleanly defined baseline and compare like with like.

HubSpot's startup guidance recommends targeted outreach, personalization, experimentation and CRM-based tracking rather than treating one static message as a finished system.

Research first. Write second. Ask small. Prove only what you can prove. Respect the recipient. Learn from the result.

The template is a starting structure. The research and judgment are the work.

• How do I write a cold email that gets replies? for the underlying writing principles and decision logic.
• Follow-up System for managing follow-up as a repeatable process.
• Sales Tracker for recording opportunity stage, evidence and next action.
• How do I sell without sounding salesy? for the conversation that follows a successful outreach message.

This template is an original SOE editorial synthesis. Current HubSpot guidance was used to verify practical principles around researching recipients, avoiding generic outreach, personalization, follow-up, privacy, experimentation and tracking. The completed template is intentionally narrower than SOE's existing cold-email question: it is a working drafting and quality-control tool rather than another article explaining why cold emails get replies.

No founder story, customer result, statistic, testimonial or credential is asserted by this template itself.

Related reading: \2 · \2

1. Fill it with one real situation rather than hypothetical inputs.
2. Record the evidence behind each important field.
3. Make the smallest decision the tool is designed to support.
4. Set a review date and update the tool when the evidence changes.

Good output: another person should be able to understand what was decided, why, what remains uncertain, and what happens next without needing a separate founder explanation.