📊 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’ launches in 2026 are misrepresentations, serving as features on vendor infrastructure rather than independent platforms. This creates vendor lock-in and misleads buyers about true capabilities.
In May 2026, a major enterprise CIO canceled two AI pilot projects branded as ‘agent platforms,’ revealing that most so-called AI agents are actually features built on vendor infrastructure rather than true, portable platforms.
The core issue is that 90% of AI launches labeled as ‘agents’ in 2026 are merely features—such as chat boxes or summaries—tied to vendor cloud infrastructure, lacking the autonomy, governance, and portability of genuine agent systems. These products often depend on vendor dashboards, do not support model swapping, and cannot persist or export state independently.
For example, a recent vendor product announced as an AI agent was a simple chat interface with no runtime, state management, or governance capabilities. Meanwhile, enterprise pilots for ‘agent platforms’ were halted because they lacked fundamental features like model independence, state control, audit trails, and portability, exposing the superficiality of many so-called agent offerings.
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.
AI agent platform with model portability
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.
The Modern AI Agent with Claude AI: A Practical Guide to Building Autonomous Workflows for Real-World Use
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
Building AI-Powered Products: The Essential Guide to AI and GenAI Product Management
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
Workflow Automation with Microsoft Power Automate: Design and scale AI-powered cloud and desktop workflows using low-code automation
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 Features as Agents Risks Enterprise Dependency
This trend matters because it leads to vendor lock-in, where enterprises rely on proprietary infrastructure that cannot be easily migrated or controlled. It also inflates expectations, causing organizations to invest in capabilities that are essentially superficial features, not true autonomous agents. Recognizing the difference is now a critical procurement skill, preventing costly misalignments and vendor dependency.
The Evolution of the ‘Agent’ Definition and Industry Practices
Before 2024, an ‘agent’ in software was a process that operated continuously, maintained state, and could be governed externally. Many vendors now use the term loosely to describe simple chat interfaces or feature sets that only work when users are actively engaged. This shift is driven by marketing, not technical capabilities, leading to widespread mislabeling.
In 2026, the industry is flooded with products branded as ‘agents’ that lack the core attributes of true autonomous systems. Instead, they are often just features built on vendor cloud infrastructure, making the term ‘agent’ more of a marketing label than a technical descriptor.
“The label has been chosen for what it does to the price tag, not for what it describes.”
— Thorsten Meyer
Extent of Industry Mislabeling and Future Trends
While evidence suggests a majority of AI launches are superficial features, precise industry-wide data is limited. It remains unclear how many vendors will shift toward genuine platform capabilities or continue to rely on superficial branding.
Emerging Procurement Skills and Industry Standards
Enterprises will need to develop new procurement filters, such as the ‘Five-Point Filter,’ to distinguish real AI platforms from marketing claims. Industry standards may evolve to better define what constitutes a true agent, potentially reducing superficial labeling and promoting more portable, governable AI solutions.
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 human login, supports model swapping, persists state externally, provides audit logs, and if work can be exported when the contract ends.
Why do vendors label features as agents?
To leverage the perceived value of autonomy and platform capability, inflating product pricing and creating dependency, even when the product lacks core agent attributes.
What are the risks of adopting superficial ‘agent’ products?
Vendor lock-in, inability to migrate or control workflows, and overestimating AI capabilities, which can lead to costly re-architectures and security issues.
Will the industry shift toward genuine AI platforms?
It is uncertain; some vendors may evolve to offer more portable, governable solutions, but the current trend suggests superficial labeling will persist unless driven by industry standards or procurement reforms.
Source: ThorstenMeyerAI.com
