Model your AI future.

The Headline

The enterprise has become an agent-operated institution.

That is the largest movement in this October 2028 projection. Critical workflows operated by AI rise from 7% to 24.1%. Agents per human in instrumented teams move from 0.3 to 1.6. The market index lifts from 79.4 to 91.5, not because every layer wins equally, but because the control point shifts from applications and models to governed execution.

The biggest category move is Layer 6 — Agent Tools, rising from 74.4 to 95.5. That is a 21.1-point jump. It is the architectural tells-the-truth layer. When agents become responsible for work, enterprises need routing, memory, permissions, monitoring, rollback, evaluation, and escalation. The model is no longer the operating system. The workflow is.

This is still a projection, not a prophecy. The scenario assumes model capability rises, cost declines accelerate, and SaaS disruption is high. No assumption shock has fired in this timeline. There is no sudden external capability discontinuity inserted into the forecast. The numbers are the consequence of the premise.

What Happened to SaaS

SaaS is not dead. It is demoted.

Layer 7 — Commercial Tools rises from 78.3 to 88.4. That is healthy on paper. But the value migrates away from seats and toward outcomes, embedded agents, workflow depth, and proprietary context. SaaS seat pricing renegotiated moves from 6% to 21.8%. One-fifth of enterprise SaaS pricing is now under direct pressure from agent substitution, bundled automation, and procurement teams that have finally learned to ask why a human seat is the right unit of value.

The application layer becomes headless in the places where workflows are repetitive, cross-system, and measurable. Agents execute across CRM, support, finance, legal, security, HR, procurement, and operations. The user interface remains, but it is no longer always the workplace. Sometimes it is the audit surface. Sometimes it is the exception queue. Sometimes it is just the place a manager goes to approve the work the system already did.

That is why the strongest commercial-tools gainer is Harvey, up 19.9. Vertical depth matters. Workflow ownership matters. Generic application gravity matters less. Microsoft, up only 3 in commercial tools, is not projected to disappear. It is projected to defend a vast installed base while the marginal dollar looks for agent-native work completion. CrowdStrike, up 6.6 in commercial tools, also holds but underperforms the disruption curve. Security remains essential. Security workflows still need authority, evidence, and response, not just dashboards.

The old SaaS bargain was simple: buy the system of record, train the users, count the seats. The 2028 bargain is harsher. Prove the workflow runs better with your agent, your data, your controls, and your economics. Otherwise the seat becomes a line item waiting for renewal.

The Data and Context Layer

The data layer stops being a passive estate and becomes the context supply chain.

Layer 3 — Data Management rises from 86 to 94.2. That is an 8.2-point move from already-high maturity. It matters because the lakehouse, warehouse, catalog, lineage, and governance stack now sit underneath live agent execution. Data management is no longer judged only by analyst productivity or dashboard trust. It is judged by whether autonomous systems can retrieve, reason, act, and be audited without poisoning the enterprise.

Layer 4 — AI-Ready Data rises from 71.8 to 86.9, the second-largest structural move after agent tools. Enterprise data that is agent-ready moves from 19% to 35%. That is still not a majority. It is enough to change operating models, but not enough to declare victory. The hard work is not vectorizing documents. The hard work is permissions, freshness, lineage, policy inheritance, entity resolution, semantic consistency, and context scoping.

Vercel is the named gainer here, up 22 in AI-ready data. The mechanism is not traditional data warehousing. It is the convergence of application delivery, retrieval, developer workflow, and real-time context assembly. In this projection, the edge between application runtime and context runtime gets thinner. Developers want governed context close to where agents and user experiences are being built.

Layer 3 has no named gainer or decliner in the dashboard, and that is the point. Data management holds the center. It becomes more important, but less theatrical. The market does not need another slogan for the lakehouse. It needs governed context that agents can use without leaking authority across systems. Architecture becomes a control discipline again. The grown-ups had a good run.

Models, Labor, and the Open-Weight Balance

Layer 2 — Model Portfolio rises from 88.4 to 95. The models get better. They also get less magical.

High model capability is one of the scenario’s premises, and the projection reflects it. More workflows can be decomposed, delegated, evaluated, and executed. The frontier providers still matter, especially for complex reasoning, multimodal work, code generation, and high-value synthesis. But the enterprise does not standardize on one model. It standardizes on a portfolio: frontier models for hard work, smaller models for bounded tasks, open weights for controllable inference, and specialized models where latency, cost, or policy requires them.

Enterprise inference on open weights rises from 23% to 31.9%. That is not an open-source takeover. It is a rebalancing. Open weights become the economic and governance pressure valve. They are used where the task is known, the data is sensitive, the cost curve matters, or the enterprise wants operational leverage over deployment. The proprietary frontier remains relevant. The default procurement conversation changes.

OpenAI rises 3.8 in the model portfolio layer. Anthropic rises 4. These are gains, but they are low relative to the category. The interpretation is not collapse. It is normalization. Model providers become part of the labor platform, not the whole labor platform. Their value is increasingly mediated by agent orchestration, governed context, evaluation, observability, and enterprise authority.

