📊 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 actually features built on vendor infrastructure, not independent platforms. This creates vendor lock-in and misleads buyers. Only 10% meet true agent criteria, making procurement more complex.
Recent AI product launches in 2026 reveal that approximately 90% of so-called ‘agent’ deployments are actually features built on vendor infrastructure, not independent agent platforms, exposing a widespread industry mislabeling that risks vendor lock-in.
In May 2026, a vendor announced an AI agent marketed as transforming knowledge work, but further investigation shows it is a simple chat feature with limited capabilities, hosted entirely on the vendor’s cloud infrastructure. Simultaneously, an enterprise CIO canceled two AI pilot projects labeled as ‘agent platforms,’ both of which lacked core agent features such as runtime independence, state persistence, or governance mechanisms. Experts say that most AI launches in 2026 fall into this category, with only about 10% representing true platform-level agents that are portable, governable, and durable.
This discrepancy stems from the industry’s redefinition of ‘agent,’ which historically implied a process capable of continuous operation, environment observation, action, and external governance. Today, many vendors rebrand simple chat tools as ‘agents’ to command higher prices, despite lacking these fundamental features. This trend complicates procurement, as buyers must now discern between real infrastructure and superficial features, a skill that has become essential in 2026.
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.
Hermes Agentic AI Platform: Delivering Autonomous AI Agents at Scale Across Any Enterprise
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 Workflow Automation for Bloggers: Build a Simple Content System to Research, Write, Optimize, and Repurpose Posts Faster with AI and No-Code Tools (AI Toolkit for Bloggers 2026 Book 8)
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
AI-Native Software Delivery: Proven Practices to Produce High-Quality Software Faster
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 state persistence solutions
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 Mislabeling AI Features as Agents
This mislabeling impacts enterprise decision-making by inflating expectations of AI capabilities and fostering vendor lock-in. Organizations investing in these so-called agents risk losing control over their workflows, data, and security, as they rely on vendor-hosted solutions that are difficult to migrate or audit. The proliferation of feature-based ‘agents’ also distorts market perception, making it harder for genuine platform providers to differentiate themselves and for buyers to make informed choices.
Industry Shift Toward Headless, Browserless Data Models
Major enterprise vendors like Salesforce, ServiceNow, SAP, and Microsoft are promoting ‘agent platforms’ that integrate directly with existing data models—such as Customer 360 or Employee 360—without requiring human interaction. This ‘headless 360’ approach enables agents to read and write data directly, blurring the line between traditional workflows and autonomous AI processes. While these developments promise efficiency, they also embed vendor dependencies and complicate governance, especially when the underlying infrastructure is proprietary and non-portable.
The industry’s pivot toward browserless, data-centric agent configurations reflects a broader trend: automation increasingly replaces human roles, but often without clear standards or transparency, raising concerns about security, control, and long-term viability.
“The label has been chosen for what it does to the price tag, not for what it describes.”
— Thorsten Meyer
Extent of Industry Adoption and Future Trends
It remains unclear how many enterprises are fully aware of this mislabeling or are actively distinguishing real agents from features. The long-term impact of this trend on vendor competition, security, and enterprise agility is still developing, with some experts cautioning that the true scale of the issue may be underreported due to marketing obfuscation.
Next Steps for Buyers and Vendors in AI Procurement
Organizations should adopt rigorous filtering criteria—such as verifying runtime independence, model swapability, state control, and auditability—before investing in AI ‘agents.’ Vendors may need to clarify their offerings and move toward truly portable, governable platforms. Industry standards and transparency initiatives could emerge to help buyers differentiate between features and genuine infrastructure, reducing vendor lock-in and improving security.
Key Questions
What is the main difference between a feature and a true AI agent?
A true AI agent operates continuously, maintains external state, can be governed independently, and is portable across environments. Features are typically limited to specific functions within vendor-controlled infrastructure.
Why is mislabeling ‘features’ as ‘agents’ problematic?
It creates false expectations, leads to vendor lock-in, complicates security and governance, and can result in costly migrations or security breaches.
How can enterprises identify genuine AI agents?
By applying criteria such as runtime independence, model swapability, explicit state management, audit trail availability, and infrastructure portability.
What are the risks of adopting feature-based ‘agents’?
Risks include vendor lock-in, lack of control over data and workflows, security vulnerabilities, and difficulty in migrating or scaling solutions.
Source: ThorstenMeyerAI.com
