How to write a cold email worth answering

I’ve sent 10,000+ cold emails. Most got no reply.

I’ve sent more than 10,000 cold emails in my lifetime. One of my favorite outcomes started with a request to interview a senior executive for a blog. The blog already had great guests and an audience, which helped make the invitation interesting.

That interview became a real friendship. He has shared wisdom and guidance throughout my career. Pretty wild, considering it started with an email. I could give him a reason to talk, but I had no idea we’d still be in touch years later.

Before writing, I’d try to answer two questions: why this person, and why would they want to hear from me? Maybe you have a question about something they built. Maybe you can offer an interview or share an idea. If the only answer is that they’re successful, spend a little more time figuring out what you’re actually curious about.

Also, the vast majority of my cold emails have gone unanswered. Even the ones I put thought into. I want to be clear about that because the friendship stories are the ones I remember and tell. They don’t represent what happens after every email.

Choose the person before you write the message.

“I want to meet more successful people” leaves you with an enormous list and very little to say. Get closer to the actual thing you’re curious about. Maybe you’re starting a writing group and want to understand why some communities feel welcoming while others feel intimidating.

Now you can look for someone who has worked on that problem. Read their post, listen to the relevant part of their interview, or try what they built. You need enough context to explain why their experience matters to your question.

Check whether they have already answered it. If they have, try the advice first. Your email can then describe what you tried and where you got stuck. That gives you much more to talk about than “Any tips?”

The best emails I send feel like they could only be for that person. I’m looking for what lights them up, something we both care about, or a real opportunity I can offer. Personalization goes much further when I actually want to hear the answer. A sentence about their job title rarely does that on its own.

• Write down the question you are trying to answer.
• Find a person whose actual work makes them relevant.
• Read what they have already shared about it.
• Choose one detail that connects their experience to your situation.
• Use a public professional contact method or a channel where they invite messages.

A networking cold email template you can make your own.

The examples below are made up to show the process. Maya, the writing group, and the conversation are fictional.

Imagine you run a small writing group. People sign up, but few post. Maya wrote about a buddy program in her community. That gives you a real starting point.

Subject: Networking

Hi Maya,

I’m passionate about community building and really admire your work. I’d love to pick your brain and hear about your journey. Would you have 30 minutes for a coffee chat sometime?

Subject: Your buddy program for new members

Hey Maya!

Your post about pairing new members with regulars got me thinking. I run a small writing group, and people join but rarely post.

Did you start the buddy program with everyone, or test it with a few volunteers? I’d love to try something similar.

Thanks!
Sydney

Make each sentence earn its place.

The second email tells Maya which part of her work caught your attention. It explains your situation in one sentence. And it asks about a decision she actually made. She could answer while waiting for a meeting to start.

The first email asks her to choose the topic, decide what advice might help, and find time on her calendar. “Pick your brain” hides all that work in a friendly phrase.

Notice what the better version leaves out: your full background, a paragraph about how busy she must be, and a list of unrelated compliments. You can be warm without making someone read much. Read the draft on your phone. If the question is buried below your biography, move it up.

Write a subject line that says what you want.

Give the person a clue about why you’re writing before they open the email. “Your buddy program for new members” names the thing you want to discuss. “Interview invitation: starting a neighborhood reading group” tells them the topic and the ask. Either is easier to make sense of than a mysterious “Opportunity.”

Compare that with “Quick question” or “An amazing opportunity.” Those phrases tell the recipient very little. They are not automatically wrong, but a more specific line usually lets you say something useful with the same space. Avoid implying urgency you do not have, a shared friend who did not introduce you, or an existing conversation that never happened.

Keep the subject consistent with the body. If you say interview invitation, the email should explain the interview. If you say a question about a particular project, ask about that project. Reusing the same thread for a completely different request can hide the change of purpose. A fresh subject makes the new request easier to understand.

I wouldn’t spend an afternoon trying to invent the perfect subject line for one email. Pick something clear and true. The interesting part should be what you’re asking them about.

You can be interesting before you have impressive credentials.

Relevant context helps someone understand who is writing. For my blog invitation, existing guests and an audience mattered. For a technical question, a small thing you built may be more useful than a prestigious company name.

If you’re starting out, show the work you have done. “I interviewed five people who run local clubs, and they all mentioned this problem” gives someone something to react to. Use the number only if it is true. A thoughtful observation can also be enough.

One useful link usually does more than five profiles. Tell them what they’ll find if they click it. The email itself should still make sense without requiring homework.

Early on, useful proof of work included paying customers, advisors, growth, and shared connections. Those gave people something concrete to evaluate before they knew me. Use the strongest thing you can truthfully show. A small project with real users gives you a more interesting starting point than trying to sound like a much bigger company.

I made a one-page welcome guide for our writing group. I’m stuck on how much guidance to give before it starts feeling like homework. Your community seems to handle that well.

Choose an ask that fits what you need.

A call can be great. It also takes more coordination than a written answer. Decide whether talking live would make the exchange better, then explain why.

If you’re inviting someone to a blog interview or an event, make the invitation concrete. Include the topic, who it is for, the format, and the preparation involved. If your audience is small, describe it honestly. A focused audience can still be interesting.

If you want investment, a job, or a customer conversation, say that. Someone who agrees to a casual conversation should understand what you hope to discuss.

You have one specific question.

Ask it in the email. Let a written answer be a complete success.

You need to explore a problem together.

Explain the topic and ask whether a short call would be useful. Offer email as an option if it would work.

You want to interview them.

Name the real publication or project, audience, topic, format, and expected time.

You mainly admire their work.

A short, specific appreciation can stand on its own. You do not need to attach a meeting request.

Make an interview invitation worth the time it takes.

