The first wave of enterprise AI has been organized largely around functions. Sales gets an assistant, procurement gets an agent, transportation gets an optimization layer, warehouse operations get orchestration, and finance gets its own analytical tools. That is a sensible way to adopt technology, but it creates a problem that supply chain leaders should recognize immediately: if every function gets better at optimizing its own objective, who optimizes the company?

This question follows directly from the coordination premium. Better intelligence increases the value of coordination because a supply chain is not one optimization problem; it is a collection of interdependent decisions made under competing objectives. AI can make each decision faster and more sophisticated, but it can also intensify conflicts that organizations have managed imperfectly for decades.

Local Optimization Has Always Been Expensive

A procurement organization may be rewarded for purchase-price variance, transportation for freight cost, inventory for working capital, manufacturing for utilization, and customer service for fill rate. Each KPI has a rational purpose, but no supply chain can maximize all of them simultaneously. When functions optimize without a shared view of the enterprise outcome, the company pays through excess inventory, premium freight, unstable schedules, or service failures.

This is one reason I have questioned whether traditional supply chain KPIs are keeping up with the job. Functional measures are useful, but they can reinforce the same silos that modern technology is supposed to eliminate. The same shift is visible in transportation, where TMS is becoming less of a routing tool and more of a decision-intelligence layer, forcing transportation decisions into a broader business context. AI agents operating against those measures could turn an old management problem into a high-speed software problem.

Agents Need Context Beyond Their Function

An agent that sees only transportation data may reasonably recommend the lowest-cost carrier. An agent with customer, inventory, production, and margin context may make a different choice because the shipment is tied to a production constraint or a strategic account. This is why context is becoming a critical requirement for supply chain AI: intelligence without business context can optimize the wrong thing very efficiently.

The problem grows when several agents interact. As discussed in Agentic AI in Supply Chain, coordinated execution will require agents to exchange information and hand work across boundaries. Communication, however, is not the same as goal alignment, and an architecture that allows agents to talk to one another still needs a way to resolve conflicts among objectives.

The Enterprise Objective Must Be Explicit

Human managers often resolve tradeoffs through experience. They know that a particular customer cannot miss a promotion, that a plant shutdown is more expensive than an expedite, or that inventory should be protected because another supplier is already unstable. Those judgments need to become more explicit when machines participate in the decision, which means organizations will have to encode priorities that were previously embedded in management behavior.

This is where the evolution from functional applications toward decision architectures becomes important. The architecture has to understand not simply what each application is designed to optimize, but how multiple objectives relate to an enterprise outcome. That may include margin, service, risk, cash, capacity, and strategic customer commitments at the same time.

Optimization Needs a Hierarchy

One practical implication is that companies may need a hierarchy of objectives rather than a flat collection of agent goals. Routine transportation decisions can optimize freight cost until a service-risk threshold is crossed; inventory can be minimized until resilience thresholds are threatened; production can maximize utilization until customer or working-capital penalties outweigh the benefit. In other words, autonomous optimization will need constraints that reflect the economics of the whole business.

This also suggests why compressing supply chain decision cycles is not enough by itself. A bad decision made in thirty seconds is not an improvement over a good decision made in thirty minutes, and a series of individually rational decisions can still produce a poor system outcome. Speed matters only when the decision logic is aligned with the right objective.

Management Becomes the Design of Tradeoffs

As agents become more capable, the managerial task may shift from supervising every transaction toward designing the tradeoffs the machines are allowed to make. Leaders will have to decide which outcomes take precedence, what risk limits apply, which decisions need escalation, and where local optimization must yield to enterprise priorities. Those are management questions expressed through software.

The implication is that the agentic supply chain cannot be designed by IT alone. Operations, finance, procurement, customer service, technology, and executive leadership all have to participate because the system is effectively encoding how the company values competing outcomes. That is a deeper transformation than adding an AI feature to an application.

Who Optimizes the Company?

The answer cannot be “the most powerful agent.” It has to be an operating model in which functional intelligence is coordinated through shared context, enterprise objectives, and explicit decision rules. Companies that solve that problem will get more value from every specialized agent they deploy because the agents will contribute to a coherent system rather than a faster collection of silos.

This is the next step after recognizing the coordination premium. Once an organization accepts that intelligence must be coordinated, it needs an architecture capable of translating coordinated decisions into action, and that is where the next article in this sequence begins: the need for an execution architecture rather than another intelligence layer.

The post When Every Function Has an AI Agent, Who Optimizes the Company? appeared first on Logistics Viewpoints.

