Cold outreach: contact the right person (and for a reason)

You've built the product, asked everyone you know for an introduction and reached the edge of your immediate network. That's when cold outreach comes into play: a way to contact the people you think should care, although the apparent ease of buying 10,000 names can make the route look much simpler than it is.

The work begins before the email. You need to know why this person at this company might care now. A job title and a mail-merge field won't answer any of those questions, even if the software has helpfully colored them green.

Cold outreach works best for B2B products and services where you can identify the likely buyer. It can run as a small test alongside warm introductions when both lead to the same kind of customer. Broad consumer outreach is a poor fit, and messages to sole traders or other individuals can fall under stricter consent rules.

Start with ten

Your first batch is ten carefully researched people. That is large enough to expose an obviously weak assumption and small enough for you to understand why each person is there.

Christina Gilbert, visiting Y Combinator advisor, recommends making at least 100 approaches manually before automating outreach. Treat this number as a learning guide: by the time you've worked through several small batches, you should be able to describe who replies, why they respond, and the wording they use. Reaching email 100 with no better idea who should receive email 101 records activity and leaves you no further forward.

During this early manual work, never send more than 30 cold emails from one inbox in a day: this preserves your domain health. That's a conservative operating ceiling for this playbook; it can't guarantee delivery, and it doesn't replace the technical checks later in this chapter.

Targeting comes first

Before writing, check the person, the company and the current reason for contact, in that order.

A recent public event gives you the easiest reason to write. The company may be hiring for the work your product changes, expanding into a new market, replacing a tool or discussing the problem in public. You don't need to manufacture an event when the person and company are a strong fit; you still need a specific reason that would make sense to the recipient.

Record the source and the date you checked it. Public information can support your reason for writing, although public availability doesn't automatically give you permission to collect or use every detail you can find. Nobody needs an email proving that you found the photos from their 2018 charity fun run.

Your prospect record needs enough information to show your working:

• who the person is and what they appear to own;
• why the company fits;
• the event or other reason for contact;
• the public source and date;
• the route you plan to use; and
• the assumption this message is testing.

A database can help you find a possible person; it's up to you to decide whether they belong in the test.

Write to one person

The first message has five purposes:

1. Give the real reason you're writing.
2. Connect it to a pressure or result the buyer might recognize.
3. Explain how you can help in one sentence.
4. Include one piece of proof you have.
5. Offer one next step that's easy to answer.

Plain and skimmable usually means fewer than 150 words, although 149 vague words don't become good outreach by passing a word-count test. The message should make sense without a slide deck, a feature list or three paragraphs about the company you founded.

The next step depends on what the buyer has already done. A specific question fits somebody who may only be exploring the problem. A short comparison call or bounded test can suit a buyer who has acknowledged the need. A demo is reasonable when the company is actively evaluating software; asking everybody else to “book a demo” makes them do too much work to discover why you emailed.

Here is a fictional example. MesaOps is an early B2B product that helps customer-success teams manage complex client onboarding. Its founder sees that Northstar, a UK limited company, is advertising three enterprise onboarding roles.

Subject: Enterprise onboarding at Dunder Mifflin

Hi Michael,

I saw Dunder Mifflin is hiring three enterprise onboarding managers. When that volume grows, the handoffs between sales, implementation and customer success can become difficult to track.

I've built MesaOps to give customer-success teams one view of the decisions, owners and outstanding work for each onboarding. I led enterprise onboarding operations for 6 years before building it, so I truly known the pain points of the process inside-out.

Would it help if I sent over the two-minute workflow so you can tell me whether it resembles the process you're hiring for?

Jane Doe

The hiring advert supports a reasonable question; it doesn't prove that Dunder Mifflin's process is broken. If the company had also published a request for onboarding software, the stronger buying signal could support an invitation to see the product.

The inbox sees two lines

Many inboxes show the opening words beside the subject, so the subject and preview need to do different jobs.

The second version gives the recipient a reason to understand the email before opening it. It doesn't need clickbait, a false Re: or a mysterious subject designed to resemble a message from their accountant.

Use the proof you have

Pre-revenue founders often have more evidence than they think, but each type proves something different.

The description in the MesaOps email is modest because modest is accurate.

Follow up with new information

One first message and no more than four follow-ups is the ceiling. Start with at least 48 hours between messages, then adjust for the channel and the decision. You can stop after two or three when another email would add nothing.

Christina Gilbert says the close-the-loop email is often the most effective. It removes the low-level irritation of an unresolved sequence and gives the recipient a straightforward way to answer:

