Cold email for SaaS founders who have to send it themselves
As a founder, send fewer emails to better-fit people. Name a specific problem you believe they have, say what you built, ask whether it is a real problem for them. Keep batches small, authenticate your sending domain, and answer replies yourself, because the conversation is the research.
Founder email is an advantage you can lose
A message from the founder is read differently from a message from a sales team. That advantage disappears the moment it reads like a template sent to hundreds of people.
Protect it by sending in small batches and writing each first line from something you actually saw. If you cannot say why you wrote to this person, do not send.
Sell the problem, not the feature list
Founders often describe the product. Buyers are deciding whether the problem is urgent. One sentence about the problem, one about what you built, one question is enough.
If they reply with a correction to your problem statement, that is a win: you just got research you could not buy.
What to do after the first ten replies
Read them together before changing anything. If the same objection appears three times, the message or the segment is wrong, not the offer.
Write the objection down in your own words and use it in the next batch. That loop is the entire advantage of a founder doing the sending.
The metrics a founder should watch
Replies per hundred sent, and the reasons behind the replies. Open rates are unreliable and easy to game; a reply is an action a person took.
Look at which first lines produced replies. Keep three that worked and write from those patterns next, rather than starting from a blank page each week.
What to do when a big logo replies
Slow down. A large company reply usually means procurement, security questions and a longer cycle, not an immediate deal. Answer promptly and ask what their process looks like before promising dates.
Do not let one exciting reply distract from the segment that is quietly producing consistent conversations.
A week of founder sending, concretely
Monday: write twenty first lines from something you saw. Tuesday: send and answer everything that comes back. Wednesday: read the replies together and change one sentence of the problem statement.
Thursday: send twenty more with the revised sentence. Friday: decide whether the segment is worth another week, and write down why.
That week produces more product insight than most customer-development interviews, and it costs an hour a day.
The sentence you are really testing
Every batch is a test of one sentence: the problem statement. If the reply corrects you, the sentence was wrong, and the correction is the most valuable output of the week.
Write the corrected sentence down before you send the next batch, or you will drift back to the version you first imagined.
What good looks like after a month
You have written to a hundred people by hand, changed one sentence four times, and can describe the objection in the customer's own words.
That sentence is now the opening of your pitch deck, your onboarding and your next twenty emails.
How to know the segment is right
You know it is right when replies include corrections rather than silence. A correction means the person recognised themselves in the problem and cared enough to fix your description.
Silence across forty messages usually means the segment is wrong, not the copy. Change who you write to before changing what you say.
Founder cold email: what works at this size
| Choice | At 20 emails a day | At 500 a day |
|---|---|---|
| First line | Written per person | Becomes a segment label |
| Volume | Small and consistent | Needs infrastructure |
| Replies | Answered by you | Handed to someone else |
| Learning | Direct and fast | Indirect and slow |
Scrape.Email plans start at $49 per month for 50,000 credits, one credit per task.
Founder send checklist
- Ten named people you can justify
- One problem sentence
- One product sentence
- One question
- Authenticated sending domain
- Twenty a day maximum at the start
- Replies read the same day
A worked example, hypothetical
A founder writes to 20 heads of operations at mid-sized logistics firms, each with a line about how their tracking page loads. Four reply, two with corrections about how the problem actually manifests.
She rewrites the problem statement using their words and sends 20 more. The second batch produces seven replies. Nothing scaled; the message just got more accurate.
- 1.Write 20 by hand
- 2.Read every reply
- 3.Rewrite the problem statement
- 4.Send 20 more
What this will not do
- Founder time is the scarcest resource in the loop.
- Small batches do not produce statistically strong conclusions.
- A reply is not a sale; the product still has to be right.
Questions people ask about this
Should a founder use automation?
For sending and tracking, yes. For the first line, not until you know what works well enough to describe it to a machine.
How do I find the right people?
Start with companies that show the symptom, then find the role that owns it. Category and title filters are enough for the first hundred.
What if nobody replies?
Change the segment before the copy. A founder writing to the wrong role will get silence no matter how good the sentence is.
How long before cold email produces anything?
It depends on the segment and the offer. The honest measure is whether replies are increasing as your message improves, not a fixed number of weeks.
Should a founder send from the company domain?
It reads as the company, which helps. It also puts campaign risk on the main domain, so authenticate it and keep volume modest.