The Agent Builder Moved Out of Engineering

For the past two years, AI adoption followed a familiar pattern. A team identified a process that could be automated. Someone from engineering evaluated the tools. Developers connected APIs, built integrations, and created the workflow. The business team described the problem, but engineering remained responsible for implementing the solution.

That structure made sense when building AI systems required technical expertise. It may not hold for much longer.

This week, Asana acquired StackAI, a no-code AI agent platform that allows companies to build workflow automations through a drag-and-drop interface. Enterprises use StackAI for tasks such as claim processing, IT ticket triage, due diligence, customer support, and RFP generation.

On the surface, it looks like another acquisition in the growing AI market. In practice, it signals something much larger. The agent builder is moving out of engineering and into operations.

For years, automation projects typically began with technical teams. Business units identified opportunities, but developers built the workflows. Even relatively simple automations often required engineering resources to connect systems, manage permissions, and maintain integrations.

No-code platforms started changing that dynamic long before AI arrived. What AI changes is the scope of what can now be automated without writing software.

A business operations team can design a workflow. A customer support leader can build an escalation process. An HR department can automate document handling. Increasingly, the people closest to the work can configure the automation themselves.

The question becomes less about whether a company can build an agent and more about whether it understands the workflow well enough to automate it effectively.

The significance of Asana’s acquisition is not the technology itself. AI agent builders already exist.

The important change is where they are appearing.

StackAI is being acquired by a work management platform, not a developer tools company. That distinction matters because work management systems sit at the center of how organizations coordinate tasks, approvals, projects, and operations.

By embedding agent-building capabilities directly into those environments, AI automation becomes part of everyday workflow management rather than a separate technical initiative. Automation moves closer to the people doing the work. Instead of submitting requests to engineering, teams may increasingly configure and deploy their own operational workflows.

That has the potential to accelerate adoption dramatically.

The next phase of AI adoption may have less to do with model quality and more to do with organizational design.

Most companies already have plenty of opportunities to automate repetitive work. The challenge is identifying which processes should be automated, how exceptions should be handled, and where human oversight remains necessary. Those are workflow decisions.

As AI becomes easier to deploy, the limiting factor shifts from implementation capacity to process design. Organizations that understand their workflows deeply will have an advantage because they can translate that knowledge into automation more effectively.

Companies that simply automate existing inefficiencies may move faster, but they may also scale the wrong processes.

The companies moving fastest are becoming more deliberate about how work flows through the organization.

Instead of treating AI as a collection of isolated tools, they are looking at entire processes. Where are approvals slowing down? Which handoffs create friction? Which tasks repeat often enough to justify automation?

Once those questions are answered, the technology becomes much easier to apply.

Engineering teams benefit as well. Instead of spending time building every internal automation request, they can focus on infrastructure, governance, integrations, and higher-leverage systems while business teams take greater ownership of workflow design.

This issue of Redeployed is brought to you by Tecla: As AI agent builders move out of engineering and into business operations, the challenge is no longer simply creating automation. It is understanding which workflows should be automated, how they connect across teams, and how they are governed once deployed. The organizations moving fastest are combining operational expertise with technical execution, bringing in engineers who can integrate systems, support workflow automation, and help teams scale AI-driven processes responsibly. Tecla helps AI-driven companies hire elite AI-ready talent, build AI, and manage it in production, all through one vetted network across the Americas.

Making automation easier does not automatically make it better.

Poor workflows can now be automated faster than ever. A process with unclear ownership, weak approvals, or inconsistent decision-making does not become more effective because AI is involved. In many cases, automation simply accelerates the underlying problem.

There is also a governance challenge. As more teams build their own automations, organizations risk creating a growing collection of disconnected workflows with limited visibility into how decisions are being made. Permissions, compliance requirements, and operational accountability become harder to manage when automation spreads across multiple departments.

The result can be agent sprawl: lots of automation and very little coordination.

This shift is changing what companies need from their teams.

The demand is no longer only for people who can build AI systems. Organizations increasingly need people who understand how business processes, operational workflows, and technology fit together.

Companies are starting to value employees who can bridge those worlds and understand both the work being done and the systems supporting it. Engineers remain essential, but their role increasingly moves toward infrastructure, governance, integration, and oversight rather than building every workflow themselves.

At the same time, new responsibilities are emerging around workflow design, automation governance, and AI operations. As automation becomes easier to create, managing it becomes more important.

The companies that benefit most from this shift will not be the ones that build the most agents. They will be the ones that build the best workflows.

They will invest time in understanding how work actually moves through the organization before they automate it. They will establish clear ownership, governance, and oversight. And they will create systems that allow business teams and technical teams to collaborate without creating operational chaos.

Because the next challenge in AI is no longer whether companies can build agents. Increasingly, they can.

The challenge is whether they can redesign their organizations well enough to use them.

Connect With Other Technology Leaders

If you want to connect with other technology leaders having real conversations about AI and how it is changing business, check out GILD Curated Circuit.

More to come…

✔️ Why Asana Bought StackAI to Bring AI Agents Into Everyday Work — TechCrunch

✔️ Enterprise Workflows Become the New Home for AI Agents — SiliconANGLE

✔️ Asana Acquires StackAI, Adding Cross-System Execution for Human-Agent Teams — Asana Press Release