Q1 Earnings Drew the Line: AI Capex Is Only Rewarded With Cloud Revenue Attach
The Bifurcation Is Now Priced
Within minutes of each other on April 29, Google, Microsoft, Amazon, and Meta printed Q1 2026, and the market did something it had not done in prior quarters. Google surged 7% to $4.3T market cap, Amazon climbed 3%, Microsoft slipped 2%, and Meta dropped 6.6%. Same quarter and same macro, but four different verdicts from the tape. The differentiator was not growth, or rather not the growth number the narrative crowd wanted to discuss. It was whether the capex had a cloud revenue line attached to it.
Google Cloud grew 63% to $20B on a $1.6B beat, with backlog doubling to $460B. AWS reaccelerated to 28% growth, up four points. Azure grew 40%, up one point, but Microsoft's cloud gross margins compressed 500 basis points to 56%, which management attributed explicitly to GitHub Copilot inference load. Meta raised capex to $145B while Zuckerberg admitted he has "no very precise plan" for the spend. The market drew a bright line.
The Capex Is Debt-Funded Now
Combined 2026 capex guidance hit $725B — up 77% from $410B last year, and BofA projects $175B in hyperscaler debt issuance to fund it. This is no longer a cash-flow story; it is a credit story, which is a different business with a different clock. Amy Hood attributed $25B of Microsoft's spend to memory chip inflation alone, the sort of line-item disclosure a CFO volunteers when she wants the market to understand the spend is not discretionary.
Capex funded by free cash flow is patient capital. Capex funded by debt issuance is capital with a clock. Amazon's TTM FCF collapsed from $25.9B to $1.2B — a 95% decline — while committing $200B to 2026 capex.
The Custom Silicon Crack Widens
Google is now selling TPUs directly to Anthropic and Meta for on-premise installation, which is the first real external commercialization of custom AI silicon, and it is happening in size. Amazon's custom chip business crossed $20B, making it a top-three chip vendor globally. These are not pilot programs, they are structural erosion of Nvidia's cloud GPU pricing power, and that erosion is already showing up in procurement decisions today rather than in some future forecast.
What This Means for Your Book
The market has stopped treating AI capex as automatic terminal-value accretion, and that discipline cascades into private rounds within 1-2 quarters. This is probably wrong in the specifics but right in direction: any portfolio company whose valuation implicitly assumes 40%+ YoY hyperscaler capex growth — GPU cloud names, data center REITs, cooling infrastructure exposure, anything downstream of the buildout thesis — needs a downside model drafted before the next round, not after. The flip side is Microsoft's capacity constraints through 2026, which mean demand spills mechanically to neoclouds like CoreWeave, Lambda, Crusoe, and Applied Digital. Call it a 2-3 quarter tradeable window before Q2 earnings confirm it.
What to do
Re-segment your AI comp table into 'Revenue Earners' (GCP, AWS) vs. 'Capex Spenders' — apply differentiated multiples to every portfolio position by end of next week
Stress-test AI infra portfolio holdings against a 2027 capex growth slowdown to 10% YoY (vs. 77% today) — present to IC within 2 weeks
Build a neocloud capacity spillover watchlist (CoreWeave, Crusoe, Lambda, Applied Digital) and position before Q2 earnings confirm Microsoft demand overflow
Re-underwrite every Nvidia-dependent portfolio company assuming 15-25% TPU/Trainium share shift by 2027