40 Cold Email Templates That Get Replies (2026 Swipe File)

Subject{Company} + {tool}

Hi {First},

Saw the {job_title} posting — the JD mentions {tool} and {tool_b}.

Getting those two to agree on what produced revenue is usually the hard part. We built for exactly that join.

Worth fifteen minutes?

{Sender}

Subjectcongrats on the {round}

Hi {First},

Congrats on the {round}.

The pressure to show pipeline usually lands about a month after the announcement. If that's the shape of your next quarter, happy to share what similar teams did with the first 90 days.

Either way — good raise.

{Sender}

Subjectnew seat, old reporting problem?

Hi {First},

Saw you started as {role} at {Company} — congrats.

Most people in that seat inherit a reporting stack that can't answer 'which activity produced cash'. If that's what you've walked into, I've got notes.

No pitch, genuinely.

{Sender}

Subjectyour {tool} review

Hi {First},

Read your {tool} review — the limitation you flagged about {issue} is real, and it gets worse as volume grows.

We took a different approach to it. Happy to show you in ten minutes, or just send a short writeup.

{Sender}

Subject{Company} → {city}

Hi {First},

Saw {Company} opened in {city}.

Second market usually breaks whatever worked in the first — different cycle, different buyers, same dashboard reporting both as one number.

If you're hitting that, worth a conversation.

{Sender}

Subjectwhich email got paid?

Hi {First},

Quick question — can you currently tell which sequence produced collected revenue, not just replies?

Most teams can't, because the CRM and the invoice live in different systems. That's the gap we close.

Worth a look?

{Sender}

Subjectbookings vs bank

Hi {First},

Your CRM reports bookings. Your bank reports cash. In most B2B teams the gap between those is 30% or more, and nobody sees it until quarter end.

We attribute to the paid invoice instead.

Interested?

{Sender}

Subject{role} at {Company}

Hi {First},

You own the number at {Company}. This is a note about the part of it you can't see.

When a deal closes-won, the CRM stops watching. Whether the invoice cleared is someone else's system.

Happy to show you what the whole chain looks like in one place.

{Sender}

Subject30 seconds

Hi {First},

Three questions:

1. Do you know which sequence produced revenue last quarter?
2. Revenue booked or revenue collected?
3. How long did it take to find out?

If any answer is uncomfortable, that's what we fix.

{Sender}

Subjectnot a demo request

Hi {First},

Not asking for a meeting.

We published a breakdown of where forecasts break between closed-won and cleared cash. It's the most useful thing we've written and it costs you nothing.

Want the link?

{Sender}

Subjectre: {Company} + {tool}

Hi {First},

Following up on the note about {tool}.

One number that might make it concrete: teams usually find 20-40% of forecast revenue lands in a later period than the CRM said. Worth checking yours.

Happy to send the calculator either way.

{Sender}

Subjectone more angle

Hi {First},

Probably not the right time — but a different angle in case the first one missed.

If you're chasing reply rate as the outbound metric, the gap between replies and collected revenue is usually where the budget conversation goes wrong.

Worth fifteen minutes?

{Sender}

Subject{First} — wrong person?

Hi {First},

If this isn't your area, who owns revenue reporting at {Company}?

Happy to stop emailing you either way — just reply 'not me' and I'll take you off.

{Sender}

Subjectthe short version

Hi {First},

Short version of the last two emails:

We show which outbound activity produced cash, not replies. One database, first touch through to paid invoice.

If that's not a problem you have, say so and I'll stop.

{Sender}

Subjectworth revisiting in Q{n}?

Hi {First},

Guessing this isn't a now problem.

Should I check back in Q{n}, or is it genuinely not a fit? Both are fine answers — I'd just rather know than keep guessing.

{Sender}

Subjectclosing the loop

Hi {First},

I'll assume the timing isn't right and stop here.

If it becomes relevant — usually when someone asks which channel produced revenue and the answer takes a week — you know where to find me.

Good luck with the quarter.

{Sender}

Subjectlast one

Hi {First},

Last note from me.

If I got the timing wrong rather than the fit, reply with a month and I'll come back then. Otherwise I'll leave you alone.

{Sender}

Subjectwas it the pitch or the problem?

Hi {First},

Genuinely curious before I close this out — was it the problem that didn't land, or the way I explained it?

Either answer is useful to me. No follow-up required.

{Sender}

