You launched a developer tool. You know it's useful. You go to the obvious places — r/selfhosted, r/devops, the relevant Discord — and you start replying to threads where someone has the exact problem your tool solves.

Reply one: "Hey, I built [Tool] which does this — [link]."

Reply two, three, four: same shape.

By reply ten, mods have nuked your account. You think the community is anti-marketing. They're not. They're anti-link-drop. There's a difference, and the difference is everything.

The spam reflex

Communities have an immune response to anyone who shows up specifically to promote something. The cues are obvious: account is one week old, only post history is in threads where their tool is on-topic, every reply ends with a link, none of them help with the actual question.

The reflex isn't anti-business. It's anti-extractive. The community feels — correctly — that you're harvesting their attention to grow your audience without giving back. The fix isn't being sneakier about the link. It's giving back first.

What value-first looks like

The core move: solve the person's problem completely without mentioning your tool. If your tool would have solved it faster — fine, they'll figure that out from your post history if they're curious, or you can mention it once they engage.

A worked example. Someone posts: "What's the cleanest way to run Claude Code, Codex, and Gemini CLI in parallel without four terminal windows?"

Spam-reflex reply:

I built 1DevTool exactly for this — multi-agent terminals, persistent sessions, full IDE around them. Try it: [link]

Value-first reply:

Two approaches that work without extra tooling. (1) Use tmux with a 2x2 split — tmux new -s ai \; split-window -h \; split-window -v \; select-pane -t 0 \; split-window -v then run a different agent in each pane. (2) iTerm2 split panes if you're on macOS. The pain points you'll hit: switching context between them visually, keeping each one's session alive across reboots, and pulling output from one into another. tmux + tmuxp can mostly fix the first two; the third is harder. (Disclosure: I work on a tool called 1DevTool that wraps this whole thing into a desktop workspace, so I'm biased — but tmux is the right starting point.)

The second one is twice as long. It's also the one that builds trust.

The disclosure pattern

Value-first doesn't mean hiding who you are. It means leading with usefulness and disclosing relevance honestly. The phrase that works:

(Disclosure: I work on [Tool], which is biased toward solving exactly this — but [generic answer] is the right starting point and [Tool] would be overkill until you outgrow it.)

That sentence does three things at once: it's transparent about your interest, it acknowledges your bias, and it volunteers that the tool isn't always the right answer. All three move you out of the "shill" category and into the "person who happens to have built something adjacent."

The 80/20 rule for tool-relevant threads

A useful constraint: in any community where you want to be active long-term, make 80% of your replies in threads where your tool isn't relevant. Just be helpful in the broader space. The 20% where your tool is relevant will then read as informed contributions, not pitches.

This is hard if you only have time for outreach. It's easy if you'd be active in the community anyway because you find it interesting. That second condition is the one to optimize for: pick communities where your participation isn't extractive.

When to drop a link (and the specific phrasing)

After you've helped a few times in a thread, dropping a link is fine. The specific shape matters:

If you want to skip the tmux setup, [tool] does the same thing — happy to answer questions if you want to compare. No pressure, your tmux setup will work fine.

Three things at work: you're offering, not pushing; you're acknowledging the alternative is fine; you're inviting questions instead of asking for a conversion. That tone is the difference between an offer and a pitch.

What kills this approach

Templated replies across threads. Even if each one is value-first, if they share a structure, readers will pattern-match you to a bot. Mix it up.
A profile bio that's just your tool. Your account profile is the second thing readers check. "Building [Tool]" as the only line reads as a marketing account. Add interests, real ones.
Following up on every reply with "Did you try [Tool]?" This is the worst possible move. Help, then move on. If they want to follow up, they will.

The longer game

Value-first outreach is slower in the first month and dramatically faster in the second. The reason: each helpful reply seeds a small amount of trust with the people who read it (not just the OP). Over a few weeks, you become a recognizable name in the community. Then your once-in-a-while mention of your tool reads as "this person I trust mentioned a thing" instead of "another founder spamming."

The shortcut feels efficient and produces nothing. The slow path feels inefficient and produces a small but real audience that compounds.