SynapticThe Next Computing Bill
Chapter 11 · Interactive edition

Five industries rewrite a purchase order

Give five suppliers the same buyer. The winning bids show how much of a million-dollar budget an AI company can collect, and how much the bank keeps.

Give me the bank's accounts payable file and I can tell you quite a lot about the business of artificial intelligence. Give me five market forecasts and I can tell you how large five analysts think their subjects are. The first file contains something precious. Each payment has left the bank exactly once. That property disappears as soon as we start adding the sales of companies that buy from one another. A dollar that pays a model company can turn up again in a cloud provider's results. A dollar that pays a consultancy can appear in both. All three firms have done real work. The bank had one dollar.

This chapter puts five claimants around the same table. Our buyer is an illustrative bank with one million US dollars of annual spending under review. It handles the same volume and mix of work after renewal. Every bidder faces the same requirements for service, evidence, reopening and recovery. The cash comes out of a single year's budget. The amounts were constructed to make the contracts independently awardable, a condition that often takes considerable work to establish in a real business. They describe a fresh procurement exercise. The separate worked examples in the preceding chapters have different scopes and cannot be stitched into a customer.

Across the table sit a cloud account director, a software sales representative, a consulting partner, a supplier supporting an installed system and a data platform vendor. Their existing claims are $280,000, $260,000, $220,000, $150,000 and $90,000 respectively. A sixth firm wants to provide AI services using some of the same suppliers. The interesting number is the fee it can collect once every person at this table has been given a chance to respond. The easy intellectual mistake would be to send the other five home before asking for their prices.

Clearing the table

Start with the biggest line. Synergy Research estimated worldwide cloud infrastructure service sales of $167.7 billion in the September 2026 quarter and $558 billion over the preceding twelve months including that quarter. At the quarterly pace the industry would have been running at about $671 billion a year. The difference between that extrapolation and the trailing total is large enough to change an investor's sense of the hurdle a challenger must clear. Synergy already includes platform activity by AI labs where it meets its definition. A supplier can enter this market statistic before it takes a procurement decision away from anyone. 25

Amazon reported $45.984 billion of AWS segment sales in that quarter. Some of a model company's success can become AWS revenue through purchased computing power even when a bank deals exclusively with the lab. For the bank's own $280,000 line in our example I include only money it pays directly for its runtime and recovery capacity. The lab may also rent machines and the bank may pay a separate data provider that does the same. Both of those upstream cloud bills belong inside their respective suppliers' costs. Taking them out of the buyer's cloud column makes the chart smaller and the displacement claim considerably more precise. 05

Futurum's enterprise application forecast offers a rare chance to compare two categories on the same basis. Its 2025 study put the SaaS delivery of those applications at $323.3 billion in 2026 and on-premises delivery at $91.8 billion. A database engine can sit underneath either application. Forecasting the engine market independently tells us something about the supplier's opportunity, yet putting that total beside the application totals on a single pie chart would give the reader a false sense of where the slices meet. Our bank avoids the problem by giving each contract line a single purchasing owner. 26

Consulting presents a different problem. Even a single market researcher can change its account of the year. Source Global Research's March 2026 estimate put worldwide consulting around $315 billion. In August the firm expected the market to pass $350 billion by year-end. Both were forecasts. The two publications give a reader too little information to reconcile that difference to contracts, currencies or a change in coverage. Choosing the later estimate gives us a dated point of reference. Treating the gap as $35 billion of newly signed business would turn a change in the researcher's account into money in somebody's till. 27 50

The vendor disclosures come in different currencies and periods. Accenture reported $9.28 billion in quarterly consulting revenue, with managed services reported separately. SAP's software licence and support line was €2.581 billion for its September quarter. Salesforce's subscription and support line reached $10.8 billion in its July quarter, including Informatica. They imply annual paces of roughly $37.12 billion, €10.324 billion and $43.2 billion if the respective quarters repeat. A firm moving an installed customer onto a subscription could move sales out of one category and into another while keeping the same customer. Getting those distinctions right is part of finding the business at risk. 09 30 29

