Start with who you are and why you're writing

An introductory email works when the first sentence tells the reader your name, what you do, and why you're contacting them right now. Don't make them guess. A hiring manager, potential client, or colleague should know within the first two sentences whether this email is worth their time.

The opening might be: "I'm James Rodriguez, a junior developer at Acme Software. I read your article on API design and want to discuss how your approach might work for our current project." That's specific. It shows you've done basic research and you're not sending a form letter to fifty people.

Avoid vague openings like "I hope this email finds you well" or "I'm reaching out because I admire your work." Those lines waste the reader's attention. Get to the point in the first sentence.

Key Takeaways

  • Your first sentence should state your name, your role or context, and the specific reason you're writing.
  • Reference something concrete about the recipient—a recent article, a mutual connection, a specific project—so they know this isn't a mass email.
  • Keep the body to three to four short paragraphs; anything longer than that loses readers.
  • End with a clear, single ask: a meeting time, feedback on a specific question, or permission to follow up.
  • Proofread for spelling and grammar before sending; errors in an introductory email suggest carelessness.

Show you've done your homework

People respond to emails that show genuine interest, not generic flattery. If you're emailing someone, mention something specific: a recent talk they gave, a project they led, a post they published, or a mutual connection who suggested you reach out.

Instead of "I think you're great," write "I saw your presentation on remote team management at the Tech Summit last month. Your point about asynchronous communication solved a problem we've been wrestling with." That tells them you actually paid attention and aren't sending the same email to twenty people.

If you have a mutual connection, lead with that. "Sarah Chen suggested I reach out to you about your experience scaling customer support teams" is stronger than cold contact because it comes with a small amount of trust already built in.

Keep the body short and focused

Three to four paragraphs is the maximum. The first paragraph introduces you and why you're writing. The second paragraph provides context or background—what you're working on, what you need, or what you want to discuss. The third paragraph makes a specific request.

Don't explain your entire background or the whole history of your project. Save that for the conversation. Your job in the email is to make them want to have that conversation, not to answer every question they might ask.

If you're asking for information, be specific about what you need: "I'm trying to figure out how to structure our API documentation for external developers. Would you have 20 minutes in the next two weeks to talk through our approach?" That's clearer than "I'd love to pick your brain sometime."

Make one clear ask at the end

End with a single, specific request. Not "let me know if you want to chat" but "Would you have time for a 30-minute call next Tuesday or Wednesday afternoon?" or "Could you point me toward someone on your team who handles vendor partnerships?"

If you're asking for feedback on something, attach it or link to it, and ask about a specific part: "I've attached our draft API spec. Would you review the authentication section and let me know if our approach matches what you've seen work elsewhere?"

Make it straightforward to say yes. If you're proposing a meeting, offer two or three specific times rather than asking them to find time in their calendar. If you're asking for a referral, name the kind of person you're looking for.

Use a clear subject line

Your subject line should tell the reader what the email is about in five to eight words. "Introduction from James Rodriguez" is too vague. "API documentation feedback—20 minutes?" or "Referred by Sarah Chen—remote team scaling" is better because it signals what you want and why they should open it.

If you have a mutual connection, put their name in the subject line. "Sarah Chen referred me—customer support scaling" gets opened more often than a generic introduction because the recipient recognizes the name.

Proofread before you send

An introductory email with spelling errors or awkward grammar signals that you didn't care enough to check your work. Read it aloud before sending. If you stumble over a sentence, rewrite it.

Check that you spelled the recipient's name correctly and used the right pronouns. Check that any links work and any attachments are actually attached. These small things matter in a first impression.

Know when to follow up

If you don't hear back in a week, send one follow-up email. Keep it short: "I wanted to follow up on my email from last Tuesday about API documentation. I know you're busy—if this isn't a good time, I understand." Then stop. Two emails is a follow-up. Three is pestering.

If they don't respond to the second email, they're not interested. Move on. Some people don't respond to cold emails, and that's not a reflection on you or your message.

Frequently Asked Questions

Should I use "Hi" or "Dear" to start the email?

"Hi [Name]" is standard in most professional contexts now, especially in tech and business. "Dear [Name]" is more formal and works if you're contacting someone in a traditional industry or much older than you. Either is fine; just match the tone of the rest of your email. Avoid "Hey" unless you already know the person.

What if I don't have a mutual connection?

Cold emails work, but you need a stronger hook. Reference something specific they've published, a company problem you know they're solving, or a reason you're contacting them now rather than six months ago. "I'm building a tool for API documentation and your article on versioning strategies directly influenced our approach" is a legitimate cold email because it's specific and honest.

How long should an introductory email be?

Aim for 150 to 250 words. That's roughly three to four short paragraphs. If you're writing more than 400 words, you're explaining too much. Save the details for the conversation.

Should I attach my resume or portfolio?

Only if you're asking for a job or if it's directly relevant to your request. If you're asking for information or a referral, don't attach anything unless they ask. If you're explore for a position, follow the job posting's instructions—some want attachments, some want a link, some want nothing in the first email.

What if I'm nervous about sending it?

That's normal. Write the email, let it sit for an hour, read it again, then send it. Most people are less critical of your email than you are. If it's honest, specific, and respectful of their time, it's good enough to send.