The labor question is now explicit. Models do not merely assist workers. In bounded workflows, they perform units of labor. The providers that win are not only the ones with the smartest model. They are the ones that fit into a governed production system where actions are authorized, costs are measurable, and errors have owners.

The Economics of Intelligence

The cost curve finally shows up in the CFO’s operating model.

Cost per governed action falls from an index of 100 to 65.6. That is the economic hinge of the scenario. Intelligence gets cheaper, but not in the abstract. Governed action gets cheaper. The distinction matters. A token is not a business outcome. A completed, permissioned, logged, reversible workflow step is closer.

Layer 1 — AI Infrastructure rises from 85.8 to 93.8. The infrastructure layer remains critical, but the gains are more measured. NVIDIA rises only 3. Amazon Web Services rises 4.7. Both remain essential to the market architecture, yet their projected deltas lag the layers where enterprise control shifts. Compute is still scarce in pockets. Specialized accelerators, inference optimization, capacity planning, and regional deployment still matter. But falling costs and open-weight adoption reduce the monopoly rent on raw infrastructure.

Capital flows toward the layers that turn cheaper intelligence into accountable work. Agent tools, AI-ready data, developer tools, and vertical commercial tools absorb the economic surplus. Layer 5 — Developer Tools rises from 78.8 to 92.4. Cursor gains 18 because developer labor itself is replatformed around AI-native coding, refactoring, testing, and system comprehension. The developer is not replaced. The developer becomes the manager of a faster and more error-prone machine.

What gets cheap: drafting, classification, summarization, first-pass code, data extraction, routine support, workflow routing, and repetitive analysis. What stays expensive: authority design, context governance, exception handling, integration debt, evaluation, security review, and change management. The CFO learns a blunt lesson. AI lowers the cost of doing the work. It does not lower the cost of knowing which work should be done.

Workforce and the Org Chart

The org chart now has machines in it.

Agents per human in instrumented teams rise from 0.3 to 1.6. That is not a metaphor. In the teams that have instrumented their work, a human worker now supervises, delegates to, reviews, or collaborates with more than one active agent. This changes spans of control before it changes job titles. The first durable redesign is not “AI department.” It is the human-agent operating model inside every function.

Roles compress where work is high-volume, rules-bound, and evidence-rich. Support triage, sales operations, finance operations, compliance prep, legal intake, procurement analysis, reporting, QA, and basic software maintenance all absorb agent labor. Middle layers of coordination are squeezed. The work of asking for status, moving information between systems, and preparing first drafts loses its premium.

New leverage appears in roles that can define outcomes, manage exceptions, tune operating rules, and maintain trust. Process owners become agent operators. Analysts become workflow designers. Developers become system foremen. Managers become reviewers of evidence, not collectors of updates. The best employees are not the ones who “use AI.” By 2028 that phrase sounds like saying someone uses email. The best employees know how to allocate judgment.

The board-level issue is capacity planning. Headcount plans built around seat-based software and human throughput are stale. The new planning unit is governed work. How many actions can be safely delegated? How much context is agent-ready? Which workflows have measurable error tolerance? Which approvals remain human by law, risk, or strategy? The org chart follows those answers.

Governance, Security, and Authority

Governance moves from policy documents to runtime authority.

The enterprise can no longer govern AI by reviewing prompts after the fact. Agents act across systems. They retrieve sensitive data, make recommendations, update records, draft communications, trigger workflows, and escalate decisions. The control plane must know who the agent is acting for, what authority it has, what context it can access, what tools it can invoke, and what evidence it must leave behind.

This is the rise of the authority graph. Identity and access management are necessary but insufficient. The authority graph connects humans, agents, tools, datasets, workflows, policies, approvals, and audit trails. It defines not only whether a user can access a system, but whether an agent can act on behalf of that user in a specific workflow under specific conditions. That is the new perimeter. The old perimeter has been tired for years.

The security posture shifts to audit-the-workflow. Logs of model calls are table stakes. Enterprises need traceability across retrieval, reasoning, tool use, data mutation, approval, exception, and rollback. Context contamination becomes a material risk. A bad document, stale policy, poisoned retrieval source, or mis-scoped permission can propagate through automated work faster than a human team can notice. This is not science fiction. It is basic operations with faster hands.

Regulation intensity rises in practical effect, even without assuming a new shock. Boards, regulators, customers, and insurers all ask the same questions: who authorized the action, what evidence supported it, which data was used, and how can it be reversed? The companies that answer with architecture move faster. The companies that answer with a committee move slower, then call it prudence.

Winners and Losers

The biggest winners are the companies closest to governed agent execution.

Zeroclaw leads the projected gainers in agent tools, up 30. Hermes follows at 26. Sierra rises 24.6. The mechanism is clear: Layer 6 — Agent Tools moves from 74.4 to 95.5, and the market rewards control planes, agent reliability, workflow execution, and enterprise-grade orchestration. The agent layer becomes where the business sees the work happen. That is a good place to be.

