10 Cold Email Templates for B2B SaaS (2026)

Maildoso is itself a B2B SaaS, and we run the infrastructure underneath a massive amount of B2B outbound — 400,000+ mailboxes, 10M+ emails a day, 6,000+ companies on the platform, 4.7/5 on G2. That gives us two angles on this problem at once: we send cold email to sell our own product, and we see across thousands of campaigns what reaches a buyer versus what dies in spam. The templates here come out of that — real patterns that convert, built on direct-response basics: be specific, ask for one thing, keep friction minimal.

Each angle maps to something a SaaS buyer already deals with:

• The average company now runs over 100 SaaS apps (Productiv State of SaaS) — so "here's another tool" is an instant objection you have to disarm.
• At least 30% of SaaS licenses go unused (Zylo 2024 SaaS Management Index) — buyers are tired of paying for software nobody adopts.
• And buyers stay at arm's length: they spend only 17% of their buying journey meeting with potential vendors, with a third preferring a rep-free experience entirely (Gartner).

That last number is why these templates lead with the buyer's outcome and offer value before a meeting — pushing for a demo in email #1 fights how SaaS actually gets bought today. Where an angle leans on proof (a metric, a customer result), we flag it so you insert your own real data. We hold that line hard: a fabricated benchmark is the quickest way to lose a buyer who reads pitches all day.

Who you're emailing. Usually two people: the function leader who feels the pain your product solves (Head of Sales, Ops, Marketing, Finance, Eng — whoever owns the workflow), and the economic buyer who signs off on spend (a VP, director, or CFO). The user wants their day to get easier; the buyer wants ROI and no new tool that goes unused.

The pains that move them: a manual, time-sucking workflow; spend on a tool nobody fully adopts; a stack so sprawling that "one more app" is a hard sell; a metric they're accountable for and missing; and a recent change (funding, a hire, fast growth) that makes the status quo break.

What resonates in the copy: specificity (name the workflow, the metric, the integration), a real trigger (a raise, a new exec, a job post that reveals the pain), proof from a comparable company with a number attached, and a low-friction CTA ("want a 2-minute Loom of it working with your data?" beats "book a demo"). Keep emails to 50–90 words.

What to avoid: "We help teams like yours" openers, listing every feature, leading with the product instead of the outcome, demo-asks in email #1, and buzzwords ("synergy," "revolutionary," "game-changing") that signal a mass blast.

Best for: buyers who care about a hard, quantifiable return.

Subject line: {{metric}} math for {{company}}
Hi {{first_name}},
Teams like {{company}} usually spend [X hours / $Y] a month on {{workflow}} — most of it work that doesn't need a human.
We automate that piece, and for {{industry}} teams it typically pays for itself within [timeframe].
Want a quick breakdown of what the numbers would look like for your team?
{{signature}}

Why it works: leads with the buyer's own cost, not your features, and frames the product as a return rather than an expense.
Make it yours: use a real time/cost figure and a payback period you can actually defend.

Best for: a function leader buried in a manual, repetitive workflow.

Subject line: {{workflow}} without the manual part
Hi {{first_name}},
If {{company}}'s team is anything like the {{industry}} teams I talk to, {{workflow}} still runs on spreadsheets and copy-paste — hours a week that don't move the needle.
We handle that automatically, so your team spends its time on the work that actually matters.
Worth a 2-minute look at how it'd fit your setup?
{{signature}}

Why it works: describes the painful status quo in concrete terms, then offers relief without a heavy commitment.
Make it yours: name the exact manual step you eliminate — vague "efficiency" claims get ignored.

Best for: teams juggling several overlapping tools.

Subject line: replacing 3 tools with 1 at {{company}}
Hi {{first_name}},
The average company now runs 100+ SaaS apps, and teams your size are usually paying for two or three that overlap with {{category}}.
We cover what {{tool_a}} and {{tool_b}} do in one place — fewer logins, fewer invoices, one source of truth.
Want to see which tools you could fold in?
{{signature}}

Why it works: turns the "we already have a tool" objection into a reason to talk, and ties it to a real sprawl stat.
Make it yours: only claim consolidation you genuinely deliver, and name the actual tools where you can.

Best for: companies that just raised, hired key leadership, or are scaling fast.

Subject line: congrats on the {{event}} — {{workflow}} next?
Hi {{first_name}},
Congrats on the {{event}} — strong moment. Usually right after, {{workflow}} is one of the first things that starts to break, because what worked at the old size doesn't scale.
We help {{industry}} teams get ahead of that before it becomes a fire drill.
If that's on your radar this quarter, worth a quick look?
{{signature}}

Why it works: the trigger creates timeliness and connects their new stage to a problem your product is built for.
Make it yours: pull triggers from funding news, new-exec announcements, or job posts, and name the specific event.

Best for: prospects who resemble a customer you've already gotten results for.

