---
url: "https://indiehunt.io/studio/how-to-send-cold-emails-to-your-first-b2b-customers"
markdown: "https://indiehunt.io/studio/how-to-send-cold-emails-to-your-first-b2b-customers.md"
category: "Growth"
type: "studio"
published: "2026-10-26"
word_count: 2658
---

# How to Send Cold Emails to Your First B2B Customers

> How to send cold emails to your first B2B customers: protect your domain, follow the law, hand-build 50 leads, write five plain sentences, follow up twice.

## Article

Cold email can work for your first B2B customers if you treat it like a short, honest letter to one person, not a campaign. Send it from a separate domain that is set up properly, so your main domain is safe. Pick a buyer you can name, with a pain you can see from the outside. Hand-build a list of about 50 people with a real trigger for each one. Write four or five plain sentences that mention the trigger, guess the problem, offer one bit of proof and make a small ask. Follow up twice at most, honour every opt-out straight away, and judge the whole thing on replies and meetings, not opens. At founder volume this is a handful of emails a day, closer to a sales conversation than to spam.

This guide is for indie SaaS founders who sell to businesses and have somewhere between zero and about 20 customers. The product, the people and the example emails below are made up. The rules and laws mentioned are real and linked, but none of this is legal advice.

## When does cold email make sense for your first customers?

Cold email is a good fit when three things are true at once:

- You sell to businesses. A company or a person buying for their work, not a consumer at home.
- You can name the buyer. A role at a type of company, like "office manager at a general contractor with 10 to 50 staff", not "anyone who uses spreadsheets".
- The pain is visible from outside. You can spot signs of it in public: a job post, a complaint, a tool they use, a change they just made.

