| Category | Business Development |
|---|---|
| Time to Run | 10 min |
| Difficulty | Standard |
| Output | |
| Client-Facing | Yes — goes directly to client |
You've identified someone who fits your ideal client profile. Maybe you found their LinkedIn post about a problem you solve daily. Maybe you heard them speak at a conference and recognized the operational gap they described. Maybe a mutual connection mentioned their name. Either way, they don't know you, and your first email is the only shot at earning a conversation.
Run this before any cold outreach where you have at least one specific thing to reference about the prospect. If you have nothing specific — no post, no talk, no article, no company news — go find something first. This skill doesn't work with generic inputs, and neither does cold outreach.
Copy the skill file below and save it as cold-outreach-personalizer-SKILL.md. Upload it to Claude along with the inputs listed above to generate your personalized outreach email.
---
name: cold-outreach-personalizer
description: >
Generates a personalized cold outreach email that earns a response from a prospect
who doesn't know you. Use when you've identified a prospect and found something
specific about them worth referencing.
metadata:
author: "Kathryn Brown, Practice Builders"
version: "1.0.0"
date: "2026-04-25"
---
# Cold Outreach Personalizer
Transforms research on a prospect into a concise, personalized outreach email that earns a response by demonstrating relevance — not by pitching.
**Core Principle: The first email is about them, not you. Your credibility comes from proving you did the homework, not from listing your credentials.**
## What This Skill Does
**Job 1: Convert research into a specific opening hook.** The skill takes something the prospect said, wrote, or did and turns it into a 1-2 sentence opener that proves you're not mass-emailing. This is the line that determines whether the rest gets read.
**Job 2: Build a relevance bridge.** Between "I noticed your [thing]" and "here's what I do" sits the most important sentence in the email — the one that connects their world to yours without making it about you. This skill constructs that bridge using the overlap between their stated challenge and your experience.
**Job 3: Create a low-friction response path.** The email closes with a question or micro-ask that's easy to say yes to. Not "Can we schedule a 30-minute call?" but "Would it be worth a 10-minute conversation to see if this applies to your situation?" The lower the commitment, the higher the response rate.
### Section 1: The Research Hook
Open with a specific reference to something the prospect published, said, or did. A LinkedIn post they wrote. A talk they gave. An article that quoted them. A company announcement. The more specific and recent, the better.
This matters because generic openers ("I came across your profile") are the fastest way to get archived. A specific reference signals effort and relevance.
Format: 1-2 sentences. Name the specific source and what caught your attention.
What to look for: The user should provide a concrete reference. If they only provide a name and company, push for at least one specific piece of content or activity. Without it, the outreach loses its edge.
### Section 2: The Relevance Bridge
Connect their situation to your experience — without making it a pitch. Pattern: "I've been working on [similar problem] with [similar type of client], and [one specific insight or result]." This is proof of relevance, not a capability statement.
This matters because the prospect needs to see themselves in your experience. Abstract credentials don't create that recognition. A specific parallel does.
Format: 2-3 sentences. One relevant parallel. One specific insight or result.
What to look for: Match the prospect's industry, role, or challenge to a real engagement from the user's experience. If the user doesn't have a direct match, use the closest relevant pattern.
### Section 3: The Micro-Ask
Close with a low-commitment question. Not "Can we schedule a meeting?" but something that requires only a reply. "Does this resonate with what you're seeing?" or "Would it be worth a quick conversation?" The goal is a response, not a booking.
This matters because cold outreach fails most often at the close — the ask is too big for the trust level. Match the size of the ask to the depth of the relationship (which at this point is zero).
Format: 1 sentence. A question, not a statement. Low commitment.
### Section 4: The Subject Line
Write a subject line that's specific to the prospect — reference their content, company, or situation. Avoid anything that reads like a marketing email. Pattern: "[Specific topic] — quick thought" or "Re: your [post/talk/article] on [topic]."
This matters because the subject line is the first filter. If it reads like mass outreach, the email never gets opened.
Format: Under 8 words. Specific to the prospect.
### Section 5: What to Skip / What to Watch For
**Leave alone:** Don't include your full bio, a list of services, or a link to your website in the first email. The goal is a reply, not a sale. Every additional piece of information gives the prospect a reason to defer rather than respond.
**Watch for:** If the prospect opens but doesn't reply (visible in CRM tools), they're interested but not enough to act. Wait 5-7 days and send one follow-up that adds new value — not a repeat of the first email. If they don't open at all, the subject line failed. Test a different angle.
## Quality Check (Internal — never shown to the user)
| # | Check | Fix |
|---|-------|-----|
| 1 | Does the opening reference a specific piece of content, not a generic profile observation? | Replace with a concrete post, article, talk, or event. |
| 2 | Does the relevance bridge connect their situation to a real engagement or result? | Add a specific client type and outcome. Remove abstract capability claims. |
| 3 | Is the close a low-commitment question, not a meeting request? | Rewrite as a question that requires only a reply. |
| 4 | Is the subject line specific to this prospect? | Include their name, topic, or company. Remove anything generic. |
| 5 | Is the total email under 120 words? | Cut ruthlessly. Cold outreach that runs long doesn't get read. |
**Enforcement:** Run all 5 checks. Identify the weakest element. Rewrite it. Verify the rewrite landed before presenting.
## Rules
- Total email must be under 120 words — every word earns its place or gets cut
- Never open with your credentials or company description
- The research hook must reference something specific and verifiable
- No links in the first email — links trigger spam filters and add friction
- One ask only. Don't give the prospect multiple options for responding
- Never use "I know you're busy" — it wastes the reader's time acknowledging they have no time
- Subject lines under 8 words. No clickbait. No emojis
- If the user can't provide a specific research point, advise them to find one before sending
## Output Format
**Subject:** [Under 8 words, specific to prospect]
[Prospect first name],
[1-2 sentences: The research hook. Reference their specific content, talk, or activity.]
[2-3 sentences: The relevance bridge. Connect their situation to your experience. One specific parallel, one result.]
[1 sentence: The micro-ask. A low-commitment question.]
[Your first name]
---
**Signal-to-Action Traceability:**
- **Signal:** Prospect published content on [topic] → **Do This:** Reference that specific piece in the opening line
- **Signal:** Prospect's company is in a phase you've supported before → **Do This:** Name the parallel in the relevance bridge with a specific result
- **Signal:** No prior relationship exists → **Do This:** Keep the ask to a reply-level commitment, not a calendar commitment
## What Makes This Different
Generic cold outreach tools give you templates with [FIRST NAME] merge fields and hope volume compensates for relevance. This skill forces you to earn the right to the prospect's attention by building the email around something specific to them. The result is an email that reads like it was written by someone who did the work — because it was.
---
Copyright (c) 2026 Kathryn Brown, Practice Builders
This skill is licensed for your personal and business use. You may run this skill inside your own practice and share the outputs it produces with your team and clients. "Your practice" includes employees and contractors engaged to perform work for your business under your direction — virtual assistants, operations support, bookkeepers, and similar team members.
You may not share, distribute, resell, or repackage the skill file itself — including this SKILL.md document, its prompts, frameworks, and structure — with anyone outside your practice. This includes peer practitioners, other consultants who would use it in their own client work, and anyone outside your operating team. Written permission from Kathryn Brown ([email protected]) is required for any redistribution.
This skill is provided "as is" without warranty of any kind, express or implied.