Subject line: how {{similar_company}} improved {{metric}}
Hi {{first_name}},
We recently worked with {{similar_company}} — a {{industry}} team about your size — and they improved {{metric}} by [X%] in [timeframe] after switching to us.
{{company}} looks like a close match, so the same result is realistic here.
Happy to share exactly how they did it — useful?
{{signature}}

Why it works: a real, numbered result from a lookalike company is the most persuasive thing you can put in front of a SaaS buyer.
Make it yours: this only works with a true customer outcome — real metric, real timeframe, permission to reference. Never inflate it.

Best for: when you have any plausible connection — a mutual contact, an investor, a customer in their network.

Subject line: {{mutual_contact}} thought we should connect
Hi {{first_name}},
{{mutual_contact}} mentioned {{company}} is working on {{initiative}} and thought our product might be relevant — we help {{industry}} teams with {{workflow}}.
Not sure if it's a priority right now, but if it is, I'd be glad to show you what it looks like in practice.
Worth a quick look?
{{signature}}

Why it works: a warm reference cuts through the skepticism a heavily-pitched buyer brings to a cold email.
Make it yours: the connection must be real — otherwise reference a shared community or a customer they'd recognize.

Best for: prospects you know (or strongly suspect) use a competing tool.

Subject line: thoughts on {{competitor}}?
Hi {{first_name}},
Noticed {{company}} likely uses {{competitor}} for {{workflow}}. A lot of {{industry}} teams switch to us when they hit [specific limitation] — usually around {{pain_point}}.
Not saying rip and replace, but if that's been a friction point, it might be worth a side-by-side.
Want me to send a quick comparison?
{{signature}}

Why it works: meets the buyer where they are, names a specific limitation they may already feel, and stays low-pressure.
Make it yours: reference a real, honest differentiator — don't trash the competitor, just name where you're genuinely better.

Best for: cautious buyers who won't book a demo but might take something free.

Subject line: quick Loom of {{product}} with your data
Hi {{first_name}},
Instead of a demo, I can record a short Loom showing exactly how {{product}} would handle {{company}}'s {{workflow}} — using a real example from your world, not a generic walkthrough.
You watch it on your own time, and there's no call required.
Want me to put it together?
{{signature}}

Why it works: matches how SaaS buyers actually want to evaluate (self-serve, async) and removes the friction of a scheduled call.
Make it yours: make the Loom genuinely specific to them — a generic recording undoes the whole point.

Best for: prospects who opened or went quiet after an earlier email.

Subject line: still worth exploring?
Hi {{first_name}},
Circling back — I know new tools are easy to deprioritize. If {{workflow}} isn't a focus right now, no worries at all.
If it's still on your list, the offer stands: a quick Loom of {{product}} working with your use case, no call needed.
Want it?
{{signature}}

Why it works: gives an easy out (which paradoxically lifts replies) and restates the low-friction offer in one line.
Make it yours: keep it genuinely short — lighter than the first touch.

Best for: the final touch in a sequence after no response.

Subject line: should I close this out?
Hi {{first_name}},
I've reached out a couple of times about helping {{company}} with {{workflow}} — haven't heard back, so I'll assume the timing's off and close things out on my end.
If it becomes a priority later, just reply and I'll pick it up. Either way, wishing the team a strong quarter.
{{signature}}

Why it works: breakup emails often pull the highest reply rate in a sequence — the implied "I'll stop" nudges a response.
Make it yours: keep it confident and light, never passive-aggressive; the clean sign-off is what makes it land.

1. Day 1 — First touch. Open with one angle above (ROI, time saved, consolidation, or a trigger).
2. Day 3–4 — Value add. Send the free proof: a personalized Loom or an ROI breakdown (Template 8).
3. Day 7–8 — Re-engagement. Template 9 — short, easy out, restated offer.
4. Day 12–14 — Breakup. Template 10.

Keep it on one thread, change the angle each touch (never "just circling back"), and stop at four. Since buyers spend most of their journey researching alone, your follow-ups should add value, not just chase a reply.

You can write the most specific, buyer-centric SaaS email in your category and still get nothing back — because it never reached the inbox. At real sending volume, that's the default outcome unless the infrastructure underneath is built for it.
We see it constantly, and we've lived it. One Maildoso client rewrote their cold email copy three times and still couldn't push reply rates above 1%. The copy wasn't the problem — their Google Workspace accounts were. After moving the same campaigns to Maildoso SMTP mailboxes, reply rates climbed to 4% — same copy, different infrastructure.

What actually decides whether your outreach lands:

• Authenticated domains (SPF, DKIM, DMARC) on dedicated sending domains, kept off your primary product domain.
• Warmed mailboxes and conservative daily volume — roughly 15 emails per mailbox per day.
• IP rotation and mailbox recovery, so one flagged IP or burned mailbox doesn't take the campaign down with it.

This is the layer Maildoso runs — SMTP and Google Workspace mailboxes with IP rotation and self-healing, so your outbound reaches the primary inbox. You can test it with 300 SMTP mailboxes free for 30 days.