The data market resists a neat boundary. Gartner's December 2025 forecast put 2026 database management system spending at $161 billion. Some modern data platforms sell services beyond that definition, and a substantial part of the database business already lives in the cloud. Snowflake reported just under $1.492 billion of product revenue in the three months to July. Four times that figure is about $5.97 billion. In August Databricks said it had crossed a $7 billion revenue run rate. These are different disclosures. The procurement question survives the imperfect market comparison. When a new agent answers a hundred questions, whose meters turn? 28 51 32

The buyer gets the first bid

I would bring the bank's head of procurement to this meeting an hour before the AI seller. Give her the authority to negotiate the five current services without changing the way a single case gets handled. She obtains prices of $268,000 for cloud, $246,000 for subscriptions, $200,000 for consulting, $150,000 for the installed estate and $88,000 for the data platform. The business can therefore keep $48,000 on its own. That saving sets the price of entry for any bidder who wants credit for changing how work gets done. A board that compares every new proposal with an unchallenged million will buy a very expensive opinion of its own innovation.

An ordinary renewal deserves as much scrutiny as an AI pilot. Suppose a cloud engineer turns off a service over a quiet fortnight and the bill falls. Was it idle or was it holding the replica that allows the bank to survive a regional failure? A software buyer sees an inactive login. Did its owner leave the firm, or is she one of two people authorised to release an emergency correction? A consulting team spends a day documenting an old exception. Was it reconstructing lost work or creating the only evidence that protects an individual customer from being charged twice? A good procurement office puts names against these questions before the owner of a budget takes credit for the saving.

There is real evidence that ordinary intervention matters. Flexera's account of renegotiating its own mixed software agreement identified $1 million of hard SaaS savings and separated that result from both installed-licence savings and cost avoidance. Engineers at Zendesk describe setting up parallel tests on three large data models to examine actual warehouse consumption. Neither buyer needed an AI vendor to discover that a commercial or technical configuration could be improved. Their methods differ, and neither case supplies a representative percentage of waste. They show why the baseline for a proposition about displacement deserves a competent buyer throughout the exercise. 38 52

Exhibit 26 / Matched buyer wallet

Five bills before and after renewal

Five disjoint expense lines add to one bank’s $1 million annual budget. Read the columns by width, then select one to inspect its competing bids.

Winning mix · one year

$928,000

Cash outlay on the original $1 million of work

AI supplier fees$79,000Additional saving against ordinary renewal$24,000
Existing suppliers $828,000AI supplier $79,000Transition $21,000Kept by bank $72,000
Cloud infrastructure · Existing suppliers · $250,000 within original budgetCloud infrastructure · AI supplier · $10,000 within original budgetCloud infrastructure · Transition · $4,000 within original budgetCloud infrastructure · Kept by bank · $16,000 within original budgetApplication subscriptions · Existing suppliers · $220,000 within original budgetApplication subscriptions · AI supplier · $15,000 within original budgetApplication subscriptions · Transition · $5,000 within original budgetApplication subscriptions · Kept by bank · $20,000 within original budgetConsulting services · Existing suppliers · $120,000 within original budgetConsulting services · AI supplier · $54,000 within original budgetConsulting services · Transition · $12,000 within original budgetConsulting services · Kept by bank · $34,000 within original budgetInstalled systems · Existing suppliers · $150,000 within original budgetData platform · Existing suppliers · $88,000 within original budgetData platform · Kept by bank · $2,000 within original budget

All payments fit the original budget.

Consulting services

$186,000

Old invoice $220,000 · ordinary $200,000

The incumbent offers a smaller team. A specialist bids for repeat preparation and pays for repair from its fee. AI route awarded at $186,000.

