SynapticThe Next Computing Bill
Chapter 14 · Interactive edition

A company larger than the cloud

Start with four quarters of filed sales. Give AWS five more years to grow. What would Anthropic have to sell to catch it, and what would those sales have to earn?

Put a date on the wager. For the four quarters ending in December 2031, I expect an AI computing company to report more recognised revenue than at least one of the two cloud businesses whose accounts let readers check the result. Anthropic is my leading candidate. Google Cloud is the nearer target today. Overtaking Amazon Web Services would settle the stronger claim. A company that reaches either milestone by taking responsibility for recurring enterprise work would change what a technology supplier can sell. A company that reaches it by reselling ever larger amounts of someone else’s compute would have accomplished something financially and industrially different.

A price on a trading screen can settle neither question. An increase in the share price changes the value ascribed to future earnings. An issue of new shares puts money in the company’s account. Someone still has to agree to buy the service, the company has to deliver what it promised, and the resulting sales have to enter its accounts. For the calculation below I start the clock with the four quarters ended September 30, 2026. An exact five-year interval ends in September 2031. The December reporting period gives the prediction its final calendar-year check. I would use the reporting period, even when the accounts appear in the following February.

The starting distance

Anthropic reported $2.040 billion of revenue in the December 2025 quarter. March, June and September brought in $4.731 billion, $11.555 billion and $16.956 billion. Add the four entries and the starting line is $35.282 billion. Multiplying the last quarter by four would put the company at $67.824 billion. That shortcut would put almost twice the revenue Anthropic actually recognised into the twelve months under comparison. The distinction is particularly consequential for the fastest-growing company in a comparison. The businesses that have already achieved scale receive much less of a head start from the same shortcut. 01

Amazon provides the check on our arithmetic. The quarterly AWS sales in its supplement add to the trailing figure the company itself prints, $161.382 billion. AWS operating income across those quarters was $61.020 billion. For Google Cloud, adding four published segment tables gives $93.169 billion in revenue and $31.846 billion in operating income. Alphabet’s nine-month segment results plus the preceding December quarter produce the same two totals. Both incumbents had profitable businesses with which to finance a response. Their shareholders already own a claim on some of the growth in AI computing, however the contest for the prime contract turns out. 05 06 84 85 86 87

Anthropic recorded a $4.096 billion operating loss over the same year. The June quarter contributed positive operating income of $974 million, between losses in March and September. Amazon’s figure belongs to a segment inside a group. Alphabet allocates certain expenses to its operating segments and leaves some shared and research costs at the parent. Anthropic’s figure belongs to the whole company and includes expenses such as stock compensation. A comparison of reported operating results tells an investor what the accounts say. Estimating what either cloud would earn as a separate listed company would require its own set of accounts. 01 05 87

Microsoft reported Azure revenue above $100 billion for the fiscal year ended June 30, 2026. That disclosure is relevant to the scale of the industry. It supplies neither an exact amount nor an Azure operating result for the twelve months to September. Microsoft Cloud includes other businesses. Substituting its revenue for Azure’s would turn improved disclosure from one company into an arbitrary penalty on another. If Microsoft publishes a comparable series, there will be a third opponent to track. Until then the two named tests can be decided on their own terms. 07

The opponent gets five years too

A stationary AWS would require Anthropic to compound revenue by about 35.5 per cent a year just to draw level after five years. A stationary Google Cloud requires about 21.4 per cent. Freeze the challenger’s present scale in one part of a discussion, declare it capable of transforming every customer’s business in another, and an important connection goes missing. Suppliers of storage, model hosting and distribution can grow precisely because the challenger succeeds. Both sides of the race deserve a growth assumption.

Exhibit 34 / Revenue and earnings hurdles

The hurdle to exceed AWS

Start with four reported quarters. Choose a cloud segment and see the path Anthropic’s sales would have to follow to draw level in September 2031. The gold ring marks a 2028 checkpoint on that path.

Five years to parity

Annual US$ billions
Lab revenue paths to AWS sales parity0200400600202620272028202920302031Annual lab revenue · US$bn2028 review

Lab at 60% growth$370.0bn

Sales needed · AWS growth 15%$324.6bn

Sales needed · AWS growth 0%$161.4bn

Sales needed · AWS growth 30%$599.2bn

