Writing Replies That Don't Feel Spammy

Nobody likes being sold to. But everyone likes being helped.

The Golden Rule

80% value, 20% (soft) pitch.

If your reply isn't helpful even without the product mention, rewrite it.

Lead with Value

Before mentioning your product, provide something useful.

Bad Example

❌ "Hey! You should check out MyProduct, it does exactly what you need!"

This is spam. It provides no value. It will be ignored or downvoted.

Good Example

✅ "Great question. For your use case, you'll want something that does X and Y. I'd also recommend looking for Z feature — it'll save you time down the road. I actually built something in this space (MyProduct) if you want to check it out, but definitely compare a few options."

This helps first, mentions the product second, and doesn't hard sell.

Be a Human, Not a Brand

People connect with people, not companies.

Do This

Use casual, conversational language
Share your own experience ("I had the same problem...")
Admit limitations ("might not be perfect for everyone, but...")
Ask follow-up questions
Use first person ("I," not "we")

Don't Do This

Corporate speak ("We at Company X are pleased to...")
Perfect grammar and formatting (too polished = suspicious)
Talking about "users" or "customers" (talk to the person)

Don't Copy-Paste

StackLead's AI drafts are a starting point. Always personalize.

Personalization Checklist

[ ] Reference something specific from their post
[ ] Add details relevant to their situation
[ ] Include your own voice and personality
[ ] Remove anything that sounds template-y

Why This Matters

Copy-paste replies:

Feel generic
Get flagged as spam
Don't build trust
Miss opportunities to connect

Match the Platform Tone

Each platform has different norms.

Casual, community-focused. Use lowercase, contractions, informal language.

honestly i dealt with the same thing last year. ended up
trying a bunch of tools before finding something that worked.

what specifically are you trying to do? might be able to
point you in the right direction.

Hacker News

More technical, thoughtful. Okay to be detailed.

Interesting problem. A few approaches I've seen work:

1. [Technical suggestion]
2. [Alternative approach]
3. [Your product, framed as one option]

We do #3 at [product] — here's how we handle the
specific thing you mentioned: [brief explanation]

Twitter

Short, direct. Get to the point.

Had this exact problem. What worked for me: [solution].
Happy to share more if helpful.

Indie Hackers

Founder-to-founder, supportive. Share your journey.

Fellow founder here — I built [product] because I was
dealing with exactly this. Happy to answer questions,
even if you end up going a different direction.

The Structure of a Good Reply

Acknowledge — Show you read and understood their post
Empathize — "I've been there" or "That's frustrating"
Help — Provide useful information or suggestions
Mention (softly) — Reference your product as one option
Offer more — "Happy to answer questions"

What to Avoid

Hard Sells

❌ "You should definitely use MyProduct!" ✅ "I built something in this space if you want to check it out"

Fake Helpfulness

❌ Pretending to help just to pitch ✅ Actually being helpful, with a soft mention

Walls of Text

❌ 500-word essays ✅ Concise, scannable replies

Feature Lists

❌ "MyProduct has Feature A, Feature B, Feature C..." ✅ "MyProduct handles [their specific problem]"

Examples of Great Replies

Example 1: Reddit

I had the same problem last year — spent forever trying to
find something that actually worked for [specific need].

Ended up building my own tool (StackLead) because nothing
quite fit. Happy to answer questions if you want to know
more, but also worth checking out [Competitor A] and
[Competitor B] depending on your budget.

What's your main priority — price or features?

Example 2: Hacker News

We've been thinking about this a lot at [company]. The
challenge is [technical insight about their problem].

Our approach is [brief explanation]. Here's a blog post
where we go deeper: [link]

Curious what you end up going with — it's a tricky space.

Example 3: Twitter

Dealt with this last month. Two things that helped:
1. [Suggestion]
2. [Suggestion]

Also been using [product] for this — works well for [their use case].

Final Check

Before posting, ask yourself:

Would I find this reply helpful if I was the person who posted?
Does it provide value even without my product mention?
Does it sound like a real person wrote it?
Is it appropriate for this platform's culture?

If yes to all four, hit send.