Inspect the five ledgers in dollars
Annual bank payments · USD thousands · Winning mix
AccountPriorOrdinarySuppliersLabChangeOutlay
Cloud infrastructure280268250104264
Application subscriptions260246220155240
Consulting services2202001205412186
Installed systems15015015000150
Data platform9088880088
Compare published market sizes and vendor run rates
Separate measurements · original currency and period
Supplier marketMarket estimateVendor disclosure and pace
Cloud infrastructure$167.7bn · Q3 2026 worldwideAWS · $45.984bn segment revenue in Q3, $183.936bn at four times the quarter. 25 · 05
Application subscriptions$323.3bn · CY2026 forecastSalesforce · $10.8bn subscription and support in FY27 Q2, roughly $43.2bn annualised. 26 · 29
Consulting servicesAbove $350bn · August forecast for 2026Accenture · $9.28bn consulting in FY26 Q4, about $37.12bn annualised. 50 · 09
Installed systems$91.8bn · CY2026 installed application forecastSAP · €2.581bn licences and support in Q3, €10.324bn at that quarterly pace. 26 · 30
Data platform$161bn · CY2026 DBMS forecast, partial proxySnowflake · $1.492bn quarterly product revenue, about $5.97bn annualised. Databricks disclosed a run rate above $7bn. 28 · 51 · 32
Download market evidence (CSV)
Figure 26. Illustrative matched wallet in US dollars. Tile area represents dollars from the original million. Quoted extra expenditure is printed separately. “Winning mix” minimises the same-service bill across all five lines under the selected discount terms. Ordinary renewals include procurement's own savings. Industry-wide estimates have overlapping boundaries.

The five columns describe a million dollars that the bank really could have paid under our assumptions. The width of the cloud column is twenty-eight cents in each original dollar. Consulting takes twenty-two. Height shows what happens inside each contract. A large column made almost entirely of retained supplier charges is a larger market and a poorer immediate opportunity than a smaller column with a generous, contestable service fee. Select consulting and the distinction becomes visible. A $220,000 line sustains a $54,000 AI bid. The bigger cloud line sustains only $10,000. The share of spending that can move depends on what the bank is prepared to stop buying.

Five decisions at renewal

Take cloud first. A lab offers scheduling improvements and accepts responsibility for the timing of a defined batch of bank work. The bank expects its direct infrastructure charge to fall to $250,000. Add the lab's $10,000 fee and $4,000 to qualify the new schedule. The buyer pays $264,000, only $4,000 below the price its own team obtained. This contract is worth bidding for if the supplier can serve it at that fee. The former cloud supplier may receive part of the $10,000 back as an upstream payment. A buyer interested in controlling its bill needs the $264,000. An investor interested in the cloud provider's growth needs both the direct loss and that second receipt.

Seats come next. The bank can purchase its existing setup for $246,000 once obvious excess rights have gone. The alternative keeps $220,000 of software and metered actions, buys a $15,000 agent service and incurs $5,000 to change access and train the staff. At $240,000, the buyer is another $6,000 ahead. Its scarce asset may be the contractual right to use a different interface. If the software agreement requires a licensed identity for every person who benefits from the work, the bank needs written confirmation of the proposed terms. In the example the parties have agreed them. A photograph of an agent producing the right answer would be a curious substitute for that letter.

Consulting accounts for the largest transfer. The incumbent offers $200,000 for the same annual programme after taking duplicate evidence collection out of its ordinary bid. Using the specialist leaves $120,000 with the existing consultancy, pays the new supplier $54,000 and costs $12,000 to qualify the work, for a total of $186,000. Of the $34,000 saved against the original contract, $14,000 requires the specialist's offer. The fee the entrant earns is considerably larger than the saving it creates for the buyer. It can be paid partly for replacing valuable work that someone else used to perform. Counting only waste would miss that business. Describing the whole fee as newly created economic value would exaggerate it.

The installed estate gives the salesperson a harder afternoon. Most of the $150,000 is hard to move because the bank still needs the system and the people who can restore it. On the proposed route those retained services cost $140,000, the lab asks $6,000 and the first-year qualification costs $5,000. Somebody is going to have to explain to the chief financial officer why spending $151,000 counts as a saving. A later year may justify the transition if the qualification does not recur and both suppliers hold their prices. The one-year buyer in this exercise keeps the present arrangement. A multiyear buyer could quite rationally make a different decision.

The data provider has an even better counteroffer. Its current $90,000 line comes down to $88,000 after ordinary changes. Paying $84,000 for the retained platform, $7,000 for an outside answer service and $2,000 for transition would bring the cost to $93,000. There are attractive reasons to buy better answers, especially if they allow more employees to investigate more problems. In our tender everyone promised the same accepted work. A broader service deserves a separate purchase request from someone prepared to pay for the extra output. It cannot make an expensive bid for this service cheaper. The agent wins three lines and loses two.

