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.
The evolution of 'agentic AI' extends beyond content generation to automating the connective tissue of business operations. Its future value is in initiating workflows that span departments, such as kickstarting creative briefs for marketing, creating product backlogs from feedback, and generating service tickets, streamlining operational handoffs.
Contrary to the vision of free-wheeling autonomous agents, most business automation relies on strict Standard Operating Procedures (SOPs). Products like OpenAI's Agent Builder succeed by providing deterministic, node-based workflows that enforce business logic, which is more valuable than pure autonomy.
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.
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.
Contrary to the view that useful AI agents are a decade away, Andrew Ng asserts that agentic workflows are already solving complex business problems. He cites examples from his portfolio in tariff compliance and legal document processing that would be impossible without current agentic AI systems.
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.
The transition from AI as a productivity tool (co-pilot) to an autonomous agent integrated into team workflows represents a quantum leap in value creation. This shift from efficiency enhancement to completing material tasks independently is where massive revenue opportunities lie.
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.
The paradigm shift with AI agents is from "tools to click buttons in" (like CRMs) to autonomous systems that work for you in the background. This is a new form of productivity, akin to delegating tasks to a team member rather than just using a better tool yourself.
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.