What should a cold email to a startup founder say?
Three things, in this order: why you are writing to this company now, one piece of proof that you can help with it, and one small ask. Everything else is optional.
The bar is low, which is the good news. Backdoor’s list page mocks up what a founder’s inbox looks like on a busy morning, and the subject lines in it are the generic kind: “Application for SDE role”, “Seeking an opportunity at your esteemed organization”, “Resume for any suitable position”. None of them says anything about the company. Hunter’s State of Cold Email 2025 asked decision-makers why they ignore cold email, and irrelevance topped the list, named by 71% of them. An email that could only have gone to one company is already ahead of most of that inbox.
Keep it short. Hunter’s study of 34 million cold emails favoured 20 to 39 words, with a caveat that length alone won’t earn the reply; AI that writes personalized job outreach sets out that research in full. YC’s Michael Seibel gives founders writing to investors a simpler test: the email should take under a minute to read. A founder deciding on a hire is the same busy reader.
The templates below sit between 60 and 100 words in the body. Anything in square brackets is yours to replace, and the bracketed examples show the level of detail to aim for.
How do you write a cold email to a startup founder for an SDE role?
Lead with something technical you noticed in their product, then one thing you built that maps to it, with a number and a link to the code. A repository or a live project is faster for a founder to check than a CV, and it shows you can ship.
Subject: Backend engineer for [your payouts API]
Hi [Ananya],
I saw [last week’s launch of instant payouts, and the note in your docs that retries are still manual].
I’m a backend engineer with [three] years in [Go and Postgres]. At [my current company] I [rebuilt our payment retry queue, which cut failed payouts from 4% to under 1%]. The code for [a smaller version] is here: [GitHub link].
If you’re hiring engineers this quarter, could we talk for 15 minutes next week?
[Rohan] [LinkedIn URL]
What each line is doing:
- The subject names the role and their product. A founder scanning a full inbox knows what it is before opening it.
- The opening is a fact you can only know by looking: a launch, and a detail from their docs. It proves the email was written for them.
- The middle is one result, not a list of languages. If your result has no number, use the scale instead (“for 40,000 daily users”).
- The link lets an engineer-founder check your work in a minute. Link one repository, not your whole profile.
- The ask is small and time-boxed. “If you’re hiring engineers this quarter” lets them say no without awkwardness.
If you are in India and your notice period is 30 days or less, one extra line can help: “I can start within [30] days.” Leave it out if it is 90 days; that conversation goes better on a call.
What if you are a fresher or have no work result to point to?
Use a project as your proof, and make it as close to their product as you can. A small thing you built with their API, or a bug you found and wrote up, does more than a degree line.
Subject: [Built a Slack bot on your API], SDE intern or junior role
Hi [Karthik],
I’ve been using [your scheduling API] for a college project and [built a Slack bot that books rooms through it]. It has [about 60] users across [two hostels] now: [link].
While building it I noticed [the timezone field is ignored on recurring events], and I wrote up a fix [here].
I graduate in [May 2027] and I’d like to start my career on a small team building [this]. Would you be open to a 15-minute call?
[Divya] [GitHub URL]
The proof here is that they can open the link and see you use their product. The bug note is optional, but it gives the founder something specific to reply to, and it is help they did not have to ask for. Keep it factual and do not turn it into criticism.
What about a product, growth or founder’s office role?
Swap the code for a piece of thinking they can read in two minutes: a teardown of their onboarding, a list of five accounts that look like their customers, or a short analysis of a metric they have shared in public.
Subject: [Three fixes for your signup flow], from a PM
Hi [Meera],
Congrats on [the seed round]. I signed up for [your clinic app] yesterday and wrote [a one-page note on three places new users might drop off, with screenshots]: [link].
I’ve spent [two] years as a product manager at [a 30-person fintech], where [I ran onboarding experiments that took activation from 22% to 35%].
If you’re adding to the team after the raise, I’d like to help with exactly this. Could we talk for 15 minutes next week?
[Sahil]
The note does the work. It shows judgment, it is useful even if they never hire you, and it gives the founder something concrete to reply to.
What should you change in each template, and why?
Change the specifics every time, and keep the shape. The structure is what makes it short; the details are what make it read as one person writing to another.
| Part | Change it to | Why |
|---|---|---|
| Subject | The role plus one thing from their company | It is the only line read before the open |
| Opening | Something from the last month: a launch, a raise, a hire, a post | Answers “why now?” and proves you looked |
| Proof | One result with a number, or one link they can open | One clear result is easier to repeat to a cofounder than a list |
| Ask | A 15-minute call, or “could I send the full note?” | Easy to accept in a gap between calls |
| Sign-off | Your name and one link | More links read like a CV; one link gets clicked |
| Recipient | The founder who owns the work you would do | At two founders, the CTO for engineering roles and the CEO for the rest |
What to cut, every time: “I hope this email finds you well”, “Respected Sir/Ma’am”, “passionate”, “results-driven”, “esteemed organization”, and an attached PDF resume. Backdoor’s homepage marks up a sample email with labels such as “Could be any company” and “Buzzwords, no proof” next to lines like these, and they are the parts a founder skips.
No address yet? Finding a startup founder’s email starts with the free lists and ends with a verified guess.
Which subject lines work for a founder?
Short, specific ones that name the role and their work. Backlinko’s study of 12 million outreach emails found that “subject lines between 36-50 characters get the best response rate”; its data is mostly content and link-building outreach, so read it as a guide to length, not a rule for job emails.
| Use | Characters | Avoid |
|---|---|---|
| Backend engineer for your payouts API | 37 | Application for SDE role |
| Android engineer, re: your offline mode | 39 | Seeking an opportunity |
| Built a Slack bot on your scheduling API | 40 | Resume for any suitable position |
| Three fixes for your signup flow, from a PM | 43 | Exploring opportunities |
| Data engineer, saw your Series A post | 37 | Job application |
Each line on the left tells the founder what you do and that you looked at their company. Each line on the right could be sent to anyone, and several of them appear word for word in Backdoor’s mock-up inbox.
How many times should you follow up, and what should each one say?
Up to three times, inside the original thread, several days apart, and each follow-up should add something new. Stop at the first reply, even a no.
The evidence leans toward following up. In Backlinko’s outreach data, one extra follow-up lifted replies by 65.8%. Hunter’s survey marks the limit: past the third follow-up, more recipients unsubscribe. Seibel’s advice to founders emailing investors is “Don’t send multiple follow-ups quickly.” Backdoor’s research page sets out the cadence it uses, three follow-ups in the original thread on days 3, 7 and 12, ending the moment the founder answers, and Backdoor says 4 in 10 of the founder replies in its data came after one of those follow-ups.
Day 3. Hi Ananya, one more detail: our retry queue cut failures most on bank holidays, when the downstream APIs were slowest. If payouts get busy around the festive season, that might be relevant. Still keen to talk.
Day 7. Hi Ananya, I wrote a short note on how we sized retry backoff for payouts: [link]. Useful whether or not you’re hiring.
Day 12. Hi Ananya, I’ll stop here so I’m not crowding your inbox. If an engineering role opens later this year, I’d be glad to hear from you.
Each one is shorter than the first email and gives the founder a new reason to answer. The last one closes the loop politely, which leaves the door open. Job-search follow-up tools compares the tools that send or draft these for you.
Can a tool write and send these founder emails for you?
Yes, with a different tool depending on who you are writing to. The table shows what each one documents for the steps that matter here: writing to the founder, sending from your own inbox, and following up.
| Tool | Emails founders | Sends from Gmail | Follow-ups |
|---|---|---|---|
| Backdoor | Finds founder emails and drafts notes Verified | Sends approved emails via your connected Gmail Verified | Follows up in the same thread until a reply Verified |
| Simplify | Not publicly documented | You send recruiter emails from the tracker via your connected Gmail Verified | Drafts follow-up emails for you to review and send Verified |
| Teal | Not publicly documented | Not publicly documented | Not publicly documented |
If writing five fresh founder emails a week is where you stall
Backdoor writes this kind of note to founders. It chooses the startups from that morning’s funding, launch and hiring news, looks up the founder’s address, and builds each draft from two inputs: your background and what it learned about the company. Its research page shows a sample draft broken into the same four pieces as the templates above: their news, your proof, why them, and a small ask.
The sentence only you can write is still yours to add. Nothing goes out until you answer the draft with SEND over iMessage or WhatsApp; EDIT and SKIP are the other replies. Sent notes leave from your own Gmail, the three nudges stay in that thread, and Backdoor texts you when a founder writes back. Finding startups and researching your background cost nothing; in India, the sending is a one-time ₹999 for 7 days.
Already applied and want to email the recruiter? Simplify
For a posted role you have already applied to, Simplify lets you write or generate a recruiter email from the tracked job and send it through your connected Gmail. Its help page is explicit that nothing in those conversations goes out automatically, so every follow-up is one you press send on. We found no mention of founders as recipients on its pages.
Writing every email yourself, with templates beside your job list
If you send everything by hand, Teal keeps templates next to the jobs you track. Teal says it has more than 40, covering each stage of a search, and the free plan gets you one per stage. Its pages describe templates, not sending; we found no mention of Teal emailing anyone on your behalf.
Five founder emails, sent by Friday
- Pick five startups that raised, launched or posted a role in the last month.
- For each, find one fact for the opening and one result of yours that maps to it. If you cannot find either, skip the company.
- Choose the template that fits your role, write five different emails, and read each one aloud. Cut anything you would not say to the founder’s face.
- Send them from your own inbox on a weekday morning, and put the day 3, 7 and 12 follow-ups in your calendar.
- At the end of the week, look at which openings got replies, and write next week’s five with that in mind.
How we chose
We compare tools on what their own public pages say, checked on the dates shown, and label every claim. How we compare tools.
FAQ
Cold email to startup founder for job
Keep it well under 100 words: open with something the company did recently, give one result of yours that maps to it, and end with one small ask such as a 15-minute call. Send it from your own inbox to the founder's work address, with a subject line that names the role and their work. If nothing comes back, nudge once in the original thread after three or four days.
Write a cold email to a startup founder for SDE role
Name the role and their product in the subject, for example "Backend engineer for your payouts API". In the body, mention one technical detail you noticed in their product or docs, one thing you built with a number attached, and a link to your code. Close with a short ask, and add your notice period only if it is short enough to help.
What subject line to use in a cold email to a founder for a job?
Use the role plus something specific to their company, such as "Android engineer, re: your offline mode". Avoid subject lines that could go to any company, like "Application for SDE role" or "Seeking an opportunity". Backlinko's outreach study found subject lines of 36 to 50 characters got the most responses, which is a useful length to aim for.
How many times to follow up on a cold email to a founder?
Up to three times, each in the original thread and spaced several days apart, with something new each time. Hunter's cold email research saw unsubscribes climb past a third follow-up, so stop there. If the founder replies at any point, even with a no, the follow-ups end.
Sources checked
Show 9 sources
- Backdoor: AI job agent that emails startup founders for you, checked
- 2,000+ Founders & HRs Hiring (Free List) - Backdoor, checked
- Do cold emails still work in 2026? What founder replies show (Backdoor research), checked
- The state of cold email 2025 (Hunter), checked
- What's the Best Word Count & Length for Cold Emails (Hunter), checked
- We Analyzed 12 Million Outreach Emails. Here's What We Learned (Backlinko), checked
- How To Cold Email Investors - Michael Seibel (Y Combinator), checked
- Email Integration, checked
- Job Application Tracker, Track & Organize Your Job Search, checked