❌ "My name is John and I'm the founder of..." ❌ "I hope this email finds you well..." ❌ "I wanted to reach out because..." ❌ "I'm sure you're busy, but..."
代わりに、彼らとの関連性から始めましょう。
✅ "Saw your post about scaling your engineering team—the challenge you mentioned about deployment frequency resonated."
✅ "Congrats on the Series B! Scaling from 20 to 100 engineers usually surfaces some interesting infrastructure challenges."
✅ "Noticed [Company] just launched in APAC—that timezone coverage for customer support can be tricky."
✅ "Your talk at SaaStr about reducing churn was excellent—curious how you're approaching the data side."
"Does this resonate with what you're experiencing?"
特定の会議の CTA（関心が確立されたら使用）:
"Do you have 15 minutes Thursday or Friday?"
"Would a 20-minute demo next week make sense?"
"Can I send over a calendar link?"
コンテンツベースの CTA:
"Want me to send over the case study?"
"I put together a quick analysis for [Company]—mind if I share?"
"We wrote a guide on this exact problem—worth a read?"
完全な SaaS コールドメールの例
例1: エンジニアリングリーダーをターゲットにする
Subject: Quick thought on [Company]'s deployment pipeline
Hi [First Name],
Noticed [Company] has been hiring aggressively for backend engineers—congrats on the growth. In my experience, that growth often surfaces deployment bottlenecks that slow down the whole team.
We've helped engineering teams at [Similar Company 1] and [Similar Company 2] reduce deployment time by 75% while cutting infrastructure costs. Their teams went from 10 deploys/week to 50+ without adding headcount.
Would it make sense to explore if we could help [Company] move faster?
Best, [Your Name]
例2: 営業リーダーをターゲットにする
Subject: [Company]'s outbound—quick idea
Hi [First Name],
Saw [Company] just opened an SDR role—scaling outbound is exciting but can be tricky to get right.
One thing we've seen trip up growing sales teams: email deliverability. When SDRs scale from 50 to 500 emails/day, bounce rates creep up and suddenly half the team's emails are hitting spam.
We help sales teams like yours maintain 98%+ deliverability even at scale. [Similar Company] increased their meeting book rate by 40% just by cleaning their prospect lists before outreach.
Worth 15 minutes to see if we could help [Company]'s new SDRs hit the ground running?
[Your Name]
例3: 製品リーダーをターゲットにする
Subject: User onboarding at [Company]
Hi [First Name],
Just tried [Company]'s product—love what you've built. The onboarding flow is solid, but I noticed the activation step around [specific feature] might be where some users drop off.
We help product teams like yours identify exactly where users get stuck and why. [Similar Company] improved their activation rate from 35% to 58% in 6 weeks using our analytics.
Would it be helpful to see how we diagnose onboarding friction?
Noticed [Company] is using [Current Tool]—solid choice for basic analytics. But I'm guessing as you've scaled, you're running into limitations around [specific capability].
We help product teams like yours get the deep behavioral insights that basic analytics miss. [Similar Company] used our platform to identify a hidden churn predictor that was costing them $500K/year—and fixed it in 2 weeks.
Worth a quick chat to see if we could help [Company] uncover similar insights?
Best, [Your Name]
メール2 - 3日目（新しい角度）
Subject: Re: [Company]'s customer data
Hi [First Name],
Following up—wanted to share something relevant.
I just published an analysis of the top 5 user behaviors that predict churn in [their industry] SaaS products. Based on [Company]'s product, #3 might be particularly relevant for you.
Here's the breakdown: [Link to content]
Let me know if any of this resonates with what you're seeing at [Company].
[Your Name]
メール3 - 7日目（ケーススタディ）
Subject: How [Similar Company] reduced churn 23%
Hi [First Name],
Quick case study I thought you'd find interesting.
[Similar Company] (similar space to [Company]) was struggling with churn despite strong NPS scores. Using our platform, they discovered that users who didn't complete [specific action] within 7 days had 3x higher churn risk.
They built a targeted intervention and reduced churn by 23% in one quarter.
Happy to walk through exactly how they did it if useful.
[Your Name]
メール4 - 12日目（ソーシャルプルーフ）
Subject: 3 companies like [Company]
Hi [First Name],
Wanted to share some quick context on who else in [their industry] is using our platform:
[Company A]: Improved activation 40%
[Company B]: Reduced support tickets 35%
[Company C]: Increased expansion revenue 28%
All started with a 15-minute conversation to see if there was a fit.
Open to a quick chat this week?
[Your Name]
メール5 - 18日目（異なる課題）
Subject: Quick question about [Company]'s expansion revenue
Hi [First Name],
Different angle—curious how [Company] handles identifying expansion opportunities.
Most product teams I talk to are leaving revenue on the table because they can't see which customers are ready for upsell until it's too late (or they've already churned).
We help teams like yours proactively identify expansion-ready accounts weeks before traditional methods. Worth exploring?
[Your Name]
メール6 - 25日目（ブレイクアップ）
Subject: Closing the loop
Hi [First Name],
I've reached out a few times about helping [Company] with product analytics, but haven't heard back. Totally understand if it's not a priority right now.
I'll close the loop here—no more emails from me on this topic.
If product analytics becomes relevant down the road, feel free to reach out. Happy to help whenever.
対応:「理にかなっています。エンジニアリングリソースは柔軟性を与えます。簡単な質問: メンテナンスの負担はどうですか? 私が話すほとんどのチームは、構築は簡単な部分であることを発見しますが、メンテナンスはエンジニアをコア製品作業から遠ざけます。[類似企業]がビルド vs バイの決定をどのように行ったかを共有できます。」
