SynapticThe Next Computing Bill
Chapter 15 · Interactive edition

The case for the incumbent

A cloud commitment, an engineering team with its own machines and a provider willing to pay for repairs can each change who wins the work.

On 16 October 2026 Britain's competition authority described an extraordinary piece of competitive progress. Two of the world's richest companies had made it easier for their customers to leave. Amazon and Microsoft had updated the terms on which UK customers could transfer data out when switching providers. The window for a qualifying move had been extended from ninety days to a hundred and eighty. The authority had examined internal company data and spoken to customers. Those customers continued to describe material obstacles to switching or operating across providers. Moving the bytes was one part of moving the business. 90

A six-month departure provision belongs in a discussion of frontier intelligence for a simple reason. A bank can evaluate a new model over a weekend and still need most of those six months to transfer the work. The people who keep the existing operation running can spend that interval improving it. They know where the files are, where the supervisors sit and what the bank has already agreed to buy. Any prediction in which AI computing companies take revenue from the cloud has to let the cloud companies use those advantages. An incumbent that politely holds still until its challenger finishes the installation is a peculiar invention of forecasters.

There is a practical lesson in what the British authority chose to investigate after prices changed. Amazon and Google had launched a direct connection between their systems, and Amazon had introduced a free tier. At the October reporting date, a direct link between Amazon and Microsoft remained in progress. The difference matters to a bidder who has thirty days to deliver a working service. A promised connection can be a sensible choice for the long-term design and an expensive one for the first release. Write two dates on the estimate, the day the bank pays the engineer and the day the connection is available for the bank's region. Until the dates meet, someone must fund a temporary route. 90

The cheque already written

Microsoft's own billing documents give an unusually clear view of the defence. Claude usage through Foundry can appear on an Azure invoice in Claude Consumption Units. Under the documented arrangement the meter counts towards the customer's Microsoft Azure Consumption Commitment. Discounts enter the conversion from model tokens into the billing unit. A company can therefore decide it wants Anthropic's intelligence and find that the easiest place to buy it is an agreement the purchasing department signed long ago. Both companies can make a sale. Only the buyer knows whether the purchase consumed an otherwise stranded commitment or displaced some other eligible work. 35

That last distinction can change the result of a tender. A prepaid unit that the bank would otherwise use for a scheduled migration has a real opportunity cost. Charge it to the new project and the migration team will eventually have to purchase another unit. A unit expiring unused next month is a different proposition. An account director talking about a customer's commitment might know the exact contractual amount while having little idea which of those two situations applies. The person who can settle it is often a finance manager with the next six months of project forecasts and the authority to challenge them.

A platform has another response. It can make the choice of model a feature of a product the buyer already likes. In September GitHub described three settings for automatic model selection in Copilot. A user could favour efficiency, balance or intelligence. Charges depended on the model selected, with a ten per cent discount for paid subscribers on qualifying automatic usage at the time of the announcement. A developer selecting a preference delegates some purchasing discretion to the platform. The model developer can win the underlying call while losing the occasion to negotiate directly with the person whose work generated it. 91

Put three bids on the same desk

Give the bank ten thousand accepted files for one operating year. All three bidders must deliver the same checked results and bring reopened files back to the same standard. A direct lab wants $142,000, to which the buyer adds $18,000 of retained operating work and $12,000 for switching. A cloud bundle costs $152,000, requires $12,000 of bank operations and costs $12,000 to switch. The bank can also host an open-weight model. It anticipates paying $65,000 for the machines and power, $83,000 for operations and $22,000 to set up the service. These are three invented bids. Their prices describe no particular company's offer.

Exhibit 36 / Comparable tender model

Which part can the incumbent bundle?

Three providers promise the same 10,000 accepted files. Pick a bar to inspect its costs. Change the repair terms or introduce a commitment that expires this year.

Lowest feasible first-year outlay

$172,000

Direct lab
Service or capacityBank operationsSwitchingBank pays repairPrior commitment
Direct lab · buyer ledger

The bank pays the fee, operating costs and switching. Covering repairs changes who carries the service risk.

Service or capacity
$142,000
Bank operations
$18,000
Switching
$12,000
Bank pays repair
$0
Prior commitment
$0
Direct lab fee awarded$142,000
Lab contribution if signed$8,000

