📊 Full opportunity report: The Agent Trap: Why 90% of AI “Launches” Are Infrastructure Liars on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
In 2026, 90% of AI ‘agent’ launches are misclassified features built on vendor infrastructure, not independent platforms. This mislabeling influences purchasing decisions and increases enterprise dependency.
Most AI ‘agent’ launches in 2026 are actually features built on vendor infrastructure, not independent, governable platforms, according to recent analysis by Thorsten Meyer.
In May 2026, industry analyst Thorsten Meyer highlighted that approximately 90% of AI ‘agent’ deployments are misclassified features relying on proprietary vendor infrastructure. These so-called agents lack key characteristics such as autonomous operation, state persistence, and governance capabilities, which define true agents. Instead, they are simple chat interfaces or tool integrations that depend entirely on vendor-controlled environments.
This misclassification is driven by marketing tactics, where vendors label basic features as ‘agents’ to command higher prices and create dependency. The remaining 10% of launches are genuine platform-based agents with portable runtime, persistent state, and open governance, making them more adaptable and less vendor-dependent. The distinction requires procurement teams to apply a five-question filter to verify true infrastructure capabilities before purchase.
Recent examples include a vendor’s meeting-summary chat box priced at $30 per seat per month, and enterprise pilots that were abruptly canceled, revealing their lack of autonomous operation or governance features. Meyer emphasizes that the ‘agent’ label now often masks a feature, not an infrastructure, which has significant implications for enterprise strategy and security.
The agent trap.
Why 90% of AI “launches” are infrastructure liars.
A vendor announces an “AI agent.” The product is a chat box that summarises meeting notes — wired to a SaaS via OAuth, no runtime, no audit trail, no portable state. List price: $30 per seat per month. This is the agent trap. The label has been stripped from its meaning. What enterprises are buying — under the word agent — is overwhelmingly a feature on top of someone else’s infrastructure.
Most “agents” are features wearing infrastructure as a costume.
In 2026, the word agent has been stripped from its meaning. Vendors monetize the label. Buyers inherit the dependency. The asymmetry has a number — and the number does the work this story needs.
enterprise AI platform with persistent state
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
A request that fails three or more is a feature.
Run the request against five questions before signing any “AI agent” PO. The 90% fail at least three. The 10% pass all five. Price the line item accordingly — because the vendor won’t.
Does it run when no human is logged in?
A real agent runs on a schedule, on a trigger, or as a daemon. If it only works when a user opens a tab, it’s a feature.
Can you swap the model without losing the work?
Real agents treat the model as substitutable. The runbook, tools, memory, and workflow survive a model change. Features are welded to one model.
Where does the state live?
Real agents persist state to a customer-controlled store with a schema you can query. Features persist to “your conversation history” inside the vendor’s database.
What does the audit trail look like to your SOC?
Real agents emit events into a SIEM or webhook stream the security team subscribes to. Features emit nothing — or vendor-side logs you can’t ingest.
What do you keep when the contract ends?
Real agents leave you with skills, prompts, runbooks, memory, integrations as exportable artifacts. Features leave you with the labor you sank into the vendor’s UI — and nothing else.
AI Agents in Action: Build, orchestrate, and deploy autonomous multi-agent systems
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Salesforce isn’t selling agents. It’s removing the seat.
The dominant 2026 enterprise pattern is “headless 360” — the same Customer 360 / Employee 360 data model the suite sold for two decades, except agents now read and write directly. SDR · CSM · support agent are increasingly configurations of an agent runtime, not job descriptions for human seats.
The 9% genuinely AI-driven layoffs cluster exactly where headless is shipping.
Tier-1 support, junior software engineering, structured-data work — paying customers of a UI. If agents become the operators, the seat license attached to the human disappears. The vendor still gets paid; they just get paid per agent action instead of per human login.
Before · Per-seat humans
After · Headless 360
Applied AI Governance: The Model Context Protocol as an Enterprise Control Plane for Autonomous Agents
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
A feature cannot be routed.
When you buy a feature agent from a SaaS vendor, you commit to whatever model the vendor chose, at whatever margin the vendor charges. Real infrastructure exposes the model layer. If the vendor can’t tell you what model is running underneath, that is the answer.
QUERY
Towards the Governance of Open Distributed Systems: A Case Study in Wireless Mobile Grids
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The leverage moves to whoever owns the motherboard — not the chip.
Claude is increasingly the engine inside other people’s products. Legal-tech vendors, customer-success platforms, contract-review startups. This is the Intel Inside playbook. The implication for buyers is not “therefore buy Anthropic.” It is the reverse.
Built on a single closed model.
Brand sits on top of someone else’s chip. Looks like a platform. Priced like one.
- Cabinet vendor sells the platform pricing
- Chip vendor (Anthropic / OpenAI) sets margin
- If the chip vendor moves up the stack, cabinet gets squeezed
- Customer keeps nothing portable when leaving
Runtime that uses models.
Routing, governance, audit, skills layer. The chip is replaceable. The motherboard captures value.
- Multiple models, swappable per-request
- Customer-controlled governance plane
- Skills + integrations are exportable artifacts
- Survives the chip vendor moving up the stack
Skills are the portable infrastructure.
A skill written for Claude Code can be loaded into Codex, into Cursor, into any agent runtime that understands the format. The skill is the IP the customer wrote. The model is the chip. A buyer with 40 skills against an internal runtime can swap the model layer in an afternoon.
declarative · versioned · portable
If the vendor cannot or will not tell you what model is running underneath, that is the answer. You’re not buying an agent platform. You’re buying a wrapper.
Five questions any executive can ask in any vendor pitch.
- Does it run when no human is logged in?
- Can I swap the model without breaking the workflow?
- Where does the state live, and can I query it directly?
- Does it emit events my SOC can ingest?
- When the contract ends, what do I keep?
Four assignments. By role.
Run the five-point filter against every agent line item.
Reclassify each as feature or infrastructure. Re-price accordingly. The exercise will recover budget — usually significant budget.
Inventory the OAuth scopes granted to feature agents.
After Vercel, the agent supply chain is your perimeter. Tokens granted to chat-box agents holding Workspace, GitHub, and CRM scopes are the largest unmanaged risk in the stack.
Per-seat agent SaaS is the most expensive way to buy LLM compute.
Per-action and per-token routing typically costs 60–85% less for the same throughput. Demand the comparison. Vendors that refuse to provide it have answered the question.
Add “AI infrastructure vs feature” to the quarterly risk review.
If management cannot draw the line, the line has not been drawn — and someone else is drawing it for you, on a price tag.
Implications of Mislabeling in Enterprise AI Deployments
This mislabeling affects enterprise decision-making, increasing dependency on vendor infrastructure and limiting control over AI workflows. It also complicates procurement, as organizations must discern between genuine platform capabilities and superficial features. The trend toward ‘headless 360’ data models further blurs the lines, with major vendors positioning their products as ‘agent platforms’ while delivering only feature-like components. Understanding this distinction is critical for enterprises aiming for scalable, governable AI solutions that can adapt to evolving models and security requirements.
Evolution of AI Agent Definitions and Market Practices
Historically, an ‘agent’ was a process that operated continuously, maintained state, and was governable externally. This definition has remained consistent in production environments. However, in 2024 and beyond, vendors began rebranding simple tool integrations—such as chat boxes and API calls—as ‘agents’ to capitalize on AI hype. This shift has led to a market saturated with superficial offerings that lack core autonomous features.
Thorsten Meyer’s analysis points out that the majority of these launches are merely features that depend on vendor-controlled infrastructure, with no portability or true autonomy. This trend has been reinforced by major enterprise vendors like Salesforce and Microsoft, who are embedding agent-like capabilities into their existing data models without delivering fully autonomous or governable platforms.
“The label has been chosen for what it does to the price tag, not for what it describes.”
— Thorsten Meyer
“90% of ‘AI agent’ launches in 2026 are features dressed as infrastructure.”
— Thorsten Meyer
Extent and Impact of Misclassification in Enterprise Markets
While Meyer’s analysis is comprehensive, the full scope of misclassified ‘agent’ launches across different industries and regions remains uncertain. The precise impact on enterprise security and long-term dependencies is still being evaluated, and some vendors may be rebranding existing features as agents to stay competitive.
How Enterprises Can Identify and Adopt True AI Platforms
Organizations should apply a five-question filter before procurement, focusing on runtime autonomy, model portability, state control, security logging, and data portability. Industry experts predict a shift toward more transparent, governable AI platforms as enterprises become more aware of the ‘agent trap.’ Vendors may also need to adjust their marketing strategies to differentiate genuine platform capabilities from superficial features, especially as security and compliance demands increase.
Key Questions
What are the key differences between real AI agents and feature-based tools?
Real AI agents operate autonomously, maintain persistent state, are portable across models and environments, and are governable externally. Feature-based tools depend on vendor infrastructure, lack portability, and are activated only when users interact with them.
Why is the ‘agent’ label misleading in current AI launches?
Because it often masks simple features that rely entirely on vendor-controlled infrastructure, inflating their perceived autonomy and capabilities to command higher prices.
How can enterprises verify if an AI ‘agent’ is genuine?
By applying the five-question filter: Does it run when no human is logged in? Can the model be swapped without losing work? Where does the state live? Does it emit security logs? What happens when the contract ends? Genuine agents pass all five questions.
What are the risks of relying on feature-labeled ‘agents’?
It increases dependency on vendor infrastructure, limits control over workflows, and may pose security risks due to inadequate audit trails and data portability.
Source: ThorstenMeyerAI.com