Artificial intelligence is usually presented as a technology story. Better models arrive, inference costs decline, applications acquire new capabilities, and companies search for places where AI can automate work. But the more I look at what is happening across supply chain software, warehouse automation, planning, visibility, and enterprise architecture, the more I think the important second-order effect is organizational: as intelligence becomes easier to acquire, coordination becomes harder to differentiate and more valuable to master.

I have argued previously that the marginal cost of intelligence is collapsing and, in As AI Becomes More Affordable, Supply Chain Software Differentiation Moves Up the Stack, that broadly available models push differentiation toward proprietary context, workflows, integration, and domain knowledge. That logic has another step. If every function can access better analytical capability, the scarce capability becomes the ability to coordinate those capabilities around an enterprise objective rather than allowing each function, system, or agent to optimize its own piece of the problem.

Cheap Intelligence Changes What Is Scarce

Supply chains have always rationed attention. Transportation planners cannot investigate every late shipment, procurement teams cannot continuously reassess every supplier, and warehouse managers cannot manually optimize every task sequence. AI changes that constraint because a machine can examine far more situations at a much lower marginal cost, but that does not eliminate the need to decide which objective matters when several good answers conflict.

Consider a late inbound component. One system may identify the delay, another may recommend an expedite, a planning engine may propose reallocating inventory from another facility, and a customer-service application may flag the order as strategically important. Each recommendation can be correct in isolation while the collective response is wrong, because somebody still has to decide whether preserving production, protecting service, reducing freight expense, or conserving inventory deserves priority.

More Agents Can Mean More Organizational Complexity

This is why the emergence of coordinated agentic execution deserves to be treated as an organizational issue as well as a software issue. A procurement agent may optimize purchase cost, a transportation agent may minimize freight spend, an inventory agent may reduce working capital, and a service agent may protect fill rate. Those goals frequently collide, which means AI can automate local optimization faster than the enterprise can resolve the tradeoffs unless the objectives are designed coherently.

Companies already know this problem in human form. Procurement can win a price concession that increases inventory, manufacturing can improve utilization by increasing batch sizes, and transportation can lower unit freight cost at the expense of lead time. AI does not make those tensions disappear; it can make them operate at machine speed. That is one reason AI alone will not fix fragmented supply chains: fragmentation of objectives can be just as damaging as fragmentation of data.

The Warehouse Shows the Pattern Early

Warehouses provide a useful preview because physical automation has already created environments where many specialized resources must act in concert. As I wrote in Why Warehouse Orchestration Is Becoming More Important Than Warehouse Automation, a facility can contain excellent robots, conveyors, labor, picking systems, and software and still underperform when those resources are not synchronized. The unit of optimization has to shift from the individual asset to the system.

The same principle is moving upward into the enterprise. Planning, execution, and visibility are increasingly interacting as a continuous loop, which is why AI is collapsing the gap between planning and execution. When decisions become more continuous, organizational boundaries that were tolerable in periodic planning cycles become much more visible sources of friction.

Organizational Design Is Moving into Software

Traditional organizations distribute authority through roles, approval limits, policies, and experience. A transportation manager may approve one level of expedite, a vice president another, and an experienced planner may know when a customer commitment should override a cost target. Agentic systems force companies to express more of those rules explicitly because a machine cannot rely on hallway knowledge or organizational intuition unless it has been translated into context, constraints, and decision rights.

This makes AI architecture inseparable from organizational design. The question is no longer simply whether an agent can determine that an action should be taken, but whether it knows the enterprise objective, understands competing constraints, and possesses the authority to act. The more capable the technology becomes, the more important those management choices become.

The Coordination Premium

Two competitors may eventually have access to comparable models, planning systems, transportation applications, warehouse technologies, and automation. One may nevertheless outperform because its data is accessible, its objectives are aligned, its decision rights are clear, and its people and machines can coordinate around the same outcome. The other may own similar technology but retain fragmented incentives, slow approvals, and conflicting local optimizations.

That difference is what I mean by the coordination premium. As intelligence becomes more abundant, the ability to coordinate intelligence becomes relatively scarce, and supply chain leaders should begin asking not only where AI can be deployed but how humans, agents, applications, and physical systems should work together to accomplish an enterprise objective. The answer will increasingly determine whether AI produces isolated productivity gains or changes the performance of the supply chain as a whole.

The post The Coordination Premium: Why AI Makes Organizational Design More Important appeared first on Logistics Viewpoints.