The agreed payments now add to $928,000. Existing suppliers receive $828,000. The AI supplier invoices $79,000 and the bank pays another $21,000 for transition. The bank keeps $72,000 against the old bill, of which $24,000 is incremental to the best ordinary renewals. One useful check is to award all five AI proposals in the exhibit. The sales organisation can now point to $92,000 of fees it proposed. The buyer would spend $934,000, or $6,000 more than when it rejected the last two offers. An addressable pipeline can grow through bids whose acceptance would make the customer worse off. A sensible revenue forecast has to model rejection.

A clause that can move two columns

One assumption in that drawing deserves a lawyer's pencil. The five lines can be awarded independently. Change a single clause. Suppose the software distributor withdraws a $9,000 discount on the remaining subscriptions if the bank gives the cloud scheduling work to the lab. That condition makes the three-winning-bid combination cost $937,000. The bank has a better response. It can accept the ordinary cloud renewal at $268,000, keep its software discount and award the other two winning bids as before. It now spends $932,000. Its AI supplier books $69,000. A discount written on one invoice has taken $10,000 of prospective revenue off another firm's order.

The point at which the choice changes is unusually easy to miss in a large negotiation. The lab's cloud route was $4,000 cheaper before the condition appeared. A lost discount above $4,000 consumes that advantage. The lab could cut its fee to try to get back in. Its ability to do so depends on a cost of service invisible to the bank's spreadsheet. A sales director looking only at her cloud opportunity might sign a concession that loses money. Her opposite number at the distributor may happily give up some software margin to retain a much larger cloud commitment. There is a reason procurement departments ask for the complete set of private offers on the same day.

One file, five clocks

Time gives us another way to see what the six businesses are selling. A customer has challenged a transaction. The bank must retrieve the original evidence, open a case, assemble the material, authorise the correction and verify the resulting balance. Five systems or service providers participate. Some tasks take minutes with a person or a computer working on the file. Others take minutes because the file is sitting in somebody's queue. If you buy a faster engine for a desk that spends most of the morning waiting for authority to proceed, the customer may have difficulty noticing the purchase.

Exhibit 27 / Case and settlement model

Five contracts for one banking operation

Walk one file from the source image to a reconciled balance. Each station has its own clock. The prime contract determines where a separate $100 service payment lands.

Bank exception deskHeight measures queue time
  1. Cloud · Retrieve source image
  2. SaaS · Open the case
  3. Consulting · Assemble evidence
  4. Installed · Approve posting
  5. Data · Verify the balance
Consulting · station 3

Assemble evidence

Compare the claim against the documents that arrived with it.

Required handling
4 min
Waiting
7 min
Repeat work
0 min
Elapsed per file44 min17 working · 27 waiting
Cash after listed transfers$60 lab$22 integrator · $18 cloud

Bank → lab $100. Lab → integrator $22. Lab → cloud $18.

Read the five-station timing table
Serial processing time per file · minutes
StageRequiredQueueRepeatTotal
Cloud2305
SaaS2507
Consulting47011
Installed68014
Data3407
Figure 27. Synthetic serial path, minutes per accepted case. Each brass collar on a station’s support marks one minute of waiting. When repeat work is included, each amber bead on the front of a tray marks another minute of handling. Each station preserves its required checks and waiting time. The separate $100 ticket illustrates settlement under two prime contracts. Upstream payments are funded from that ticket. This per-file exercise uses a separate scale from the annual wallet in Figure 26.

In the illustrative serial trace there are seventeen minutes of required handling, twenty-seven of waiting and ten of repeated work. The customer experiences fifty-four minutes. Removing all ten repeated minutes gets the result to the customer in forty-four. The single largest opportunity left is waiting. A revised shift pattern or a clearer delegation may release more of that time than another model upgrade. A buyer could pay for a different service level, or retain the twenty-seven minutes as an acceptable cost of keeping two authorised people involved. A shorter clock on a dashboard earns its way into the economic argument when someone knows which minute changed and what else depended on it.