The lab wins the prime contract. The bundle’s wholesale model spend is undisclosed in this exercise.

Figure 36. Three illustrative US-dollar bids for one year. The vertical rule marks the lowest feasible outlay. Shading on a withdrawn quote preserves the cost comparison. The buyer requires equal quality and accepts the cheapest firm bid. The lab requires positive contribution. The cloud quote includes repairs and stays firm across this exercise.
Read the assumptions behind the tender

Repairs cost $32 each. The direct provider has $118,000 in ordinary annual delivery costs. The optional $15,000 is unavoidable and otherwise unused, due whatever route wins. On the eligible cloud route it pays part of the $152,000 service charge. Other forms of commitment can behave differently. Documented billing mechanism

Download reported evidence (CSV)

At a five per cent reopening rate, five hundred files require repair. Allow $32 per repair. The lab includes that service in its direct quote. So does the cloud bidder. On the self-hosted route the bank pays the $16,000 itself. It is looking at annual cash outlays of $172,000, $176,000 and $186,000 respectively. The lab wins this contest by $4,000. One per cent of the files being much harder than expected could mean very little to the buyer's contracted cash outlay and a great deal to the supplier that promised to pay for repairs.

Look inside the winning offer. Assume ordinary delivery costs the lab $118,000, including the work needed to support the bank throughout the year. Its $142,000 fee leaves $24,000 before reopening costs and $8,000 afterwards. At a reopening rate of seven and a half per cent the entire $24,000 is gone. A supplier that requires a positive contribution would withdraw that offer at that point. It can quote a higher fee next year. It can also ask the bank to bear the repair bill. At five per cent the latter change takes the direct route to $188,000. The cloud's $176,000 offer now wins.

An old commitment can reverse the award without a single bad file. Assume $15,000 of unavoidable cloud expenditure will expire unused and the bundle's invoice qualifies against it. On the direct and self-hosted routes the bank still pays that $15,000. Their total outlays become $187,000 and $201,000. The cloud route stays at $176,000 because the same $15,000 settles part of its invoice. The bank has paid it once in all three cases. The balance due on the bundle's $152,000 service charge is $137,000 after applying the commitment. Describing the commitment as a discount on next year's bill would mislead both the buyer and the investor.

The company that bought its own machines

Nutanix has described a decision of precisely this kind about its own engineering work. The infrastructure vendor says it invested $20 million in a self-operated system for open-weight models after the economics of its external coding tools changed. It describes a design that directs routine work to its own equipment while sending the more demanding jobs to external frontier services. The company's stated allocation is eighty per cent routine and twenty per cent external. This is a supplier describing itself as a customer of the equipment it sells. Its account establishes a purchasing decision and a design intention. An audited saving per accepted engineering change would require different evidence. 92

Buying the machines changes the shape of the problem. On a quiet Sunday the bank under our self-hosted proposal will still pay for the installation and the people who can restore it. On a busy Monday an extra request within the available capacity can be cheap. A fleet large enough for an ordinary week may be poorly matched to the month-end peak. Outsourcing the tail can make the internal installation more attractive by reducing the capacity it needs to reserve. In that case an outside model supplier can help a customer reduce its outside purchases while earning healthy revenue from the smaller, harder set it retains.

The buyer also has to count the jobs it sends twice. If an internal model attempts a file, fails the validation and passes it to an external service that starts again, both providers have consumed resources. Routing ninety per cent of initial requests internally could be entirely consistent with paying an external supplier for the most expensive half of the work. The invoice and the routing log measure different things. I would ask the owner for costs by accepted file, the distribution of those costs on deadline days and the number of cases that needed both routes. A press release describing a target allocation supplies none of these measurements.

There is a financial test for owning the equipment too. Spread an illustrative $20 million capital outlay over four years of service with no residual value. Recovering that investment alone requires $5 million a year before electricity, financing, maintenance or engineering. If the equipment supports ten million accepted jobs annually, capital recovery amounts to fifty cents each. At two million jobs it is two dollars and fifty cents. This calculation uses the size of the investment Nutanix reported to illustrate the sensitivity to utilisation. Its own service life, use of the machines and avoided external payments would be needed to calculate the company’s actual payback. Resale proceeds and a longer working life would lower the annual hurdle. 92

