A 107-company survey confirms it: AI-agent governance is ready, cost isn't — and nobody knows what each agent actually costs
A VentureBeat Pulse study conducted in July 2026 among 107 companies with more than 100 employees shows AI-agent governance has matured — rising budgets, hybrid control wanted by 78% of respondents. But 21% of companies have no real-time way to stop a runaway agent before the bill arrives, and another 30% rely solely on their vendor's built-in caps. At AppH too: traceability of what an agent does already exists, the precise cost of each agent, not yet.
VentureBeat surveyed 107 organizations with more than 100 employees in July 2026 about how they orchestrate their AI agents. The first finding is hardly surprising: nobody is betting on a single platform. 85% of companies run at least two orchestration platforms in parallel, 64% run three or more, averaging 3.1 per organization. Microsoft AI Foundry / Copilot Studio appears in 70% of architectures (75 of 107 companies), OpenAI's Agents SDK in 68%, and Anthropic's Claude Platform / Agent Skills in 47%. Among the 61 respondents willing to name a single primary platform, Microsoft leads with 41%, Anthropic second with 28%. Purchasing logic confirms this plural approach: flexibility across models is the No. 1 criterion (29%), far ahead of affinity for one specific model (10%) — companies are buying what doesn't lock them in, not what comes bundled with their favorite model.
The real signal in this study isn't platform fragmentation, it's the gap between governance and cost that its own title sums up in one line: "AI-agent governance is ready, cost isn't." On governance, companies have clearly moved forward: 78% want to keep at least part of the control out of the vendor's hands, and the top growing investment area is agent monitoring and debugging (31%), closely followed by enforcing security permissions (30%). On cost, the picture is very different: 21% of companies only track their agent spending after the fact, in logs, with no real-time way to cut off a runaway agent before the bill explodes. Another 30% rely solely on their primary platform's built-in caps — a control that's only as good as the vendor's tooling, nothing more. And among the three satisfaction scores the study measures, value for money ranks last (3.63 out of 5), well behind overall satisfaction (4.17) — the sign of a sector that likes what agents do and doesn't like what they cost. At AppH, this same gap exists, on a smaller scale: the audit log that traces who did what, when, and why (append-only, deployed module by module this summer across Automations, Fleet Maintenance, and Appointments) already answers the governance half of the question. The cost half — how much a specific agent actually cost this month, action by action — doesn't yet exist as a dedicated dashboard for us either. That's exactly the same gap this study documents, just at our scale.
For AppH
- A single agent per account, never a swarm, and no action with real consequence going out without the owner's explicit approval — this architecture is, by design, a circuit breaker against exactly the scenario the 21% of companies without a real-time kill switch fear: at AppH, an agent can't run away unsupervised, because it never acts alone on anything that matters.
- The governance half of the problem — knowing what an agent did and why — is already solved at AppH with a real append-only audit trail, deployed across several modules this summer (Automations, Fleet Maintenance, Appointments): exactly the same investment category (monitoring and permissions) that 61% of the agentic budget in this study prioritizes.
Against / the honest limit
- AppH doesn't yet have a per-agent cost dashboard — how many tokens, how many euros a specific action actually cost this month. That's the exact same gap this study documents at enterprise scale (30% rely on built-in caps, 21% are purely reactive); we're not claiming to have solved it, we're naming it as a real gap, not a minor detail.
- The human-circuit-breaker argument works at AppH's scale (one agent per account, one SMB) — it isn't a direct architectural answer for a company with thousands of employees running three orchestration platforms and dozens of agents in parallel. This study's sample and AppH's SMB customer base aren't directly comparable.
It would be easy to write that this study proves us right — it documents exactly the kind of gap between rhetoric and mechanism we regularly point out in others. But honesty requires turning the mirror around: the same gap exists here, just smaller. We know how to trace what an agent does; we don't yet know how to precisely price what it costs, module by module, action by action. That's not a difference in principle from the 107 companies VentureBeat surveyed, it's a difference in scale — and scale doesn't excuse anything. The real lesson of this study isn't "big companies have a problem we don't," it's that governing an agent (knowing what it does) and measuring it (knowing what it costs) are two separate projects, and the first never automatically solves the second. We've done the first. The second remains a real open project, not a box we've checked.
Reviewed by an AppH human