Walk into the majority of enterprise AI pitches right now and you’ll hear a version of the same story: the agents are here, they come with job titles, and you manage them the way you manage people. Workday has announced an “Agent System of Record,” an HR platform for your digital employees where you hire, onboard, assign responsibility, and manage outcomes “the same way businesses manage people.” Salesforce is shipping pre-built role templates (HR Agent, Finance Agent, Banker Agent) alongside its new Headless 360 announcement that exposes the entire platform as APIs and MCP tools. Microsoft is talking about “agent bosses” and “human-agent ratios” as if we’re optimizing a staffing model.
The common thread isn’t really about pricing or packaging, it’s about rerunning the same playbook. These incumbents are taking the org chart we built for scarce human intelligence and laying it down as the template for abundant machine intelligence, and the framing is intuitive enough that most buyers aren’t questioning it.
Anthropomorphism was a useful bridge but it’s the wrong destination.
When ChatGPT launched, making AI feel human (conversational, personable, a little quirky) was a smart move because it lowered the barrier. People talked to it like a colleague and it worked. The anthropomorphism served a purpose: it made an alien technology approachable.
The problem is what happened next. A UX choice that worked at the chat interface got promoted into an operating model, and the metaphor that helped a single user feel comfortable talking to a chatbot is now being used to describe how entire enterprises should deploy, govern, and manage AI at scale. That’s a much bigger claim, and the metaphor doesn’t stretch that far. Making something feel familiar to a first-time user is not the same thing as designing how an organization should run.
Roleification places unnecessary limits.
“Paul the Paralegal” and “Sally the Salesperson” are agents defined by the specialization constraints of existing knowledge workers: an HR Agent that can only do what an HR person does, a Finance Agent bound by the walls of the finance department.
When you “onboard” an agent into a role, you are telling it to think within those walls. Of course, the agent does need to respect the access controls, data boundaries, and policies that define the task, and that part genuinely matters. But beyond those guardrails, the whole promise of generalized intelligence is that the thinking doesn’t have to be bound by the same walls that the job description is. Within what it’s permitted to see, the agent should be free to reason across whatever the work requires. Roleification optimizes for familiarity, making AI look like something a manager already understands, and familiarity is not the same as capability. The gap between the two is where all the value leaks out.
The work, not the worker.
The reframe that matters is this: stop thinking about what agents are and start thinking about what work needs to get done.
Take employee onboarding, which doesn’t really live in HR. It touches recruiting, IT provisioning, facilities, payroll, compliance, and the hiring manager’s calendar, and it’s slow today precisely because it’s distributed across six departments with their own systems, handoffs, and queue times. The HR Agent framing doesn’t fix this, it just automates HR’s slice and leaves the handoff friction untouched.
The more useful approach isn’t deciding which department an agent belongs to, but what outcome the business actually wants, what information is needed to get there, and what the fastest path to completion looks like. That path will almost always cut across the silos you’ve built, which is the whole point. The organizations starting to see real returns from AI aren’t the ones that bolted agents onto existing processes, they’re the ones willing to rethink the processes underneath.
This is process reengineering, not headcount planning.
Vendors don’t lead with this message, because process reengineering is hard, unsexy, and impossible to sell as a per-seat license, but it’s where the value actually sits.
Some of the incumbents are starting to acknowledge, at least in their marketing, that the game is moving. Salesforce going headless is the most visible example: the company that invented per-seat SaaS is repackaging itself as an API surface for agents, which is a recognition that the agent is the interface and the data layer is where the value will be captured, while also being a move to make sure they remain the ones capturing it. Our view has always been that the systems of record were going to have to become data companies, and exposing the API surface is the price of admission rather than a gift to the ecosystem.
When intelligence becomes abundant, and any node in your enterprise can reason, synthesize, and act, the binding constraint changes. It’s no longer whether you have enough smart people in the right roles, it’s whether your information architecture is set up to let intelligence flow to where the work actually is. That’s a fundamentally different question, and it demands a fundamentally different investment: not in agent personas, but in data flows, in breaking down the information silos that were built for a world where intelligence was scarce and expensive and had to be rationed into departments.
Your company’s competitive advantage was never the org chart anyway. It was the institutional knowledge, the customer relationships, and the proprietary processes, the things that actually differentiate you. Agents don’t protect that advantage by mimicking your current structure, they unlock it by making that knowledge actionable across every surface of the business.
The real infrastructure investment.
Getting this right starts with the layer underneath the agents. Before you deploy anything that calls itself an agent, you need a runtime that can govern what it sees, what it does, and what it’s allowed to conclude. Your proprietary data, business rules, and strategic priorities need to be extracted, structured, and made available as living context, rather than trapped inside department-specific tools or siloed in applications that don’t talk to each other. The question isn’t which agent you deploy, it’s whether any intelligence, human or machine, can access the right context, act on it safely, and be held to account for the outcome.
That means investing in how your organizational knowledge is modeled, how context is delivered to the point of work, how memory accumulates across interactions, and how every action an agent takes can be governed and audited. The cross-cutting layer where all of that lives cannot be owned by any single vendor whose data it’s governing access to. It has to sit on your side of the line, portable across models and across systems, or the independence you think you’re buying is an illusion.
When that foundation is in place, you don’t need to “hire” an HR agent or a Finance agent. You compose capabilities (reason, research, draft, decide, escalate) dynamically around whatever the work demands. You give your agents a goal and guardrails.
Where we think things will go.
The companies that will look back on this era and wonder what they were thinking are the ones building agent org charts today, meticulously onboarding digital employees into the same departmental silos that have been slowing them down for decades. Right behind them will be the ones who accepted a vendor’s headless pivot as the whole answer, and only discovered later that the runtime governing their agents was never really theirs.
The ones that will win are doing something less photogenic but far more consequential: rewiring how their business thinks. Not adding AI to the machine but rebuilding the machine around what AI makes possible.
Your agents don’t need job titles. Your enterprise needs intelligent plumbing.