Stats
Actions
Tags
From Claudient — SDR
- You are building a 4-email outbound campaign with specific timing (Day 0, 3, 7, 12) - You need subject line formulas that avoid spam filters while driving opens - You are designing branching logic:
How this skill is triggered — by the user, by Claude, or both
Slash command
/claudient-sdr:cold-email-sequenceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- You are building a 4-email outbound campaign with specific timing (Day 0, 3, 7, 12)
The sequence is built on progressive context-stacking: each email assumes the previous was read but unanswered. Subject line formulas and body copy are designed to move the needle on open rates, reply rates, and psychological receptivity.
Purpose: Establish relevance with zero ask. Trigger signal or personalization hook only.
Subject Line Formula:
[specific fact about their business] + [question marker]hiring 12 engineers this quarter? | moving to [region]? | saw the [product] launchBody Copy Rules:
Template:
[Name],
[Trigger signal: specific, fact-based observation about their business].
Quick question: [one question that shows you read their context and care about the answer].
[Your name]
Word Count Check: Count every word in the body. Stop before hitting 61.
Purpose: Connect their likely pain to concrete KPI impact. One proof point. One CTA.
Subject Line Formula:
re: [original subject] (reply-threading for deliverability; technically a re- subject)[metric/outcome] at [similar company type]Body Copy Rules:
Template:
[Name],
[Pain statement: what's probably costing them time/money/growth].
[Similar company name] saw [specific metric improvement] after [brief intervention description].
[One question linking their pain to next step].
[Your name]
Proof Point Specificity: Use real benchmarks. "We helped a [size]-person [industry] team reduce [metric] by [%]" is stronger than "typical companies see results."
Purpose: Remove ego. Assume they own the problem OR someone else does.
Subject Line Formula:
re: [original subject] (threading)might be on someone else's desk?Body Copy Rules:
Template:
[Name],
Not sure if [specific problem/initiative] is on your radar right now, or if [peer/function] owns this at [company].
[One value statement or context reminder].
Happy to follow up with them directly, or circle back in [timeframe]. What makes most sense?
[Your name]
Purpose: Leave a gift, no ask. Often generates unexpected replies (curiosity, guilt, or genuine interest).
Subject Line Formula:
re: [original subject] (threading)last note: [insight/resource type]Body Copy Rules:
Template:
[Name],
I'll stop reaching out after this—but thought you might find [specific resource type] valuable regardless of timing.
[Brief insight or why this resource matters to their context].
[Link or description of resource].
All the best,
[Your name]
Gift Ideas: Case study, benchmark report, template, article, integrations guide, competitor analysis, hiring rubric, etc.
If the prospect replies at any point in the sequence:
replied_email_[n] (e.g., replied_email_2)If the prospect does not reply to any of the 4 emails:
Park indefinitely (remove from active nurture) if:
Spam Triggers to Avoid (will tank deliverability):
re: [fresh angle])High-Performing Patterns:
| Personalization Level | Examples | |
|---|---|---|
| Email 1 | High: Individual signal | "Just saw you hired 12 engineers" / "Caught your podcast on [topic]" |
| Email 2 | Medium-High: Role + company context | "Finance teams at [industry] usually see [metric] improve after" |
| Email 3 | Medium: Assume role or delegate | "If [role] handles [initiative] at [company]..." |
| Email 4 | Low: Gift is universally relevant | Resource/insight applies broadly |
| Metric | Benchmark Range | Healthy |
|---|---|---|
| Email 1 Open Rate | 35–50% | 40%+ with strong signal |
| Email 2 Open Rate | 20–35% | 25%+ |
| Email 3 Open Rate | 15–25% | 20%+ |
| Email 4 Open Rate | 10–20% | 15%+ |
| Cumulative Reply Rate (All 4) | 5–12% | 8%+ for B2B SaaS |
| Cost per Reply (including time) | $50–200 | Depends on load, ICP |
Conversion to Conversation (reply → first call):
START: Prospect added to list
|
+→ Email 1 sent (Day 0)
|
+→ Reply received? YES → EXIT sequence, tag "replied_email_1", hand to sales
|
+→ No reply → wait 3 days
|
+→ Email 2 sent (Day 3)
|
+→ Reply received? YES → EXIT sequence, tag "replied_email_2", hand to sales
|
+→ No reply → wait 4 days
|
+→ Email 3 sent (Day 7)
|
+→ Reply received? YES → EXIT sequence, tag "replied_email_3", hand to sales
|
+→ No reply → wait 5 days
|
+→ Email 4 sent (Day 12)
|
+→ Reply received? YES → EXIT sequence, tag "replied_email_4", hand to sales
|
+→ No reply → PARK for 60 days
|
+→ Day 72: Monitor for new signal
|
+→ New signal detected? → Send Reactivation Email with fresh subject
|
+→ No signal after 60 days? → Move to low-priority nurture or remove
Use only if NEW signal is detected.
Subject Line Formula:
saw [announcement/change] at [company] (fresh subject, no "re:")saw the new Chief Revenue Officer hire | caught the Series A announcementBody:
[Name],
Saw that [specific new signal: hiring, launch, funding, partnership, etc.] at [company].
Thought it might be relevant timing to revisit [original pain/opportunity], especially given [how new signal connects to original context].
Would be worth a brief chat?
[Your name]
Rules:
Company Context: Mid-market SaaS company, Series B funding, 3-month-old VP Sales hire, scaling sales team
Email 1: The Hook (Day 0)
Subject: hired your third sales manager?
Body:
Marcus,
Saw you just promoted your second sales manager. Curious: are you planning a third hire before year-end, or are you hitting hiring cap?
The reason I ask—most VPs in your stage are getting bottlenecked on pipeline velocity, not headcount.
[Your name]
Word count: 48 words ✓
Email 2: The Pain (Day 3)
Subject: re: hired your third sales manager?
Body:
Marcus,
Most VP Sales at your stage see pipeline velocity as the #1 blocker to hiring more AEs without losing quality.
Notion saw a 40% increase in pipeline quality once they standardized their discovery process and started tracking leading indicators instead of lag indicators.
Worth spending 15 minutes exploring whether you're measuring the right metrics?
[Your name]
Word count: 65 words ✓
Email 3: The Delegation Ask (Day 7)
Subject: re: hired your third sales manager?
Body:
Marcus,
Not sure if ops/analytics own this at [company], or if it's still on your plate with the new VP role.
Either way, most teams benefit from having a clear view of which metrics actually predict deal closure.
Happy to loop in whoever owns RevOps, or circle back with you when things settle.
[Your name]
Word count: 61 words ✓
Email 4: The Break-Up (Day 12)
Subject: re: hired your third sales manager?
Body:
Marcus,
I'll stop reaching out after this—but thought you might find this useful regardless: we put together a "Sales Leading Indicators Checklist" (used by Notion, Figma, Airtable), focused on metrics that actually predict early-stage growth.
It's a one-pager, no pitch.
[Link to resource]
All the best,
[Your name]
Word count: 59 words ✓
Reactivation Signal (Day 72+): New signal detected: "Just saw Marcus's company raised Series C"
Reactivation Email:
Subject: caught the Series C announcement
Body:
Marcus,
Just saw you closed the Series C. Congratulations.
Series C is exactly the moment where pipeline quality becomes make-or-break. Most teams either accelerate hiring and lose the sales floor, or move too slow and miss growth windows.
Worth a brief call to talk about how you're thinking about scaling without losing margin?
[Your name]
Word count: 58 words ✓
Company Context: Regional manufacturing company, 3-year growth from $50M to $120M ARR, recently promoted Finance Director, scaling finance team
Email 1: The Hook (Day 0)
Subject: how are you tracking cash position with supply chain volatility?
Body:
Jennifer,
With commodity prices moving the way they are, I'm curious: are you rebuilding cash flow forecasts weekly, monthly, or are you still on the old cadence?
Most finance teams your size are getting surprised by working capital swings they could've flagged 30 days earlier.
[Your name]
Word count: 57 words ✓
Email 2: The Pain (Day 3)
Subject: re: how are you tracking cash position with supply chain volatility?
Body:
Jennifer,
Finance teams at distributors your size typically waste 15–20 hours a week rebuilding cash forecasts manually, and they still miss signals.
A regional distributor we worked with reduced forecast error from 18% to 5% once they automated supplier payment and inventory lookback.
Would be worth seeing if the same approach works for you?
[Your name]
Word count: 62 words ✓
Email 3: The Delegation Ask (Day 7)
Subject: re: how are you tracking cash position with supply chain volatility?
Body:
Jennifer,
Not sure if this sits with your supply chain partner or if you're running point on cash forecasting at [company].
Either way, most teams benefit from having supply chain and finance sync on inventory and payables once a week.
Happy to connect with your supply chain lead, or follow up when you have 15 minutes.
[Your name]
Word count: 64 words ✓
Email 4: The Break-Up (Day 12)
Subject: last note: cash flow template for supply-constrained teams
Body:
Jennifer,
I'll stop reaching out after this, but I put together a cash flow forecast template built specifically for distribution teams managing volatile supplier payment windows.
It's built for Excel, no setup needed.
Some teams have found it useful as a starting point even if they don't use our full system.
[Link to template]
All the best,
[Your name]
Word count: 62 words ✓
Reactivation Signal (Day 72+): New signal detected: "Saw Jennifer's company received a major contract win (industry news)"
Reactivation Email:
Subject: saw the new [major client] contract
Body:
Jennifer,
Just saw [company] landed the [major client] contract—a big win for the region.
That kind of growth typically means your cash cycles get more complex: longer payment terms, inventory ramp, customer concentration risk.
Might be a good moment to revisit your cash forecasting approach?
[Your name]
Word count: 58 words ✓
Company Context: Series A fintech startup, 6-month-old engineering manager hire, scaling engineering team from 8 to 15 people
Email 1: The Hook (Day 0)
Subject: moving from 8 engineers to 15—how are you keeping shipping velocity?
Body:
David,
Saw on LinkedIn you just ramped from 8 to 15 engineers over the last 6 months. That's fast.
Quick question: are you still hitting your sprint goals on time, or has velocity started to slip with the new headcount?
[Your name]
Word count: 52 words ✓
Email 2: The Pain (Day 3)
Subject: re: moving from 8 engineers to 15—how are you keeping shipping velocity?
Body:
David,
Most engineering teams see a 20–30% velocity drop in months 2–4 after scaling headcount (onboarding tax, context switch, architectural debt surfaces).
A Series A fintech we worked with flattened their velocity loss to 8% by documenting their architecture decisions and pairing new hires with systems ownership from day one.
Might be worth a conversation?
[Your name]
Word count: 67 words ✓
Email 3: The Delegation Ask (Day 7)
Subject: re: moving from 8 engineers to 15—how are you keeping shipping velocity?
Body:
David,
Not sure if architectural documentation or developer onboarding is your call at [company], or if you're sharing the load with a Staff Eng or Tech Lead.
Either way, most teams benefit from having a clear map of "who owns what system" before they hit 15+ headcount.
Happy to loop in whoever runs architecture, or circle back next month.
[Your name]
Word count: 70 words ✓
Email 4: The Break-Up (Day 12)
Subject: last note: system ownership template for growing teams
Body:
David,
I'll stop reaching out after this, but thought you might find this useful: we built a "System Ownership Matrix" template that helps teams clarify who's accountable for each major system, which usually cuts onboarding time for new hires by 40%.
No product involved—just a template you can modify.
[Link to template]
All the best,
[Your name]
Word count: 65 words ✓
Reactivation Signal (Day 72+): New signal detected: "David's company just announced Series B funding"
Reactivation Email:
Subject: caught the Series B news
Body:
David,
Saw [company] just announced the Series B. Nice work.
Series B means you're probably hiring 8–12 more engineers in the next 9 months. That's when poor system ownership and onboarding really hit. Teams usually see another 15–20% velocity dip if they don't get documentation in place now.
Worth a quick chat on how to structure the next phase?
[Your name]
Word count: 68 words ✓
Never
Always
Timing Windows (strict adherence required for sequence integrity)
Use this prompt to set up your email sequence in your CRM (HubSpot, Pipedrive, Close, etc.):
1. Create a workflow: "Cold Email Sequence – 4 Touch"
2. Trigger: Contact added to list "Outbound Sequence [Campaign Name]"
3. Actions (sequential, with delays):
- Day 0: Send Email 1 (subject: [insert subject], body: [insert body])
- Wait 3 days
- If no reply: Send Email 2
- Wait 4 days
- If no reply: Send Email 3
- Wait 5 days
- If no reply: Send Email 4
- Wait 60 days
4. Branching: If contact replies at any step, immediately:
- Tag contact with "replied_email_[n]"
- Move contact to "Sales Engagement" queue
- Pause/remove from automation
5. After Email 4: Tag as "sequence_complete_no_reply", set reminder for Day 72 reactivation check
After you've sent at least 50 complete sequences, measure:
Iterate based on data, not gut. If Email 1 open rate is under 30%, your trigger signal is weak—change it. If Email 2 reply rate is under 1%, your pain point doesn't land—test a different KPI.
npx claudepluginhub claudient/claudient --plugin claudient-sdrProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.