JPMorganChase put a number on its technology plans for 2026 that would make a respectable market all by itself. Management expected technology expense of roughly $19.8 billion, up about $1.9 billion from the year before. In the same presentation it identified roughly $600 million of efficiencies, about a quarter of them related to AI. For a seller looking for money to displace, there is a temptation to circle the smaller number. For a seller trying to understand what the customer will actually buy, the more interesting fact is the direction of the larger one. The bank expected to save money on particular activities and to increase its technology expense. 118 119
Look at who owns that estimate. The consumer and community bank accounted for $8.2 billion of the outlook. The commercial and investment bank accounted for $8.8 billion. Asset and wealth management accounted for $2.2 billion and corporate functions for $600 million. Within the projected increase, the firm identified higher prices for labour, hardware and other inputs, more demand for cloud infrastructure and software, and investment in new capabilities. Those are rounded management figures. They describe an organisation buying and making things for different customers. A model developer that wins a mandate in one division has earned a place in one budget negotiation. An analyst who treats the whole bank as a single subscription will miss the next three. 118
The roughly $150 million one can infer by multiplying the two management estimates is particularly easy to misuse. It is an approximate AI-related component of identified efficiencies in a technology expense outlook. The slide gives no corresponding invoice from Anthropic, no population of redundant employees and no division of the benefit between better purchasing, faster engineering and changes in service. Management told investors that efficiencies enabled additional investment. A bank can use cheaper infrastructure to add a facility for its clients. The firm selling that facility could be the most important commercial beneficiary without having made the infrastructure cheaper itself. 118 119
Six spending lines and a tempting division
In October 2026 Gartner put worldwide IT spending for the calendar year at $6.391 trillion. The forecast for 2027 was $7.352 trillion. Both estimates came from the same release, used the same six categories and were expressed in US dollars. That makes them suitable for a comparison of what this particular forecaster expected to change between two years. The first figure was published while part of the year still lay ahead. When someone describes it as the cash enterprises had already spent, ask where the final two months of invoices came from. 08
Which IT expenditure counts?
Six categories make up Gartner’s worldwide forecast. Compare the two years, then inspect which purchases account for the $961 billion increase between them.
$6,391bn
IaaS is the infrastructure service category in this forecast. Other definitions of cloud also count platforms, hosted private clouds or applications. $292bn is 4.6% of $6,391bn.
Read both years and the change by category
| Category | 2026 | 2027 | Change |
|---|---|---|---|
| Data centre systems | 879 | 1,366 | 487 |
| Devices | 847 | 916 | 69 |
| Software | 1,464 | 1,679 | 215 |
| Services | 1,557 | 1,633 | 76 |
| Infrastructure as a service | 292 | 367 | 75 |
| Communications services | 1,352 | 1,391 | 39 |
| Total | 6,391 | 7,352 | 961 |
Infrastructure as a service accounts for $292 billion in the 2026 table, about 4.6 per cent of the total. It is a remarkably small fraction for an industry that dominates so much discussion of corporate computing. Yet assigning the other 95.4 per cent to technology outside the cloud would produce a remarkable mistake. A customer renewing a hosted payroll application has bought software. A consultant moving a bank's records into a cloud environment can issue a services invoice. A data centre supplying cloud capacity buys equipment. A product, a delivery method and the buyer of a machine answer different questions about the same system. 08
The composition of growth is more revealing than a single share. Gartner's two columns imply $961 billion of additional worldwide spending. Data centre systems account for $487 billion of that difference, just over half. The IaaS line rises by $75 billion, software by $215 billion and services by $76 billion. These are differences between rounded forecasts. An equal dollar of extra equipment and extra software revenue has a different life thereafter. Equipment can be put to work for years before the purchaser has recovered its cost. An application must keep enough customers to support its next renewal. An investor trying to identify the winner of a computing cycle needs to know where the equipment goes and who gets to set the price of using it. 08
Five markets seen from different tills
Take the cloud first. Synergy Research estimated $167.7 billion of cloud infrastructure service revenue in the third quarter of 2026. Its definition includes infrastructure services, platform services and hosted private cloud. Four quarters at the September pace would give $670.8 billion. The same researcher reported $558 billion for the twelve months actually covered by its estimate. The difference is $112.8 billion before anyone has changed a contract, simply because the industry was growing and the two calculations answer different questions. Putting the annualised Synergy figure beside Gartner's $292 billion as rival estimates of the same business would add a second error involving the products each researcher counted. 25 08
Enterprise applications offer a case where two numbers can legitimately be combined. Futurum's Table 2 forecasts $323.3 billion of 2026 sales delivered as SaaS and $91.8 billion delivered on premises across the applications it studies. Within that particular table the two delivery categories amount to approximately $415 billion. A customer replacing a licensed application with the same vendor's hosted version moves between the categories. To establish that an AI company captured revenue, we would need to identify a change of supplier or a new paid AI component and trace it through the agreement. A shift of delivery method on its own cannot tell us whose shareholders got the money. 26
There is less reason to add the data market. Gartner's 2025 forecast for database management systems put 2026 at $161 billion. A bank can run a database on its own equipment, buy it as a managed cloud service or consume it inside an application. Its application vendor may be the party paying for the database. There are also analytical services outside the definition of a database management system. The estimate gives a sense of the scale of one contested activity. A survey of bank purchases would still need to identify whether the bank actually sees the database invoice or whether the application company decides what engine to buy. 28
Consulting presents a further problem of time. Source Global Research's March outlook put the market around $315 billion. In August it expected the worldwide market to pass $350 billion in 2026. Without a published reconciliation it would be unwise to assign the difference to AI demand, new geographies or any particular service. Nor can the entire consulting category simply be added to a worldwide IT services estimate. Some engagements help a client reorganise a business, others implement software, and an outsourcing contract can contain both work and software rights. To price a bid against a consultant, start with the statement of work that expires this year. Its boundaries are at least negotiable by the people in the room. 27 50
The customer who never issued an invoice
Technology bought from an outside supplier leaves a price and a payee. A tool written by the bank's engineers for use in its own branches can enter the economy through another door. The US Bureau of Economic Analysis counts qualifying software developed for a business's own use as investment. Where there is no arm's-length sale, its method estimates production costs, including the labour that goes into developing the software. It distinguishes new or substantially enhanced software from ordinary running activity. An archive of vendor invoices and a national estimate of software investment can therefore both be carefully assembled and cover different work. 121
This matters to the proposed AI computing company because the first cheque it receives can come from an employer that has never purchased the task before. Think of a group that builds the internal tool for assigning payment disputes to specialists. Employees write the application and keep its rules up to date. The bank then buys a service to prepare the evidence for those specialists. Its external technology bill rises immediately. Its internal developers may go on maintaining the same assignment tool. If a new job has been bought, the bank can be better served, and the lab can earn recurring sales, without a dollar coming off an incumbent software invoice.
A different bank might already employ an outside firm to assemble those files. There the same product could replace a renewal. The commercial evidence in the two cases would look almost identical to the lab's finance team. Both customers could have the same accepted volume, the same price and the same implementation cost. Even a perfect statement of the lab's recognised revenue would leave the origin of the two payments undetermined. The buyer has to supply that part of the story. A staffing plan, an expiring services contract or an order authorising a previously unfunded job will say more about the source of growth than a list of impressive customer names.
Even a purchase with a named supplier can reach the financial statements on a different timetable from the cash. The IFRS Interpretations Committee considered a customer paying to configure a cloud application. In the circumstances it examined, the customer received access to software controlled by the supplier. The committee asked first whether the additional work created an identifiable asset the customer controlled. If it did not, the timing of expense depended on who supplied the configuration and whether it was a distinct service. A separate service could be expensed when performed. Work inseparable from access could be expensed as the supplier provided access over the contract term. 122
For a reporter examining a migration, that distinction changes the documents worth asking for. A bank may pay for installation in December, begin receiving service in January and show part of the expense well after the original project team has dispersed. Comparing two quarters of expense could then suggest a price reduction that the cash ledger never experienced. The order, the payment date, the expiry clause and the period of service each belong in the file.
One purchase, several sellers
The national accountants have a way of thinking about this problem. At industry level the Bureau of Economic Analysis distinguishes gross output from the contribution left after purchased intermediate inputs are deducted. A material can appear first in the sale of a component and again inside the price of the finished article. Both producers made actual sales. The intermediate input has to be dealt with before adding up what industries contributed to domestic product. A bank buying one service has a simpler question. How much left its own account? The answer can be smaller than the sum of the perfectly genuine sales made down the chain. 120
How a dollar gets counted twice
A bank buys a completed file for $120. Read across to see what each party pays and down to see what a seller bills. Change who buys the cloud capacity and compare the two totals.
| Payer ↓ Payee → | Processor | Model lab | Data platform | Cloud |
|---|---|---|---|---|
| Bank | $120 | · | · | · |
| Processor | · | $30 | $32 | · |
| Model lab | · | · | · | $10 |
| Data platform | · | · | · | $14 |
| Billed | $120 | $30 | $32 | $24 |
$120
- Buyer’s cash
- $120
- Transfers between suppliers
- $86
Follow the bank’s row to see who invoices it. The other rows pass that money between suppliers.
Processor bills $120, pays $62 within this chain, and retains $58 before its own costs.
Give a processor $120 for a completed file. It buys a $30 model service and a $32 data service. The lab spends $10 of its receipt on cloud capacity and the data supplier spends $14 on the same cloud. Add what the four sellers billed and the total is $206. Deduct the $86 of purchases that moved money among them. The balances are $58 for the processor, $20 for the lab, $18 for data and $24 for infrastructure. They add to the customer's $120. Each seller still has wages, equipment and other costs outside the illustration. Its balance after the listed payments gives us no entitlement to call it operating profit.
Now have the bank procure all $24 of cloud capacity directly and have the other parties reduce their quotes by exactly the charges they no longer incur. The processor bills $96. The lab and data suppliers bill $20 and $18. The cloud still bills $24. The customer spends the same $120, every supplier retains the same balance and the sum of supplier invoices falls to $158. Put a revenue chart beside the two contracts and the industry appears to have lost $48 of business. Put the transaction records beside the chart and you can identify the change as a new billing address for the same work.
A sensible starting point for a market forecast is therefore a small set of records that can actually be matched. Pick a buyer and a period. Record the party issuing each invoice and whether the charge sits inside a larger purchase. Keep the contracted service level, the accepted volume and the old renewal quote. Then ask what the prospective supplier can collect after the buyer has exercised its own options for a better price. There is ample money in the world for the prediction in this essay to succeed. The test begins with the customer whose next payment can be followed twice, first into the seller's account and then out to the companies that make the sale possible. In the cloud those companies can include the seller's most determined competitor.