For the blog invitation, the audience and earlier guests mattered. I think that gets lost when people look only at the wording of a successful cold email. We had something to offer. Start there if you want to try interviews yourself.

A small audience can still be interesting. I’ve done this several times in my career, and even a few hundred readers has sometimes been enough. Explain who the interview is for and why you’d love to talk to this person. If it’s your first interview, say so. You can still prepare thoughtful questions and make something you’re proud to share.

Give the person a way to judge the work involved. Are you asking for written answers to three questions, a recorded conversation, or a live appearance? Will you send topics beforehand? Where will the finished piece appear? Say what you intend to do, and only promise preparation or review that you will actually provide. Someone should not discover halfway through a casual call that you intend to publish it.

After a yes, make the practical side easy. Send the agreed topics, confirm the format, and do the preparation. If you promised a link when the interview goes live, send it. You have a natural reason to reconnect because you made something together. Whether that grows into a friendship depends on the interest on both sides. An interview is already a worthwhile outcome on its own.

My usual process was to write up the conversation, often ask the guest to confirm it or make changes, then publish. Guests would often share it too. That gave us a reason to stay in touch through the project, without needing to pretend we were already friends.

Most of those conversations ended with the interview. Three became friendships. One executive gave me advice that changed several habits in my life. I really value those friendships, but the other interviews were worthwhile too. Staying in touch feels much more natural when you’re both interested.

How I follow up on a cold email.

My normal pattern for an unanswered cold email is one follow-up, then I stop. I wait at least a few days; sometimes a week or two. The timing depends on the situation. I’m giving someone another chance to notice a useful invitation, while accepting that they may simply not want it.

There have been exceptions. In rare cases, I’ve followed up more than 20 times. Sometimes it worked! Sometimes I upset people. Both happened, and I wouldn’t feel right sharing only the wins. One follow-up is the much more normal version of what I do.

A relationship where someone has already replied or we have met is different. There may be a real conversation to continue, a promise to complete, or a next step they asked for. I follow through more actively there. Read what the person actually said, and stop if they decline or ask you to stop.

Once we’ve exchanged numbers and texting is welcome, I often find it much easier to keep a conversation going there. Ask for the best way to stay in touch when you talk. An unanswered email alone isn’t a reason to move into somebody’s private texts.

Keep the follow-up short and in the same thread so they can find the original question. If they still don’t reply, I’d move on. You may never know whether it was the timing, the ask, or something else entirely.

Hey Maya, one follow-up on the buddy-program question. If you’ve already written about how you started it, I’d love a pointer. Thanks either way!

If nobody replies, take another look at the email.

If an email goes unanswered, you have very little information about why. You can still review the part you control. Read your draft as someone who has never met you. Is it obvious what you want? Could the recipient respond without reading a document, researching you, or booking a meeting first? Does their actual experience fit the question?

First check the basics. Did the email arrive? Does this person know anything about the problem? Are you asking for a quick answer or an afternoon of work? Those are different things to fix.

Avoid drawing a grand conclusion from a handful of messages. People’s availability changes, and you are choosing different people for different reasons. Keep a simple note about what you asked and what happened. A useful reply, a referral to something already published, a decline, and no answer tell different stories. Tracking them separately gives you a more honest picture than counting every response as a networking win.

Their work does not fit the question.

Choose a more relevant person. A cleverer email cannot give someone experience they do not have.

You have several questions and no clear priority.

Ask the first question whose answer would change what you do. Keep the rest for a later conversation if it develops.

The email bounced.

Check the address or an appropriate public contact route. Keep a delivery problem separate from a declined request.

They declined the request.

Acknowledge the answer and stop. Do not interpret a polite response as an invitation to keep negotiating.

They replied! Now follow through.

Answer what they actually said before introducing something new. If Maya sends a resource, read it. If she asks about your group, explain it. If she offers a call, make scheduling easy and arrive with the question you raised.

Actually try the suggestion. Then tell them what happened. I think this is one of the nicest reasons to reach back out: someone helped you, you did something with it, and now you have an update they might enjoy.

You don’t need to turn the first reply into a mentorship arrangement. I enjoy learning from people and helping where I can, often with an idea or an introduction. Shared interests give us reasons to keep talking.

Some of my best relationships develop over text. Let that happen when it feels normal to both people. For now, send a good email and be someone who follows through.

Hey Maya! We tried the buddy idea with a few volunteers. Having one person to ask questions made the welcome feel much less overwhelming. Still figuring out how to keep it going, but your suggestion gave us a useful place to start. Thank you!

A resource can be the beginning of a real exchange.

Here is a second fictional sequence, with a different outcome from getting a meeting. Devon is organizing a neighborhood bird count. Leila has published a guide for first-time volunteers. All people, messages, and results in this example are invented.

Devon has read the guide and wants to know whether to train everyone together or pair beginners with experienced volunteers. That is a question Leila can answer from the work she has already shared. Devon does not need to turn it into a request for ongoing mentorship.

The update closes the loop with something concrete. It does not attach a new favor or claim the event succeeded because of one email. Devon can leave the conversation here and reconnect later if there is a real reason.

Subject: Pairing beginners for a first bird count

Hey Leila!

Your volunteer guide helped me plan our neighborhood’s first count. We have a few experienced birders and several complete beginners.

Would you pair them up straight away, or start with a short group practice? I’m trying to keep the first morning approachable.

Thanks!
Devon

Leila: We start together, then pair people. The practice sheet near the end of the guide may help.

Devon: Ah, I’d skipped that sheet. Thanks! I’ll use it for the first few minutes before we split into pairs.

Hey Leila! We tried the practice sheet before pairing people up. It surfaced a few questions that would have been harder to explain once everyone spread out. Thanks for pointing me to it. I’ll keep it in the plan for next time.

Common questions