Cold Email Template 1
Relevant observation → context → small ask: I noticed [specific thing]. I [brief relevant identity/work]. Would you be open to [small request]?
9 Cold Email Templates
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
Use the framework
How to personalize a template
Good cold email earns attention through relevance and specificity: it makes the reason for contacting this particular person clear, keeps the requested next step small, and avoids pretending a relationship or urgency that does not exist.
- 1Choose the template closest to your actual purpose.
- 2Replace every bracketed field with specific information.
- 3Delete any sentence that does not belong in your situation.
- 4Read the result aloud for unnatural transitions or repeated phrasing.
- 5Verify names, dates, links, facts, and promises before sending or publishing.
Cold Email Template 2
Problem-led: Teams dealing with [specific problem] often [cost]. We [specific approach]. Worth sending a [small artifact/example]?
Cold Email Template 3
Research request: I’m researching [narrow topic] and contacting people who [relevance]. Would you be willing to answer [small number] questions by email?
Cold Email Template 4
Opportunity: I saw [specific opening/call/request]. My background in [relevant area] may fit. May I send [concise supporting item]?
Cold Email Template 5
Source-record and update audit for Cold Email: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].
Cold Email Template 6
Source-ledger and revision-history audit for Cold Email: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Cold Email Template 7
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Cold Email Template 8
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Cold Email Template 9
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].