Plan, draft, audit, and rewrite cold outreach to strangers across sales, founder-led, investor, recruiting, partnership, research, and PR contexts. Use when launching or refreshing a cold campaign, writing one targeted email, designing a front-end offer, handling silent replies, or diagnosing deliverability, subject-line, body, cadence, or CTA problems.
Plan, draft, audit, and rewrite cold outreach to strangers across sales, founder-led, investor, recruiting, partnership, research, and PR contexts. Use when launching or refreshing a cold campaign, writing one targeted email, designing a front-end offer, handling silent replies, or diagnosing deliverability, subject-line, body, cadence, or CTA problems.
Use this skill for cold outreach to strangers: B2B sales, founder-led outreach, investor fundraising, recruiting, partnerships, customer research, podcast/PR pitches, and single high-value relationship openers.
Do not use it for newsletters, lifecycle email, onboarding email, support replies, or messages to opted-in subscribers. Those audiences have different rules.
Core idea: cold email is not one template. It is a mode router plus a drafting and audit system. Deliverability and sender trust are the floor. Mode determines research depth, subject style, body structure, CTA, cadence, and reply routing.
Reference Modules
Use this root skill by default. Load a reference module only when the request needs deeper mode-specific guidance:
references/source-map.md: source provenance, conflict resolution, and the full local research map.
references/high-volume-and-deliverability.md: volume campaigns, deliverability, list hygiene, offer tests, and back-end qualification.
references/deliverability-provider-requirement-matrix.md: provider, sender, and compliance gates for pass/blocked/manual-only readiness decisions.
references/strategic-and-single-target.md: named-account, executive, founder-to-founder, recruiting, podcast/PR, and other high-research one-recipient outreach.
references/internal-outreach-operating-system.md: internal-only blueprint for designing the full market-learning and relationship-starting operating system. Do not publish externally without review.
references/internal-skill-architecture.md: internal-only map for separating root skills, child skills, and tangential relationship-building skills. Do not publish externally without review.
references/internal-child-skill-source-development-plan.md: internal-only sourcing plan for maintaining and deepening source-backed cold email child skills. Do not publish externally without review.
references/internal-source-acquisition-queue.md: internal-only corpus status and remaining queue for experts, books, sites, videos, and official documents behind the full cold email architecture. Do not publish externally without review.
Required Inputs
Target recipient or persona: role, seniority, function, industry, company size.
Known objections, proof, customer examples, call transcript language, or case studies.
Campaign scale and desired cadence.
If essential inputs are missing, make conservative assumptions and surface the missing input in the output. Do not invent research, proof, customer names, or deliverability status.
Workflow
1. Choose Outreach Mode
Pick exactly one mode before drafting. Mode locks the research bar, CTA, and cadence.
Mode
Use When
Default Goal
Default CTA
Cadence
High-volume offer test
More than 1,000 prospects, agency-scale, broad founder outbound, market testing
Find a winning offer/reply angle
Send/share more about a useful artifact
2 touches, then recycle non-responders
Strategic-account sales
Named accounts, enterprise, partnerships, senior buyers, fewer than 100 prospects
Earn a reply or meeting
Availability ask or artifact offer
4 touches max, in-thread
Single-target relationship
One specific person: founder, creator, candidate, podcast host, customer interview, partner
Start a relationship
Send note/snapshot/sample or ask one small question
4 touches max, high research
Reply revival / objection fork
Prospect went quiet or likely has one of several objections
Convert silence into context
Reply with a number
One tactical fork after silence
Investor fundraising
Cold email to angels, VCs, accelerators, or startup investors
Start a back-and-forth
Permission to send more / deck if in lane
Short initial, slow follow-up
Never mix modes inside one campaign. If a list contains different personas or goals, split it first.
2. Verify Sender Trust
For volume mode, confirm before drafting:
SPF, DKIM, and DMARC are configured on every sending domain.
Spam complaint rate is under 0.1%.
Max 5 inboxes per domain.
Start around 30 emails per inbox per day; do not exceed 50 without evidence.
Keep roughly 250 emails per domain per day as the ceiling.
Warm inboxes for at least two weeks before sending.
Use inbox rotation.
For strategic, single-target, and investor modes, sender identity matters more than rotation:
Prefer a real named sender and a normal company domain.
Do not impersonate the founder or any other person.
For investor outreach, use a named founder address at the company domain, not info@ or a strange personal address.
If deliverability or sender trust is unverified, include a pass/fail check in the output and refuse to recommend sending at scale.
3. Segment or Research
Volume mode uses segment relevance. Each campaign should map to one persona x one narrowing signal:
Investor: thesis, portfolio, stage, geography, recent posts, categories they avoid.
Reject generic "saw your recent post", shared location/school alone, follower-count observations, AI snippets with no source, and personal facts that do not connect to the reason for outreach.
4. Select Frame and Artifact Offer
The cold ask should usually be the smallest useful yes, not a meeting. Pick one frame and one artifact.
Frame
Best For
Smallest Useful Yes
Free audit / teardown
Services, agencies, consulting
"Want me to send the teardown?"
Insight drop
You found one useful observation
"Want me to send the note?"
Sample / snapshot
Physical goods, data, SaaS, signal tools
"Can I send samples / 3 signals?"
Customer reference
You have credible adjacent proof
"Worth sending the example?"
Builder pitch
Founder-led product outreach
"Mind if I send access?"
Research ask
Customer development, journalism, market research
"Open to 15 min if I send the summary?"
Investor payload
Fundraising
"Does this fit what you like to see?"
Reply fork
Silence or objections
"Reply with the number."
Rules:
One offer, one CTA, one yes.
The artifact must be useful even if the recipient never buys.
A Loom or calendar link is not the offer.
"Worth a chat?" is not an offer.
5. Run the Packaging Pass
Draft subject and preview before the body.
Subject rules:
Should look internal, not promotional.
Use lowercase or sentence case, never Title Case.
Avoid money words, ROI claims, hype, all caps, and emojis by default.
Volume: 2-5 words, curiosity plus relevance.
Strategic: 3-8 words, often a specific noun, direct-report name, initiative, or trigger.
Single-target: can be longer only if the specificity is real and instantly recognizable to the recipient.
Reject subjects like:
"Quick question"
"Following up"
"Are you the right person?"
"[Their company] x [Your company]"
"Loved your post"
"Increase revenue by 30%"
Preview rules:
60-90 characters when possible.
Do not repeat the subject.
Drop the anchor or trigger early.
Make it feel like the email was meant for this recipient or segment.
6. Draft by Mode
High-volume offer test
Use a casual, human-sounding body:
First name on its own line; no greeting.
1-3 short lines.
One sentence describing the artifact/front-end offer.
CTA: "would that be worth sharing more?" or "want me to send it?"
Keep personalization upstream in the segment and enrichment columns. Do not fake one-to-one intimacy at volume.
Strategic-account sales
Use a formal three-part structure, 4-6 total sentences:
Who I am: name, company, team, why you are in their orbit.
Why I am relevant: persona priorities, trigger, problem, proof.
What I want: meeting or artifact, stated directly.
Use assumptive but respectful language. If the fit is strong, a calendar ask can work. If trust is low, ask to send the artifact first.
Single-target relationship
Use the full micro-anatomy:
Subject.
Preview.
Anchor line: specific, real, recent reference.
Bridge: connect anchor to why you are writing.
Offer line: useful artifact or small request.
CTA: smallest possible yes.
Optional P.S.: proof or identity-congruent aside, never a second CTA.
Bridge audit: if the personal/public hook were removed, would the reason for outreach still make sense? If yes, the hook may be decorative. Rewrite until the bridge does real work.
Reply revival / objection fork
Use a numbered response fork after silence, ambiguity, or likely objections.
Pattern:
I may be off here, but guessing one of these is true:
1. This is active now.
2. It matters, but not this quarter.
3. You solved it another way.
4. Wrong person / close the loop.
Reply with the number and I will take the right next step.
Rules:
Options must be respectful and mutually exclusive.
Include a dignified opt-out.
Do not add a second CTA.
Pre-plan the response route for each number.
Use sparingly; repeated numbered forks become gimmicky.
Investor fundraising
Goal: get the investor to understand enough to reply. Do not ask for a meeting before explaining the company.
Include, in plain language:
Problem.
Solution.
Launch status.
Traction or growth, if any.
Market size or why the opportunity can be large.
Cofounders and technical ability.
Contrarian insight: what you know that others may not believe.
Optional standard startup-format deck.
Rules:
Readable in under 60 seconds.
No jargon.
No long origin story.
No hidden company description.
Sender is a named founder at company domain.
Slow follow-up; do not hammer after confirmed opens.
7. Add Proof
Add proof only when it is relevant and true:
Peer company in the same situation.
Similar buyer role.
Specific customer result.
"I found 3 signals..." or "I pulled a snapshot..." as artifact proof.
Named mutual contact only when real.
Avoid logo walls, vague "teams like yours", unsupported claims, and proof that creates a second pitch.
8. Replace Passive Language
Audit every draft for passive or interest-based phrasing.
Replace
With
"I was hoping to..."
"I am looking to..."
"If you are interested..."
"Do either of these work?"
"Worth a chat?"
"Want me to send the note?" or "What does availability look like?"
"Is this worth exploring?"
"I can send the snapshot if useful."
"Just nudging this..."
Restate the original offer in one line
"Probably bad timing..."
Cut it
The goal is a response, not always a meeting. Yes, no, referral, objection, timing cue, and "wrong person" are all useful.
9. Plan Cadence
High-volume:
Day 0: initial offer.
Day +3: one-line restatement or alternate framing.
Stop. Recycle non-responders into a new campaign with a different opener/offer.
Strategic-account:
Day 0: initial.
Day +2: benefit-of-the-doubt follow-up, in-thread.
Day +4: ask for thoughts, in-thread.
Day +6: assumptive close-loop, in-thread.
Single-target:
4 touches max.
Keep the original thread.
Test Thursday/Friday and weekend timing for senior executives only when appropriate.
Do not write a fresh pitch in each follow-up.
Investor:
One concise initial.
One slow follow-up if relevant.
Do not send multiple quick follow-ups, especially after an open.
Reply revival:
One numbered fork after meaningful silence.
Then route based on the number or stop.
10. Route Replies
Create reply routes before sending:
Yes / interested: send artifact or offer specific times.
No: acknowledge, ask if there is a better owner only when appropriate.
Not now: ask permission to follow up at a specific future time.
We already have a solution: acknowledge and contrast the specific gap only if true.
Send info: send the artifact, not a brochure.
Wrong person: ask for the right owner.
Numbered reply: execute the matching route.
For volume campaigns, gate calendar links with a pre-call form: name, business email, phone, company site, revenue/deal-size band, and what they want help with. Quality filters on the back end.
11. Track Diagnostics
Track separately:
Metric
Diagnoses
Fix
Open rate
Subject, preview, sender reputation
Rewrite packaging; check deliverability
Reply rate
Offer, body, CTA, relevance
Tighten artifact offer; replace passive language
Positive reply rate
Offer-market fit
Re-segment; test a new pain/offer
Meeting-booked from replies
Reply handling and fit
Improve routing, proof, and qualification
Spam complaints
List quality and offer mismatch
Stop sending; clean list; narrow segment
Do not treat a single "reply rate" as the whole diagnosis.
Output Formats
When generating a campaign, return a campaign bundle:
Mode and why.
Segment or target research anchor.
Sender trust / deliverability check.
Core offer and artifact/front-end offer.
Subject line plus 1-2 alternates.
Preview text.
Email body.
Proof slot or note that proof is unavailable.
CTA and why it is the smallest useful yes.
Cadence map.
Reply routes and top objection responses.
Tracking targets.
Back-end qualification form if volume mode.
Refusal note if a precondition is not met.
When auditing, return a diagnostic report:
Mode mismatch.
Deliverability or sender-trust gap.
Subject/preview problem.
Research or segmentation gap.
Offer/artifact gap.
Passive-language hits.
Missing bridge or unearned personal hook.
Proof issue.
Cadence violation.
Reply-routing gap.
3 rewrite candidates, highest-impact first.
Guardrails
Do not send, schedule, or publish outreach without human confirmation.
Do not fabricate research, proof, mutual contacts, customer names, or metrics.
Do not use fake personalization or personal hooks without a business bridge.
Do not run mixed personas in one campaign.
Do not recommend volume sending without verified deliverability.
Do not exceed 2 touches in volume mode or 4 touches in strategic/single-target mode.
Do not use "worth a chat" as the offer.
Do not use a Loom, deck, or calendar link as the cold value unless the mode specifically supports it.
Do not leave preview text to chance.
Do not use investor meeting-first emails.
Do not stack multiple offers or CTAs.
Do not use a Calendly link in the first cold email unless the user explicitly chooses that risk.
Do not use sensitive, regulated, medical, legal, or financial claims without review.
Michael Seibel / Y Combinator: investor-mode schema, short factual fundraising payload, no meeting-first investor CTA, sender trust.
Local deep reads live under apps/web/src/content/blogs/source-analyses/. The consolidated source map and mode-specific references live in references/. Resource inventory and v2 synthesis live beside this file in docs/research/youtube-library/skill-drafts/cold-email-engagement-first-outreach/.
