Guides / Ideas and launching

Cold Email for Startups: A Practical Playbook with Templates

How to write cold emails that get replies: building a small target list, a four-part email structure, follow-ups, templates, and the rules to respect.

Mythex Team · 2026-09-29 · 7 min read

Cold email works for startups when it is small, specific and honest: a short list of people who clearly have the problem you solve, a short message that proves you did your homework, and one easy question to answer. It fails when it becomes a volume game with generic templates. This playbook covers the list, the message, follow-ups, deliverability and the rules — with templates you can adapt.

Cold email is one tactic inside a bigger plan. If you are still working out who your first customers are, start with how to get your first 100 customers, and for a full launch sequence see how to launch an app and get first users.

What cold email is good for at an early startup

Cold email is a direct message to someone you have no prior relationship with. For an early startup it is most useful for three jobs:

The learning use is underrated. If you do not yet know whether the problem is real, a cold email asking for an interview is easier to say yes to than a sales pitch. How to do customer interviews covers what to ask once you get the call.

Step 1: Build a small list you can defend

A good list is short and specific. Before adding anyone, you should be able to say in one sentence why this person, at this company, probably has the problem.

1. Write the filter. Role, company type, size and one trigger. Example (made up): "Operations leads at independent veterinary clinics with more than one location, who are hiring front-desk staff."
2. Find people who match. Company websites, industry directories, conference speaker lists, public posts in communities, and professional networks.
3. Record the reason. Next to each name, write the specific thing that made you pick them — a job post, a talk, a public complaint, a new location.
4. Start with 30–50 people. Enough to learn from, small enough to personalise.

Keep the list in a spreadsheet or a simple CRM with columns for name, company, role, source, reason, date sent, follow-ups and outcome. If you outgrow the spreadsheet, a simple CRM is a quick build.

Only collect work contact details that people have made available for business purposes, keep what you collect to a minimum, and delete it when you no longer need it. Buying large contact lists is where many founders get into trouble — both legally and with spam filters.

Step 2: Write the email in four parts

Most good cold emails fit on a phone screen without scrolling. A structure that works:

1. Why them. One sentence that could only be written to this person.
2. The problem. One sentence naming a problem people in their role commonly have — phrased as a question or observation, not a claim about them.
3. What you have. One or two sentences on what you built or are exploring, in plain words, with no adjectives doing the work.
4. One small ask. A question that can be answered in a few words.

Rules that help:

• Subject lines: short, lowercase-looking, specific. "question about your rota process" beats "Revolutionise your scheduling!".
• No attachments or many links in the first email. One link at most.
• Say who you are. Your real name, your company and a way to contact you.
• Make it easy to say no. "If this isn't relevant, just let me know and I won't follow up."

Templates you can adapt

These are starting points. Replace every bracket with something real; if you can't, that person probably shouldn't be on the list.

Template 1: Asking for a learning conversation

Subject: question about [task] at [company]

Hi [name],

I saw [specific thing: their post, talk, job listing] and it made me think you've dealt with [problem] first-hand.

I'm building a small tool for [role] at [type of company] and I'm trying to understand how teams handle [task] today — what's annoying about it, and what you've tried.

Would you be open to a 20-minute call next week? Not a pitch — I'm still deciding what to build.

If it's not a fit, no worries and I won't chase.

[Your name], [company], [one-line signature with website]

Template 2: Offering a pilot to a likely customer

Subject: [their tool/process] + [your product category]

Hi [name],

[Company] [specific trigger: opened a second location / is hiring for X], which usually means [task] gets harder to keep track of.

We built [product], which [does one concrete thing] for [type of business]. It replaces [the spreadsheet / email thread they likely use].

Would it be worth a 15-minute look? If it helps, I can set it up with your real data so you're not testing an empty app.

[Your name]

Template 3: Partnership

Subject: idea for your [newsletter / community / customers]

Hi [name],

I read [their newsletter / community] and noticed your audience asks about [problem] a lot — for example [specific thread or issue].

We make [product] for exactly that. Would you be interested in [a free guide we write together / an extended trial for your members / a short session]? Happy to do the work.

[Your name]

Step 3: Follow up without being annoying

Replies often come after a follow-up rather than the first email, so a short sequence is normal. A polite pattern:

Stop the moment someone asks you to, and record it so they are never emailed again. Don't send follow-ups that pretend to be replies ("Re:") when they aren't.

Step 4: Protect deliverability

If your emails land in spam, nothing else matters.

• Authenticate your domain. Set up SPF, DKIM and DMARC DNS records with your email provider. How domains and DNS work explains the record types.
• Consider a separate sending domain for outreach, so complaints don't affect the email your product sends to customers.
• Warm up slowly. A brand-new mailbox that suddenly sends many messages looks suspicious. Start with a handful per day.
• Send plain text. Heavy HTML, tracking pixels and many links make messages look like marketing mail.
• Watch bounces. Verify addresses before sending and remove any that bounce.

Step 5: Respect the rules

Anti-spam and privacy laws vary by country, and what applies can depend on where you are, where the recipient is, and whether you email a business address or a private person. For example, the US CAN-SPAM Act sets rules on honest headers and subject lines, identifying yourself, including a physical address and honouring opt-out requests. In the EU and UK, GDPR and related e-privacy rules affect whether you can email someone without prior consent and how you must handle their personal data, including having a lawful basis and telling people where you got their details if they ask.

This is general information, not legal advice. Before running outreach at any scale, check the rules for the countries you are emailing into or ask a qualified adviser. Good practice that helps almost everywhere: identify yourself clearly, make opting out easy, honour opt-outs immediately, keep only the data you need, and never mislead in the subject line.

Step 6: Measure and improve

Track a few numbers per batch of emails: sent, bounced, replied, positive replies and calls booked. With small lists, look at the replies themselves more than the percentages — they tell you which sentence landed and which objection keeps coming up.

Change one thing at a time: the list filter, the subject line, the problem sentence or the ask. If replies are polite but negative, the problem may be the audience, not the wording. If there are no replies at all, check deliverability first.

Common mistakes

• Writing about yourself. The first two sentences should be about them.
• Fake personalisation. "I loved your recent post!" with no detail is obvious.
• Asking for too much. "Book a 60-minute demo" is a big ask from a stranger.
• Sending before the landing page is ready. Interested people will look you up. Make sure your site explains what you do — see how to build a landing page that converts.
• Ignoring opt-outs. It is disrespectful and, in many places, against the law.

Cold email checklist

• Clear filter for who you're emailing and why
• 30–50 people with a written reason for each
• SPF, DKIM and DMARC set up for the sending domain
• Short email: why them, problem, what you have, one ask
• Your name, company and an easy opt-out in every message
• Two or three follow-ups at most, each adding something new
• Opt-outs recorded and honoured
• The rules for your recipients' countries checked

Where Mythex fits

Cold email sends people to your product, so it helps to have something real to show. With Mythex you can build the landing page, a working first version or a demo populated with a prospect's sample data by describing it in chat, then publish it to a public URL. If you want to track your outreach in your own tool, a small CRM or outreach tracker is a quick build — the CRM use case in the docs shows a starting point. Mythex doesn't send email for you; if your app needs to send messages, the agent wires up your own email provider, as described in the send email recipe.