Cold email templates that sound like a person
These are cold email templates you paste into Claude. Each one was tested, and the real output is right below it.
1 of 9
Write a first email with one real reason to reach out
For anyone who sells to businesses. Use it when you have a real, dated reason to write to one person.
Claude
What to paste in
- The reason you're writing, with its link and date (a job post, a new location, a post they wrote)
- Their first name, job title and company
- What you sell, in one line
- One true proof point, if you have one
- Your first name and website
Idea from the prompts.chat community. My version is below.
You are my sales writer. You write cold emails that sound like a real person typed them. Who I'm writing to: [first name], [job title] at [company] The reason I'm writing now: [the fact, for example a job post for a sales rep] Link to that fact: [link] Date of that fact: [date] What I sell: [one line] One true proof point: [a real result or customer, or "none"] My first name: [first name] My website: [website] Write one cold email to this one person. 1. Subject line: their first name, a slash, then my first name. Like "Dana / Sam". 2. First line: the reason I'm writing, in plain words. Put the link on a few words from that line. Never paste a bare link. 3. Next: what I do, and why it matters to them because of that reason. 4. Add the proof point only if I gave you one. 5. Last line: one easy question they can answer in a few words. 6. Sign off with "Thanks," then my first name, then my website in lowercase. Rules: - Under 80 words, not counting the subject and sign-off. - Short sentences. Use words a 10 year old knows. Use contractions. - No dashes longer than a hyphen. No semicolons. - Never use any past form of the word see. - Don't open with "I hope this finds you well", "I wanted to reach out" or a compliment. - Don't ask for a meeting time or add a booking link in this first email. - Never make up a fact, a number or a deadline. If the reason is weak or old, tell me before you write. Give me the email, then its word count, then one line on what I should check.
What changed: We wrote our own prompt from the idea. We added one dated reason with its link, the two-names subject, an 80 word cap, one question at the end, a sign-off rule and a stop when the reason is weak. We cut the 70 to 120 word range and only use a proof point when you have a real one.
See a real example
What went in
What Claude wrote
Tested on Claude Opus 5.5, October 2026
Check before you use it
- Open the link. Make sure the post is still live and is for this exact company and city.
- Check the date. An old post is not a reason to write today.
- Email law: in the US (CAN-SPAM), add your mailing address and a way to opt out. In Canada (CASL), you need consent first, plus your contact info and an unsubscribe link.
How I'd use it
When a company posts a job for sales reps, that's my reason to write. I put the link right on the job title, so they know which post I mean. I keep it short and end on one easy question. The meeting ask can wait.
Related guide: Find companies hiring for what you do
2 of 9
Get subject lines that look like a person wrote them
For any new cold email. Use it when your subject lines look like ads.
Claude
What to paste in
- The email you plan to send
- Their first name and yours
- Whether it's a new email or a reply
From my own emails at Coda.
You are my email editor. You write subject lines that look like a person sent the email, not a company. My email: [paste] Their first name: [first name] My first name: [first name] New email or a reply: [new / reply] Do this: 1. If it's a reply, stop. Tell me to keep the subject that's already in the thread, so the thread stays together. 2. If it's new, give me the two-names subject first: their first name, a slash, my first name. Like "Dana / Sam". 3. Then give me 5 more options. Each one is 2 to 5 words, lowercase, and comes from the real reason in my email. 4. For each option, say in a few words why it fits. 5. Tell me which one you'd pick and why, in one line. Rules: - No clickbait, no fake "Re:" or "Fwd:", no all caps, no emojis. - Never promise something the email doesn't give them. - No "quick question", "following up", "checking in" or "touching base". - Never use any past form of the word see. - Don't add facts that aren't in my email. Give me a numbered list.
See a real example
What went in
What Claude wrote
Tested on Claude Opus 5.5, October 2026
Check before you use it
- Use their first name the way your CRM has it, not from a call note.
- On a reply, keep the old subject so the thread stays together.
- Read the subject and your first line together. They should match.
How I'd use it
For a new email, my subject is their first name and mine, like "Dana / Corey". That's my rule for every new thread. It reads like a note from one person to another. When they reply, I keep their subject so the whole talk stays in one thread.
3 of 9
Follow up with something useful, not "just checking in"
For the 2nd or 3rd email when they haven't written back yet.
Claude
What to paste in
- Your last email to them
- What their company does, from their website
- One useful link about their world, with a one-line summary
- What you sell, in one line
From my own emails at Coda.
You are my sales writer. You write follow-ups that give the person something useful. My last email to them: [paste] Their first name and job: [first name, job title] What their company does: [paste from their website] A useful link about their world: [link, plus one line on what it says] What I sell: [one line] My name and website: [first name, website] Write a follow-up email in 2 parts. It goes in the same thread, so no subject line. 1. The useful thing: one line on what the link says and why it matters to them. Put the link on a few words. Never paste a bare link. 2. One question about their business that a person in their job would stop and think about. Name their product, service or market. Rules: - Under 50 words, not counting the sign-off. - Don't repeat my last email. Don't mention that they didn't reply. - Never write "just checking in", "following up", "circling back" or "bumping this". - No guilt, no "sorry to bother you" and no offer to stop emailing. - Short sentences. Use words a 10 year old knows. Use contractions. - No dashes longer than a hyphen. No semicolons. - Never use any past form of the word see. - Only say what the link really says. If I didn't give you a summary, ask me for one. Sign off with "Thanks," then my first name, then my website in lowercase. Give me the email and its word count.
See a real example
What went in
What Claude wrote
Tested on Claude Opus 5.5, October 2026
Check before you use it
- Read the article yourself before you send it.
- Make sure the question names their real product or market, not a guess.
- Send it in the same thread as your last email.
How I'd use it
For one of our clients, a custom software company, my follow-ups are a link and one question. The link is an article from their site or a trade magazine that fits what the person told us on the call. Then I ask one thing about how they run their business. That's the whole email.
Related guide: Get replies by giving something useful first
4 of 9
Answer "not right now" and keep the door open
When someone writes back "not now", "maybe next quarter" or "we're good for now".
Claude
What to paste in
- Their reply, word for word
- Their first name and company
- What you sell, in one line
- Anything they said about timing
- Something useful you could send later (optional)
From my own emails at Coda.
You are my sales writer. Someone just told me "not right now". I want to keep things friendly and open, without pushing. Their first name and company: [paste] Their reply: [paste it word for word] What I sell: [one line] What they said about timing: [paste, or "nothing"] Something useful I could send later: [a guide, an example, a list, or "nothing"] My name and website: [first name, website] Write a short reply. 1. Thank them for telling me, in a few words. Don't argue with their reason. 2. If they named a time, repeat it back so we agree on it. If they didn't, ask one easy question about when is better. 3. If I gave you something useful to send, end with this shape: "I'll send over other [type of thing] relevant to [their company] as we build them." If I gave you nothing, skip this step. 4. Sign off with "Thanks," then my first name, then my website in lowercase. Rules: - Under 50 words, not counting the sign-off. - No guilt and no pressure. Don't write "no rush" or "no worries". - Never offer to stop emailing, and never say I'll leave them alone. - Short sentences. Use words a 10 year old knows. Use contractions. - No dashes longer than a hyphen. No semicolons. - Never use any past form of the word see. - Don't promise anything I didn't list. Then tell me in one line when I should write next, so I can add it to my CRM.
See a real example
What went in
What Claude wrote
Tested on Claude Opus 5.5, October 2026
Check before you use it
- Put the date they gave you in your CRM.
- Don't stack up bumps before that date. Only write if you have something useful.
- Only promise to send things you really have.
How I'd use it
When someone says not right now, I don't push. I write back short, agree on a time and put that date in Close. I don't stack up bumps in between. If something useful comes up for them, like a new example that fits, I send that.
Related guide: Learn why people say no and fix it
5 of 9
Ask to be pointed to the right person
When someone says "talk to Jane" or "that's not me", and you need a way to reach the right person.
Claude
What to paste in
- What they said, word for word
- Who you spoke to and when
- Who they pointed you to (a name or a team)
- Whether you found a real email for that person
- What you do, in one line
From my own emails at Coda.
You are my sales writer. Someone pointed me to another person at their company. I need a short email to get to the right person. What they said: [paste, word for word] The person I spoke to: [first name, job title] When we spoke: [day and how, like "phone call on Monday"] Who they pointed me to: [name and title, or just a team, like "marketing"] Did I find a real, checked email for that person? [yes, with the email / no] What I do: [one line] My name and website: [first name, website] If I found a checked email, write email A. If not, write email B. Email A, to the new person: 1. First line: say who sent me, with their full name and job title. Like "Jo Park, your ops lead, said you're the one to talk to about [topic]." 2. One line on what I do and why it fits what they said. 3. One easy question. Email B, back to the person I spoke to: 1. Remind them in one line who I am and what I do. They may not remember me. 2. Say I couldn't find a way to reach the person they named. 3. Ask them to point me to that person, or to pass my note along. Rules: - Under 60 words, not counting the sign-off. - Never guess an email address. - Only use names exactly as I gave them. If a last name is missing, use the first name only, and tell me. - Short sentences. Use words a 10 year old knows. Use contractions. - No dashes longer than a hyphen. No semicolons. - Never use any past form of the word see. - Sign off with "Thanks," then my first name, then my website in lowercase.
See a real example
What went in
What Claude wrote
Tested on Claude Opus 5.5, October 2026
Check before you use it
- Never guess an email. Find a real one, or ask.
- Make the new person their own lead in your CRM the same day.
- Check both names against your CRM, not your call notes.
How I'd use it
On our calls, people say "you want to talk to Jane" a lot. I make Jane her own lead that same day. If I can't find a real email for her, I don't guess. I write back to the person who sent me, remind them who I am, and ask them to point me to her.
Related guide: Get anyone's work email and mobile
6 of 9
Send a one-line nudge to someone who knows you
For past clients, old leads and people you've already talked to. Not for strangers.
Claude
What to paste in
- Who they are and how you know them
- The last thing you talked about (optional)
- What you do now, in a few words
From my own emails at Coda.
You are my writing helper. I want to send a one-line email to someone who already knows me. Who they are: [first name, how we know each other] The last thing we talked about: [one line, or "nothing"] What I do now: [a few words] My first name: [first name] Write 3 versions of a one-line email. Each one: 1. Starts with "Hey [their first name],". 2. Asks one casual question about whether they need help with what I do. Like "any chance you need some hands on deck for [what I do]?" 3. Ends with just my first name on the next line. Rules: - One sentence. Under 25 words. - No proof, no prices, no links and no "hope you're well". - Sound like a text to a friend, not a sales email. - Never use any past form of the word see. - No dashes longer than a hyphen. No semicolons. Then pick the one that sounds most like a real person, and say why in one line.
See a real example
What went in
What Claude wrote
Tested on Claude Opus 5.5, October 2026
Check before you use it
- Only send this to people who know you.
- Make sure nobody on your team is already talking to them.
- If they gave you a time, make sure it has passed.
How I'd use it
For past clients and old leads, I send one line. Something like "any chance you need some hands on deck for cold calling?" and just my first name. No proof, no price. They already know what I do.
7 of 9
Cut a long email to under 80 words
When your email is long, sounds like a robot or reads like a brochure.
Claude
What to paste in
- The long email
- The one thing you want them to do
- What's attached or linked
Idea from Anthropic. My version is below.
You are my email editor. My email is too long. Cut it so a busy person can read it on a phone. My email: [paste] The one thing I want them to do: [for example: reply, pick a time, read the attached file] What's attached or linked: [list, or "nothing"] Do this: 1. Find the one main point. Put it first. 2. Cut it to 3 short parts: why I'm writing, the one useful thing, and the one next step. 3. Move long detail out of the body. Point to the attachment or link instead. 4. Rewrite every line so I'd say it out loud to a friend. 5. Ask yourself: could this email go to a different company if you changed two words? If yes, tell me what's missing. Rules: - Under 80 words, not counting the sign-off. - Keep the facts, names, numbers and dates you use exactly as I wrote them. Don't add new ones. - Cut openers like "I hope this finds you well" and "I wanted to reach out". - Cut buzzwords and sales talk. - Short sentences. Use words a 10 year old knows. Use contractions. - No dashes longer than a hyphen. No semicolons. - Never use any past form of the word see. - No bold labels or bullet lists unless I had them. Give me the new email, its word count, and a short list of what you cut.
What changed: We took two checks from it: read the email out loud, and ask if it could go to a different company with two words changed. Step 5 of our prompt rewords that second check. The rest of the prompt is our own, built on my short email rules.
See a real example
What went in
What Claude wrote
Tested on Claude Opus 5.5, October 2026
Check before you use it
- Check that no fact changed in the cut.
- Make sure the file is really attached before you send.
- Read it out loud once.
How I'd use it
I keep emails short. Prospect emails run about 50 to 60 words, and client emails stay under 80. Once, one client's ten follow-up drafts ran over 150 words each, and we cut every one to under 70. Long detail goes in a PDF, because nobody reads 500 words on a phone.
Related guide: Draft every follow-up email the same day
8 of 9
End an email run without closing the door
Use it instead of a break-up email, for the last email in a run when they haven't written back.
Claude
What to paste in
- Short versions of what you've sent so far
- Their first name, job and company
- What their company does
- One useful link, with a one-line summary
- What you sell, in one line
From my own emails at Coda.
You are my sales writer. This is the last email in my run to this person. They haven't written back. I don't want a break-up email. I want to leave them with something useful and keep the door open. What I've sent so far: [paste short versions] Their first name, job and company: [paste] What their company does: [paste from their website] One useful thing: [a news link, an article or an example, plus one line on what it says] What I sell: [one line] My name and website: [first name, website] Write the email. 1. Open with the useful thing and why it matters to them. Put the link on a few words. Never paste a bare link. 2. Ask one or two short "are you doing this yet?" questions about their business. 3. End with this shape: "I'll send over other [type of thing] relevant to [their company] as we build them." 4. Sign off with "Thanks," then my first name, then my website in lowercase. Rules: - Under 70 words, not counting the sign-off. - Never say this is my last email. Never say I'll stop, leave them alone, close the loop or close their file. - Never mention that they didn't reply. No guilt and no "sorry to bother you". - Never write "no rush" or "feel free to ignore this". - Short sentences. Use words a 10 year old knows. Use contractions. - No dashes longer than a hyphen. No semicolons. - Never use any past form of the word see. - Only say what the link really says. Don't make up news, numbers or deadlines. Give me the email and its word count.
See a real example
What went in
What Claude wrote
Tested on Claude Opus 5.5, October 2026
Check before you use it
- Read the link yourself. Only say what it says.
- Put a reminder in your CRM to send them the next useful thing.
- Email law: in the US (CAN-SPAM), add your mailing address and a way to opt out. In Canada (CASL), you need consent first, plus your contact info and an unsubscribe link.
How I'd use it
I don't send break-up emails. We keep in touch with everyone we've talked to, unless they ask us to stop. So the last email in a run still gives them something useful. It ends with "I'll send over other projects relevant to [company] as we build them."
Related guide: Get replies by giving something useful first
9 of 9
Check names, links and facts before you send
Right before you send any sales email. It takes one minute.
Claude
What to paste in
- The email you're about to send
- Who it's going to
- Their name and company from your CRM
- Your call notes, if there was a call
- Today's date
From my own emails at Coda.
You are my email checker. Read my email before I send it and find mistakes. Don't rewrite it unless I ask. My email: [paste] Who it's going to: [email address] Their name and company, from my CRM: [paste] My call notes: [paste, or "none"] Today's date: [date] Check these and give me a pass or fix for each: 1. Name: does the name in the email match my CRM exactly? Trust my CRM over call notes, because notes often get names wrong. 2. Links: list every link. Tell me to open each one and make sure it goes to the right page. Flag any bare link that isn't on words. 3. Facts: list every fact, number and date. Mark each one as found in my notes, or not found. 4. Dates: flag any date that's already past, or a weekday that doesn't match the date. 5. Blanks: flag any blank like [name] I forgot to fill in. 6. Words: flag dashes longer than a hyphen, semicolons, any past form of the word see, and filler like "just checking in". 7. Length: give the word count. Flag it if it's over 80. 8. Inbox: flag it if it's going to a shared inbox like info@ or sales@ instead of a person. Rules: - Only check what's here. Never make up a problem. - Keep it short. A table is fine. End with one line: "Ready to send" or "Fix first", and the top thing to fix.
See a real example
What went in
What Claude wrote
Tested on Claude Opus 5.5, October 2026
Check before you use it
- Open every link yourself. A page can load and still be the wrong page.
- Fix the top problem first, then run the check again.
How I'd use it
Before anything goes out, I open every link and read the page. A link can load and still be the wrong page. Names come from my CRM, never from the call transcript, because transcripts get names wrong. Both have gone wrong for me before.
Don't see your work here?
Tell me what you do every day, and I'll make guides and prompts for it.
Got it. Thank you. I read every request.
Got a prompt that works? Add it here.
Feeling stuck? I can help you personally build this. Want ongoing help? Join one-on-one.
Want the calls made for you? My team at Coda Outbound does it.