Terminal operating margins

Change in percentage points from the reported trailing segment margin. Margin assumptions apply to the profit test.

Lab sales growth for parity55.87%
2031 cloud revenue$324.60bn
2031 lab revenue$369.96bn

AWS grows at 15% a year. The lab finishes $45.36bn above parity. The parity path passes $85.72bn in September 2028.

Inspect the twelve quarterly observations
Recognised revenue and operating result · USD billions
AnthropicAWSGoogle Cloud
Quarter endedSalesOp. resultSalesOp. resultSalesOp. result
2025-12-312.040−2.83635.57912.46517.6645.313
2026-03-314.731−1.66737.58714.16120.0286.598
2026-06-3011.5550.97442.23216.62124.7688.814
2026-09-3016.956−0.56745.98417.77330.70911.121
Four quarters35.282−4.096161.38261.02093.16931.846

For Azure, Microsoft reports annual revenue above $100bn for its year to June 2026. An exact September trailing revenue and comparable standalone operating result are unavailable here. Microsoft annual report

Calculation and accounting scope

Grow each cloud’s trailing sales for five years. For the profit test, multiply projected cloud sales by its assumed terminal margin, then divide the result by the lab’s terminal margin to find the sales the lab needs. Divide the required sales by the lab’s $35.282bn starting sales, raise to the one-fifth power and subtract one. This is the rate for equality. Winning requires more. The lines depict a smooth route between endpoints. The lab starts with a GAAP operating loss, so a compound growth rate in operating earnings would be undefined.

Figure 34. Quarter ends run from December 2025 through September 2026. Reference paths assume 0% and 30% annual incumbent growth. Margins belong to the operating-profit comparison. All future observations are scenarios. Anthropic prospectus · AWS supplement · Alphabet segment filing
Download filed data (CSV)

Give AWS 15 per cent annual growth as an exercise. Its trailing sales reach $324.597 billion in September 2031. Equality then requires Anthropic to grow by 55.868 per cent a year from the disclosed starting line, with a fraction more needed to take the lead. Apply the same incumbent growth assumption to Google Cloud and the target becomes $187.396 billion, requiring 39.650 per cent annual growth from Anthropic. The reader can replace either rate. These numbers describe the size of a bet somebody has chosen. They contain no estimate of the probability of winning it.

One way to see the burden is to work backwards from the order book. An annual increase of fifty or sixty per cent on a modest base can come from a handful of large customers. The same percentage near the end of the exercise requires tens of billions of dollars of additional sales in a year, on top of retaining the existing buyers. A bank that expands its deployment from one business unit to six can contribute to that increase once. In the following year, the supplier must renew all six and find the next set of operating budgets.

Consider a lab that compounds at 60 per cent. Its sales reach $369.959 billion. At a 20 per cent operating margin, that business earns $73.992 billion in the terminal year. Give both cloud segments their starting operating margins and the assumed 15 per cent sales growth. AWS generates about $122.733 billion in operating income and Google Cloud about $64.054 billion. The lab wins both revenue comparisons and one profit comparison. Relative to AWS at those sales, the lab would need to earn more than 33.17 cents of operating income per dollar of revenue to win the second contest.

There is no sensible positive compound growth rate for earnings that starts with a loss and ends with a profit. Instead, take the incumbent’s terminal operating income and divide it by the operating margin the lab could earn then. At a 20 per cent margin, matching AWS’s $122.733 billion requires around $613.665 billion in lab revenue. Its sales would have to grow by about 77.0 per cent a year to get there. This arithmetic gives due weight to the compute bill, the engineers who maintain the service and the promises made to buyers whose cases come back.

What an accepted case would have to earn

A procurement director can do more with a price and a volume than with a compound growth rate. Construct a separate possible business for 2031. Assign $60 billion of annual revenue to subscriptions, model access and work outside the outcome contracts in this exercise. Assume those lines leave $18 billion after direct delivery costs. Put $30 billion of annual operating expense beneath the combined businesses for research, selling, administration and other fixed expense, including relevant equity compensation. These round numbers are terms of the illustration. Every dollar of expense belongs to one category and the other lines exclude the cases we are about to price.

