Systems Lab

Agent skill

outbound-email-strategy

Comprehensive outbound email strategy skill for cold outreach, email sequences, and multi-channel campaigns.

slowingSelf-containedActs undeclared1,653 words

Filed under Outbound email.

From manojbajaj95/claude-gtm-plugin · 51 skills · 92 · pushed 2026-05-18

What it does when it runs

Comprehensive outbound email strategy skill for cold outreach, email sequences, and multi-channel campaigns. Use when writing cold emails, creating outreach sequences, optimizing response rates, designing follow-up cadences, or building outbound campaigns. Covers prospecting, personalization frameworks, sequence design, subject lines, response handling, compliance, email design, HTML email templates, email layout, email marketing, newsletter design, drip campaigns, email subject lines, email headers, and cold email templates for discovery calls and SDR workflows.

Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It does act, so it runs under whatever permissions your session already grants.
Actions present in the files
writes files

Ask about outbound-email-strategy

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/manojbajaj95/claude-gtm-plugin.git /tmp/claude-gtm-plugin
git -C /tmp/claude-gtm-plugin sparse-checkout set "skills/outbound-email-strategy"
mkdir -p ~/.claude/skills/outbound-email-strategy
cp -R "/tmp/claude-gtm-plugin/skills/outbound-email-strategy/." ~/.claude/skills/outbound-email-strategy/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 51 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add manojbajaj95/claude-gtm-plugin
/plugin

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from manojbajaj95/claude-gtm-plugin/blob/3c308fa4f7879d13d3d3df394247eabf6d26b684/skills/outbound-email-strategy/SKILL.md, which is licensed MIT (repository). 1,653 words, 47 headings.

Outbound Email Strategy

Workspace Context

Read bootstrap context before asking questions: strategy/brand.md for brand, audience, offer, channels, tools, constraints, and metrics; about/me.md for personal voice; content/ideas.md and content/calendar.md for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md, and route durable learnings back to strategy/brand.md, about/me.md, or content/ideas.md.

Operating Contract

This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.

Expert outbound email execution for B2B sales and business development. Build high-response cold outreach campaigns that feel personalized and drive conversations.

Quick Start

  1. Define ICP — Who are you targeting and why?
  2. Research Prospects — Find personalization signals
  3. Craft the Hook — Lead with value, not a pitch
  4. Build Sequence — 5-7 touches across channels
  5. Handle Responses — Script for every outcome

ICP Framework

Define Your Target

ElementQuestionExample
TitleWho decides?VP of Engineering
CompanyWhat type?B2B SaaS, $1-10M ARR
PainWhat hurts?Content isn't converting
TriggerWhy NOW?Just raised funding
ProofWhy YOU?Helped similar company get result

Questions to Answer

  1. What's their job title/role?
  2. What company size/type?
  3. What industry or vertical?
  4. What pain are they experiencing RIGHT NOW?
  5. Why should THEY specifically care?

Writing Principles

Write Like a Peer, Not a Vendor

The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.

Every Sentence Must Earn Its Place

Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it.

Personalization Must Connect to the Problem

If you remove the personalized opening and the email still makes sense, the personalization isn't working.

Lead with Their World, Not Yours

"You/your" should dominate over "I/we." Don't open with who you are.

One Ask, Low Friction

Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests.


Subject Lines

Short, boring, internal-looking. The subject line's only job is to get the email opened.

Rules:

  • 2-4 words, lowercase, no punctuation
  • Should look like it came from a colleague
  • No product pitches, no urgency, no emojis

Examples:

  • "reply rates"
  • "hiring ops"
  • "Q2 forecast"

Email Sequence Framework

Sequence Types

TypeDurationBest For
Classic Cold7 emails, 2 weeksStandard outreach
Fast-Track5 emails, 1 weekQuick follow-up
Long-Play12-14 emails, 4-6 weeksEnterprise/Nurture
Event-Based3-5 emailsTrigger-specific

Sequence Flow

EmailDayGoalLengthCTA
1: Introduction0Awareness + relevance50-100wSoft ask
2: Value Proof2Establish credibility75-125wMeeting time
3: Different Angle4Alternative pain point50-75wYes/no question
4: Social Proof6Peer validation60-90wSimple reply
5: Resource Share8Give before asking40-60wSoft
6: Direct Ask10Be straightforward30-50wMeeting request
7: Breakup14Final attempt + opt-out25-40w"Close your file?"

Optimal Send Times

Tue–Thu, 10–11 AM or 2–3 PM in recipient's timezone.


Personalization Framework

4-Level System

LevelTimeWhat to Include
Tier 1 (Basic)30 secName, company, industry
Tier 2 (Researched)2-3 minNews, LinkedIn content, job postings
Tier 3 (Deep)10-15 minPodcast quotes, custom video, mutual connections

Research Sources

  • LinkedIn posts and activity
  • Company news/press releases
  • Job postings (indicate priorities)
  • Podcast appearances
  • Conference presentations
  • Mutual connections

