The standard advice is now settled. Write excellent documentation. Build community. Hire developer relations. Teach instead of pitching. Don't be salesy, because developers detect inauthenticity instantly.
All of it is correct. All of it is also owned media — your docs, your blog, your community, your employees. Every channel on that list is one where you are the speaker, and developers apply a steep discount to anything a company says about itself.
The channel that survives the discount is the one those guides skip: what other people say about you where developers already are.
Why the discount exists
Developers evaluate tools by trying to break them. That instinct extends to claims. A benchmark you ran on your own product is treated as a starting hypothesis, not evidence. A case study on your site is understood to be a customer you selected and edited.
None of this is cynicism. It's calibration, and it's mostly correct, which is why it doesn't yield to better copywriting.
What it means practically is that owned media has a ceiling. Documentation can be superb and still not answer the question a developer is actually asking, which is whether people like them who don't work for you have used this thing and what happened.
Where opinions actually form
Ask an engineer how they picked their CI provider, their testing platform, or their infrastructure vendor, and the answer is rarely a company website.
It's a colleague who used it at a previous job. A Hacker News thread where the tradeoffs got argued out. A blog post by an engineer at an unrelated company describing a migration, including what went wrong. A conference talk by someone who isn't on your payroll. A benchmark run by a third party with no stake in the outcome.
These share a property: you didn't produce them, which is exactly why they carry weight. The 59% of developers who have real influence over what their team adopts are forming views in those places, and most devtools companies have no strategy for any of them.
Why companies under-invest here
Because it's uncomfortable in three specific ways.
You can't control it. A third-party benchmark might not favor you. An engineer writing about a migration will mention the friction. Marketing teams are measured on things they control, so they gravitate to the channels they control.
It's slow. A documentation overhaul ships in a quarter. Becoming the tool engineers mention unprompted takes years, and it doesn't produce a clean quarterly chart.
It has no dashboard. There's no attribution model that captures a conversation between two engineers, so it looks like nothing is happening right up until your pipeline changes shape.
The result is predictable. Devtools companies pour effort into the channels with clean measurement and wonder why developers still haven't heard of them.
What actually moves it
Get your engineers published somewhere that isn't your blog. The same technical post lands differently in a publication engineers already read than on a company site they've never visited. Trade and technical outlets are underused by devtools companies chasing general tech press that their buyers don't read.
Make it easy for other people to evaluate you honestly. Open benchmarks, a real free tier, reproducible test conditions. Companies that make independent evaluation easy get evaluated, and being evaluated at all beats being ignored.
Support the talk you don't control. Conference talks by users, not employees. A customer engineer describing their architecture, including the parts where your product wasn't the right fit. That last detail is what makes the rest credible.
Show up where the argument happens. Hacker News and the relevant subreddits are where technical reputations get made and unmade. Participating honestly, including when the thread is critical, does more than any campaign. Astroturfing gets caught, and getting caught is worse than being absent.
Publish data only you have. Devtools companies sit on telemetry about how software actually gets built, tested and shipped, and mostly publish opinion instead. Original data is the one form of owned media that gets treated as third-party evidence, because the numbers can be checked and the collection can't be faked.
The honest tradeoff
This work is slower and less controllable than the owned-media playbook, and it will occasionally produce a public assessment you'd rather not have. That's the cost of the credibility, and the two aren't separable.
The compensation is that it compounds in a way owned media doesn't. Documentation has to be maintained. A reputation among engineers keeps working while you sleep, and it's the reason a developer who has never visited your site arrives at a trial already predisposed to trust it.
Most devtools companies are one channel short of a complete strategy, and it's the one they can't control.
Common questions
What is developer marketing? Marketing software products to developers as the buying audience or the primary influencer on the purchase. It relies more on demonstrated technical credibility and less on persuasion than conventional B2B marketing.
Why is marketing to developers different? Developers evaluate claims adversarially and discount anything a vendor says about itself. That makes third-party evidence — peer recommendation, independent benchmarks, coverage in outlets they already read — disproportionately influential compared with other B2B audiences.
Does developer relations replace developer marketing? No. DevRel is an owned channel staffed by your employees, which developers correctly identify as such. It works best alongside earned credibility from people with no stake in your success.
What's the biggest mistake in developer marketing? Investing exclusively in channels the company controls. Docs, blog, community and DevRel are all necessary and all discounted, because the audience knows who's speaking.
How do you measure developer marketing? Imperfectly. The highest-value activity — engineers recommending you to each other — has no clean attribution. Useful proxies include unprompted mentions in technical communities, inbound trials with no traceable source, and whether independent evaluations of your category include you at all.
Salient PR works with developer tools and software testing companies, and has built earned-media programs across CI/CD, testing infrastructure and developer platforms since 2016.
About Salient PR
Salient is a B2B tech PR agency. We help startups become the story — landing tier-one coverage, building executive visibility, and turning attention into pipeline.
Senior team. No hand-offs. Radical transparency. If you’re ready to talk, reach out.
