# How to Write a First Message That Gets a Reply (With Templates) Co-founders guide by RUV Labs · Updated October 5, 2026 · https://ruvlabs.com/guides/first-message-templates > A first message that gets a reply is short, specific and easy to answer: one line of context about you, one specific reason you are writing to this person, one clear ask, and an easy way to say no. Keep it brief enough to read on a phone, leave out attachments and long pitches, and follow up once after about a week if you hear nothing. Most first messages go unanswered not because the sender is unqualified, but because the message is long, generic or hard to reply to. Whether you are approaching a potential co-founder, an investor, a candidate or a company you want to join, the same simple structure works. This guide explains that structure, gives you templates to adapt, and covers common mistakes and when to follow up. ## Key takeaways - A strong first message has four parts: context about you, a specific reason for writing to this person, one clear ask, and an easy way to say no. - Specificity is the clearest signal of effort; one concrete detail about the recipient does more than any compliment. - Ask for something small and easy, such as a short call or a single question, rather than a commitment. - Keep it short enough to read on a phone, and leave out attachments, long pitches and contact details. - Follow up once after about a week with something new, and stop after a second follow-up at most. ## What makes a first message get a reply? A first message gets a reply when the recipient can tell within a few seconds who you are, why you chose them and what small thing you want. Short, specific and easy to answer beats impressive and long. People who receive many messages scan for three things. Is this person real and credible? Is this actually about me, or a mass message? Can I answer quickly? Your job is to settle all three in the first few lines. ## What structure should a first message follow? Use four parts, in this order: context, specific reason, ask and easy out. Each part is usually one or two sentences. 1. **Context:** who you are, in one line that matters to the recipient. "I am a backend engineer who spent five years on payments infrastructure" works better than your full biography. 2. **Specific reason:** why this person, and why now. Reference their post, their past work, a shared interest or a mutual contact. 3. **Ask:** one concrete, low-effort next step, such as a short video call, an answer to one question, or permission to send more detail. 4. **Easy out:** a line that makes no a comfortable answer, such as "If the timing is wrong, no problem at all." The easy out is the part that is easiest to forget. It lowers pressure, shows respect for the recipient's time, and makes it easier for people to answer honestly, which is what you want. On RUV Labs, first contact happens through a message request, and phone numbers, emails and messenger handles are blocked in first requests. Leave contact details out of your first message and share them once the other person accepts. ## First message templates you can copy Use these templates as starting points and replace every bracket with something specific to the person; a template sent unchanged reads like a template. Each one follows the four-part structure. ### To a potential co-founder whose post you saw If you are still working out where to look, start with [how to find a co-founder](https://ruvlabs.com/guides/how-to-find-a-cofounder). ```text Hi [Name], I saw your post about building [product or idea] for [customer]. I'm a [role] who has spent [time] on [relevant experience], most recently [specific project]. What caught my attention was [specific detail from their post]. I've seen that problem firsthand when [brief example]. Would you be open to a 20-minute video call in the next week or two to compare notes on what you're building and what you're looking for in a co-founder? If you've already found the right person, no worries at all. Good luck with it either way. [Your name] ``` ### From a founder to someone who could be a co-founder ```text Hi [Name], I'm building [one-line description] and looking for a [technical or commercial] co-founder. So far we have [one line of evidence: users, pilots or interviews]. Your work on [specific project or experience] is close to what we need, especially [specific skill or insight]. Would you be up for a short call to see whether there's a fit? I can share a one-page overview beforehand if that helps. If you're not looking right now, I completely understand. [Your name] ``` ### To an angel investor you do not know For where to find the right investors in the first place, see [how to find angel investors](https://ruvlabs.com/guides/how-to-find-angel-investors). ```text Hi [Name], I'm the founder of [company], which helps [customer] [achieve outcome]. Since [month], we've [one specific proof point]. I'm reaching out because you've backed [relevant type of company] and worked on [relevant experience], which is the market we're in. We're raising a [round size] pre-seed on a [instrument]. Would you be open to a 20-minute call, or would you prefer I send a short deck first? If it's not a fit for your focus, a quick no is genuinely helpful. [Your name] ``` ### Asking a mutual contact for an introduction ```text Hi [Name], Hope you're well. I'm raising a pre-seed round for [company], and I noticed you know [investor's name]. Given their background in [area], I think they could be a strong fit. Would you be comfortable introducing us? If so, there's a short note below you can forward as is, and please check with them first. [Two to four sentence forwardable blurb] And if you'd rather not, no problem at all. [Your name] ``` ### To a candidate you want to hire For the rest of the hiring process, see [how to hire your first engineer](https://ruvlabs.com/guides/hire-first-engineer). ```text Hi [Name], I'm [your name], founder of [company]. We're [one line on what you do and your stage], and we're hiring our first [role]. I came across your [project, profile or post] and was impressed by [specific detail]. It's close to the hardest problem we're working on right now: [one line]. Would you be open to a 20-minute call to hear more? No preparation needed, and no assumption that you're looking. If the timing isn't right, I'd still be glad to stay in touch. [Your name] ``` ### To a startup you want to join Before you reach out, it helps to know [what to ask when joining an early-stage startup](https://ruvlabs.com/guides/joining-an-early-stage-startup). ```text Hi [Name], I'm a [role] with [years] of experience in [relevant area]. I saw that [company] is [hiring for a role or working on a problem]. I've been following [specific detail: a launch, a post or a problem], and I worked on something similar at [type of company], where I [specific result]. Would you be open to a short call about where I might help, even if there isn't an open role that fits yet? If now isn't a good time, I understand completely. [Your name] ``` ### From an investor to a founder ```text Hi [Name], I'm [your name], an angel investor focused on [markets] at [stage]. I usually help founders with [specific kind of help]. I came across [company] through [source], and [specific thing that interested you]. If you're raising now or soon, I'd welcome a 20-minute call to learn more. If not, I'd be glad to follow your progress. Either way, no need to reply if this isn't relevant. [Your name] ``` ### A follow-up after no reply ```text Hi [Name], Bringing this back to the top in case it got buried. Since I last wrote, [one new piece of progress or relevant detail]. Still happy to do a short call if it's useful. If not, no need to reply, and thanks for reading. [Your name] ``` ## What are the most common first-message mistakes? The most common mistakes are writing too much, being generic, asking for too much and creating pressure. Each one makes the message harder to answer. - **Too long.** If it needs scrolling on a phone, cut it. - **Generic.** "I love what you're doing" with no detail reads like a mass message. - **Pitching instead of asking.** The first message opens a conversation; save the full story for the call. - **Several asks at once.** Pick one: a call, a question or permission to send more. - **Vague asks.** "Can I pick your brain?" puts the work on the recipient, so ask a specific question instead. - **Attachments and lots of links.** Offer to send a deck rather than attaching one unasked. - **Pressure and urgency.** "We close Friday" in a first message to a stranger feels like a sales tactic. - **Contact details in the first message.** On RUV Labs they are blocked until a request is accepted, and elsewhere they still read as presumptuous in a first note. - **Getting their name or company wrong.** Check spelling before you send. ## When and how should you follow up? Follow up once after about a week if you have not heard back, add something new, and stop after a second follow-up at most. A common rhythm is a first nudge after about a week and, if it still seems relevant, one final note a week or two later. - **Add new information.** A short update, a relevant milestone or a sharper question gives the person a reason to reply now. - **Keep it shorter than the original.** Two or three sentences are enough. - **Do not guilt the recipient.** Skip lines like "Did you see my last message?" and simply restate the ask. - **Close the loop on introductions.** If someone introduced you, thank them and tell them how it went. - **Respect a no.** Thank them and move on; a graceful response is often remembered. ## How RUV Labs helps - Verified members contact each other through message requests, and the recipient can accept, decline or block, so every conversation starts with consent. - Phone numbers, emails and messenger handles are blocked in posts, profiles and first message requests, so contact details are shared only after a request is accepted. - Anyone can read the public feed and member profiles, so you can find specific details to reference, for example in the [Co-founders feed](https://ruvlabs.com/feed/cofounders), before you write. - A verified identity and document-verified badges help the recipient see that you are who you say you are. ## Frequently asked questions ### How long should a first message be? Short enough to read on a phone without scrolling, which usually means a few short paragraphs. If you cannot cover your context, reason and ask in that space, the message is trying to do too much. ### Should I send my pitch deck in a first message to an investor? Usually not. Include a one-line summary of the company and the round, offer to send the deck, and let the investor ask for more. This keeps the first message easy to read and lets you share materials in stages. ### Is it okay to use writing tools or AI to draft a first message? Yes, as long as the final message is specific, accurate and sounds like you. Recipients notice generic phrasing quickly, so add real details about them and about your own work before sending. ### How do I message someone much more senior or well known? Be even shorter and more specific, and make the ask smaller. A single focused question that only they can answer well is more likely to get a reply than a request for a meeting. ### What should I do if someone replies with a no? Thank them and, if it feels natural, ask one light question, such as whether they know someone who might be a better fit. Keep the relationship warm, because people often remember those who handled a no gracefully. This guide is general information, not legal, tax or investment advice.