// Use when writing cold outreach emails for sales, partnerships, or networking. Helps craft emails that get opened, read, and replied to by focusing on recipient value over self-promotion.
| name | cold-email-crafter |
| description | Use when writing cold outreach emails for sales, partnerships, or networking. Helps craft emails that get opened, read, and replied to by focusing on recipient value over self-promotion. |
Create cold emails that actually get responses. This skill helps you write outreach that cuts through inbox noise by leading with relevance, demonstrating research, and making reply easy.
SUBJECT LINE OPTIONS (3 variants):
1. [Personalized reference]
2. [Curiosity or question]
3. [Direct value proposition]
---
EMAIL BODY:
[OPENER - 1-2 sentences showing research]
[RELEVANCE - Why you're reaching out to THEM specifically]
[VALUE PROPOSITION - What's in it for them, not you]
[CREDIBILITY - Brief proof you can deliver]
[CTA - Single, low-friction ask]
[SIGN-OFF]
[Name]
[One-line credential]
---
FOLLOW-UP SEQUENCE:
- Follow-up 1 (Day 3): [Approach]
- Follow-up 2 (Day 7): [Approach]
- Follow-up 3 (Day 14): [Approach]
| Element | Best Practice |
|---|---|
| Subject line | 4-7 words, personalized |
| Email length | 50-125 words ideal |
| Opener | Reference specific detail |
| CTA | One question, easy to answer |
| Signature | Name + one credential |
| Follow-ups | 3-4 max, varied angles |
| Timing | Tuesday-Thursday, 8-10 AM |
Input: Write a cold email selling marketing automation services to a Series A SaaS founder
Output:
SUBJECT LINE OPTIONS:
1. Question about [Company]'s content strategy
2. [Founder name], quick marketing thought
3. Saw your ProductHunt launch—idea for you
---
Hey [Name],
Congrats on the ProductHunt launch last week—#3 in dev tools is no joke. Noticed you're ramping up content (saw the blog posts from your new content hire).
Quick thought: We've helped 3 Series A dev tools companies (including [Similar Company]) turn content into pipeline—averaging 40% increase in demo requests within 90 days.
Would it be worth a 15-minute call to see if our approach fits what you're building?
Either way, rooting for the next launch.
[Your Name]
Marketing @ [Agency]
---
FOLLOW-UP SEQUENCE:
Follow-up 1 (Day 3):
Subject: Re: Question about [Company]'s content strategy
"Bumping this up—I know Series A is chaotic. Here's the case study I mentioned: [link]. Happy to walk through the approach if helpful."
Follow-up 2 (Day 7):
Subject: Different angle
"Realized I should've led with this: [Similar Company] went from 12 to 47 demo requests/month using our system. If that's interesting, happy to share exactly how. If not, no worries—I'll stop bugging you."
Follow-up 3 (Day 14):
Subject: Should I close the loop?
"Last note from me. If content-to-pipeline isn't a priority right now, totally get it. If timing changes, happy to reconnect. Good luck with the next milestone!"
Input: Write a cold email to a podcast host proposing a guest appearance
Output:
SUBJECT LINE OPTIONS:
1. Guest idea: [Specific topic related to their show]
2. Loved ep. 147—topic pitch for you
3. [Host name], quick podcast idea
---
Hey [Name],
Just finished your episode with [Recent Guest]—the part about building in public vs. stealth mode stuck with me. Shared it with my team.
I run [Company/Role], and we've done something your audience might find useful: [Specific achievement or unique angle, e.g., "grew from $0 to $2M ARR with zero paid ads using a system most founders haven't tried"].
A few topics I could cover:
- [Topic 1 that fits their show]
- [Topic 2 that fits their show]
- [Topic 3 that fits their show]
Would any of these fit an upcoming episode? Happy to send more details on whichever interests you.
Thanks for the show—looking forward to wherever it goes.
[Your Name]
[One-line credential]
---
FOLLOW-UP SEQUENCE:
Follow-up 1 (Day 5):
Subject: Re: Guest idea
"Floating this back up. I checked your recent episodes and think [Topic 1] would pair well with what [Recent Guest] discussed. Happy to send a quick outline if that helps."
Follow-up 2 (Day 10):
Subject: One more idea
"Last thought: I could also share the exact playbook we used for [achievement]—step by step, no fluff. Your audience seems to love tactical breakdowns based on the comments. Let me know if interesting."
Follow-up 3 (Day 18):
Subject: Closing the loop
"I'll assume timing isn't right—no worries at all. If a guest spot ever makes sense down the road, I'm easy to find. Keep up the great episodes."
Input: Write a cold email to connect with a senior professional in your industry for mentorship/advice
Output:
SUBJECT LINE OPTIONS:
1. Your advice on [specific challenge]
2. [Name], quick question from a fellow [industry] person
3. Inspired by your [article/talk/post]
---
Hey [Name],
I came across your article on [specific topic]—your point about [specific insight] changed how I'm approaching [relevant situation].
I'm [brief credential, e.g., "5 years into building B2B SaaS products"] and currently navigating [specific challenge they might have experience with].
Would you be open to a 15-minute call to share how you approached [specific aspect of their experience]? I've done my research and have 3 specific questions—I won't waste your time.
Either way, appreciate the work you're putting out there.
[Your Name]
[Brief role/context]
---
FOLLOW-UP SEQUENCE:
Follow-up 1 (Day 5):
Subject: Re: Your advice on [specific challenge]
"Know you're busy—just wanted to resurface this. Happy to work around your schedule, even if it's a quick voice memo instead of a call."
Follow-up 2 (Day 12):
Subject: Happy to give before I ask
"Thought about this more—I'd love to find a way to be helpful to you too. I noticed [something you could help with based on research]. Let me know if that would be valuable."
Follow-up 3 (Day 20):
Subject: No worries either way
"Last note. I completely understand if this doesn't fit your bandwidth. If there's ever a better way to connect (conference, community, async Q&A), I'm all ears. Thanks again for the content you share."
Use when documenting architectural decisions, technology choices, or significant design decisions. Helps create structured ADRs with context, alternatives, and consequences.
Use when creating step-by-step technical tutorials, how-to guides, or learning materials. Helps structure tutorials with clear prerequisites, incremental steps, and working code examples.
Use when creating project status reports, weekly updates, or progress summaries for stakeholders. Helps structure clear, actionable reports that communicate status, blockers, and next steps without wasting readers' time.
Use when creating migration or upgrade guides for software, APIs, or frameworks. Helps structure step-by-step migration paths with breaking changes, automated tooling, and rollback procedures.
Use when drafting contract language, terms and conditions, or legal clauses for business agreements. Helps structure clear, enforceable clauses that protect both parties while remaining readable.
Use when creating executive summaries for reports, proposals, or business documents. Helps distill complex information into concise, scannable summaries that busy decision-makers can act on.