For most of modern business history, intelligence has been expensive. A transportation planner has only so many hours in a day. A procurement analyst can investigate only so many suppliers. A warehouse manager can examine only so many exceptions. A demand planner can explore only so many scenarios before a decision has to be made. Because human attention is finite and costly, companies have always rationed intelligence. They decide which shipments deserve investigation, which suppliers warrant deeper analysis, which inventory problems require intervention, and which operational exceptions simply are not important enough to justify someone’s time.

Artificial intelligence is beginning to change that economic constraint.

A recent analysis by Christopher Penn illustrates just how far the economics have moved. Penn describes how someone can assemble a surprisingly capable agentic AI environment using roughly $500 of commodity computing hardware, Linux, an open-source AI harness, and inexpensive cloud inference. He estimates that moderate usage could cost only a few dollars per month after the hardware purchase. The exact components will change quickly. Today’s preferred model could be replaced next month. Inference prices will continue to move, and open-source software will evolve.

But the important development is not the $500 computer. It is what the $500 computer represents: the marginal cost of applying intelligence to work is collapsing.

For supply chains, that could prove more important than another incremental increase in model intelligence.

From the Cost of Labor to the Cost of Reasoning

Consider how a supply-chain organization handles a late shipment today. A shipment is projected to arrive two days behind schedule, but that fact alone tells the company very little. Someone still has to determine whether the delay actually matters. They may need to examine the customer order tied to the shipment, available inventory at several locations, production requirements, alternative transportation options, contractual commitments, and perhaps even the importance of the customer involved.

Most companies cannot afford to conduct that level of analysis for every shipment continuously. Instead, they establish thresholds and exception rules. Software identifies something unusual, generates an alert, and places it in front of a planner or manager. At that point, the human becomes the scarce resource.

The same constraint appears throughout the supply chain. Procurement teams cannot continuously reassess every supplier. Inventory planners cannot investigate every potential imbalance. Transportation managers cannot evaluate every possible routing alternative every few minutes. Customer service teams cannot conduct deep root-cause analysis on every order exception. Managers cannot continuously model every possible response to every operational disruption.

Human attention is expensive, so organizations reserve it for the decisions they believe matter most.

AI changes the equation because the cost of another analytical cycle can approach fractions of a cent. An AI agent does not have to decide whether investigating a $500 problem is worth spending 30 minutes of a planner’s time. It can investigate thousands of such problems continuously, which creates a fundamentally different operating model.

The First AI Race Was About Intelligence

Much of the generative AI market has focused on a relatively straightforward question: who has the smartest model? OpenAI, Anthropic, Google, DeepSeek, and others compete across reasoning, coding, mathematics, multimodal capabilities, context windows, and benchmark performance. Those differences matter, but enterprise buyers are likely to become increasingly interested in another question: what is the least expensive intelligence capable of reliably performing this particular task?

That changes how enterprises should think about AI architecture.

A company probably does not need its most capable model to classify a routine transportation exception. It may not need frontier-level reasoning to retrieve a bill of lading, compare an invoice with a purchase order, summarize carrier correspondence, check inventory availability, or identify the appropriate standard operating procedure. A relatively inexpensive model may perform those tasks perfectly well.

More sophisticated models can then be invoked as complexity increases. A higher-end reasoning system might be reserved for ambiguous situations involving multiple objectives, financial tradeoffs, or incomplete information. Humans can remain responsible for decisions where judgment, accountability, or uncertainty warrants intervention.

The objective is no longer simply to deploy the smartest available AI. It is to match the cost of intelligence to the value and complexity of the decision. Once that shift occurs, AI begins to look much less like a software feature and much more like an economic resource.

Supply Chains Contain Millions of Small Decisions

This distinction is particularly important in supply-chain management because supply chains generate enormous numbers of decisions, and most of them are not strategic. They are small, repetitive, operational decisions that occur every minute of every day.

Should this order be expedited? Does this late shipment actually threaten production? Should inventory be transferred between distribution centers? Does this carrier invoice require review? Is this supplier’s declining performance statistically meaningful? Should this replenishment order be increased? Which customer orders are exposed to this port delay? Does this exception require a planner? Should this load be reassigned? Is there a lower-cost resolution available?

Individually, many of these decisions are not economically significant enough to justify extensive human analysis. Collectively, however, they determine enormous amounts of supply-chain performance. They drive freight expense, inventory levels, working capital, planner workload, expediting costs, service failures, production disruptions, and ultimately customer satisfaction.

This is why falling AI costs matter. AI does not merely make existing analysis cheaper. It potentially makes previously uneconomic analysis economically rational. That is a much larger shift.

