
Why ChatGPT Recommends Your Competitor: LLMs & the Future of DevTool Marketing with Adam DuVander
The MonkCastShow Notes
Why does ChatGPT recommend one DevTool over another, and what can founders do about it? In this RedMonk Conversation, Kate Holterhoff sits down with Adam DuVander, Principal Consultant at EveryDeveloper and author of Developer Marketing Does Not Exist, to explore how AI assistants are transforming software discovery. They discuss Adam’s LLM Rank research, which tracks how models like ChatGPT, Claude, and Gemini recommend developer tools, and why those recommendations often differ. The conversation covers the practical steps DevTool companies can take to improve AI discoverability, from documentation and developer experience to use-case positioning and contextual content. Along the way, Kate and Adam examine the expanding definition of “developer,” the rise of AI-assisted builders, and why developer marketing is evolving rather than disappearing. Whether you’re building a developer product or rethinking your go-to-market strategy, this episode offers a practical framework for succeeding in an LLM-first world.
Show notes: https://redmonk.com/videos/adam-duvander/
Chapters 00:00 Defining the Modern Developer 04:25 The Role of Every Developer 09:38 Marketing to the New Breed of Developers 12:37 Understanding LLM Rank and AI in Development 19:57 The Evolution of Documentation and Developer Experience 22:06 Understanding Developer Context and Use Cases 25:31 Navigating AI Recommendations for Developer Tools 28:55 The Importance of Language and Phrasing in Queries 31:50 The Long Game of SEO and LLM Rankings 36:44 Addressing Outdated Documentation and Bad Advice 42:20 The Distinction Between Discoverability and Developer Success 47:51 The Future of Developer Marketing in an AI World
More from The MonkCast
In this episode of the MonkCast, James Governor sits down with Sanjay Sarathy, SVP of Developer Experience at Cloudinary, to discuss developer trust, and why it still matters in the agentic software development era. With more than four million developers signed up, and 40% of new registrations now coming from agents, Cloudinary is rethinking what trust means, but maintaining true to its core values. Sanjay walks through the principles guiding that work: products that work as promised every time, human support that scales, accuracy in AI-assisted answers, transparency, long-term API stability, keeping the developer voice in the product loop, and investing in education for students and early-career developers.
In this RedMonk Conversation, Anne Bertucio de Hollembeak, COO of ROOST (Robust Open Online Safety Tools) , chats with Kate Holterhoff about the importance of open source tools in trust and safety, especially in the age of AI. She shares insights on building safety tools, the role of open source, and how these efforts can create a safer online environment for everyone.
Why do some teams see massive speedups from AI coding agents while others barely notice a difference? In this RedMonk New Builders Conversation with AWS, Kate Holterhoff talks with Liam Greenamyre, Principal PM of Developer Platforms at AWS, about the uneven impact of AI on software development and how to restructure work so agents can succeed. Liam explains why making tasks verifiable is the single biggest lever, then walks through the Agent Toolkit for AWS: a remote MCP server, 100+ skills, plugins, and a rules file that work with Claude Code, Codex, Kiro, and more. They dig into how a single RunScript tool covers 15,000+ AWS APIs token-efficiently, how IAM context keys separate human and agent actions, how agents discover new services like Aurora DSQL, and why isolated dev accounts make safe sandboxes for autonomous agents. Liam closes with a bold prediction: the biggest changes ahead are organizational, not technological.
Most of an enterprise application stack is open source that nobody is paid to maintain. Gunnar Hellekson of Red Hat puts it at 60 to 70 percent, and that gap is what IBM's Lightwell is built for. He walks James Governor through the mechanics: members scan and triage their own dependencies, submit what they find with the source identity stripped out, and get fixes back after an embargo period before those fixes reach a wider network and, where a maintainer still exists, the upstream project. Financial services goes first. Hellekson is candid that plenty of customers cannot use the service yet, because joining would only lengthen a patch backlog already measured in months. Mythos, the two agree, mostly revealed how bad things already were. They also work through token economics, why nobody needs to scan OpenSSL separately, and why a fix should end up as deterministic code rather than something an AI keeps rediscovering.
In this RedMonk conversation, Pankaj Gupta, Senior Director of Product Marketing, VCF Division, at Broadcom, chats Platform Engineering in the AI era with Stephen O'Grady. Gupta explains that more than 90% of organizations run an internal platform, but despite widespread adoption, Gupta thinks most platforms are hitting two ceilings. They were built, in his phrase, "AI blind," and they were built for exactly one user, the developer. AI has already moved the bottleneck from writing code to getting it into production, and the user base is about to change shape. Also in this episode: when golden paths harden into golden cages, why FinOps and security can no longer be bolted on, and Gupta's five pillars for platform engineering 2.0. The RedMonk conversation is sponsored by Broadcom.