The prime contract changes the cash trace without moving a minute on the clock. In a separate hundred-dollar example the lab collects the payment, sends $22 to an integrator and $18 to the cloud. It keeps $60 before other costs. Give the prime to the integrator and it pays $32 to the lab, which in turn pays $12 for cloud. The integrator now retains $68, the lab $20 and the cloud $12. In both arrangements the bank spends $100. None of the three balances includes every expense of delivering the service. A change in who signs has moved more cash between suppliers than the removal of a single queue, because in this example nobody renegotiated the service price when the queue moved.

That is a practical reason executives should care about the contract even when the technology works superbly. The party that can demonstrate how long a file sat and who had the authority to release it can defend its price against the next bidder. The bank can preserve that evidence itself. It can ask for time stamps in a form a replacement supplier can read and a documented method for calculating reopened cases. If it hands the record exclusively to its prime, it may be buying better service today at the cost of a weaker tender next year.

Where the work surfaces

It would be easy for a reader to imagine that all these decisions travel through a grand new software platform. Consider a more familiar ending to the exercise. An analyst puts the five awards in a workbook. Her manager uses a paragraph from it in a spending memo. Counsel corrects a term that lets a supplier count a reopened file as finished. The committee sees a one-page illustration of the saving. The number passes through four documents and changes its meaning in every one. The workbook can show $72,000 below last year while the committee needs to know that only $24,000 is attributable to the new route. Somewhere between the two documents a human being has to notice the difference.

Exhibit 28 / Working documents

The desktop handoff

Follow the same renewal number through four working documents. At every handoff a different person can send it back.

Workbook · working copy

Annual fees

Prior outlay$1,000,000
Selected renewals$928,000
Difference$72,000
Inputs and formula

Finance analyst

Trace the two totals to the five contracts. Check the reporting period and exclude transfers between suppliers.

Anthropic describes financial modelling, formula audit and scenario analysis in Excel. Product source 13

Read the complete approval sequence
DocumentAccountable readerAcceptance check
WorkbookFinance analystTrace the two totals to the five contracts. Check the reporting period and exclude transfers between suppliers. Source 13
MemoBudget ownerName the next-best offer. Separate the buyer’s extra saving from the full year-on-year difference. Source 13
RedlineBank counselCounsel checks that the proposed warranty and exclusions match the pricing assumptions. Source 14
Design proofRelease ownerThe release owner checks that the amount, comparator and unresolved exceptions survived the layout. Source 15
Figure 28. The four specimens are an editorial reconstruction using the illustrative wallet in Figure 26. The cited product materials document individual capabilities. The handoffs, approval rules and bank documents are illustrative.

There is commercial substance to this apparently prosaic sequence. Anthropic has described financial workflows inside Microsoft's Excel, Word, PowerPoint and Outlook. Its legal plugin repository includes a vendor agreement review against a firm's playbook. Claude Design can take document inputs and export a presentation or PDF for review. Each capability provides a place from which to contest a piece of paid work while the existing desktop applications keep running. The depicted route through this particular bank is mine. The vendors document the individual tools. An uninterrupted, approved journey across all four desks would require a customer willing to demonstrate it. 13 14 15

The incumbent has several ways to benefit. A data platform can charge for the queries behind the workbook, preserve access controls and offer a native agent that costs less than a separate service. A software vendor can keep a smaller seat order while selling a larger volume of paid activity. A consultant can sell independent testing to a bank that quite reasonably declines to let an AI provider mark its own work. A mainframe operator can expose an approved transaction through a supported interface and sell more capacity when more good cases reach it. Each response puts a price on something the bank still needs. Disruption can increase one supplier's unit volumes at precisely the moment another supplier wins the customer relationship. 17 19 57

There is also a way for the buyer to lose. Picture a contract in which nearly every performance credit depends on whether a file was eligible for automation. The vendor can make its resolution rate look excellent by removing difficult cases from the eligible population. Staff now receive a smaller, harder queue while an old per-case price falls apart. The budget holder discovers the error only after the department pays for overtime or commissions a new support agreement. A fair comparison keeps the entire original cohort under observation and assigns the cost of each exception to whoever actually paid it. The expensive case deserves the same place in the ledger as the easy sale.

