The Short Answer
An enterprise needs an AI Platform Team because the ways AI agents fail in production are platform problems, not model problems: bad tool inputs, silent tool failures and out-of-scope actions. One central team owns the runtime, permissions, approvals and audit trail; engineers embedded in each business unit build agents on it. On ibl.ai you own all the code and the data, so that governance layer stays yours.
The pattern has a name now. Superblocks CEO Brad Menezes described "the rise of the AI Platform Team" in November 2026 after conversations with hundreds of CIOs, CISOs and Heads of AI: "centralize the platform and governance, embed internal FDEs in the business."
This post is the enterprise version of the argument. Our companion piece covers how the same model maps onto a university.
How wide is the gap between AI agent deployment and AI agent governance?
The gap between agent deployment and agent governance is wide in every large survey published this year. Companies are putting agents into production faster than they are building the controls around them.
Deloitte's State of AI in the Enterprise 2026, a survey of 3,235 business and IT leaders in 24 countries, found close to three-quarters of companies planning to deploy agentic AI within two years. Only 21% report a mature model for agent governance.
McKinsey's State of AI in 2026 shows the deployment side moving. 40% of respondents from organizations with more than $1 billion in revenue report scaling AI agents, up from 27% a year earlier.
Capgemini's World Cloud Report for Financial Services 2027, published 5 November 2026 from a survey of 1,100 leaders in 14 markets, puts the gap in one line. 59% of firms are piloting or deploying multi-agent AI; only one in ten has the orchestration to run it autonomously across the enterprise.
| Survey | Deployment signal | Governance or scale signal |
|---|---|---|
| Deloitte, January 2026 | Close to three-quarters plan to deploy agentic AI within two years | 21% have a mature agent governance model |
| McKinsey, 2026 | 40% of $1B+ organizations scaling agents, up from 27% | Scaling in at least one function, not across the enterprise |
| Capgemini, November 2026 | 59% piloting or deploying multi-agent AI | One in ten orchestrating it enterprise-wide |
The three surveys measure different things and different populations, so the figures should not be subtracted from each other. They point the same way: building an agent is no longer the hard part.
Why do AI agents fail in production?
AI agents in production fail mostly in three ordinary ways, and none of them is the model being "not smart enough." This is the taxonomy we use when an agent breaks in a deployment.
- The agent passes the wrong input to a tool. A malformed parameter, a wrong identifier, a field in the wrong type. The intent was right; the call was wrong.
- A tool fails and nothing catches it. An API returns an error or a query times out, and the agent carries on reasoning over bad state.
- The agent acts outside its scope. It takes an action nobody authorized it to take, because nothing in the runtime said it could not.
Each of those is a property of the system around the model. A stronger model makes the first one rarer and does nothing at all for the other two. That is the argument for a platform team: these are controls, and controls belong in one place.
What does an enterprise AI Platform Team own?
An enterprise AI Platform Team owns the shared rails every agent runs on, the way a cloud platform team owns accounts, networking and security policy so product teams do not each invent their own.
| Failure mode | Platform control the team owns | Where it lives on ibl.ai |
|---|---|---|
| Wrong input to a tool | Typed state, approved connectors, transforms before a call | Workflows (typed state variables, Transform, MCP nodes) |
| Silent tool failure | Checked outputs, a defined path when a step fails, a log of every run | Workflow Continue on error, If / else and Guardrails nodes; Transcripts |
| Out-of-scope action | Permissions, human approval, isolated execution | Roles, the User approval node, Sandbox |
| Nobody knows what changed | Change history and spend per agent | Audit and Costs |
Model choice belongs on that list too. Capgemini found 90% of financial services firms using or planning intelligent model routing, which only works if one team decides which models are approved for which data and can switch them without rebuilding agents.
Department teams then configure agents on those rails rather than building stacks of their own. Our earlier post on the enterprise agent governance gap covers the policy side in more depth.
Why does an AI Platform Team need forward-deployed engineers?
An AI Platform Team needs forward-deployed engineers because a central team alone produces governance that blocks real work, and business units alone produce agents nobody can govern. Menezes's formula has both halves for that reason.
A forward-deployed engineer sits with the legal, finance or operations team, learns which data an agent may touch and which actions need a person's sign-off, and encodes that on the shared platform.
The approvals and permissions in the table above are only as good as the domain knowledge that set them.
The goal is internal capability. ibl.ai's AI Transformation service puts our engineers alongside the enterprise's own team for the first agents, then hands over code, data and configuration the enterprise keeps. ibl.ai is family-owned and operated from New York, NY, with no venture capital: a long-term partner, not a vendor that sells licenses and moves on.
What should an AI Platform Team look for in an agent platform?
An AI Platform Team should look for a platform it can actually own, because governance you rent can change under you. The controls above are only durable if the team controls the runtime they run in.
On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing, so you can deploy anywhere, from your own cloud to a fully air-gapped network.
That matters for the governance function specifically.
A platform team that holds the source can inspect how permissions are enforced, keep audit logs inside its own perimeter and swap a model provider without asking a vendor. 1.6M+ users across 400+ organizations use ibl.ai, on Agentic OS.
Per-seat pricing is the wrong shape for this model as well: a platform team rolling agents out unit by unit should pay for what the agents consume, not for every employee who might one day open one.
When should an enterprise set up an AI Platform Team?
An enterprise should set up an AI Platform Team before its second business unit ships an agent to production, because every agent built on its own stack is a set of permissions, logs and model contracts the team will later have to unwind.
Deloitte's figure says most companies are already past that point: close to three-quarters are planning agentic deployments and only 21% have mature governance for them. The practical start is small.
Name the central team, choose one platform, and embed engineers with the one or two units that already have an agent working. Then route the next agent request onto the shared rails instead of onto a new stack.