How AI Changes the Cost Structure of Every Business

To understand what AI will do to a business, follow the cost curve.

Picture three companies.

1. A manufacturer uses computer vision to catch defects near the beginning of a production run rather than at the end. The company sells the same physical object, but consumes less material and machine time for every acceptable unit.

2. A hospital uses AI to draft clinical notes. The care has not become an “AI product.” But clinicians spend less time documenting it, which changes the cost and capacity of delivering care.

3. A software company sells an agent that researches a question, calls external tools, checks its work, and produces an answer. The product can do something conventional software could not. But every successful answer now carries a variable cost.

These look like three different AI stories. Economically, they begin with the same two questions:

What got cheaper, and who keeps the difference?

In the previous essay, we separated two ideas commonly collapsed into the label “AI company”: AI in the product and AI in operations. That distinction tells us where AI enters a business. It does not yet tell us what happens to the economics once it gets there.

For that, the practical lens is cost structure.

Here, “product” means whatever outcome the customer pays for: software, a physical good, professional work, healthcare, transportation, or another service. AI does not need to be visible in that outcome to change its economics. The model may be the thing being sold, or it may quietly alter how much labor, material, time, computation, and capital the company requires.

This gives us three parts of the argument:

1. AI changes the cost of producing an outcome.

2. That changes what customers build, buy, and pay for.

3. Someone captures the difference.

Every business turns inputs into outcomes. The inputs differ by industry.

A software company relies largely on talent, computing infrastructure, data, and third-party services. A manufacturer adds raw materials, components, energy, equipment, and inventory. A hospital coordinates clinicians, beds, supplies, diagnostic capacity, and information. A logistics company combines labor, vehicles, fuel, warehouse capacity, and time.

AI can change how much of those inputs is required for each successful result.

The simplest gains come from avoiding waste.

A retailer that forecasts demand more accurately can carry less excess inventory. A manufacturer that detects a defect earlier can avoid spending additional material and machine time on a unit that will eventually be discarded. A logistics company that reduces empty miles gets more deliveries from the same fleet. A hospital that anticipates patient volume can align staffing before an expensive mismatch appears.

In none of these cases is the model the customer-facing product. It sits underneath the product and changes the amount of economic input consumed.

This is an important corrective to the idea that an “AI company” must sell an AI feature. A business can expose no model to its customers and still be transformed by one. Conversely, a company can add a conspicuous AI interface without materially changing its underlying economics.

The feature is visible. The cost curve is consequential.

Software development is the most visible example. Code-generation tools reduce the time required to draft routine code, interpret unfamiliar systems, write tests, produce documentation, and explore implementation options.

That does not make software engineering free. It shifts the scarce input. Typing code becomes less important relative to defining the system, understanding the user, choosing an architecture, and evaluating whether the output is correct.

The same pattern appears in services.

In a law firm, AI can produce a first-pass document or search a body of case law. Attorney time moves toward judgment, negotiation, and accountability. In healthcare, AI can draft documentation while the clinician remains responsible for its accuracy and for the care itself. In insurance, a system can assemble the evidence for a routine claim while an experienced adjuster handles ambiguous cases.

In each example, AI makes an intermediate artifact abundant: code, text, analysis, or classification. The scarce resource moves elsewhere.

That distinction matters because abundant output can create its own costs. Faster code generation can produce more software to maintain. Faster document generation can create more material to review. A factory system optimized for throughput can push defects downstream if quality is poorly measured.

When generation becomes cheaper faster than evaluation improves, the result is not leverage. It is clutter or risk.

This is why “we reduced headcount” is an incomplete account of AI’s value. So are prompt counts, generated lines of code, and numbers of AI licenses.

The useful denominator depends on the business:

• Cost per acceptable manufactured unit.

• Clinician time per patient treated.

• Cost per correctly resolved claim.

• Cost per successful delivery.

• Cost per validated product improvement.

• Cost per trustworthy answer.

The distinction can reverse an apparent conclusion. Suppose an AI legal product doubles its model expense but reduces professional review time by 80 percent. Its inference bill has worsened, but the total cost of producing a trustworthy work product has improved.

Or consider an agent that completes a task only after twenty attempts. The final result may look impressive. The economics may be terrible once we include model calls, retrieval, tool use, verification, and human intervention.

The relevant unit is not the token, prompt, document, or feature. It is the successful outcome.

The operating question remains: What got cheaper?

A lower internal cost is only half the story. AI also changes what the customer can do without the company.

Every customer has alternatives. They can buy a product, build an internal version, hire people to perform the work, outsource it, tolerate the problem, or stop doing the work entirely. When AI changes the cost of one option, it changes the value of the others.

Software provides the clearest case. For years, vendors benefited from a straightforward calculation: building internally was slow, expensive, and risky, so buying a specialized product was usually rational.

AI lowers the cost of creating the first version. A customer can prototype a workflow, build a lightweight internal tool, or automate a narrow process faster than before. That puts pressure on products whose primary value was packaging a simple workflow behind an interface.

But “easier to build” is not the same as “easy to own.” Internal software still requires maintenance, security, integration, evaluation, support, and adaptation. AI may make the prototype cheap while leaving the long-term obligation expensive.

The same recalculation extends beyond software. A professional-services firm may automate work it previously outsourced. A manufacturer may bring some design or quality analysis in-house because a smaller team can now perform it. A health system may buy an AI-enabled workflow rather than add administrative staff, while continuing to send difficult exceptions to specialists.

Companies will continue to buy software and services. The threshold will simply move.

That creates an uncomfortable question for every vendor:

