Enterprise AI Is Learning To Charge For Work, And Owning The Outcomes Becomes The Contest

retained text

The most consequential change in enterprise AI this year is not a model release, it is a change in what buyers agree to pay for. OpenAI's CFO has recast the buyer's question away from cost per token and towards cost per successful task, proposing "useful intelligence per dollar" as the scorecard and arguing that AI should be measured by work accomplished rather than usage. By August 2026, the same leadership was telling investors that the age of “tokenmaxxing” had passed, as enterprises routed routine work to the cheapest capable model and reserved frontier models for the tasks that justified them. The deeper reason this shift was inevitable is that effort and value were never tightly coupled. Industry observers building agentic products point out that an agent which closes a tenth of the deals while consuming a hundredth of the tokens is still the one worth paying for. Token count measures exhaust, not distance travelled. Sierra, the customer service agent company, already prices on this basis, charging a set rate for a resolved conversation and nothing when the case escalates to a human. Salesforce has begun reporting Agentic Work Units in the billions, a unit defined by work performed rather than seats occupied. Value based pricing is a seller's construct as much as a buyer's, and analysts at Constellation Research have noted it has historically served vendors more than customers. The question is more than whether the meter is moving, it is whether the outcome lands when it does. Interface Is Dissolving Into The Agent Once work is priced by outcome, the product stops being the screen and becomes the agent that produces the outcome, and the interface starts to disappear behind it. AI founders describe the valuable object not as the API, the actions initiated when a button is clicked, but as the harness around it, the skills, documentation and rules that encode how the best expert runs workflows on and extracts value from a system. On this reading, the application of the future is not the form and the dashboard, it is that harness. Claudeforce is that argument arriving as a product. Announced on 26 August 2026, it makes Anthropic's Claude the default reasoning engine across Salesforce and brings the platform's data, actions and governed workflows into Claude through a layer Salesforce itself calls a harness, AIforce, with 37 prebuilt sales skills. A seller can run a pipeline review or prepare a deal without opening Salesforce at all. One account of the launch put it plainly, that customers may never need the Salesforce app UI again. The market read it as strength rather than threat, with Salesforce reporting that Agentforce’s annual recurring revenue had crossed $1.5 Bn, up more than 240% year on year, and its CEO using the earnings stage to say the talk of a software apocalypse should stop. What founders should take from this is how durable billing moves now. The harness converts a customer's accumulated institutional knowledge into portable skills that travel across the enterprise, and that encoded knowledge, as valuable as the model weights, is what becomes hard to replace. Even the way today's agents remember, through scribbled notes rather than elegant databases, makes the point, since it is that messy accumulated context that carries institutional memory forward. Agents Are Inheriting Department Boundaries The fantasy of one harness that holds the whole company runs straight into a problem four decades old, because centralising an organisation's knowledge in a single place has never worked at enterprise scale. Each great system of record conquered one domain and stopped there. Salesforce owned sales, SAP owned the procure to build cycle, Workday owned HR, and none of them became the company's apex brain. The agents inherit exactly those boundaries. Claudeforce is the agentic expression of the CRM, not of the enterprise, and the same will most likely be true of every system of record that ships or partners for its own agent. The reason the boundary holds is organisational as much as technical. Companies ship their org charts, so no one owns the process that runs end to end, and AI gets bolted onto each silo instead of rewiring the workflows that cross them. The universal enterprise harness therefore waits on a reorganisation that most companies have not attempted, which is why the near term winner is not the universal agent but the team that owns the harness and the outcome unit inside one bounded, high value domain. That is a narrower and more winnable problem, and it is where new entrants take share before incumbents finish reorganising around agents. The counter case deserves a hearing. Frontier agents can already reason across disconnected systems, plucking data from many places without a unifying database, which argues against hard boundaries. Yet the trust, governance and audit trail that regulated enterprise buyers demand still live inside each system of record, and that keeps the boundary standing for longer than the raw capability would suggest. Pricing The Outcome May Turn Into Claiming A Share Of It Outcome pricing and deep embedding are the same capability seen from two angles, and once a platform is embedded enough to price your result, it is embedded enough to measure your upside. The clearest statement of intent comes from the vendor, not a critic. OpenAI has said that as intelligence moves into scientific research, drug discovery, energy systems and financial modelling, licensing, IP based agreements and outcome pricing will "share in the value created." A platform contributing materially to a discovery has a short journey from charging for the work to claiming a cut of the result. The dependency compounds as it deepens. The further an agent sits inside a workflow, the harder it is to remove, and the more credibly the supplier can attribute the outcome to itself when the contract comes up for renewal. The benign version is the agent that holds memory and manages a relationship rather than a single conversation, one that owns a territory and compounds value over time. The same depth that lets an agent own a territory lets the platform behind it argue for a share of what the territory produces. Attribution is the pressure point, and it cuts both ways. A closed deal or a saved cost owes something to marketing, seasonality and human judgement, not the model alone, and that difficulty protects the customer today. It also means the embedded platform, holding the fullest record of the process, is the party best placed to win the attribution argument tomorrow. Control Is Moving Back Inside the Customer's Perimeter The response to that exposure is business model sovereignty, and it is a sharper argument than the data sovereignty case made earlier in this series. Even a customer with no regulatory obligation has reason to keep the model inside its own perimeter, because a model you run cannot quietly reprice your upside. Ownership of the machine is now a commercial defence, not only a compliance posture. The practicality has caught up with the logic. Open weight models now handle increasing volumes of enterprise work, and on premises or private cloud deployment reaches cost parity at steady volume through hybrid designs that reserve frontier models for the tasks that earn them. Prosus has publicly disclosed inference cost reductions of the order of 26X from moving suitable workloads onto open models, a number that changes the architecture decision. A company category is already forming to serve this, from specialists that keep AI workloads inside a customer's own infrastructure to established vendors running open models on premises for regulated buyers. The demand exists because most enterprises do not want to buy a model or software, they want a solution to a problem, and the missing layer of implementation companies is itself a major constraint on AI adoption today. This is India's opening, and it is services shaped with a significant orbital shift on the value chain. India built a services export industry by implementing other people's software on client terms, and the AI version of that industry is larger, because implementation now reaches up the value chain into model selection, private fine tuning, evaluation, integration, and the compliance evidence that regulators want, all delivered on infrastructure the client owns. The Global capability centres (GCC) already embedded inside these enterprises are the natural beachhead, and open Indian model weights now exist to build on. The founder's move is to build a model agnostic deployment stack for one regulated domain, increasingly price it on the outcome, establish a common-sense maintenance SLA, and run it on infrastructure the client determines. Comparisons Between Human And Agent Get Clearer As covered across my series on AI adoption, this argument now closes an open loop. Enterprises should pay for outcomes rather than effort, they should define those outcomes on their own terms, and the outcome economy will also decide who keeps the value that the outcome creates. The genuine progress is that the enterprise is shifting to pay for work delivered rather than tokens consumed, and for the first time the substitution question can be asked cleanly, one agent measured against one human on the same outcome unit, day after day. An honest caveat holds the enthusiasm in check. The atomic unit of AI productivity is a process, not a person, and these are difficult distinctions to make. Outcome pricing makes the per task comparison exact without making the swap one for one, a more useful truth than either the headcount panic or the claim that nothing changes. The Indian founder's opening is to build the layer that lets enterprises get the work done without giving up “alpha” to the machine, and to build it for the world quickly as the paradigm takes shape in real time.

document fetched 2026-09-11 03:01 · canonical https://inc42.com/resources/enterprise-ai-is-learning-to-charge-for-work-and-owning-the-outcomes-becomes-the-contest