Measure and optimize growth using the AARRR (Pirate Metrics) framework with stage-specific KPIs and funnel analysis
日本語の概要は準備中です。原文の説明を表示しています。
Design multi-touch outbound sequences with optimal timing, channel mix, and messaging progression for SDR campaigns
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Create high-converting outbound sequences with strategic touchpoint timing, channel orchestration, and message progression.
Based on Outreach.io Sequence Science and SalesLoft Cadence Research, combining:
| Claude Does | You Decide |
|---|---|
| Designs sequence structure | Message copy |
| Suggests optimal timing | Brand voice |
| Recommends channel mix | Tool selection |
| Creates progression logic | A/B test priorities |
| Identifies optimization areas | Resource allocation |
Key Variables:
| Parameter | Options |
|---|---|
| Touches | 8-14 typical |
| Duration | 14-30 days |
| Channels | Email, Phone, LinkedIn, Video |
| Goal | Meeting, Response, Qualification |
Recommended Mix:
| Channel | Percentage | Purpose |
|---|---|---|
| 50-60% | Scale, persistence | |
| 20-25% | Personal touch | |
| Phone | 15-20% | Direct connection |
| Video | 5-10% | Differentiation |
Framework: 4-Phase Sequence
| Phase | Days | Purpose | Intensity |
|---|---|---|---|
| Opening | 1-3 | Hook, establish | High |
| Building | 4-10 | Value, credibility | Medium |
| Urgency | 11-18 | Social proof, FOMO | High |
| Breakup | 19-25 | Final push, close loop | Low |
Progression Pattern:
Output:
## Enterprise Outbound Sequence (14 touches, 21 days)
### Sequence Overview
- **Target**: VP+ at enterprise companies
- **Goal**: Booked meeting
- **Duration**: 21 days
- **Touches**: 14 total
### Channel Mix
| Channel | Touches | % |
|---------|---------|---|
| Email | 7 | 50% |
| LinkedIn | 4 | 29% |
| Phone | 2 | 14% |
| Video | 1 | 7% |
---
### Full Sequence
#### Phase 1: Opening (Days 1-3)
**Day 1 - Email #1 (Trigger-based)**
Subject: [Trigger] + [Company]
Hi [FirstName],
[Trigger observation - funding, hire, news].
I work with [similar companies] who face [challenge]. Curious if that's on your radar?
[One line value prop]
Worth a quick call?
[Name]
**Day 1 - LinkedIn Connection**
- Send connection request
- Note: "Hi [Name], [brief reason for connecting]"
**Day 2 - Phone Call #1**
- Goal: Live conversation
- If VM: "Hi [Name], [Name] from [Company]. Quick call about [trigger]. Will follow up via email."
**Day 3 - LinkedIn Voice Note**
- 30-second personalized message
- Reference trigger + offer value
---
#### Phase 2: Building (Days 4-10)
**Day 4 - Email #2 (Value)**
Subject: Re: [Previous subject]
[FirstName],
Wanted to share what [Similar Customer] achieved:
They were in a similar situation when we first connected.
Worth comparing notes?
[Name]
**Day 6 - LinkedIn Engagement**
- Engage with their content (like, comment)
- OR share relevant content, tag them
**Day 8 - Email #3 (Different Angle)**
Subject: Quick question about [specific challenge]
[FirstName],
Most [Titles] I talk to say [specific challenge] is their #1 priority this quarter.
Quick question: Is that true for you too, or is something else taking priority?
Genuinely curious—helps me understand what matters most to leaders like you.
[Name]
**Day 10 - Phone Call #2**
- Morning attempt
- Different VM: "Hi [Name], following up on my emails. Would love 15 minutes to discuss [value]. [Your number]."
---
#### Phase 3: Urgency (Days 11-18)
**Day 11 - Email #4 (Social Proof)**
Subject: How [Competitor's Customer] solved [problem]
[FirstName],
[Competitor's Customer] was dealing with [same problem].
After [implementing solution], they saw: • [Result 1] • [Result 2]
Happy to walk through their approach if useful.
[Name]
**Day 13 - LinkedIn Direct Message**
Hi [Name],
I've reached out a few times—wanted to try a different channel.
Not trying to sell you anything. Genuinely think [insight] could help [Company].
Open to a quick chat?
**Day 15 - Email #5 (Video)**
Subject: Recorded this for you, [FirstName]
[FirstName],
Put together a 60-second video on why I think [Company] would benefit from [approach].
[Video thumbnail/link]
If this resonates, let's talk. If not, no worries—I'll stop reaching out.
[Name]
**Day 18 - Email #6 (Urgency)**
Subject: [Event/timing trigger]
[FirstName],
With [event/quarter end/budget cycle] coming up, a lot of [Titles] are locking in [decisions].
Last chance to get this on your calendar before [deadline].
Quick call this week?
[Name]
---
#### Phase 4: Breakup (Days 19-21)
**Day 19 - LinkedIn Final**
- Send article or resource relevant to them
- No ask, just value
**Day 21 - Email #7 (Breakup)**
Subject: Should I close your file?
[FirstName],
I've reached out several times and haven't heard back. Totally understand—you're busy.
Just want to check: should I close out your file, or is this something worth revisiting in the future?
If timing isn't right, let me know and I'll circle back in [timeframe].
Either way, wishing you a great [quarter/year].
[Name]
---
### Sequence Metrics (Benchmarks)
| Metric | Target | Excellent |
|--------|--------|-----------|
| Open Rate | >40% | >55% |
| Reply Rate | >8% | >15% |
| Meeting Rate | >3% | >6% |
| Positive Reply | >60% of replies | >75% |
Output:
## SMB Quick-Hit Sequence (8 touches, 14 days)
### Sequence Overview
- **Target**: Manager/Director at SMB
- **Goal**: Demo or trial signup
- **Duration**: 14 days
- **Touches**: 8 total
### Channel Mix
| Channel | Touches | % |
|---------|---------|---|
| Email | 5 | 63% |
| LinkedIn | 2 | 25% |
| Phone | 1 | 12% |
---
### Rapid Sequence
**Day 1 - Email #1 (Direct)**
Subject: Quick question, [FirstName]
Hi [FirstName],
Do you handle [function] at [Company]?
If so, I have an idea that could help you [specific outcome] in [timeframe].
Interested?
[Name]
**Day 1 - LinkedIn Connect**
- Simple connection request
**Day 3 - Email #2 (Value)**
Subject: Re: Quick question
[FirstName],
[One stat or proof point from similar company]
That's what [Customer] did with us.
Worth 10 minutes to see if we can do the same for [Company]?
[Name]
P.S. Here's a 2-min video showing how: [link]
**Day 5 - Phone Call**
- Quick call attempt
- VM: Keep to 20 seconds
**Day 7 - LinkedIn Message**
Hey [Name] - saw you opened my email but haven't had a chance to connect. Totally get it. Is [problem] even a priority for you right now?
**Day 9 - Email #3 (Different Hook)**
Subject: [Competitor name] alternative?
[FirstName],
A lot of [Company size] companies tell us they're frustrated with [competitor/status quo].
We're simpler + faster. Most customers are up and running in [timeframe].
Worth a look?
[Name]
**Day 11 - Email #4 (Offer)**
Subject: Try us free?
[FirstName],
Want to just show you instead of tell you?
Here's a free [trial/assessment/audit]: [link]
No commitment, no call required.
[Name]
**Day 14 - Email #5 (Breakup)**
Subject: Last one from me
[FirstName],
Haven't heard back, so this will be my last email.
If [problem] becomes a priority, I'm here: [calendar link]
Good luck with everything!
[Name]
icp-matching - Target the right accountssignal-monitoring - Trigger-based outreachlead-qualification-bant - Qualify responsesまだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Measure and optimize growth using the AARRR (Pirate Metrics) framework with stage-specific KPIs and funnel analysis
日本語の概要は準備中です。原文の説明を表示しています。
Calculate A/B test statistical significance. Use when: determining if test results are significant; calculating required sample size; estimating test duration; analyzing conversion experiments; making data-driven decisions
日本語の概要は準備中です。原文の説明を表示しています。
Assess customer account health using product usage, support sentiment, payment status, and relationship signals
日本語の概要は準備中です。原文の説明を表示しています。
Analyze paid advertising performance across channels and recommend budget reallocation to maximize ROAS and minimize CAC. Use when: planning quarterly ad budget allocation, diagnosing underperforming ad channels, deciding whether to scale spend on a channel, calculating marginal ROI across Google Ads, Meta, LinkedIn, or TikTok, rebalancing media mix after performance shifts, or setting up a test-and-scale framework for new channels.
日本語の概要は準備中です。原文の説明を表示しています。
Use when testing skills, commands, or agents for quality. Use after creating new skills, before deploying agents, or when debugging inconsistent agent behavior. Triggers on "evaluate", "test quality", "is this skill working", or QA of AI workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Use when analyzing server logs to understand how AI crawlers (GPTBot, ClaudeBot, PerplexityBot) interact with your site. Use when optimizing content placement for LLM retrieval, diagnosing why AI search isn't citing your content, or auditing crawl patterns to find optimization gaps.
日本語の概要は準備中です。原文の説明を表示しています。