📊 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 simple features built on vendor infrastructure, not independent platforms. This mislabeling affects enterprise buying decisions and long-term flexibility.
Recent industry analysis confirms that approximately 90% of AI ‘agent’ launches in 2026 are actually features built on vendor infrastructure, not independent, governable platforms. This misclassification impacts enterprise procurement and long-term operational flexibility.
In May 2026, vendors announced AI products labeled as ‘agents,’ promising to transform knowledge work. However, investigations reveal that most of these products are simple chat-based features tied to vendor infrastructure, lacking core agent capabilities like persistent state, governance, or model portability. For example, a vendor’s chat box for meeting summaries, priced at $30 per seat per month, exemplifies this trend. These products often depend on vendor-hosted models, with no options for model or data residency choice, and cannot be migrated or governed outside the vendor ecosystem.
Industry insiders note that only about 10% of these launches qualify as true infrastructure platforms—capable of running independently, with portable state, and integration into enterprise security and governance systems. This disparity has led to a new procurement skill: distinguishing between marketing labels and actual platform capabilities. The distinction is critical because enterprises inheriting vendor lock-in face significant risks, including loss of control over data, workflows, and operational continuity.
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.
HP ProBook 440 G11 Business AI PC Laptop (14" FHD+ Anti-Glare, Intel 12-Core Ultra 5 125U (> i7-1355U), 16GB DDR5 RAM, 512GB SSD), Fingerprint, Webcam w/Shutter, Ethernet, HDMI, Wi‑Fi 6E, Win 11 Pro
BUSINESS‑ORIENTED LAPTOP – Within the ProBook line, HP ProBook 440 G11 delivers an excellent balance, offering a lighter,…
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.
Artificial Intelligence (AI) Governance and Cyber-Security: A beginner’s handbook on securing and governing AI systems (AI Risk and Security Series)
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
Practical MLOps: Operationalizing Machine Learning Models
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
enterprise data residency 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.
Why Mislabeling ‘Agents’ Risks Enterprise Flexibility
This trend matters because misclassified products create vendor lock-in, limit control over data and workflows, and inflate costs. Enterprises relying on these features may find themselves unable to adapt or migrate, risking operational resilience and security. The false promise of ‘agent’ capabilities can lead to strategic misalignment and increased dependency on vendor infrastructure, which may hinder innovation and agility in the long term.
Evolution of the ‘Agent’ Definition and Market Trends
Prior to 2024, ‘agent’ in software referred to a process that operated continuously, maintained state, and was governable externally. By 2026, the term has been co-opted by vendors to label simple chat interfaces or API calls that lack these core features. The market’s pivot toward branding basic features as ‘agents’ is driven by marketing incentives to command higher prices. Industry analysts, including Thorsten Meyer, highlight that most current launches fail key criteria for true agents, such as model portability, persistent state, and security compliance.
Major enterprise vendors like Salesforce, SAP, and Microsoft are aligning their product strategies around ‘headless 360’ data models, where agents read and write directly to enterprise data without human intervention, further blurring the line between features and platforms.
“90% of ‘AI agent’ launches in 2026 are just features dressed as infrastructure, not real platforms.”
— Thorsten Meyer
Extent of Enterprise Adoption and Future Trends
It remains unclear how widespread the misclassification is across different industries and whether vendors will adapt their offerings to meet true platform standards. The long-term impact on enterprise security, data control, and operational agility is still emerging, and some vendors may shift strategies in response to market pressures or regulatory scrutiny.
Implications for Procurement and Platform Development
Enterprises should refine their procurement criteria, applying the five-point filter to distinguish genuine platforms from features. Future developments may include stricter standards for ‘agent’ claims, increased emphasis on portability, and vendor accountability for security and governance. Monitoring vendor product evolution and regulatory responses will be critical in the coming months.
Key Questions
How can I tell if an AI product is a true platform or just a feature?
Apply the five-point filter: check if it runs without a logged-in user, if the model is replaceable, if state is stored externally, if it emits security logs, and if the work is portable when the contract ends.
Why are vendors labeling features as ‘agents’?
Labeling features as ‘agents’ allows vendors to command higher prices and create a perception of advanced, autonomous capabilities, even when the product lacks core agent functionalities.
What risks do enterprises face by relying on these ‘agent’ features?
Risks include vendor lock-in, loss of control over data and workflows, security vulnerabilities, and difficulty migrating or scaling operations independently.
Will the market shift back toward genuine platform offerings?
It is uncertain. Increasing awareness, regulatory scrutiny, and enterprise demand for control may incentivize vendors to develop more portable, governable AI platforms in the future.
Source: ThorstenMeyerAI.com
