Cold Email Swipe File
What this is: 12 cold email frameworks that work for B2B SaaS. Each one has a structure, an example, and notes on when to use it.
What this is not: Templates to copy and send as-is. Every email here needs your specific product, your specific buyer, and your specific voice. Generic = deleted.
| ← Back to Right Suite | Test your outreach with RightEngagement → |
The rules before the frameworks
- One email = one idea. If you have two things to say, write two emails.
- One email = one ask. “Would you be open to a 15-minute call Thursday?” beats “let me know if you’d like to connect or learn more or whatever works for you.”
- The subject line is a promise, not a description. “Quick question” is not a promise. “[Company] + [outcome]” is.
- Never open with yourself. The first sentence should be about them, their company, or their problem — not your product.
- Short wins. Under 100 words for the first email. Under 75 for follow-ups. If you can’t say it in 3 short paragraphs, you don’t know what you’re asking for yet.
Framework 01 — The Specific Observation
When to use: When you have a real, specific reason to reach out to this person at this company right now.
Structure:
Subject: [Company] + [problem category]
[Specific thing you noticed about their company or role that relates to your product's value prop].
[One sentence connecting that observation to the problem you solve].
[What you do in one sentence].
Worth a 15-minute call this week?
[Name]
Example:
Subject: Kora + pricing page
Noticed Kora just moved from flat-rate to usage-based pricing — that's usually when conversion on the pricing page drops before it goes up.
We help B2B SaaS teams validate pricing changes with simulated buyer reactions before rolling them out.
Would it be useful to see how your current pricing page scores? Happy to send the report before we talk.
[Name]
Why it works: The specific observation signals you’re not blasting a list. The connection to a timing event (“just moved to”) makes it feel relevant right now, not generically.
Framework 02 — The Problem-First
When to use: When your buyer has a well-known, painful problem and you want to lead with empathy before introducing a solution.
Structure:
Subject: [The problem in their words]
[Describe the painful situation your buyer is in, in language they'd use themselves. No product mention.]
[One sentence: what most people do about this, and why it doesn't work.]
[What you do differently, in one sentence.]
Do you have 15 minutes [DAY]?
[Name]
Example:
Subject: pricing your SaaS when you have no customers yet
Most B2B SaaS founders pick their price by looking at competitors and splitting the difference. It's fast, but it means you're pricing based on what other founders guessed — not what your buyers would actually pay.
We built a simulation tool that tells you how your target audience responds to your price before you launch.
Do you have 15 minutes Thursday?
[Name]
Why it works: Naming the exact situation before introducing the solution builds credibility. The buyer thinks “they get it” before they know what you’re selling.
Framework 03 — The Contrarian
When to use: When there’s a widely-held belief in your category that you disagree with and your product reflects a different approach.
Structure:
Subject: [Contrarian belief stated as fact]
[State the conventional wisdom]. [One sentence: why that's wrong or incomplete].
[What you believe instead, and why].
[One sentence on how your product reflects that belief].
Worth 15 minutes?
[Name]
Example:
Subject: "validate with real users first" doesn't work when you have none
Everyone tells founders to validate pricing with real customers. That's great advice if you have customers. If you're pre-traction, you're validating with whoever will talk to you — which isn't your ICP.
We built a simulation approach that tests your offer against synthetic buyers modeled on your actual target segment — before you have a list to burn through.
Worth 15 minutes?
[Name]
Why it works: Pattern-interrupts the inbox. The recipient either agrees (they’ll reply) or disagrees enough to say so (also a reply).
Framework 04 — The Benchmark
When to use: When you have a relevant benchmark or data point that your buyer would find surprising.
Structure:
Subject: [Surprising stat about their situation]
[State the benchmark or data point]. [One sentence on what it means for them specifically.]
[One sentence on what you do about it.]
[Ask.]
[Name]
Example:
Subject: 8 hours
The average SaaS company spends 8 hours total on pricing decisions over the life of the business. (Price Intelligently, 2023.)
That's less time than most founders spend on their homepage copy — for a decision that directly determines whether the business is profitable.
We built a tool that gives founders a pricing confidence score in 10 minutes. Happy to run one on your product and send you the report.
Interested?
[Name]
Why it works: A specific, sourced number is immediately credible. It reframes the problem in a way the buyer hasn’t seen before.
Framework 05 — The Ask for Advice
When to use: Early in your validation phase, before you have a product to sell. Generates warm conversations that often convert to early customers.
Structure:
Subject: advice from someone who's done [THING]
[Why you're reaching out to this specific person — their experience or expertise.]
[What you're building in one sentence.]
[The specific question you want their input on — one question, not three.]
[Name]
Example:
Subject: advice on pricing a pre-revenue SaaS tool
You've launched a few B2B products from scratch — wanted to get your take on something before we go live.
Building a pricing validation tool for SaaS founders and trying to figure out whether to launch at $29 or $49 with a free trial.
Would 15 minutes be possible this week to get your read on it?
[Name]
Why it works: Nobody gets asked for advice and feels sold to. The “ask for advice” frame creates a fundamentally different dynamic than the standard cold pitch.
Framework 06 — The Case Study
When to use: Once you have one customer with a measurable result. This becomes your most powerful email.
Structure:
Subject: how [CUSTOMER TYPE] got [SPECIFIC RESULT]
[One sentence describing the situation the customer was in — should mirror your prospect's situation.]
[What they did (your product) and what happened — be specific with numbers.]
[One sentence: are you dealing with a similar situation?]
[Name]
Example:
Subject: how a B2B SaaS founder moved from $49 to $79 without losing signups
Maya was about to launch her analytics tool at $49 because that's what similar tools charged. She ran a pricing simulation first and found her target segment had a willingness to pay ceiling of $89.
She launched at $79. Her conversion rate is the same. Her MRR is 61% higher than it would have been.
Are you pricing for launch soon?
[Name]
Why it works: Specific numbers make it real. The situation-match in the first sentence makes the reader see themselves in the story.
Follow-up frameworks
Follow-up 1 (3 days after no reply):
[First name] — just bumping this up in case it got buried.
[One new piece of value: a relevant article, a benchmark, a question they'd find interesting.]
Still happy to [the original ask].
Follow-up 2 (7 days after no reply):
[First name] — last note from me on this.
[One sentence acknowledging they may not be the right person or this may not be the right time.]
If you know someone dealing with [the problem], I'd appreciate the intro.
[Name]
What never to write in a follow-up:
- “Just checking in” — says nothing
- “I know you’re busy” — everyone is, this isn’t a differentiator
- “Did you get a chance to look at my last email?” — passive and slightly hostile
Subject line patterns that work (and ones that don’t)
| Pattern | Example | Why it works |
|---|---|---|
| Company + problem category | “Kora + pricing page” | Signals relevance before they open |
| The surprising number | “8 hours” | Curiosity without being clickbait |
| The specific situation | “pricing your SaaS when you have no customers” | Self-identifies the right reader |
| Contrarian claim | “‘validate with real users first’ doesn’t work when you have none” | Pattern interrupt |
| Name + short question | “quick question about [Company]” | Personal, low-commitment |
| Pattern | Example | Why it doesn’t work |
|---|---|---|
| “Quick question” (alone) | “Quick question” | Overused, says nothing |
| Feature announcement | “Introducing [Product] — the [category] tool for [persona]” | Sounds like a press release |
| Flattery opener | “I love what you’re building at [Company]” | Every cold emailer says this |
| Vague value | “Improve your [process] by 3x” | Generic, unbelievable |
For predicted reply rates on your specific emails across 100+ simulated buyer reactions, use RightEngagement.