Every era of enterprise software has a defining question. For the past two years it was "which model should we use?" In mid-2026, that question has quietly retired. The models are good enough, plural. The new question — the one every IT leader we talk to is actually wrestling with — is "what job do we give the agent, and how do we hold it accountable?"
That reframing is the trend. Agentic AI is now the top technology priority for enterprise IT leaders, and the center of gravity has moved from individual productivity tools to autonomous agents executing multi-step workflows across business systems [1]. Agents are not getting smarter this quarter so much as they are getting hired. Here is our field report.
The copilot era asked "how do I help this person work faster?" The coworker era asks "which work can this agent own end to end?" Those are different products, different architectures, and different budgets.
The vendors are embedding, not bolting on
The clearest signal of the shift is where agents now live. Nobody wants another destination app, so the platform vendors are embedding agents directly into the tools people already work in [2].
Microsoft made its Sales Agent and Service Agents generally available inside Microsoft 365 and Dynamics 365 — not chat assistants that draft emails, but role-scoped agents grounded in live CRM data that research leads, nurture pipeline, and resolve support cases [2]. Slack, meanwhile, is turning Slackbot into a cross-system actor on the Salesforce platform: a conversational prompt in a channel can now trigger actions that span the CRM, tickets, and documents behind it [3]. And Anthropic expanded Claude Cowork to web and mobile, betting that the interface for agentic work is not a chat window you babysit but a dashboard where you monitor long-running tasks asynchronously — assign work, walk away, review results [4].
Three different companies, one identical conclusion: an agent earns its keep when it is embedded in the systems where work actually happens, with a defined role and a defined scope. That has been our thesis at Intueo since day one, and it is validating to watch the giants converge on it.
The money is starting to move
Follow the budgets and the trend gets sharper. Gartner now identifies "agentic arbitrage" as a major market disruptor, estimating that up to $234 billion in traditional SaaS spend could shift toward outcome-based agentic platforms by 2030 [5].
The logic is simple once you see it. Classic SaaS charges per seat for software a human operates. If an agent operates the workflow instead, you are no longer buying seats — you are buying outcomes: calls answered, leads qualified, invoices processed. The pricing unit of enterprise software is migrating from "user per month" to "work completed," and organizations have started evaluating AI initiatives on P&L impact rather than soft productivity metrics [1]. That is a healthy correction. "Saved everyone 30 minutes a day" was always unfalsifiable; "handled 84% of inbound calls without escalation" is a number a CFO can audit.
The uncomfortable half of the report
Now the caveat that keeps this from being a victory lap: 43% of enterprises still cannot measure the business value of their AI agents, and the culprits are consistent — fragmented data and insufficient governance [1].
We have seen this pattern up close, and it rhymes with what we wrote in our breakdown of why 95% of AI pilots fail. The failure mode of 2026 is no longer "the model was not smart enough." It is "we gave an agent a job but not the context to do it, and no trail to prove what it did." An agent reasoning over five disconnected data silos produces confident work from incomplete information. An agent with no audit trail produces results nobody can trust enough to act on.
The successful deployments share an unglamorous checklist: an orchestration layer that coordinates agents rather than scattering point solutions, unified data context so the agent sees what an employee in that role would see, and audit trails that make every action reviewable 1[2]. None of that ships with a model API. All of it is the actual product.
What we take from this at Intueo
Reading the mid-2026 landscape, three convictions of ours have hardened into industry consensus.
Agents need roles, not prompts. Microsoft's agents work because they are scoped to sales and service, grounded in the data those roles live in [2]. Our managed agents are built the same way — a defined job, the memory of everything that job has encountered, and tools scoped to what the role requires.
Asynchronous is the real interface. Claude Cowork's monitor-your-agents model [4] matches how our clients actually use their AI employees: assign, verify, refine. Nobody wants to watch an agent type.
Governance is a feature, not friction. The 43% who cannot measure value [1] are not short on capability — they are short on the boring infrastructure of accountability. Every agent we deploy logs what it did and why, because an agent you cannot audit is an agent you will eventually turn off.
The copilot era made AI a better tool. The coworker era makes it a unit of labor — hired for a role, measured on outcomes, and accountable for its work. If you want to see what a properly employed AI agent looks like inside your business, get in touch. We will skip the pilot purgatory and start with the job description.
References
- [1]
- [2]
- [3]
- [4]
- [5]
