You open a project page for a new open-source tool. The description reads: “Leverage cutting-edge AI to optimize your workflow. Unleash unprecedented efficiency.” Something feels off. It’s not wrong — it’s just… empty. You can almost hear the ChatGPT prompt behind it: “Write a compelling product description for an open-source tool.”
That sinking feeling has a name: the uncanny valley of marketing copy. And it’s killing the very trust your open-source project needs to survive.
When you automate the voice of a community, you automate the trust right out of it.
I saw this firsthand. A developer posted their new project — a free, local-first bar inventory app licensed under GPLv3. The code was genuine, the architecture was local-first, the ethos was pure open source. But the announcement copy was clearly AI-generated. One commenter nailed it: “the phrasing sits in uncanny valley for me.” They couldn’t trust the project. Not because the code was bad, but because the language felt like it came from a machine pretending to be human.
Here’s the paradox we’re living in: AI has made software creation easier than ever. Anyone can “vibe code” an app and push it to GitHub. But that same AI is also generating marketing copy at zero cost. And when you use AI to write your project’s introduction, you’re signaling something you don’t intend: I didn’t put the work in here either.
The open-source community was built on human struggle. People saw the sweat in the commit history, the late-night debugging in the README, the personality in the issue responses. That authenticity was the bedrock of trust. But now, with a single AI-generated paragraph, you can erase all of that. The reader doesn’t see a human who cares. They see a template.
Neutrality is death here. Take a side: either write like a human or accept that your project will be treated like a commodity.
This isn’t about hating AI tools. It’s about understanding what makes people trust software. We’ve learned to distrust polished marketing from corporations. But we gave open source a pass because it felt real. Now, with AI leveling the playing field, realness is the only differentiator left.
So here’s the twist: the same AI that democratized software creation has also democratized the appearance of effort. Now that everyone can generate marketing copy in seconds, the projects that stand out will be the ones that sound like they were written by someone who actually built the thing.
If you’re building an open-source project, stop outsourcing your voice. Write the first paragraph yourself. Let the awkward phrasing and tykes stay in. Because the absence of human struggle is immediately detectable — and deeply off-putting.
The most viral thing you can do in an era of AI-generated noise is to sound like a real person who cares.
Your code might be brilliant. But if your marketing reads like a robot’s last resort, nobody will stick around long enough to find out.
FAQ
Q: Isn't using AI for marketing just being efficient? Why should I hand-write copy when a tool can do it better?
A: Efficiency is great for internal tasks. But marketing is about signaling trust. AI copy is efficient at generating words, not at generating trust. The moment a reader suspects a machine wrote the pitch, they question whether the project has any real human investment behind it. Open source runs on community goodwill, not polished prose.
Q: So I should never use AI for any part of my open-source project marketing?
A: Use AI for drafts, brainstorming, or formatting, but edit heavily to inject your own voice. The key is that the final output must sound like a specific human wrote it. If you wouldn't say that sentence out loud to a friend at a meetup, it doesn't belong on your project page.
Q: But what if the AI copy is indistinguishable from human writing? Isn't the uncanny valley just a temporary problem?
A: Even if AI copy becomes flawless, the <em>knowledge</em> that it was generated will still trigger skepticism. When people know a machine wrote the pitch, they subconsciously assume the project itself was also low-effort. The human struggle behind open source was always a signal of dedication. Taking that signal away changes the entire trust calculus.