Why I'm Done Blasting My AI Project to Random Discord Servers

Last month, I launched a small CLI tool for managing Cursor sessions across teams. I was genuinely proud of it. The code was solid, the documentation was clear, and I had maybe three real use cases I'd tested with friends. So I did what every developer does: I posted it everywhere. HackerNews, Dev.to, Reddit's r/webdev, three different Slack communities, and probably five Discord servers I'd half-forgotten about.

I got 47 replies. None of them were from people who actually needed what I built.

Most were "cool idea, good luck" messages. A few were spam. One person asked if I could pivot it to work with Claude instead (I was already targeting Claude users). I spent two weeks responding to messages that didn't matter, while the two people who actually cared about solving their specific QA workflows never even saw my post because it got buried in the noise.

That's when I realized I was solving the wrong problem. I wasn't trying to find users. I was trying to be heard.

The Noise Problem Nobody Talks About

Here's what I think most developers—especially AI builders right now—are getting wrong about finding early users: we're treating discovery like a volume game when it's actually a precision game.

The original problem isn't that people don't know your project exists. The problem is that you're trying to tell strangers on the internet about your specific needs, constraints, and constraints around a specific problem, and they have maybe 15 seconds to decide if they care. So you compress everything down to something generic and performative. "Built an AI tool" becomes a headline. The actual need—"I need three teams using Cursor who do manual release testing and hate it"—becomes impossible to communicate without looking like you're oversharing.

Then you get replies from people who thought your tool was about something else entirely.

Public Posting Optimizes for the Wrong Thing

When you post publicly, you're playing a game designed for engagement, not fit. Reddit upvotes go to clever titles and broad appeals. Twitter rewards being interesting to many people at once. Neither of those algorithms cares that you need exactly two design partners, not an audience.

I've seen this destroy early-stage projects. The builder gets excited about visibility, optimizes their pitch for virality, and suddenly they're talking to people who were just bored and scrolling, not people who actually have the problem they're solving.

The real matches—the ones that turn into actual partnerships—come from a different channel. Someone knows someone who knows you, or a trusted person vouches for the fit on both sides. That happens in private conversations, not public feeds.

What Private Intent Actually Means

The idea that grabbed me most from the article is this concept of "private intent." Instead of broadcasting vaguely to everyone, what if you could clearly specify to a system: "This is what I'm building. This is specifically who I need. This is what I can offer them. This is what should never be public."

Then on the other side, someone could say: "We have this specific problem. We're willing to test something early if it solves this particular thing and the person building it actually listens."

And only when those two things genuinely match would either party even know the other exists.

That's fundamentally different from a marketplace or directory. A marketplace says "browse inventory." A private matching layer says "I'll only introduce you if it actually makes sense for both of you."

My Take: This Is Worth Building, But Requires Trust

I'm convinced this approach would work better for finding early collaborators. But it only works if both sides actually believe the matching is thoughtful, not just different packaging for the same old cold outreach.

The hard part isn't the technology. It's building enough trust that people will actually express their real constraints and needs privately, rather than giving a vague version publicly. If it feels like another directory with better filtering, it'll fail.

What I'd want to see is something that helps me clarify my intent before I even try to reach out. A structured conversation that says: "Okay, you're building a testing tool. Who shouldn't use this? What would be a bad match? What do you actually need from beta users?" By the time I'm done answering those questions, I have a clear picture of who I'm looking for, not just a vague idea.

Right now, I'm trying this manually. I'm writing out specific constraints before reaching out to anyone. It takes longer, but the replies I get back are actually useful.

Source: This post was inspired by "AI Builders Do Not Need More Cold Outreach. They Need Private Introductions." by Dev.to. Read the original article