I expect AI computing companies to win operating budgets that once seemed inaccessible to a software supplier. This example puts a size and a condition on the claim. A single bidder can take $79,000 from five categories of spending at one bank even though two of its offers fail. Its advantage survives a competent purchasing department by $24,000. Its own profitability depends on costs the bank never sees. To take that prediction out of the model and into the market I would want the winning orders, the losing offers and a year's worth of case outcomes from the same buyer. At that point we could give the finance director a number to sign, the customer a service to judge and the investor a business worth pricing.

Sources and reading notes

  1. 05 · Amazon third-quarter 2026 earnings

    AWS segment revenue and operating profit. Quarter to September. Exclude equity gains in Anthropic from AWS operating performance.

  2. 09 · Accenture FY26 Q4 earnings

    Consulting and managed services by type of work. New bookings can span years. One firm's revenue cannot establish total industry size.

  3. 13 · Anthropic finance agents

    Named tasks and Microsoft 365 integration. Track availability per product/platform. No independent productivity estimate.

  4. 14 · Claude for Legal

    Plugin inventory and supported workflows. Reproduce version before testing and record human legal sign-off.

  5. 15 · Claude Design by Anthropic Labs

    Design artefacts and handoff. Availability is evidence of entry, independent adoption needs additional reporting.

  6. 17 · Snowflake Cortex evaluation guide

    Distinct AI and warehouse meters, geography-specific example and usage history. Do not generalise effective pricing.

  7. 19 · IBM z/OS Connect

    API access to existing mainframe applications. Example architecture requires client authorisation and testing.

  8. 25 · Synergy Research, 29 October 2026

    Worldwide Q3 enterprise spend on IaaS, PaaS and hosted private cloud. Report text gives $167.7bn, or $670.8bn at that quarterly pace, and $558bn trailing twelve months. Different scope from Gartner IaaS.

  9. 26 · Futurum, enterprise applications market, H1 2025 edition

    Table 2, April 2025 forecast vintage. 2026 forecasts $323.3bn SaaS and $91.8bn on-premises enterprise applications. Excludes many infrastructure and middleware categories.

  10. 27 · Source Global Research, 2026 service line forecasts

    About $315bn worldwide consulting market by this firm's definition. Forecast, not audited turnover. Test sensitivity to inclusion of systems integration.

  11. 28 · Gartner, worldwide DBMS forecast, 2025 update

    $161bn forecast for 2026 DBMS. Partial proxy for data platforms. Includes cloud databases, excludes some engineering, orchestration and governance.

  12. 29 · Salesforce FY27 Q2 earnings

    Quarter to July 2026. $10.8bn subscription and support includes $440m Informatica. Separate acquisition contribution from organic change.

  13. 30 · SAP Q3 2026 consolidated results

    Table A.1, EUR millions. €2.581bn software licences and support. Vendor revenue category is a proxy for exposure to installed software.

  14. 32 · Databricks Q2 announcement, 13 August 2026

    Company-reported run rate above $7bn. Method and audited annual sales are separate questions.

  15. 38 · Flexera's own three-year software renewal

    First-party account of a $46m mixed software and cloud agreement. $1m hard SaaS savings, $1.5m other hard savings and $4.5m cost avoidance over three years. No matched invoices disclosed.

  16. 50 · Source Global Research, August 2026 global consulting market forecast

    20 August 2026. Forecast to pass US$350bn worldwide in 2026. March forecast S27 was about US$315bn. The articles do not reconcile the two estimates.

  17. 51 · Snowflake, Form 10-Q for the quarter to 31 July 2026

    Note 3 gives $1,491.861m product revenue. The segment table reports third-party cloud infrastructure expenses at approximately 75% of cost of product revenue in the quarter. Those percentages use different denominators.

  18. 52 · Zendesk engineers on parallel warehouse tests, 25 November 2025

    The authors cloned three large data models and their production workflows. They report more than 80% lower credit costs on right-sized warehouses. Customer-authored on a Snowflake publication. The whole-company invoice and the cost of the newly added workloads are unavailable.

  19. 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.