📊 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 ‘agent’ products launched in 2026 are misrepresented features built on vendor infrastructure, not true autonomous agents. This creates hidden dependencies and lock-in for enterprises.
Recent AI product launches in 2026 demonstrate that approximately 90% of so-called ‘agent’ deployments are actually features built on vendor-controlled infrastructure, not true autonomous agents. This misrepresentation impacts enterprise dependency and procurement strategies.
In May 2026, vendors announced AI products claiming to ‘transform knowledge work,’ but closer inspection reveals most are simple chat features linked to vendor infrastructure, lacking key qualities of true agents. These products typically run solely on vendor cloud services, lack portability, and do not allow model or state swapping without vendor lock-in. An enterprise CIO recently canceled two pilots labeled as ‘agent platforms’ because they lacked runtime, governance, or persistent state, exposing the gap between marketing and reality. Industry experts warn that this trend, dubbed the ‘agent trap,’ has led to a situation where 90% of AI launches are essentially features that depend on vendor infrastructure, with only 10% qualifying as genuine platform plays. This shift complicates procurement, as organizations must now develop skills to distinguish real infrastructure from marketing claims.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 COHERENCE in the Age of AI
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.
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
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 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 AI ‘Agent’ Claims for Enterprises
This trend means enterprises are often unknowingly locking into vendor-controlled infrastructure, which hampers portability, governance, and long-term control. It inflates costs and dependencies, making it harder to upgrade or switch platforms. Understanding the difference between features and true infrastructure is critical for making informed procurement decisions and avoiding vendor lock-in that can persist long after initial deployment.Evolution of the ‘Agent’ Definition and Market Trends in 2026
Before 2024, ‘agent’ in software referred to processes that operated continuously, maintained state, and were governable externally. However, by 2026, vendors have rebranded simple chat features as ‘agents’ to capitalize on AI hype. Many of these products are lightweight, run only when a user interacts, and lack the ability to swap models or persist state independently. A key driver is the enterprise push for ‘headless’ data models, where AI components read and write directly to core systems without human intervention, blurring the line between automation and feature enhancement. Recent high-profile product announcements from Salesforce, ServiceNow, and Microsoft exemplify this shift, emphasizing configurability over true autonomy.“What enterprises are buying—under the word agent—is overwhelmingly a feature on top of someone else’s infrastructure. The vendor monetizes the label, and the buyer inherits the dependency.”
— Thorsten Meyer
Extent of Market Deception and Long-term Impact
While the analysis suggests that 90% of AI launches are features rather than true agents, precise quantification remains challenging due to inconsistent vendor disclosures and evolving definitions. It is also unclear how quickly enterprises will adapt their procurement practices to this new reality, or how vendors will respond to increasing scrutiny.
Future Steps for Buyers and Industry Standards
Enterprises should adopt rigorous filtering strategies, such as verifying runtime independence, model swapability, and state ownership, before investing in AI products labeled as agents. Industry bodies and standards organizations may develop certifications or guidelines to distinguish genuine autonomous agents from feature-based offerings. Vendors may also need to clarify their product capabilities to prevent further misrepresentation. Monitoring these developments will be crucial as the market matures and organizations seek to avoid vendor lock-in.
Key Questions
How can I tell if an AI product is a true agent or just a feature?
Apply the five-point filter: check if it runs without user login, if models can be swapped without losing work, where state is stored, if it produces security logs, and whether work can be exported. True agents meet all these criteria.
Why are vendors labeling features as agents?
Vendors do this to capitalize on AI hype, increase perceived value, and command higher prices, often without providing the infrastructure needed for true autonomy.
What are the risks of deploying feature-based ‘agents’?
Organizations risk vendor lock-in, lack of control, security vulnerabilities, and higher long-term costs, as they depend on vendor infrastructure and cannot easily migrate or upgrade.
Will the market correct itself over time?
It is uncertain. Increased scrutiny, procurement discipline, and industry standards could push vendors to deliver genuine infrastructure, but current trends favor marketing over technical fidelity.
Source: ThorstenMeyerAI.com