Hi Michael - I'll stop here after this note. If you're reviewing enterprise onboarding at a later time, I'm happy to send the short workflow then. If it isn't relevant, no reply needed.

There is no guilt, countdown or threat to give the slot to somebody else. An opt-outA request to stop receiving marketing messages. The address should be added to a suppression list so it isn't contacted again by mistake., direct no, bounceAn email the receiving server couldn't deliver. A hard bounce usually means the address or domain doesn't exist and should be suppressed from future sends. or legal concern ends the sequence. A clear lack of fit does too.

Choose one route

Email, LinkedIn, phone, a referral or a conversation after an event can all work - the best route is the one this buyer uses for conversations of this kind. A second channel should add context, such as referring to a substantive LinkedIn exchange before emailing. Appearing in somebody's inbox, LinkedIn messages and missed calls before they've had their second cup of coffee adds recognition of a less helpful kind.

The rules still travel with the message. Moving an approach into a social direct message doesn't remove privacy law or the platform's own restrictions.

Check the sending setup and the law

Your first test should come from an address that clearly belongs to the business. Four checks cover the practical minimum:

A separate sending subdomainA subdomain used for one type of email, such as `outreach.example.com`. It still belongs to the real business and needs its own correct authentication. can protect different types of company email. It should clearly identify the real business; deceptive lookalike domains have no place here.

Google, Yahoo and Microsoft publish different requirements according to sender volume. Their bulk thresholds are compliance limits; they don't suggest an appropriate campaign size. The 30-per-inbox ceiling in this chapter remains much lower.

Cold email law depends on who receives the message and where they're located:

Use this table as a starting point and obtain legal advice when the recipient type or jurisdiction is unclear. Public availability isn't automatic permission, and tracking pixels can bring additional privacy rules that you don't need at an early stage. Your email service and the recipient platform may also set stricter rules than the law, so check their current terms before the first send.

AI can prepare the work

AI can summarize public information you've supplied and organize the prospect record. It can also prepare a draft or compare two versions. You still decide whether the person belongs in the test; every fact, final edit, and send needs your approval.

It can't invent personal details or infer a private problem from a public event. It also shouldn't send on its own. If the draft says you loved somebody's recent post, reading and loving the post remains a fairly reasonable entry requirement.

Read the results in the right order

Silence is normal. Instantly's 2026 benchmark report, based on billions of interactions across active customer workspaces, reports a 3.43% average reply rate. Instantly sells cold-email software and counts every reply, including negative ones; it doesn't measure positive replies or meetings. Use the figure only to understand how common silence is.

For each batch, keep three small groups of numbers:

An objection or a clear no can improve the next decision even though neither looks exciting in a dashboard.

Weak results should be checked in this order:

1. Was it the right person?
2. Was it the right company?
3. Did the subject and preview establish relevance?
4. Did the message and next step fit the situation?
5. Did your website and profile support what you said?
6. Was the message delivered and legally compliant?

When those six checks hold up across a meaningful manual sample, and nobody engages, the question moves to the market, the problem or what you're offering. More volume would give the same assumptions a larger audience.

Your first manual outreach test

The cold outreach record gives you space to research ten prospects and draft the first message. It also contains the follow-up, sending and legal checks, followed by a blank results log.

I'm preparing a first manual cold-outreach test for 10 B2B prospects.
Use my attached cold outreach record, positioning and supplied public sources.
Don't send messages, contact anyone, enrich personal data or change an account.

For each prospect:
1. Separate the facts in my sources from my assumptions and missing information.
2. Assess the person, company and current reason for contact. Remove anyone
   whose fit depends on an invented need, private information or unsupported
   job-title assumption.
3. Record the public source and date for every reason to write.
4. Draft one plain first message, usually under 150 words. Include the real
   reason for writing, a plausible pressure or result, one sentence on how I
   can help, one truthful proof point and one easy next step.
5. Match the next step to the buying signal. Don't default to a demo.
6. Review the subject and opening preview together.
7. State what any supplied proof establishes and what it can't establish.
8. Suggest the job of each possible follow-up, within a five-message total
   ceiling and my stop rules. Don't draft an endless sequence.
9. Flag the recipient type and jurisdiction for human review. Don't give a
   legal clearance or assume a business address may always be contacted.
10. Leave all send and result fields blank for my approval.

Return standard Markdown in my first person. Don't invent events, quotations,
customer results, urgency, familiarity or personal details. Mark every unknown
as unknown. Stop with the prepared record for human review.

Once the record contains ten people you can defend, one message you can stand behind and a checked route to contact them, the test is prepared. Sending remains your decision; a reply moves the work into the founder-led sales conversation.