Give the company 70,000 accounts, each buying a million accepted cases a year at four dollars of recognised supplier revenue per case. These contracts add $280 billion to the $60 billion earned elsewhere. If delivering an accepted case costs two dollars, the case business contributes $140 billion before fixed expenses. Add the $18 billion from the other lines and deduct the $30 billion operating expense. The result is $128 billion of operating income on $340 billion in revenue. That clears both AWS hurdles in the selected scenario, with substantially less room to spare on profit.

Exhibit 35 / Unit economics model

The growth surface

Build a separate 2031 business one accepted case at a time. The gold contour marks portfolios that just match the cloud target. Move the fee, the number of customer accounts and the cost of keeping the promise.

Annual contract portfolioAWS · revenue hurdle
revenue surface by accepted volume and fee. Gold line marks the AWS target at $324.6bn.$340bn0200400600800US$bn0k50k100k$3$6
Gold · parityPoint · your portfolio

Floor axes show active accounts (0–100,000) and recognised dollars per accepted case ($0–$6). Height shows annual US$ billions. Each account buys one million accepted cases a year.

Portfolio revenue$340.0bn
Portfolio operating income$128.0bn
Accounts to exceed target66,150

AWS revenue at 15% annual growth is $324.60bn. The selected portfolio is $15.40bn above that target.

Read the exact two-dimensional slice
Plan view of required recognised fee for a given number of customer accounts0k20k40k60k80k100k$0$1$2$3$4$5$6Recognised fee per accepted case · USDActive accounts · one million accepted cases per account/year

At 70,000 active accounts, parity requires a recognised fee of $3.7800 per accepted case at the selected cost and cloud target. A higher fee crosses the line.

Figure 35. This is a portfolio assembled from assumptions. Its customer count is hypothetical. Revenue equals accepted volume times the recognised fee plus $60bn of other, mutually exclusive sales. Operating income starts from $18bn of other direct contribution, adds case revenue less direct costs and deducts $30bn of fixed operating expenses. The two figures share the selected incumbent’s 2031 target. The portfolio replaces the lab’s growth extrapolation with an independent calculation.
Inspect the cloud target

Look closely at the unit of adoption. A million accepted cases per customer per year is about 2,740 a day, counted through weekends and holidays. That could describe a large payment operation with a tightly defined task. A legal team commissioning a handful of consequential opinions each month has a different price, volume, review cost and responsibility for error. A million inexpensive data lookups and a million signed opinions are equivalent in the model only if they command the same recognised fee and incur the same full delivery cost. The distribution across contracts is a question for reporting.

Move the delivery cost to three dollars per accepted case. Sales still come to $340 billion. Operating income falls to $58 billion. A second model call on a difficult file, a review by somebody with the appropriate authority, an allowance for remedying late errors or an expensive minimum compute purchase can all take part of that extra dollar. The supplier holding the case contract can give the bank a price cap only by carrying the costs that breach it. If a vendor reports margin on accepted cases while charging failed attempts to another business unit, follow the costs back into the consolidated accounts.

Fee compression has a different signature. A customer that obtains a reduction from four dollars to three cuts recognised revenue at the original volume by $70 billion and also reduces operating income by $70 billion before any compensating savings. The service may become popular enough at the lower price to win new customers. To recover the original $280 billion of case sales at three dollars, the company would need over 93 billion accepted cases a year. Recovering the original case contribution at two dollars delivery cost takes 140 billion. Growing into a price reduction is possible. The required sales and delivery capacity have different magnitudes.

Who controls the dollar that enters the accounts

A four-dollar fee needs a definition. Anthropic’s prospectus says it recognises the intelligence service gross in specified cloud marketplace arrangements. It establishes the price, contracts directly with the customer and takes responsibility for the service. Under those circumstances, money it spends on infrastructure enters the cost calculation. In an arrangement where a company only arranges somebody else’s service, the amount it earns can instead be the commission. The model asks for revenue the seller can recognise per accepted case. It places the cost of providing its own promised service on a separate line. Changing the agreement can change the first number even when the bank writes the same cheque. 01

Suppose a bank buys ten dollars of service and one dollar belongs to an agent for arranging the sale. Counting ten dollars of lab revenue in a commission business would inflate its scale tenfold. Conversely, deducting wholesale compute from a principal’s recognised sales and also charging it as a delivery expense would make the seller pay twice on paper. In comparing public companies I would retain each reported figure and identify related purchases alongside it. In reporting total customer expenditure I would follow the original ten dollars once. Whether the AI company became bigger and whether the buyer spent more are separate empirical questions.