Vercel gains 22 in AI-ready data because the build layer and context layer converge. Cursor gains 18 in developer tools because software creation becomes agent-managed and spec-driven. Harvey gains 19.9 in commercial tools because vertical expertise, workflow depth, and outcome orientation defend value better than generic seat software. These are not random deltas. They are the map of where enterprise spend migrates.

The projected decliners are not necessarily losers in absolute terms. They are underperformers against the new control points. Microsoft rises only 3 in commercial tools, showing the burden of defending a large installed SaaS estate as pricing and seat logic erode. NVIDIA rises only 3 in AI infrastructure, and Amazon Web Services rises 4.7, reflecting a market where compute remains essential but the margin narrative shifts toward optimization, inference mix, and higher-level control.

OpenAI rises 3.8 and Anthropic rises 4 in model portfolio. Again, not collapse. Repricing. The model layer is foundational, but it is no longer the only place strategic value accumulates. CrowdStrike rises 6.6 in commercial tools, held back by the same force affecting much of security software: the buyer wants autonomous response, evidence, and authority-aware remediation, not more panes of glass.

Opportunity Spaces and New Entrants

The largest white space is Layer 6 — Agent Tools, with an opportunity score of 70.2 out of 100.

The frontier is a cross-system agent control plane and authority graph. The likely entrant is not another chatbot company. It is an agent-operations and reliability specialist. This company owns execution policy, permissions, evaluation, observability, incident response, and rollback across agents. It looks less like a productivity app and more like the operations layer for synthetic labor.

Layer 4 — AI-Ready Data follows with an opportunity score of 58.6. The frontier is real-time retrieval plus a policy mesh. The entrant archetype is an open, hybrid retrieval-infrastructure company. The job is to make enterprise context usable at runtime without breaking governance. That means freshness, lineage, entitlements, semantic routing, retrieval quality, and policy enforcement in one fabric. The winner will not sell “RAG.” It will sell governed context.

Layer 5 — Developer Tools carries a 54.8 opportunity score. The frontier is a spec-to-system agent development platform. The entrant is an agent-foreman IDE that keeps architecture under human control. This is where requirements, code, tests, diagrams, deployment, observability, and refactoring begin to collapse into one supervised loop. The open question is whether developers get more leverage or just better ways to generate technical debt at machine speed.

Layer 7 — Commercial Tools has a 48.4 opportunity score. The frontier is the outcome-priced vertical agent. The entrant is a workflow-deep vertical agent operator. This is the SaaS replacement pattern: do not sell seats, sell completed work under constraints. The verticals most exposed are those where process knowledge, proprietary documents, compliance rules, and measurable throughput meet. Which is to say, most of the back office.

The Laws That Held

Context beats model size in bounded workflows.

The best model loses to the good-enough model with the right data, permissions, tools, and evaluation harness. Enterprises pay for completed work, not benchmark theater.

Authority is the new integration layer.

APIs connect systems. Authority connects responsibility. The enterprise that cannot define who an agent acts for, under what policy, with which evidence, cannot scale beyond demos.

Seats erode before applications disappear.

SaaS does not vanish. Its pricing unit breaks first. The application survives where it owns workflow depth, data gravity, or regulated accountability.

Governed action is the economic unit.

Tokens are inputs. Agents are labor containers. Governed actions are what finance can measure, audit can inspect, and operations can improve.

Open weights become leverage, not religion.

Enterprises use open weights where control, cost, latency, or data posture demands it. They use proprietary frontier models where capability justifies the premium. The portfolio wins.

The Brian Letort Take

The operator’s move is not to chase the smartest model. It is to decide which work the company is willing to let software perform.

Start with the workflows. Rank them by volume, cost, error tolerance, regulatory exposure, data readiness, and business value. Then ask the uncomfortable question: if an agent did 30% of this work next year, what would have to be true? The answer will expose the real backlog. It is usually not model access. It is context, authority, integration, evaluation, and ownership.

Build the authority graph before the agent sprawl hardens. Instrument the work before procurement renegotiates the seats. Move from AI pilots to governed operating lanes. Give finance a cost-per-governed-action metric. Give security an audit-the-workflow model. Give business owners exception queues, not toy copilots. Give architects the mandate to make context reusable without making it reckless.

This forecast is extrapolated from what is observable in the AI market today through an underlying projection model. It does not predict unknowable future shocks: a sudden DeepSeek-style cost collapse, a capability jump, or a new entrant that does not yet exist. Those belong on the AI Shockwave Timeline as they happen. New vendors are not invented here; they enter through companion market views as they emerge, then feed back into the forecast.

The October 2028 base case is clear enough without pretending certainty. Intelligence gets cheaper. Agents become coworkers. SaaS loses pricing power. Context becomes infrastructure. Authority becomes architecture.

The companies that treat AI as a feature will buy efficiency at retail.

The companies that treat governed agent labor as an operating model will compound it.