📊 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, approximately 90% of AI products marketed as ‘agents’ are actually simple features layered on vendor infrastructure, not independent platforms. This mislabeling complicates procurement and raises security and control concerns.
Recent AI product launches in 2026 reveal that roughly 90% of so-called ‘agent’ deployments are actually features built on vendor infrastructure, not independent, governable platforms. This mislabeling affects enterprise procurement decisions and highlights a broader industry trend of inflated claims.
In May 2026, a vendor announced an AI agent marketed as a transformative tool for knowledge workers, priced at $30 per seat per month, with a target of 4,000 paid seats by year-end. Simultaneously, a CIO canceled two of seven AI pilots, both branded as ‘agent platforms,’ but lacking core features such as runtime, state management, or governance capabilities. These incidents exemplify the ‘agent trap,’ where vendors label simple feature sets as full-fledged agents to command higher prices.
Industry analysis indicates that approximately 90% of AI launches labeled as ‘agents’ in 2026 are actually features layered on vendor-controlled infrastructure. These offerings typically run on the vendor’s cloud, are not portable, and lack the ability to be governed or integrated with enterprise security tools. The remaining 10% are genuine platform plays that support portability, governance, and state persistence. Distinguishing between them has become a key procurement skill.
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.
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 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 platform portability solutions
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
AGENTIC AI SECURITY HANDBOOK: Design Patterns, Threat Models, and Defensive Controls for Autonomous LLM 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
AI runtime and state management tools
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 Misleading ‘Agent’ Labels for Enterprises
This trend matters because enterprises relying on mislabeled ‘agents’ risk vendor lock-in, security vulnerabilities, and loss of control over their workflows and data. The misrepresentation inflates the perceived value of these products, leading to potentially costly investments in features that do not meet true operational or governance needs. Understanding the difference is crucial for making informed procurement decisions and avoiding dependency on non-portable solutions.
Industry Shift Toward ‘Headless’ Agent Architectures
Historically, an ‘agent’ was a process running continuously, maintaining state, and acting autonomously. In 2026, many vendors are repurposing the term for simple chat-based features that invoke tools without persistent state or external governance. Major enterprise players like Salesforce, ServiceNow, and Microsoft are increasingly integrating ‘agent’ configurations into their existing data models, blurring the line between human roles and automated agents. This shift reflects a strategic move to embed AI deeper into enterprise workflows under the guise of ‘agent platforms,’ often without the core capabilities traditionally associated with autonomous agents.
“The label has been chosen for what it does to the price tag, not for what it describes.”
— Thorsten Meyer
Extent of Enterprise Awareness and Impact
It is still unclear how widespread awareness of this mislabeling is among enterprise buyers and whether procurement practices are adapting accordingly. Additionally, the long-term impact on security, control, and vendor relationships remains to be fully assessed as more products are launched and adopted.
Emerging Standards and Buyer Vigilance in 2026
Going forward, enterprises are expected to develop more rigorous procurement filters, such as the five-point test outlined by industry experts, to distinguish genuine platforms from superficial features. Vendors may also face increased scrutiny and calls for transparency regarding the capabilities and governance of their ‘agent’ offerings. The industry will likely see a push toward establishing clearer standards for what constitutes a true autonomous agent versus a feature label.
Key Questions
How can I tell if an AI ‘agent’ is a true platform or just a feature?
Use the five-point filter: check if it runs without human login, if the model can be swapped without losing work, where state is stored, if it provides an audit trail, and what happens when the contract ends. True platforms meet all five criteria.
Why do vendors label features as agents if they are not?
Vendors use the ‘agent’ label to command higher prices and create a perception of advanced autonomy, even when the product is simply a feature layered on existing infrastructure.
What are the risks of relying on these ‘agent’ features?
Risks include vendor lock-in, lack of portability, security vulnerabilities, and loss of control over workflows and data, especially if the product cannot be governed or audited effectively.
Will the industry move toward better standards for ‘agent’ definitions?
Yes, there is growing recognition of the need for clearer standards and procurement filters to distinguish genuine autonomous agents from superficial features, which will likely influence future product development and purchasing decisions.
Source: ThorstenMeyerAI.com
