Guide · Cold email

Cold email templates you can copy

The short answer

A good cold email is short, about the reader and ends with one easy ask. Below are six templates for different situations, written with {{variables}} so you can personalize them from a lead list.

Updated 6 Oct 2026 Facts link to their sources

Anatomy of a cold email

Subject: three to six words, specific to them (see subject lines).
First line: about them, not you. A reason you're writing to this person.
The point: one sentence on the problem you solve.
The ask: one small, easy-to-answer question.
Sign-off: your name. No long signature, no banner.

6 cold email templates

The direct ask · Subject: Quick question, {{first_name}}

Hi {{first_name}}, I help teams like {{company}} book meetings from outbound without adding headcount. Is that something you're working on this quarter? If not, no worries. {{sender_name}}

The trigger event · Subject: Congrats on the {{event}}

Hi {{first_name}}, Saw the news about {{event}} at {{company}}. Growth like that usually means more pipeline to build, fast. We help teams set up outbound in a week. Worth a 15-minute call? {{sender_name}}

The problem-first · Subject: {{company}}'s outbound stack

Hi {{first_name}}, Most teams we talk to pay for four or five tools just to send cold email and track replies. We replace that with one, run from your coding agent. Open to seeing how? {{sender_name}}

The referral · Subject: {{referrer}} suggested I reach out

Hi {{first_name}}, {{referrer}} mentioned you're rebuilding outbound at {{company}} and thought we should talk. Would a short call next week work? {{sender_name}}

The right-person question · Subject: Who owns outbound at {{company}}?

Hi {{first_name}}, I'm trying to find the right person at {{company}} to talk about outbound tooling. Is that you, or could you point me to them? Thanks, {{sender_name}}

The resource offer · Subject: A playbook for {{company}}

Hi {{first_name}}, We wrote up how teams like {{company}} run outbound from a coding agent: lists, sequences and replies in one loop. Want me to send it over? {{sender_name}}

Personalizing at scale

Variables only work if the data behind them is right. Before you send, check that every row has the columns your template uses: a missing {{company}} turns a personal email into an obviously broken one. Meerko previews each email per lead and skips rows with missing variables when you enroll them.

Turning templates into a sequence

A first email rarely gets the reply on its own. Pair one of these with two or three short follow-ups in the same thread: see how to follow up on a cold email. Then keep the volume where your mailbox can handle it: Gmail sending limits.

Try it in Claude Code

Add the Meerko MCP server and ask for a lead list, a sequence or a reply triage in plain language.

Set up the MCP server See pricing

FAQ

How long should a cold email be?

Short enough to read on a phone without scrolling: roughly 50 to 125 words is a good target for a first email.

Should cold emails include links or attachments?

Keep the first email plain: no attachments, and at most one link. Offer the resource and send it when they say yes.

What are template variables?

Placeholders like {{first_name}} or {{company}} that are filled in from your lead list when the email is sent.