Decision-to-Action Latency Becomes the Battleground

This connects directly to another emerging problem in supply-chain management: decision-to-action latency.

Supply chains have spent years improving visibility. Organizations can see shipments moving across networks. They receive estimated arrival times, weather alerts, inventory warnings, supplier notifications, and demand signals. The problem increasingly is not whether the organization can detect something. The problem is what happens after detection.

An event occurs. The organization sees it. Someone evaluates it. Information is gathered. Alternatives are considered. A decision is made. Approval may be requested. Someone else executes the decision. Every handoff introduces latency.

The economic promise of agentic AI is therefore not simply better prediction. It is the compression of the interval between signal and action.

Imagine that a shipment agent identifies a likely two-day delay. Instead of simply generating an alert, it determines which orders are affected. An inventory agent evaluates available stock. A production agent determines whether manufacturing schedules are exposed. A transportation agent examines alternative routes and expedited options. A procurement agent determines whether substitute material is available elsewhere. Another agent calculates the economic impact of the available responses.

Within seconds, the system can potentially transform a simple message — “Shipment delayed” — into something far more useful: “Three customer orders are exposed beginning Thursday. Transferring 240 units from Atlanta prevents two service failures. Expediting the remaining 80 units costs $1,840. No production schedules are affected. Recommended action: initiate the inventory transfer and expedite the remaining quantity.”

That is not simply visibility. It is decision architecture. And when the intelligence required to perform those calculations becomes inexpensive, that architecture becomes viable across far more exceptions.

Intelligence Is Becoming a Stack

Penn’s cheap-AI example also illustrates another structural change: AI is becoming modular.

The model providing reasoning can be separated from the inference provider supplying compute. The orchestration layer can be separated from the hardware. Databases, applications, containers, networking, and security can all exist as distinct components. That matters because enterprise AI does not have to be built around a single vertically integrated vendor.

The model becomes one component of a larger architecture rather than the architecture itself.

A company could use one model for inexpensive classification tasks, another for coding, another for complex reasoning, and perhaps smaller locally hosted models for workloads requiring low latency or greater data control. Models could increasingly be routed dynamically according to task complexity, cost, risk, and performance requirements.

In other words, enterprises may eventually operate portfolios of intelligence. That is a very different architecture from the idea that one flagship model should do everything.

The Model Is Not the Moat

This leads to an uncomfortable possibility for parts of the technology industry. If capable intelligence becomes inexpensive and models become increasingly interchangeable, simply having access to an advanced model becomes less differentiating. Something else becomes more valuable: the surrounding architecture.

A highly intelligent model that knows nothing about your business is interesting. A somewhat less intelligent model that understands your orders, shipments, inventory, suppliers, facilities, operating procedures, and customer commitments — and can act on them — may be far more valuable.

The durable competitive assets therefore become enterprise data, workflow integration, domain knowledge, operational history, knowledge graphs, governance, business rules, and execution capabilities.

The model provides intelligence. The enterprise provides context. And context is what turns generic intelligence into operational capability.

Why MCP, RAG, and Graph RAG Matter

This is also why the surrounding AI infrastructure is becoming so important.

Supply-chain AI cannot operate effectively if every agent exists in isolation. Agents need controlled access to enterprise tools and information. They need mechanisms for interacting with other agents. They need access to current knowledge that was never contained in the model’s original training data. Increasingly, they also need to understand relationships.

That is where technologies such as agent-to-agent communication, the Model Context Protocol, retrieval-augmented generation, and graph-enhanced reasoning become important. The key point is not the acronym. It is what these technologies collectively enable. This reflects the broader architectural direction toward connected intelligence described in ARC’s AI in the Supply Chain, where A2A, MCP, RAG, and Graph RAG are treated as complementary elements of an AI-enabled supply-chain architecture.

An AI system needs to know not merely that Supplier A exists. It needs to understand that Supplier A produces Component B, that Component B goes into Products C and D, that those products are manufactured at Plant E, that Plant E currently has six days of inventory, that replacement Supplier F requires twelve days, and that the material normally enters through Port G, which has just been disrupted.

Supply chains are networks of relationships.

An AI architecture capable of reasoning across those relationships can begin answering much more consequential questions: What happens next? Who is affected? What alternatives exist? What should we do?

That is where Graph RAG and related architectures become especially interesting. The objective is not simply better document search. It is system-level reasoning.

Cheap Intelligence Does Not Mean Cheap Architecture

There is an important caveat.

