Cold Outreach That Doesn't Feel Sleazy (And Actually Gets Replies)

Most founders avoid cold outreach because it feels gross. They’ve received too many LinkedIn pitches that start with “I hope this message finds you well” and end with a calendar link. They don’t want to be that person. So they wait for inbound traffic that takes months to build, while the easiest channel — talking directly to people — sits unused.

Here’s the mindset reframe that makes cold outreach feel different: you’re not pitching. You’re finding people who have a specific problem and asking if you can help. When done right, the person on the other end is relieved to hear from you, not annoyed.

Why Most Cold Outreach Fails (It’s Not What You Think)

Bad cold outreach fails because it’s selfish. Every sentence is about the sender: what they built, how great it is, why the recipient should care. The recipient’s brain processes this as noise and deletes it.

The failure isn’t the cold part — it’s the “me-first” framing. People don’t respond to pitches. They respond to relevance. They respond when someone demonstrates they actually understand the problem the recipient has.

The second failure mode: targeting too broadly. Founders send 500 identical messages to anyone who vaguely fits a persona. Conversion rates are 0.5-2%. The better approach is sending 50 highly targeted messages to people you can clearly identify as having the exact problem. Conversion rates go to 15-30%.

Volume is not the variable to optimize at this stage. Relevance is. A list of 50 people you’ve genuinely researched beats a list of 500 people scraped from a database.

The third failure: a terrible call-to-action. “Let me know if you’d like to schedule a call” requires the recipient to do work. They won’t. The CTA should be one click or one sentence: “Would it be useful if I sent you a quick walkthrough?” is better than a calendar link. “Do you want early access?” is better than “Let me know your thoughts.”

The One-Sentence Framework for Non-Sleazy Outreach

Every effective cold message does one thing: it shows the recipient that you understand their specific problem, and that you might be able to help.

The formula: [Something specific you noticed about them] + [The problem you solve] + [A low-friction ask].

That’s it. The specific observation is what separates you from every other cold message they receive. It doesn’t have to be elaborate. “I saw your comment in [subreddit] about struggling with X” works. “Your LinkedIn post about [specific topic] resonated” works. “You mentioned on your podcast that [specific thing] is a challenge” works.

The specificity signals that you actually looked at them as a person, not as an entry in a spreadsheet. It’s the difference between someone feeling seen and someone feeling targeted.

Crafting the Message

Here’s a template that gets consistent 25-35% reply rates for indie hackers doing early-stage outreach:

---

Subject: [Specific observation]

Hi [Name],

[Specific observation about them — one sentence that shows you paid attention.]

I built [product] because I had the same problem. [One sentence on what it does — not features, the outcome.]

If it’s relevant, I’d love to give you free access and get your take on whether it’s solving the right things. No pitch, just would find your feedback genuinely useful.

Worth a quick try?

[Your name]

---

Keep it under 100 words. That constraint forces you to be specific and cut the noise.

A few things to avoid: don’t attach anything to the first message, don’t include a calendar link unless they’ve expressed interest, don’t put more than one question in the message, and don’t use the word “synergy” (obviously).

One channel note: Twitter/X DMs tend to get higher open rates than email for indie-hacker-adjacent audiences because the platform is less cluttered with sales noise. LinkedIn works well for B2B. Email is the most versatile. The message format above works on all three with minor adjustments for tone.

The full guide to getting your first 100 users goes into how to build the list of 50 people to reach out to — who to look for, where to find them, and how to vet them before you send.

If this is the kind of thing you want more of, the Struggling Entrepreneur newsletter covers it every week.

What to Do When They Don’t Reply

Most people who don’t reply aren’t saying no. They’re busy, they missed the message, or the timing was off. One follow-up is appropriate. Two is the limit. Three is harassment.

The follow-up should be shorter than the original message. Something like: “Bumping this in case it got buried — happy to keep it short if a call feels like a lot. Even just curious if this is something you’d find useful.” That’s it.

The best follow-up adds something new rather than just asking again. Share a short result you’ve seen: “Quick update — one of our early users saved 4 hours on [specific task] this week. Thought that might be relevant given what you mentioned.”

If someone says they’re not interested, respect it immediately. Don’t argue, don’t ask why, don’t try to reframe. Say thank you and move on. Your reputation in small communities — which is where most early-stage founders operate — is worth more than a single conversion.

For the people who do reply: get on a call within 48 hours if they’re open to it. Send access immediately if they’re not. And once they’re in the product, check in personally within 72 hours. The difference between a beta tester who gives you useful feedback and one who silently churns is almost always one personal message.

Check out how to recruit beta testers if you’re at the stage where outreach is specifically for getting product feedback — the same principles apply, but the message framing shifts slightly.