If the customer can reproduce the visible part, what remains uniquely ours?

The durable answer is unlikely to be “our AI.” Models will improve and diffuse. Stronger answers include trusted data, deep integration, reliability, security, regulatory capability, distribution, maintained domain knowledge, and accountability for the final outcome.

The interface is increasingly easy to imitate. A maintained system that works under real-world constraints is not.

AI products introduce a special cost problem.

Traditional software taught companies and investors to expect very low marginal costs. Once the code was written and the infrastructure was running, serving another customer was often inexpensive. The meter largely switched off after the product was built.

With customer-facing AI, the meter keeps running.

Every generated answer, analyzed document, autonomous action, or multimodal interaction consumes computation. A difficult task may require repeated reasoning, retrieval, tool calls, verification, and review. The product performs work each time the customer uses it, and that work has a cost.

This does not make the business unattractive. Runtime inference enables products that could not previously exist. It does mean the company must understand the total cost of making the product work reliably.

A compelling demonstration can conceal weak economics. An agent may appear magical while consuming more resources than the outcome is worth. On the other hand, an expensive model call can be entirely rational if it eliminates a much larger amount of labor or prevents a costly error.

Again, the question is not “How many tokens did we use?” It is “What did a successful result cost?”

Traditional SaaS pricing is organized around seats. That works when software assists a person whose job remains the basic unit of production.

If the software begins doing the work, seat count becomes a poor proxy for value. A customer may need fewer users precisely because the product is effective. At the same time, greater use can raise the vendor’s inference cost.

Token pricing solves only part of the problem. Tokens represent a vendor’s input, not a customer’s outcome. A customer no more wants to buy tokens than a restaurant customer wants to pay according to the kitchen’s electricity consumption.

Different products will therefore require different models:

• Seat pricing when AI primarily assists existing workers.

• Usage pricing when each interaction has clear incremental value.

• Workflow pricing when the product completes a recognizable unit of work.

• Outcome pricing when the result can be measured and attributed.

• Hybrid pricing when a stable platform and variable consumption both matter.

Whatever the model, the price must be compared with the customer’s new alternative. A vendor cannot price forever against the labor cost of an old process if AI has made that process much cheaper.

The external question is: What can the customer now obtain more cheaply elsewhere?

Suppose AI reduces the cost of producing a successful outcome from ten dollars to six. Four dollars of economic value has appeared. But that does not tell us who receives it.

The company might keep the difference as margin. It might lower its price to win market share. Employees might capture some of it through higher compensation or reduced workload. A model provider might absorb it through inference fees. Customers might demand it during procurement. A new competitor might use it to enter the market with a different business model.

Technology creates the possibility of surplus. Competition, pricing, and organizational design determine where the surplus goes.

A company can make a process cheaper and still fail to benefit.

If every competitor has access to the same model and the customer can switch easily, much of the saving may flow into lower prices. If the company adds AI subscriptions without removing old systems or workflows, costs may rise. If faster production creates more review, compliance, or support work, the apparent gain may migrate to another line of the budget.

This is why local productivity can coexist with flat company performance. One employee completes a task faster, but the surrounding process remains unchanged. The saved time is absorbed by another queue, another meeting, or simply more low-value output.

Real transformation should appear in the operating model: shorter cycle times, lower support expense, less waste, faster onboarding, improved quality, greater capacity, or more revenue from the same resources.

If none of those move, AI adoption may be visible while its economic value remains missing.

When one input becomes cheaper, another often becomes more important.

When code becomes abundant, product judgment and system design become scarcer. When analysis becomes abundant, trusted data and evaluation matter more. When prototypes become easy, integration and distribution become harder differentiators. When autonomous systems act faster, governance and accountability become more valuable.

The winning company is not necessarily the one that reduces the most obvious cost. It may be the one that identifies the next bottleneck first.

Return to the manufacturer. Early defect detection saves material, but only if the system is trusted enough to influence production. Better scheduling raises throughput, but only if downstream logistics can absorb it. More output has little value if demand is unchanged.

Or return to the hospital. Drafting notes faster can return time to clinicians. It can also produce a larger volume of text that must be checked, stored, interpreted, and defended. The benefit depends on whether the full workflow improves, not whether one step accelerates.

A cost curve never moves in isolation.

The strategic question is: Who keeps the difference after the entire system adjusts?

Once a cost curve moves, two further questions follow.

Which existing companies can reorganize around the new economics? And where do those economics create opportunities that did not previously exist?

We can think of incumbents as green trees or dead trees. Green trees can redirect resources toward new growth while preserving what customers value. Dead trees may still have revenue, brand, and scale, but their structures cannot adapt. They add AI to the surface while the economics underneath remain unchanged.

Then there is blue sky: opportunities that become viable when AI makes a previously impractical product, service, customer segment, or business model affordable. Blue sky is not simply “the AI market.” It appears wherever the boundary of what can be profitably produced or delivered has moved.

Cost structure tells us where to begin looking. It does not tell us which incumbents can move or which apparent openings are real. That is the next question.

AI will continue to attract arguments about intelligence, labor, consciousness, and power. Those arguments matter. Business strategy requires a more disciplined frame.

Start with three questions:

1. What got cheaper?

2. How did the customer’s alternatives change?

3. Who keeps the difference?

These questions apply whether a company sells software, physical goods, professional services, healthcare, or transportation. They apply whether AI is visible in the product or buried inside operations.

AI does not create business value merely by making something technically possible. It creates business value when it changes the cost of producing a successful outcome and someone finds a way to capture the difference.

To understand what AI will do to a business, follow the cost curve.