The most significant productivity gains come from applying AI to every stage of development, including research, planning, product marketing, and status updates. Limiting AI to just code generation misses the larger opportunity to automate the entire engineering process.

As AI evolves from single-task tools to autonomous agents, the human role transforms. Instead of simply using AI, professionals will need to manage and oversee multiple AI agents, ensuring their actions are safe, ethical, and aligned with business goals, acting as a critical control layer.

True Agentic AI isn't a single, all-powerful bot. It's an orchestrated system of multiple, specialized agents, each performing a single task (e.g., qualifying, booking, analyzing). This 'division of labor,' mirroring software engineering principles, creates a more robust, scalable, and manageable automation pipeline.

Top-performing engineering teams are evolving from hands-on coding to a managerial role. Their primary job is to define tasks, kick off multiple AI agents in parallel, review plans, and approve the final output, rather than implementing the details themselves.

Instead of focusing on foundational models, software engineers should target the creation of AI "agents." These are automated workflows designed to handle specific, repetitive business chores within departments like customer support, sales, or HR. This is where companies see immediate value and are willing to invest.

As businesses deploy multiple AI agents across various platforms, a new operations role will become necessary. This "Agent Manager" will be responsible for ensuring the AI workforce functions correctly—preventing hallucinations, validating data sources, and maintaining agent performance and integration.

The durable investment opportunities in agentic AI tooling fall into three categories that will persist across model generations. These are: 1) connecting agents to data for better context, 2) orchestrating and coordinating parallel agents, and 3) providing observability and monitoring to debug inevitable failures.

Instead of relying on a single, all-purpose coding agent, the most effective workflow involves using different agents for their specific strengths. For example, using the 'Friday' agent for UI tasks, 'Charlie' for code reviews, and 'Claude Code' for research and backend logic.

Historically, developer tools adapted to a company's codebase. The productivity gains from AI agents are so significant that the dynamic has flipped: for the first time, companies are proactively changing their code, logging, and tooling to be more 'agent-friendly,' rather than the other way around.