Subjecttaking you off the list

Hi {First},

Taking you off my list — no reply needed.

Before I do: the resource on attribution to paid invoices is here if it's ever useful. Free, no form.

All the best.

{Sender}

Subjectone line

Hi {First},

Just need a yes or no on whether this is worth a conversation. Either is fine and I won't chase.

{Sender}

Subjectyou said come back when

Hi {First},

You told me to come back when we'd built {feature}.

We built it. Closing the loop as promised.

Worth fifteen minutes now?

{Sender}

Subject{n} months on

Hi {First},

We spoke back in {month} about {problem}. Timing wasn't right, which was fair.

Curious whether it got solved, got worse, or got ignored. Genuinely asking — not a pitch.

{Sender}

Subjectnew role, same question

Hi {First},

Saw you moved to {Company} — congrats.

We talked about {problem} at {prev_company}. Does it follow you to the new seat, or is it a different set of problems now?

{Sender}

Subjectwe fixed the thing you flagged

Hi {First},

You passed on us because of {objection}. Fair at the time.

That's changed. Not asking for a meeting — just thought you'd want to know the reason no longer holds.

{Sender}

Subjectstill worth a conversation?

Hi {First},

Our last conversation stalled and I never found out why.

If it's dead, tell me and I'll close it properly. If it's dormant, tell me when to come back.

{Sender}

Subjectquick pointer?

Hi {First},

Not pitching you — you're not the buyer for this.

Who owns revenue reporting at {Company}? Happy to go direct and leave you out of it.

{Sender}

Subject{mutual} suggested you

Hi {First},

{mutual} mentioned you're the person who'd have opinions about {topic}.

She was right about the last three people she pointed me at, so here I am.

Worth a conversation?

{Sender}

Subjectasking for one intro

Hi {First},

You mentioned {other_company} were solving the same problem.

Any chance of an intro? Happy to send a forwardable paragraph so it costs you one click.

{Sender}

Subjectforwardable

Hi {First},

As promised, here's the forwardable version:

---
We use Quotarider to trace outbound through to the paid invoice — it answers 'which sequence produced cash' as a query instead of a reconciliation project. Worth fifteen minutes if that's a live question.
---

Thanks {First}.

{Sender}

Subjectwho replaced {person}?

Hi {First},

I worked with {person} at {Company} on {topic} before they moved on.

Who picked that up? Happy to share what we'd already worked out so it isn't lost.

{Sender}

Subjectwhat we agreed

Hi {First},

Three things from today:

1. {point_one}
2. {point_two}
3. I'll send {deliverable} by {day}

Anything I've got wrong?

{Sender}

Subjectthe forwardable summary

Hi {First},

A version you can forward internally without me in the room:

{one_paragraph}

Happy to adjust it if the framing is off for your audience.

{Sender}

Subjectwhat has to be true

Hi {First},

One question before we go further — what has to happen internally for this to move?

Not chasing, just want to build the timeline around your process instead of guessing at it.

{Sender}

Subjectthe number you asked for

Hi {First},

You asked what the gap looks like at your volume. Rough figures:

{calculation}

Happy to run it properly with your real numbers.

{Sender}

Subjectnext step, dated

Hi {First},

Proposing {date} for the next one — {purpose}, thirty minutes.

If that's too soon or the wrong people, tell me and I'll rework it.

{Sender}

Subjectone page

Hi {First},

Proposal attached — deliberately one page.

Problem, what changes, price, next step. If you need a longer version for procurement, say so and I'll produce it.

{Sender}

Subjectthe honest version

Hi {First},

Before you decide — two things we're genuinely not the best choice for: {limitation_one} and {limitation_two}.

If either is central to you, I'd rather say so now.

Otherwise, ready when you are.

{Sender}

Subjectwhat's blocking it?

Hi {First},

Proposal's been with you a week.

Usually that means one of three things: budget, a stakeholder I haven't met, or it slipped down the list. Which is it?

Happy to help with any of them.

{Sender}

Subjectif price were half

Hi {First},

Direct question: if the price were half, would you buy this quarter?

If yes, it's a budget conversation and I can work with that. If no, it was never about price and I'd rather know what it is.

{Sender}

Subjectclosing this out

Hi {First},

I'd rather close this properly than leave it open in a forecast.

Is this a no, a not-yet, or a still-working-on-it? Any of the three is fine.

{Sender}