top of page

Your Next Developer Might Be an AI Agent: Rethinking the Developer Journey

Nov 13
1 min read
Developer Journey Map 2.0 header graphic showing the developer journey rebuilt for AI agents

Developers no longer walk the adoption path alone: AI assistants recommend tools, and coding agents read docs and write code before a human reviews it. Relaris Group's Developer Journey Map 2.0 updates the classic five-stage framework to put that second traveller on the map, showing what the agent does at each stage and where it quietly gives up. If your product isn't agent-ready, you may be losing builders without ever seeing a signal.

Key takeaways

  • Friction has gone invisible. When an AI tool can't find, parse, or run your product, it simply moves on, so drop-off now happens at stages most teams never measure.

  • Five stages, rebuilt for agents. The map keeps the original structure but reframes it around AI-era jobs (Search, Try, Context, Verify, and Evolve), adding rows for agent behaviour, friction points, touchpoints, and marketing.

  • Test your path the way an agent would. Ask whether AI tools recommend you, whether a coding agent can reach a working Hello World from your quickstart unaided, and whether pricing is visible before a sales call.

Read the full, in-depth guide over on Relaris Group here: https://relarisgroup.com/blog/developer-journey-map-2-ai-agents.

 
 
bottom of page