Personalization Patterns

Content-Based:

"Your post on X resonated — especially the point about Y."

Hiring Signal:

"Noticed you're hiring X — usually means Y pain."

Company News:

"Saw the news about X. Insight: Y."

Mutual Connection:

"X mentioned you're working on Y. Made me think of Z."


Message Components

The Hook (First Line)

Make it impossible to ignore. Prove you know them.

Good:

  • "Saw your post about X — made me think of Y"
  • "Noticed you're hiring X — usually means Y"
  • "Your talk on X was Y"

Bad:

  • "Hope this email finds you well"
  • "I'm reaching out because..."
  • "I came across your profile..."

The Observation

Show you understand their world.

"Companies at your stage usually struggle with X" "Saw you're scaling — that usually creates Y"

The Value Offer

Give before you ask.

  • "Made you a quick audit"
  • "Put together resource that might help"
  • "Happy to share how we solved this for X"

The CTA

Make it natural and low-friction.

Good:

  • "Worth a look?"
  • "Interested?"
  • "Want me to send it over?"

Bad:

  • "Let's book a 30-minute call"
  • "When are you free to chat?"

Follow-Up Sequences

Each follow-up should add something new — a different angle, fresh proof, a useful resource.

Follow-Up Templates

Email 2 (Value Bump):

"Quick follow-up — additional insight. [Restate offer]."

Email 3 (Different Angle):

"New observation about their business. Thought this might be relevant."

Email 4 (Social Proof):

"Just helped similar company with result. Thought of you."

Email 5 (Break-Up):

"Closing the loop. If problem isn't a priority, no worries. Door's open."


Response Handling

Classification & SLA

Response TypeExampleSLAAction
Positive"Yes, let's talk"5 minBook meeting
Curious"Tell me more"1 hrSend proof point
Objection"Too small"Same dayHandle with framework
Timing"Not now, Q3"Same daySet reminder
Referral"Talk to CFO"1 hrReach out to referral
Hard No"Not interested"24 hrPolite close

Response Scripts

Positive Response:

"Thanks! Here's what I promised. Quick question: [qualifying question]? If [condition], [next step]."

"Not Now" Response:

"No problem. Would it make sense to reconnect in [timeframe]?"

"What's This?" Response:

"In short: [1-sentence value]. [Reoffer value]. Worth a look?"

Skeptical Response:

"Fair to ask. [Proof point]. Happy to share case study if useful."


Cold Call Scripts

Talk Track

  1. Opener: Permission + value in one line
  2. Discovery: 3 questions (current flow, pain metric, priority)
  3. Value Hits: Match pain, cite proof, propose next step
  4. Objections: Acknowledge → brief proof → micro-commit
  5. Close: Time-bound CTA + send calendar while on call

Performance Benchmarks

MetricGoodGreatExceptional
Open Rate35-45%45-55%55%+
Reply Rate3-8%8-15%15%+
Meeting Booked1-3%3-6%6%+

High Reply Rate Signals

  • Personalized opening
  • Clear value prop in first 2 sentences
  • Similar-company social proof
  • Low-friction CTA
  • Clean plain-text formatting

A/B Testing Strategy

Test Elements

ElementTest Approach
Subject linesQuestion vs. Statement
First lineHook types: signal vs. pain vs. question
CTADirect vs. soft vs. value offer
TimingMorning vs. afternoon
LengthShort (50w) vs. medium (100w)

Method

Send 50/50 split to 100 prospects. Wait 48h, measure opens + replies. Winner goes to remaining list.


Volume Guidelines

StageVolumeFocus
Testing (Week 1-2)20-50/dayFind what works
Scaling (Week 3-4)50-100/daySystematize
Cruising (Month 2+)100+/dayMaintain and iterate

Rule: Never sacrifice personalization for volume.


Compliance & Deliverability

Authentication (Required)

  • SPF: Sender Policy Framework
  • DKIM: DomainKeys Identified Mail
  • DMARC: Domain-based Message Authentication

Spam Rate Thresholds

  • Hard ceiling: 0.3% complaint rate
  • Target: <0.1% for reliable inbox

Best Practices

  • Keep sending identity stable
  • Warm up new domains gradually
  • One-click unsubscribe (List-Unsubscribe-Post)
  • Follow CAN-SPAM requirements

Common Mistakes

MistakeWhy It FailsFix
Generic opener"Hope you're well" ignoredSpecific observation
Feature dumpThey don't care yetLead with their pain
Multiple CTAsConfusionSingle clear ask
Long emailsWon't be readUnder 75 words
Same angle each emailNo reason to replyNew value per touch
No personalizationFeels like spamAdd research

The Outbound Math

Example:

  • 100 emails/day × 5 days = 500 emails/week
  • 5% response rate = 25 responses
  • 50% positive = 12-13 interested
  • 50% book calls = 6-7 calls/week
  • 20% close = 1-2 customers/week

That's 4-8 customers/month from outbound.


Related Skills

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what outbound-email-strategy does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.