Investor Cold Email Guide for Founders (2026)

How to write a cold email to an investor that opens a real conversation: subject line, opening line, proof, and ask.

Cold Email to Investors That Actually Gets Replies

Warm intros beat cold email every time, but they don't scale to 60 investors. Cold email is the second-best tool — and if it's written like most founder cold emails, it doesn't work at all.

The opening line

One sentence proving you researched them. Reference a specific investment they made, a talk they gave, or a thesis they published. Generic openers ('I saw you invest in SaaS...') get filed as spam.

The proof

Two lines. What you do, in plain language. The one metric that makes you interesting — revenue, growth rate, retention curve, marquee customer. If you don't have a metric that would make an investor lean in, cold email won't fix that.

The ask

One specific ask. '15 minutes to discuss our Series A' beats 'would love to connect.' Attach the deck OR link to it — don't require a reply to get the deck. Investors want to evaluate before scheduling.

What kills cold email

Long paragraphs. Generic openings. No metrics. Multiple asks. Not attaching the deck. Sending to a firm's info@ address. Following up 3 times in a week.

Deliverability basics

Send from your company domain (not gmail.com). SPF, DKIM, and DMARC configured. Plain text, not HTML with images. One email at a time — bulk sending destroys deliverability and reads as bulk.

Frequently asked questions

What reply rate should I expect?
5–15% for well-researched cold emails to investors who match your stage. 1–3% for generic mass sends.
Should I follow up if there's no reply?
Once, 7 days later. A short bump with one new signal. After that, add them to your monthly update list.
Is cold email better than LinkedIn?
Email for the pitch, LinkedIn for warm-up context. Cold LinkedIn DMs work worse than cold email for a fundraise pitch.

Related fundraising guides (40)

Investor directory · Fundraising library · Articles A–Z · Company funding database