# Marketing to developers without losing them

*Developer Marketing · The Litebox team · Last updated: September, 2026 · 5 min read*

Developers tell marketers exactly what loses their trust, in their own words on GitHub and Reddit, and a technology marketer's review of over 100 of those conversations found the same handful of patterns driving them away, starting with copy that reads like it was written for a boardroom.

## Key Facts

- A technology marketer's ChatGPT-assisted review of 100+ real forum conversations found five recurring frustrations with vendor marketing, jargon, unclear homepages, and overpromising among them.
- Words like "enterprise-grade" and "synergy" function as a stop sign for developers reading a homepage, and words like "strategic alignment" pulled straight from enterprise marketing read the same way.
- Justin Jackson's Marketing for Developers book helped him make $66,000 in side-project revenue its first year, a self-reported figure with no independent audit behind it.

Practitioners disagree on where DevRel ends and developer marketing begins, a debate [Developer marketing: a practical guide](https://litebox.ai/blog/developer-marketing) covers, and [DevRel](https://litebox.ai/blog/devrel) develops in full.

## What losing a developer actually looks like

[Kevin Kerner](https://mightyandtrue.com/insights/blog/what-developers-really-think-of-your-marketing-and-what-you-should-do-about-it/), a technology marketer, had ChatGPT analyze over 100 real conversations from Reddit, Hacker News, developer Discords, and GitHub issues to see what developers say about vendor marketing when nobody from that vendor is reading. One developer, on GitHub, put it this way: "If the homepage reads like it was written for a board meeting, I know this tool isn't for me."

His review turned up five recurring frustrations. Three of them show up directly in a product's own marketing copy, starting with jargon. "Every time I see 'enterprise-grade' I wonder if that means bloated, overpriced, and hard to use." "'Synergy'? Just say integration and move on." Kerner's read is that teams are still writing to sound smart, optimizing for a slide deck a business buyer would nod along to.

The second is homepages that never say what the product is. "I read three paragraphs and still don't know what this thing is." "If I have to click four pages in to find out what it does, I won't." Kerner traces this to messaging built for generalized personas, language approved for selling a vision to an executive that leaves a technical visitor unsure what they're even looking at.

The third is overpromising. "If your tool promises to replace three entire departments, I'm already suspicious." "Saying it solves security, compliance, and observability all in one? Hard pass." Kerner's take is that developers read a sweeping claim as a red flag when a page tries to cover too much ground at once.

A fourth frustration, separate from those three, is missing technical detail. "If there's no GitHub link or documentation on the homepage, I assume it's not real." "No architecture diagram? No thanks." Kerner's read is that gating real implementation detail behind a sales conversation costs credibility with an audience that would rather dig in on its own.

## The tone mistake that repeats

[Ceci Stallsmith, of Calyx Consulting](https://calyx.substack.com/p/how-to-do-developer-marketing-that), names tone-deaf content as the single biggest offender in developer marketing. One specific version of it she calls "code-washed," marketing that borrows the visual shape of code without saying anything a developer would actually read. Her example, a hiring pitch dressed up as a code snippet:

```
if(developer.isGood()) {
  while(developer.looksForJob()) {
    return yourCompany.hires(developer);
  }
}
```

Her diagnosis: "It looks developer-y, it's code! But it repels." She makes a related point worth carrying into any developer marketing program. "Developer" isn't one audience. Frontend, backend, data, and DevOps engineers each have their own language preferences, and even within each of those groups, seniority and expertise vary widely.

Stallsmith points to AWS as a company that gets this right for a technical, experienced audience, copy she calls "gloriously straightforward," cutting to the value with no jargon and no hesitation about asking readers to do some reading. Vercel, aimed at developers who want to skip past setup friction, carries more personality and stays just as clear about who the product is for and what it does.

Her example of the mismatch runs one way. AWS adopting Vercel's lighter homepage tone would frustrate the technical, experienced audience AWS actually serves.

## What one practitioner's own numbers show

[Justin Jackson](https://marketingfordevelopers.com/about/), who wrote the original Marketing for Developers book in 2015, frames the problem in one line: "The hard part was never building a SaaS: it's getting anyone to notice you." Its first year helped him make $66,000 in side-project revenue, and the book has sold more than 5,000 copies in total.

He also co-founded Transistor.fm, a podcast hosting company, with Jon Buda in 2018, building it on nights and weekends before either could work on it full time. Twelve months after launch, they reached $20,000 in monthly revenue, a result Jackson says they'd thought might take five years. Transistor has since hired four employees beyond the two founders and serves over 35,000 podcast feeds, including shows like Acquired and Diggnation.

Jackson doesn't name the mechanism behind either number on the page reporting them, and both figures are self-reported, with no independent audit behind them.

## FAQ

### What does "code-washed" marketing mean?

Marketing that uses code syntax or developer-adjacent visual style, brackets, slashes, snippet formatting, without saying anything substantive to the developer reading it. The form looks right, and the content underneath it reads as generic marketing anyway.

### What's the fastest way to lose a developer's trust with marketing?

Copy that sounds like it was written for a business buyer, when the person actually reading it is the one evaluating the product. One developer summed it up on GitHub: a homepage that "reads like it was written for a board meeting" is enough to end the evaluation before it starts.

### What actually works to market to developers?

No single tactic is confirmed across every practitioner. Justin Jackson's self-reported numbers, $66,000 in side-project revenue from his book's first year and $20,000 in monthly revenue twelve months into Transistor.fm, are one practitioner's own account of his own results, unaudited.

### Is "developers" one single audience?

No. Frontend, backend, data, and DevOps engineers use different language, and seniority and expertise vary even within each of those groups, so a single generic message rarely lands well with any of them.

Jargon, vague homepages, and sweeping claims are easy to spot from the outside and surprisingly easy to repeat from the inside. If your team wants marketing built by people who've actually worked with DevTools audiences, our [DevTools startup program](https://litebox.ai/services) is where that work happens.

[All articles](https://litebox.ai/blog) · [Talk to the team](https://litebox.ai/contact-us)

---

HTML version: https://litebox.ai/blog/marketing-to-developers · All pages: [sitemap.xml](https://litebox.ai/sitemap.xml) · Agent guide: [llms.txt](https://litebox.ai/llms.txt)