📊 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 actually features layered on vendor infrastructure, not independent platforms. This mislabeling leads to vendor lock-in and inflated expectations. True infrastructure plays are only about 10%.
Most AI ‘agent’ launches in 2026 are actually features built on vendor infrastructure, not autonomous, governable platforms, according to recent industry analysis and enterprise cancellations.
A vendor announced an AI agent product claiming it would ‘transform knowledge work,’ priced at $30 per seat per month, targeting 4,000 paid users by year-end. Meanwhile, an enterprise CIO canceled two of seven AI pilots branded as ‘agent platforms,’ citing their lack of runtime, state management, or governance capabilities. These examples illustrate a widespread pattern where what is marketed as an ‘agent’ often lacks the core qualities of a true autonomous process. Industry experts, including Thorsten Meyer, note that 90% of AI launches in 2026 are merely features layered on vendor infrastructure, with only 10% representing genuine platform architectures. This distinction is now a critical procurement skill, as many buyers are misled by marketing labels, inheriting dependency on vendor-controlled environments that cannot be easily migrated or governed independently.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.
The Power Platform Playbook for Digital Transformation: Implement strategy, automation, and AI for scalable digital transformation
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.
Agentic AI Engineering: The Definitive Field Guide to Building Production-Grade Cognitive Systems (Generative AI Revolution Series)
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
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.
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 portability and migration 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.
Why Mislabeling AI ‘Agents’ Risks Enterprise Security and Flexibility
This misrepresentation inflates vendor dominance, increases enterprise dependency, and hampers security and compliance efforts. Genuine platform-based AI offers portability, control, and auditability, essential for enterprise resilience. The widespread use of superficial ‘agent’ features risks locking companies into vendor ecosystems with limited governance and high switching costs, potentially exposing them to security vulnerabilities and operational inflexibility.The Evolution of ‘Agent’ Definitions and Market Confusion
Before 2024, ‘agent’ in software referred to processes that ran continuously, maintained state, and were governable externally. However, in 2026, many products labeled as ‘agents’ are simple chat interfaces or feature layers that invoke tools without persistent state or external governance. Industry analysis by Thorsten Meyer highlights that vendors increasingly market these features as ‘agent platforms’ to command higher prices, despite lacking the core capabilities traditionally associated with agents. This shift reflects a broader trend where marketing labels are divorced from technical reality, creating confusion among enterprise buyers and complicating procurement decisions. The emergence of ‘headless 360’ data models further blurs the line, as major vendors embed ‘agent-like’ features into existing enterprise systems without delivering true autonomous or portable platforms.“The label has been chosen for what it does to the price tag, not for what it describes.”
— Thorsten Meyer
Extent of Enterprise Adoption of True AI Platforms
It is still unclear how many enterprises are adopting the 10% of genuine AI platform solutions versus superficial features. The actual market share and long-term viability of true platform architectures remain uncertain, as many organizations may continue to be misled by marketing claims or lack the technical expertise to differentiate.
Emerging Standards and Procurement Skills for AI ‘Agents’
Industry experts predict that procurement teams will develop more rigorous filters, such as the five-point test outlined by Meyer, to distinguish genuine platforms from features. Additionally, vendors may face increased scrutiny and regulation around marketing claims, pushing the market toward clearer standards. The development of technical benchmarks for true agent capabilities is expected to accelerate, helping enterprises avoid costly dependencies and ensure security, portability, and governance in their AI investments.
Key Questions
What exactly distinguishes a true AI agent from a feature?
A true AI agent runs autonomously, maintains persistent state, can be governed externally, and can be swapped or upgraded without losing context. Features lack these qualities, often relying on vendor-controlled infrastructure and limited to session-based interactions.
Why are vendors marketing features as ‘agents’?
Marketing the features as ‘agents’ allows vendors to command higher prices and create the perception of advanced autonomy. It also simplifies messaging for enterprise buyers unfamiliar with the technical distinctions.
What risks do enterprises face by relying on superficial ‘agent’ features?
Dependence on vendor infrastructure limits control, complicates security and compliance, and increases switching costs. It also reduces flexibility and can expose organizations to security vulnerabilities if the vendor’s infrastructure is compromised.
How can organizations identify genuine AI platform solutions?
Organizations should apply filters such as: Does the solution run without human login? Can the model be swapped without losing work? Does it store state externally? Does it produce audit logs? Can the work be migrated or exported? These criteria help differentiate real platforms from features.
Source: ThorstenMeyerAI.com
