📊 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, about 90% of AI ‘agent’ launches are marketing labels for features built on vendor infrastructure, not genuine autonomous platforms. This mislabeling affects enterprise buying decisions and dependency.
Recent industry analysis in May 2026 confirms that approximately 90% of AI ‘agent’ launches are actually features layered on vendor infrastructure, not true autonomous agent platforms. This misrepresentation influences enterprise procurement and dependency, raising questions about what organizations are truly acquiring.
In 2026, the majority of AI products labeled as ‘agents’ are not independent, self-governing systems but are instead features integrated into vendor cloud infrastructure. These so-called agents lack key qualities such as runtime autonomy, state persistence in customer-controlled environments, and comprehensive governance capabilities, making them more akin to augmented features than true autonomous agents.
For example, a recent vendor announcement of a meeting summarization chat box at $30 per seat per month was marketed as an agent but lacked runtime, state management, and governance features. Meanwhile, enterprise CIOs are shutting down or questioning similar pilot projects that are merely chat interfaces tied to existing SaaS platforms, underscoring the disconnect between marketing and reality.
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.
Hermes Agentic AI Platform: Delivering Autonomous AI Agents at Scale Across Any Enterprise
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.
Securing AI Agents with the Microsoft Agent Governance Toolkit
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
AI feature layered on cloud infrastructure
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
The Agentic AI Advantage: A Comprehensive Collection of Practical Methods, Real-World Projects and Deployment Tactics to Build Reliable AI Agents, Reduce Chaos & Take Control of Your Digital Future
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 for Enterprise AI Procurement Strategies
This trend matters because enterprises are increasingly investing in AI labeled as ‘agents’ under the false premise of acquiring autonomous, portable, and governable platforms. The reality is that most of these launches are dependent on vendor infrastructure, which limits control, increases lock-in, and complicates migration or integration efforts. Mislabeling leads to inflated expectations and can result in costly vendor dependencies that are difficult to unwind.
Shift from True Agents to Feature-Based Labels in 2026
Historically, ‘agent’ referred to a process that ran continuously, maintained state, and was governable externally. However, in 2026, vendors increasingly use the term to describe simple chat interfaces or feature layers that invoke tools or call APIs without true autonomy or portability. This shift is driven by marketing strategies that leverage the ‘agent’ label to command higher prices and secure vendor lock-in.
Industry experts emphasize that most so-called agent launches lack critical qualities such as runtime independence, model swapability, and secure state management, which are essential for genuine autonomous agents. The proliferation of these feature-based ‘agents’ has made it a procurement skill to distinguish real platforms from marketing noise.
“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.”
— Thorsten Meyer
Extent of Industry Adoption of Misleading ‘Agent’ Labels
While industry analysis suggests that 90% of launches are feature-based, precise data on the total number of such launches and their adoption rates across different sectors remains incomplete. It is also unclear how many enterprises fully understand the distinction at the procurement level.
Industry Response and Evolving Procurement Criteria
Expect increased scrutiny in enterprise AI procurement, with organizations implementing the five-point filter to distinguish genuine platforms from feature-labeled products. Vendors may also adjust marketing strategies to better align with the technical realities, but the trend towards transparency is likely to grow as awareness spreads.
Key Questions
What defines a true AI agent in 2026?
A true AI agent operates autonomously, maintains persistent state in a customer-controlled environment, can be governed externally, and is portable across models and regions. It runs independently of user presence and can be swapped or upgraded without losing context.
Why are so many AI launches labeled as ‘agents’ if they are features?
Vendors use the ‘agent’ label to command higher prices and create a perception of advanced autonomy, even though most products are simple features built on vendor infrastructure. This marketing strategy increases dependency and lock-in.
What are the risks for enterprises relying on feature-based ‘agents’?
Dependence on vendor infrastructure limits control, complicates migration, and exposes organizations to vendor lock-in. It also creates a false sense of capability, potentially leading to strategic and operational setbacks.
How can enterprises identify genuine AI platforms?
Using criteria such as runtime independence, model swapability, persistent state management, security auditability, and portability can help distinguish real platforms from marketing-labeled features.
Source: ThorstenMeyerAI.com