The falling cost of AI does not mean enterprise AI transformation suddenly becomes trivial. In many cases, intelligence may actually become one of the least difficult pieces.

The hard work remains. Enterprise data is fragmented. Product identifiers do not match. Supplier records contain duplicates. Transportation systems and ERPs disagree. Legacy applications lack modern APIs. Permissions are inconsistent. Operational knowledge lives in spreadsheets, email, documents, and people’s heads. Business processes contain exceptions that were never formally documented. And autonomous actions introduce serious governance questions.

An agent capable of recommending an inventory transfer is one thing. An agent authorized to execute one is another.

As AI becomes less expensive, these architectural and organizational problems become more visible. Companies may discover that they do not have an AI problem. They have a data problem, an integration problem, a process problem, or a governance problem.

The intelligence itself may increasingly be available on demand.

The Economics of Experimentation Change

There is another consequence that should not be overlooked: cheap intelligence dramatically reduces the cost of experimentation.

A supply-chain organization does not necessarily need to begin with a multimillion-dollar autonomous supply-chain transformation. It can start with a bounded workflow. Transportation exception management is an obvious example.

Give an agent controlled access to shipment events, order information, inventory availability, and the appropriate operating procedures. Allow it to retrieve relevant historical exceptions. Have it identify exceptions, determine business impact, diagnose probable causes, and recommend responses. Keep a human responsible for approval.

Then measure everything. How many exceptions did it correctly prioritize? How much planner time did it eliminate? How often were recommendations accepted? How frequently did humans override them? Did resolution time improve? Did transportation costs decline? Did service improve?

If the economics work, increase the scope. Then increase the agent’s authority. Then add another workflow.

The decreasing cost of AI makes this iterative approach increasingly practical.

A New Supply-Chain Metric: Intelligence per Dollar

This ultimately suggests that enterprises may need to think differently about AI economics.

The relevant measure may not be how much they spend on AI. It may be how much useful intelligence they obtain from that expenditure.

Call it intelligence per dollar.

How many decisions can the organization economically analyze? How many exceptions can it investigate? How many scenarios can it evaluate? How many decisions can it improve? How much decision-to-action latency can it remove? And what does each incremental unit of useful reasoning cost?

Once framed this way, the implications become significant.

An organization that can apply reliable intelligence to one million operational decisions for the same cost that a competitor spends analyzing 100,000 has an advantage even if both companies technically “use AI.”

The competitive advantage is not access. It is deployment efficiency.

The Next AI Race Is About Orchestration

For the past several years, the AI industry’s center of gravity has been the model: bigger models, smarter models, longer context windows, higher benchmark scores, more parameters, and better reasoning. Those advances will continue, but enterprise competition is likely to move upward through the stack.

The question becomes less “Who has the smartest AI?” and increasingly “Who can put useful intelligence against the largest number of economically meaningful decisions?”

That requires much more than a model. It requires enterprise context, reliable data, retrieval, agent orchestration, integration, governance, execution, and an architecture capable of determining which intelligence should be applied to which problem at which cost.

This is why the humble $500 AI server is more interesting than it initially appears. Nobody is going to operate a global supply chain from a bargain mini-PC. But the fact that an individual can now assemble a capable agentic computing environment from commodity hardware, open-source software, and a few dollars of monthly inference illustrates how dramatically the economics have shifted.

Intelligence is becoming abundant. The scarce resource is increasingly the ability to connect that intelligence to the business.

Intelligence Is Becoming a Commodity. Orchestration Is Not.

This may ultimately be one of the defining transitions of enterprise AI. The first phase was about gaining access to machine intelligence. The next phase will be about the economics of deploying that intelligence against work.

As inference prices decline and capable models proliferate, companies will increasingly be able to apply reasoning to decisions that previously could not justify human attention. For supply chains, with their enormous volume of small, interconnected, time-sensitive decisions, the implications are particularly significant.

The winners may not be the companies with access to the smartest model. They may be the companies that build the best decision architecture around increasingly abundant intelligence: companies that can determine what happened, understand what it affects, evaluate the alternatives, select the appropriate response, and execute that response with progressively less latency.

That changes the competitive question. It is no longer simply, “Who has the best AI?”

It becomes:

Who can deploy the most useful intelligence, against the most decisions, at the lowest cost, with the shortest path from decision to action?

That is a much more consequential race.

And it has already begun.

The post The Marginal Cost of Intelligence Is Collapsing. Supply Chains Will Never Be the Same. appeared first on Logistics Viewpoints.