Competitive Brief: Call Sheet
Researched: AWS · for Google Cloud reps
Focus: AI/ML infrastructure
Today's angle
Amazon raised its 2026 capital-expenditure guidance to $220B (up from the ~$200B it had held since February), blaming higher memory prices, on its July 30, 2026 Q2 earnings call. Even at $220B, Jassy said AWS still will not have enough capacity to meet all its 2026 demand and expects the same shortfall in 2027. Q2 capex alone hit $54.2B, and free cash flow flipped to a $7.6B outflow.
Top 3 plays
PLAY 01
We win the largest-scale training and inference workloads on silicon depth.
For AI-native startups, frontier labs and research-heavy enterprises, Google's 8th-gen TPUs (8t/8i) and single-fabric scale to 1M+ chips are a genuine moat: customers run on the same hardware that trains Gemini. AWS Trainium is competitive on cost-per-token but supply-locked and scales across multiple clusters, not one fabric.
"You can run on the exact infrastructure that trains Gemini (one fabric, a million-plus chips) and you can actually get the capacity, today."
PLAY 02
External capital is validating TPU demand, not just Google's own books.
On May 19, 2026, Blackstone committed $5B to a Google-backed venture to sell TPU capacity as a service, targeting 500MW by 2027. A third party betting billions on TPU (not Nvidia) compute is independent proof that TPU price-performance is credible at enterprise scale. AWS has no comparable outside vote of confidence in Trainium.
"Blackstone just put $5 billion behind TPU capacity. Outside money proves the silicon delivers."
PLAY 03
We just closed our biggest historical gap: enterprise delivery muscle.
On June 4, 2026, IBM and Google Cloud launched a joint practice putting thousands of IBM consultants behind industry-specific AI agents (banking, healthcare, telecom, government) on Gemini Enterprise. For regulated buyers who once rejected Google for thin systems-integrator support, there's now a credentialed delivery partner.
"Worried about delivery depth? You now get IBM's consultants building your agents on Google's stack. That's a combination AWS can't simply match."
Objection handling
"Google Cloud had that massive 2025 outage. Why trust critical AI to them?"
Counter: Don't minimize it: acknowledge, point to the concrete process changes and pivot the reliability conversation to forward architecture, not past incidents.
"Google kills products. You just retired Vertex AI. Why bet our ML platform on that?"
Counter: Convert the deprecation fear into contractual commitments rather than denying the pattern; that's what earns credibility.
"Even Pichai says Google Cloud is compute-constrained. We'll be stuck in a queue."
Counter: Turn the constraint into proof of demand, and lock in committed capacity now, because AWS is just as supply-limited.
"We want Claude, and that means AWS Bedrock."
Counter: Neutralize the "Claude = AWS" reflex early; make the conversation about which infrastructure runs Claude best, not which cloud has it.
"AWS is the market leader. That's the safe pick."
Counter: Concede the current-share point, then redirect to a 3 to 5 year trajectory framing where the growth gap and AI differentiation favor Google.
Agent Scout · every claim verified against its source · 51 claims tracked