Who can reserve the scarce hour?

Power introduces a constraint neither a benchmark nor an elegant contract can remove. Lawrence Berkeley National Laboratory estimated that US data centres used 176 terawatt-hours in 2023, about 4.4 per cent of national electricity consumption. Its 2024 report gave a wide range of possible consumption by 2028, roughly 325 to 580 terawatt-hours. Those numbers cover data centres broadly. They measure national energy over time. They cannot tell a bank whether a particular operator has spare capacity in the required region on the evening it must close the books. That local question is often the one for which a buyer will pay a premium. 93

A cloud operator that can demonstrate capacity at the contracted time can charge for a promise a model developer would otherwise have to buy from it. A lab with a long-term reservation can offer the bank comparable assurance but must carry the reservation through quiet periods. A bank willing to delay some work can get a better deal from either party. The commercial advantage of scale comes partly from mixing customers whose peaks fall at different times. To price that advantage a supplier has to know whether the next customer's busiest afternoon coincides with everyone else's. Ten more banks with the same reporting deadline are a less attractive addition than a simple volume model suggests.

What would make me change my mind

The strongest incumbent response may be to sell the same result the challenger has promised, through a route already qualified. Salesforce's acquisition of Fin brought an outcome-priced business inside an established application company. Databricks describes its newer Genie as able to take on work across enterprise sources. The fact that a lab can build a better agent gives it a bargaining position. It gives the incumbent a reason to buy, partner, integrate or improve its own. A bank accepting any of these offers can record a genuine gain in productivity while renewing with the business that supplied the old interface. 40 57

There is a test that involves considerably less speculation than comparing model announcements. Read the tender after the pilot credit has expired. Establish whether the bank could have used the rest of its cloud commitment elsewhere. Identify the owner of the reopening obligation. Compare the actual repair cost against the price at which the winning supplier promised to carry it. Then give the runner-up the same incident record and ask for its next price. A lab that wins the first year, pays for its mistakes and wins the extension has defended something more valuable than a successful demonstration.

I would narrow the original prediction if established firms repeatedly kept those extensions while labs competed for replaceable inputs. The incumbent could lose the privilege of charging for every human seat and gain the privilege of choosing the model on every accepted job. A supplier of intelligence might become a much larger business in absolute terms under that arrangement. Its shareholders would still own a different business from the one that had captured the customer's operating budget. The decisive document would be readily recognisable to anyone who has bought enterprise software. Above the signature, next to the price, it says exactly who the bank expects to come back tomorrow.

Sources and reading notes

  1. 35 · Microsoft Foundry, Claude consumption unit billing

    Billing unit, marketplace private offers and application to a Microsoft Azure Consumption Commitment. Other account arrangements can differ.

  2. 40 · Salesforce completes its acquisition of Fin

    Closing announcement dated 10 September 2026. Buying an outcome-based service can still pay the incumbent group.

  3. 57 · Databricks announces the second generation of Genie, 11 November 2026

    The company describes proactive work and connections across enterprise data sources. Product announcement. Platform usage, customer cash savings and retention are separate measurements.

  4. 90 · UK Competition and Markets Authority, cloud actions update of 16 October 2026

    Pages 7–8. UK switching egress terms, longer windows and interconnect availability. Findings are specific to geography, provider and date.

  5. 91 · GitHub, cost and quality settings for automatic model selection, 14 September 2026

    Three routing tiers and a 10% discount on eligible automatic usage for paid subscribers at announcement. A product setting gives no market share measure.

  6. 92 · Nutanix describes its own private AI deployment

    Nutanix reports $20m invested and an 80/20 routing strategy for its own engineering workloads. Self-reported implementation by an infrastructure seller. No audited return on capital or cost per accepted change is supplied.

  7. 93 · Lawrence Berkeley National Laboratory, 2024 United States Data Center Energy Usage Report

    Executive summary. Estimated US data centre electricity use in 2023 and 2028 scenarios. Annual energy at national scale cannot establish site-specific power availability or a particular provider’s cost.