📊 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
Most AI products branded as ‘agents’ in 2026 are actually features built on vendor infrastructure, not independent platforms. Only 10% meet the criteria of real, portable AI agents, making procurement decisions complex.
Most AI ‘agent’ launches in 2026 are actually features built on vendor-controlled infrastructure, not independent, portable agent platforms, according to recent industry analysis and enterprise pilot outcomes.
In May 2026, a vendor announced a new AI agent product marketed as transforming knowledge work, priced at $30 per seat per month, with a target of 4,000 paid seats by year-end. Simultaneously, an enterprise CIO canceled two of seven AI pilot projects, both marketed as ‘agent platforms,’ but lacking core features such as runtime, state persistence, or governance. This discrepancy exemplifies the ‘agent trap’—where vendors rebrand features as agents to monetize infrastructure dependency. Industry experts estimate that 90% of AI launches labeled as ‘agents’ are in fact features relying on vendor infrastructure, while only 10% are genuine platform plays that offer portability, model flexibility, and governance. This distinction is now a critical procurement skill, as most buyers are unaware they are inheriting vendor lock-in rather than acquiring autonomous, portable systems. The core issue is that the traditional definition of an AI agent—running continuously, maintaining state, and being governable—has been replaced by superficial branding aimed at increasing price and lock-in.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.
Practical Microsoft Copilot Studio: Build, Connect, and Deploy AI 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.
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.
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
Machine Learning Production Systems: Engineering Machine Learning Models and Pipelines
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 the ‘Agent’ Mislabeling in Enterprise AI
This mislabeling affects enterprise decision-making, leading to vendor lock-in, limited control, and higher costs. Buyers often assume they are acquiring independent platforms, but most are buying features that depend entirely on vendor infrastructure. Recognizing the difference is crucial for long-term AI strategy, as true agents offer portability, governance, and resilience, whereas features do not. The trend also influences market dynamics, with major vendors racing to rebrand existing products as ‘agent platforms,’ further muddying the landscape. As a result, organizations must develop procurement skills to distinguish between superficial branding and genuine platform capabilities, ensuring investments yield sustainable, flexible AI systems.
Evolution of AI ‘Agent’ Definitions and Market Trends
Before 2024, ‘agent’ in software referred to processes that operated continuously, maintained state, and were governable externally. However, by 2026, most so-called ‘agent’ launches are simple chat interfaces calling tools or APIs without persistent state or external control. Vendors have adopted the ‘agent’ label primarily for marketing, leveraging the perceived value of autonomy and control. Industry sources, including Thorsten Meyer, emphasize that true agents are characterized by features such as runtime independence, model substitutability, persistent state, and auditability—criteria that most current offerings fail to meet. Major enterprise vendors like Salesforce, ServiceNow, and Microsoft are shifting towards ‘headless 360’ data models, embedding agent-like capabilities directly into their platforms, blurring the lines further. This evolution underscores a widening gap between genuine AI platforms and superficial feature sets marketed as agents.
“90% of ‘AI agent’ launches in 2026 are really just features relying on vendor infrastructure, not true portable platforms.”
— Thorsten Meyer
What Details About the Market and Future Developments Remain Unclear?
It is still unclear how widespread the adoption of genuine platform-based AI agents will become in the next year, and whether vendors will shift towards more transparent and portable offerings. The long-term impact of the ‘agent’ rebranding trend on enterprise security, compliance, and innovation remains to be seen, as does the evolution of technical standards defining true AI agents.
Next Steps for Enterprise Buyers and Market Evolution
Enterprises should develop procurement criteria based on the five-point filter to distinguish real AI platforms from features. Expect vendors to continue rebranding efforts, but more organizations may adopt technical assessments to ensure portability, governance, and control. Regulatory and industry standards may also emerge to define what qualifies as a true AI agent, influencing future market offerings and enterprise strategies.
Key Questions
How can I tell if an AI product is a true agent or just a feature?
Use the five-point filter: check if it runs without a human logged in, if the model can be swapped without losing work, where the state is stored, if it emits audit trails, and what happens when the contract ends. Genuine agents meet all five criteria.
Why are vendors rebranding features as agents?
Vendors do this to capitalize on the perceived value and market demand for autonomous AI systems, increasing pricing and lock-in without delivering true portability or control.
What risks does relying on feature-based ‘agents’ pose for enterprises?
It leads to vendor lock-in, limited control over the system, higher costs, and potential security and compliance issues due to lack of auditability and portability.
Will true AI agents become more common in the near future?
It is uncertain. While some vendors may develop and promote genuine platform-based agents, the current trend suggests superficial branding will continue unless industry standards and procurement practices evolve.
Source: ThorstenMeyerAI.com
