📊 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 product launches in 2026 are marketed as agents but are actually simple features built on vendor infrastructure. Only 10% are genuine platform plays, making procurement decisions more complex and risky.
Recent AI product launches in 2026 reveal that 90% of so-called ‘agent’ products are actually features built on vendor infrastructure, not true autonomous agents or platforms, leading to risks of vendor lock-in and unmet enterprise expectations.
In May 2026, a vendor announced an AI agent marketed as transforming knowledge work, but it was a simple chat box summarizing meeting notes, priced at $30 per seat per month. Meanwhile, an enterprise CIO recently canceled two AI pilots labeled as ‘agent platforms’ because they lacked core features such as runtime, state persistence, audit trails, or governance controls. This discrepancy highlights a widespread trend where products marketed as ‘agents’ are primarily features on top of vendor-controlled infrastructure, not autonomous, portable systems.
According to industry analysis, approximately 90% of AI launches in 2026 fall into this ‘feature’ category, while only about 10% qualify as genuine platform-based agents. True agents are defined by their ability to run autonomously, persist state independently, be governed externally, and be portable across infrastructure. Many products claiming to be agents fail these criteria, often locking enterprises into vendor ecosystems without the ability to migrate or control the underlying workflows and data.
This distinction is now a critical procurement skill, as enterprises risk investing in products that cannot be migrated, audited, or governed independently. The trend is reinforced by major enterprise vendors like Salesforce and SAP, which are pushing ‘headless 360’ data models that enable direct, agent-like interactions without human intervention, blurring the lines further.
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.
Mastering Enterprise Platform Engineering: A practical guide to platform engineering and generative AI for high-performance software delivery
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.
Synthetic Media Disclosure Tracker: A Professional Audit Trail for Artificial Intelligence Workflows and Digital Replicas
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 model state persistence solutions
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
vendor lock-in mitigation 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 for Enterprises
This trend matters because enterprises are increasingly investing millions into AI products marketed as autonomous agents, expecting portability, control, and compliance. The reality is that most of these products are features dependent on vendor infrastructure, leading to vendor lock-in, hidden costs, and potential security risks. Recognizing the difference can prevent costly misallocations and enable better procurement decisions, ensuring investments yield sustainable, controllable AI capabilities.
Evolution of ‘Agent’ Definitions and Market Trends
Prior to 2024, an ‘agent’ was a well-defined software entity capable of continuous operation, environment observation, action execution, state maintenance, and external governance. However, in 2026, the term has been co-opted by vendors to describe simple chat features or API calls that lack these core attributes. This shift has been driven by the desire to monetize AI products through branding and marketing, rather than delivering true autonomous systems. Recent pilot cancellations and product announcements underscore the gap between marketing claims and technical realities, with many products failing basic criteria for being considered genuine agents.
The market’s focus on ‘agent’ branding has led to a proliferation of features that are tightly coupled to vendor infrastructure, with little portability or control for the enterprise. As a result, procurement now requires a five-question filter to distinguish real platform plays from superficial features, emphasizing runtime, model flexibility, state management, auditability, and portability.
“What enterprises are buying under the label ‘agent’ in 2026 is overwhelmingly a feature on top of someone else’s infrastructure. The vendor monetizes the label, and the buyer inherits dependency.”
— Thorsten Meyer
Unclear Extent of Enterprise Exposure to ‘Feature’ Agents
While anecdotal evidence and pilot cancellations suggest widespread mislabeling, the exact proportion of enterprises affected and the long-term impact on vendor relationships remain uncertain. Further industry surveys are needed to quantify the full scope of this issue.
Steps for Enterprises to Identify Genuine AI Platforms
Enterprises should adopt a five-question filter before investing in AI ‘agents’: Does it operate without human login? Can the model be swapped without losing work? Where does the state reside? Is there an audit trail for security? What happens when the contract ends? Developing internal expertise in these criteria will help avoid vendor lock-in and ensure investments in sustainable AI infrastructure. Additionally, vendors may need to adapt their offerings to meet these standards as enterprise procurement becomes more sophisticated.
Key Questions
What is the main difference between a feature and a true AI agent?
A true AI agent can operate autonomously, persist state independently, be governed externally, and be portable across infrastructure. Features lack these capabilities and are often tied to vendor-controlled environments.
Why are so many products marketed as ‘agents’ if they are not?
Vendors use the ‘agent’ label to command higher prices and market perception, despite many products only offering simple tool calls or chat interfaces without autonomous capabilities.
How can enterprises avoid buying features disguised as platforms?
By applying a five-question filter focused on runtime independence, model flexibility, state control, audit trails, and data portability before procurement.
What are the risks of investing in ‘feature’ agents?
Risks include vendor lock-in, inability to migrate workflows or data, security vulnerabilities, and unmet operational expectations.
Will the market shift toward genuine AI platforms?
There is growing awareness and demand for portable, governable AI systems, which may incentivize vendors to develop more robust, platform-like offerings in the future.
Source: ThorstenMeyerAI.com