Acquisitions pose a related test. Imagine the lab buys a deployment firm billing the bank ten million dollars a year, six million of it for work that has never used the lab’s models. After the purchase closes, acquired external sales can lift the lab’s consolidated revenue. Payments between the two units disappear on consolidation. I would show the reported total, the acquisition’s disclosed contribution and the date control changed hands. A takeover can put the outcome contract in the lab’s name immediately. Evidence that the combined company can deliver it more efficiently comes later, when the bank receives a comparable offer and decides whether to renew.

What I will look for in 2028

At the September 2028 review the smooth path to sales parity with AWS under the 15 per cent assumption reaches $85.718 billion of annual lab revenue. The corresponding Google Cloud path reaches $68.808 billion. A slower opening can be recovered with faster subsequent growth. Record the actual trailing sales for each side, the remaining three years and the new rate required. A lab can fall behind the initial reference and still improve its prospects if it has accumulated customers with demonstrated expansions, lower delivery costs and purchase commitments that convert into recognised revenue on a credible timetable.

For example, suppose the 2028 accounts show the lab at seventy billion dollars and AWS at two hundred billion. Allow AWS another three years at fifteen per cent. Its target is now $304.175 billion. Starting from seventy billion, the lab needs about 63.2 per cent annual growth to reach it. This update asks how much more the lab has to sell from that date onward. The original calculation survives in the historical record, so readers can see which assumptions changed. A board investing against this route can also translate the new target back into accepted volume, prices and support obligations.

I would also follow a bank through its first renewal after twelve months of service. Ask for the accepted volumes and the fee actually realised after rebates. Ask who paid the warehouse bill, how many files reopened and whether the supplier can recover its integration cost at the renewal price. A lab can license a large model to the winner of a contract and collect a useful wholesale fee. That is a less extensive claim on the customer than becoming responsible for the outcome. The supplier’s ability to retain that responsibility after a competing bid should carry weight in any revision to the forecast.

The deciding entry in 2031 will be a dated pair of trailing revenue figures. Report the operating result beside them and name the group that holds the prime contracts behind the growth, wherever the evidence permits. If neither revenue comparison clears, I will record the miss. If one clears and the larger seller still has poorer operating economics, the revenue prediction will have succeeded and the advantage claimed for its business model will remain in dispute. The bank that renews an accepted outcome at a price both parties can live with supplies a more durable reason for expecting the next billion.

Sources and reading notes

  1. 01 · Anthropic final prospectus, 18 November 2026

    Use of proceeds, summary statements, quarterly results, financial statement Note 2 Other Concentrations and commitments. Nine-month statements unaudited. Keep GAAP and pro forma denominators.

  2. 05 · Amazon third-quarter 2026 earnings

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

  3. 06 · Alphabet third-quarter 2026 earnings, SEC exhibit

    Segment table, Google Cloud revenue and profit. Product scope includes more than infrastructure and results include TPU system sales.

  4. 07 · Microsoft FY2026 annual report

    Azure revenue exceeded $100bn for FY to June. Microsoft Cloud has broader scope. Keep threshold separate from exact quarterly series.

  5. 84 · Alphabet, fourth-quarter 2025 results, SEC exhibit

    Quarter to 31 December 2025, segment results in USD millions. Google Cloud revenue 17,664 and operating income 5,313. The other three quarters bring the comparison to September 2026.

  6. 85 · Alphabet, first-quarter 2026 results, SEC exhibit

    Quarter to 31 March 2026, Google Cloud revenue 20,028 and segment operating income 6,598, USD millions.

  7. 86 · Alphabet, second-quarter 2026 results, SEC exhibit

    Quarter to 30 June 2026, Google Cloud revenue 24,768 and segment operating income 8,814, USD millions. Product scope includes sales of TPU systems beginning in this quarter.

  8. 87 · Alphabet, September 2026 Form 10-Q

    Segment note reconciles the first nine months and explains how shared costs and Alphabet-level activities are treated. Google Cloud segment operating income has a different cost boundary from the lab’s consolidated operating result.