It is a poor fit when you sell to consumers, when the buyer is impossible to identify, or when you cannot yet say in one line what problem you solve. More emails will not fix any of those. Go back to talking with users, or to the broader playbook for [getting your first 10 paying customers without a launch day](https://auraplusplus.com/studio/how-to-get-your-first-10-paying-customers-without-a-launch-day), and come back to cold email when you can write that one line.

If someone can introduce you, that beats a cold email. Cold email is for people you have no path to yet.

## How do you protect your main domain before you send anything?

Your main domain sends password resets, receipts and customer replies. If cold emails get marked as spam, that reputation can follow the domain, so many founders send cold email from a second domain that clearly belongs to the same company, for example a "get" or "try" version of the name, with the website redirecting to the main site. A subdomain is another option, though it sits closer to your main domain's reputation.

Then set up the basics on that sending domain:

- Authentication. SPF, DKIM and DMARC tell inbox providers that you are allowed to send for the domain. I won't repeat the setup here, because the walkthrough on [checking SPF, DKIM and DMARC before you send](https://praneetbrar.hashnode.dev/check-spf-dkim-dmarc-before-launch-email) covers the records step by step.
- A real mailbox. A normal business mailbox with your real name, which you read every day.
- Warm-up, honestly. A new domain has no history. Use it for a week or two to send normal emails to people who know you and will reply, then start cold email at a handful a day and raise it slowly. Google's guidance is to start low, send at a steady rate and avoid sudden spikes. I would skip anything that promises to fake engagement for you.
- Plain text. No images, no tracking pixels, no HTML templates, at most one link.

### What do the Gmail and Yahoo sender rules mean for you?

Google's [email sender guidelines](https://support.google.com/a/answer/81126?hl=en) set requirements for everyone sending to personal Gmail accounts: SPF or DKIM, valid forward and reverse DNS, a TLS connection, and a spam rate reported in Postmaster Tools below 0.3%. Google adds that you should aim to stay below 0.1% and never reach 0.3%. Senders of more than 5,000 messages a day to Gmail accounts must also add DMARC, alignment and one-click unsubscribe. Yahoo's [sender best practices](https://senders.yahooinc.com/best-practices/) list the same 0.3% spam rate ceiling and similar bulk sender rules.

A founder sending 15 emails a day is nowhere near the bulk threshold. The spam rate is what matters, and the math is unkind at small numbers: two spam reports in a week of 75 emails is far above 0.3%. The best protection is sending only to people with a real reason to care.

## Is it legal to send cold emails to businesses?

Generally yes, with conditions that depend on where the recipient is. This is a plain summary, not legal advice; if unsure, read the source or ask a lawyer.

### United States: CAN-SPAM

The FTC's [CAN-SPAM compliance guide](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business) says the law covers all commercial email and makes no exception for business-to-business messages. The main rules: accurate "From", "To", "Reply-To" and routing information; a subject line that matches the content; a clear disclosure that the message is an ad; your valid physical postal address; a clear way to opt out; and opt-outs honoured within 10 business days. The guide also lists harvesting addresses or generating them with a "dictionary attack" among the aggravated violations, which is one more reason not to guess addresses at random.

### United Kingdom: PECR

The ICO's guidance on [electronic mail marketing](https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/guide-to-pecr/electronic-and-telephone-marketing/electronic-mail-marketing/) says you can send marketing emails to corporate bodies, such as companies, limited liability partnerships and government bodies, but sole traders and some partnerships are treated as individuals, which means you need their specific consent. The ICO recommends keeping a "do not email" list of businesses that object, and notes that emailing a named employee can still bring in data protection rules. The page also says it is under review after the Data (Use and Access) Act, so check it again before you start.

### European Union: GDPR

An email to a named person involves personal data. GDPR [Recital 47](https://gdpr-info.eu/recitals/no-47/) says direct marketing "may be regarded as" a legitimate interest, but only after a careful balancing test, and the person's reasonable expectations count. [Article 21](https://gdpr-info.eu/art-21-gdpr/) gives people the right to object to direct marketing at any time, says you must stop when they do, and says the right must be brought to their attention by the first message. EU countries also have their own e-privacy rules for business email, so check the country you are emailing.

The practical version for all three: be truthful about who you are, write to people about their work, include your company address and a line like "Reply 'no' and I won't email again", make it plain that you are offering something (the FTC allows leeway in how), and keep a do-not-contact list you actually check.

![indiehunt-2026-10-26-inline-1.jpg](https://txmhk1zrnc.ufs.sh/f/xSkWTCqmKWx9heXKG4RJkXTmPie5h04ySvxCrwdZbuRtDGBl)

## How do you build a list of 50 people by hand?

Fifty is enough for a first round, and small enough to research each person properly. The rule: nobody goes on the list without a trigger, a public sign that the problem might be live for them right now. Good triggers include:

- Job posts. Hiring for the role you help, or listing the chore you remove.
- New funding or growth news. More staff or locations usually means more of the painful work.
- Tool reviews. A frustrated review of the tool you replace, under a real name or company.
- Public complaints. A forum, community or LinkedIn post describing exactly the problem.
- Changelog and hiring signals. A launch that creates the problem you solve, or a new team that will feel it.

Keep it all in one sheet. Here is the shape I would use, with a made-up row:

Company

Person and role

Trigger (with link)

Problem guess

Email source

Status

Made-up builder, 30 staff

Office manager

Job post for a "project coordinator" that mentions chasing subcontractor paperwork

Insurance certificates tracked in a spreadsheet and inbox

Team page on company site

Sent day 3

The "problem guess" column matters most. If you cannot fill it in specifically, skip the person for now. Once replies start, move live conversations into whatever you use to track deals; there is a separate guide on [setting up a simple sales pipeline as a solo founder](https://auraplusplus.com/studio/how-to-set-up-a-simple-sales-pipeline-as-a-solo-founder), so I won't redo that here.

## How do you find and verify email addresses without buying a list?

Do not buy lists. Google's guidelines say plainly not to purchase email addresses, the ICO notes that the soft opt-in never covers bought-in contacts, and old lists mean bounces that hurt a new domain.

Instead, in rough order of quality:

1. The company website. Team pages, contact pages, press pages and blog author bios often list addresses.
2. Things the person published. A talk, a podcast page or a public profile.
3. The company's own pattern. If you can see two real addresses at the company and they follow the same format, the third person's address is probably that format too. Treat it as a guess, not a fact.
4. Ask. A short note to a general address asking who handles the thing you help with.

Verification tools can flag addresses likely to bounce, but they cannot tell you whether the person cares. If you are not fairly confident in an address, skip that person.

## What should a first cold email say?

Four or five sentences, in this order:

1. The trigger. What you saw and why you are writing to them.
2. The problem guess. What that might mean for them, phrased as a guess.
3. The proof. One concrete thing your product does, or a customer like them.
4. The small ask. A yes or no question, not a 30-minute meeting.
5. The opt-out. "Reply 'no' and I won't write again", plus your address in the signature.

Here is a made-up example. Quillpail is a fictional tool that tracks subcontractors' insurance certificates for small general contractors.

Part

Weak version

Better version

Opening

Hope this finds you well! I'm the founder of Quillpail, the leading compliance platform.

Saw your project coordinator job post mentions chasing subcontractor paperwork.

Problem

Companies like yours lose time and money every day.

My guess is someone on your team spends part of every week checking which insurance certificates have expired.

Proof

We use AI to transform your workflow end to end.

I built Quillpail to read the certificates as they arrive and email the sub 30 days before one expires.

Ask

Do you have 30 minutes this week for a demo?

Is that a real problem for you, or have you already got it handled?

Close

Looking forward to hearing from you!

If it's not relevant, just reply "no" and I won't email again.

The better version mentions something only this person would recognise, makes no claim it cannot back up, and asks a question they can answer in five seconds.

## How do you write a subject line for a cold email?

Keep it short and honest, like an email from a person, not a newsletter. A few patterns:

- The trigger: "your project coordinator post"
- The problem: "expired insurance certificates"
- A plain question: "question about sub paperwork"

Never fake a reply with "Re:" or "Fwd:"; Google's guidelines say not to unless it really is one, and CAN-SPAM requires subject lines that match the content. No urgency tricks or emoji.

![indiehunt-2026-10-26-inline-2.jpg](https://txmhk1zrnc.ufs.sh/f/xSkWTCqmKWx9LdlmoqOdJwXvPk48AGU3H1bn2SagyrxeKciY)

## How do you follow up without being annoying?

Two follow-ups at most, spaced out. A simple rhythm is the first email on day 1, a short follow-up around day 4 or 5, and a last one around day 10 to 12. Send each follow-up as a reply in the same thread, so the context is right there.

- Follow-up 1: add one new thing, like a short example. Never just "bumping this up".
- Follow-up 2: close the loop politely. "I'll stop here. If certificates ever become a headache, this thread will still be here."

Then stop. A third or fourth chase is exactly the kind of mail people report as spam.

## How should you handle replies, including "not now" and "unsubscribe"?

Reply the same day if you can. Speed and a human tone are your edge over bigger companies.

- Yes or curious: answer their question in the email, then offer a short call with two specific times.
- Not now: thank them, ask if you can check back in a few months, and write the date in your sheet. Then do it, once.
- Wrong person: ask who handles it, and mention the referral when you write to them.
- No: thank them and stop. Never argue.
- Unsubscribe, stop, or anything like it: add them to your do-not-contact list the same day, even though the US gives you 10 business days. Do not send a "sorry to see you go" email.

## What should you track, and why not open rates?

Track three numbers per batch: **reply rate** (any reply divided by people emailed), **positive reply rate** (interested or "tell me more" divided by people emailed) and **meetings booked**. Watch bounces and opt-outs as warning lights: rising bounces mean sloppy address finding, rising opt-outs mean the list or message is off.

Skip open tracking. Apple's [Mail Privacy Protection](https://support.apple.com/guide/mail/protect-email-privacy-mlhlp1205/mac) downloads remote content in the background when a message arrives, not when it is read, so opens from Apple Mail users look like opens whether the person read it or not. Google's sender guidelines also say Google does not track open rates and cannot verify open rates reported by third parties. A tracking pixel also turns your plain-text email into HTML. Replies are the honest number.

## Do you need a cold email tool?

Not for the first 50 emails. Plain Gmail or Google Workspace, your sheet and a few saved drafts are enough, and writing by hand forces the research.

A tool earns its place when you are emailing a few hundred people a month and losing track of follow-ups. The two categories are mail merge add-ons inside Gmail and dedicated sequencing tools that schedule follow-ups and stop when someone replies. Check that it sends through your own mailbox, stops on reply, sends plain text without tracking and makes opt-outs easy. Ignore promises of guaranteed inbox placement.

## What are the common cold email traps?

- Sending from your main domain. One bad week can affect your product's emails.
- Volume before message. If 50 careful emails get no positive replies, 500 sloppy ones will not fix it.
- Fake personalisation. "Loved your recent post!" with no detail reads as automated, because it is.
- Hiding the opt-out. It is required in many places, and a visible one gives people an option other than the spam button.
- Emailing UK sole traders as if they were companies.
- Giving up after one batch. Rewrite the message or change the segment, then send another 50.

## What does a 14-day cold email plan look like?

Days

What to do

Done when

1 to 2

Write the one-line problem and buyer role. Set up the sending domain, mailbox, SPF, DKIM, DMARC and a signature with address and opt-out line.

Records check out; mailbox works

3 to 5

Build the 50-row list sheet. Use the mailbox for normal email meanwhile.

No blank triggers

6

Write the first email and two follow-ups. Read them aloud.

Five sentences or fewer each

7 to 10

Send 5 to 10 first emails a day, written one by one. Reply to every response the same day.

All 50 sent

11 to 12

Send follow-up 1 to everyone who has not replied or opted out.

Follow-ups sent

13 to 14

Count replies, positive replies, meetings, bounces and opt-outs. Decide: new message or new segment. Start the next 50; final follow-ups go out over the next few days.

Numbers in the sheet; next list started

This plan is a planning guess. If research takes longer, let it.

## Cold email FAQ

### Is cold email legal?

In many places, yes, if you follow the rules: truthful headers, a postal address and fast opt-outs under CAN-SPAM in the US, corporate bodies but not sole traders under PECR in the UK, and a legitimate interest test plus national rules in the EU. Not legal advice; see the legal section above.

### How many cold emails should I send per day?

At the start, 5 to 20 a day from a new domain, written by hand. Raise it slowly only if bounces and complaints stay low. Research should be your bottleneck, not sending.

### Should I use open tracking?

No. Apple Mail Privacy Protection makes opens unreliable and the pixel turns a plain email into HTML. Track replies instead.

### What reply rate is good?

I would not trust a universal benchmark; it depends on the market, the list and the offer. Use your first 50 as your baseline and try to beat it. If a full batch with follow-ups gets no positive replies, change the segment or the problem guess before anything else.

And once your first customers are happy, [IndieHunt](https://indiehunt.io/) is a good place to launch the product to other indie makers.

## Links

- Article: https://indiehunt.io/studio/how-to-send-cold-emails-to-your-first-b2b-customers
- AI-friendly Markdown: https://indiehunt.io/studio/how-to-send-cold-emails-to-your-first-b2b-customers.md
- Studio index: https://indiehunt.io/studio

## Featured image

- https://txmhk1zrnc.ufs.sh/f/xSkWTCqmKWx9owDmVe3waZD4fI5qz2hmxQ0kUL1XNBntoS7M

## Explore

- [More in Studio](https://indiehunt.io/studio)
- Category: Growth


_HTML version: https://indiehunt.io/studio/how-to-send-cold-emails-to-your-first-b2b-customers_
