Missouri governor and Google announce $15 billion data center in Montgomery County

Google announced a $15 billion investment in a data center in Montgomery County, Missouri, with the company set to pay for power and infrastructure costs. The project is positioned to support more than 2,300 construction workers over the next two years and is expected to create nine additional community jobs for every direct job at the center. The announcement comes amid ongoing local opposition and litigation related to separate Amazon Web Services data center projects in the county.

Analysis

The bigger signal is not the headline capex itself but the acceleration of grid buildout economics in the Midwest. Google’s willingness to absorb power and infrastructure costs lowers the probability that this is a stranded-site story, which should support local utilities, transmission contractors, and equipment suppliers before it translates into visible revenue. The second-order winner is the labor and electrical supply chain: a multi-year data-center backlog tightens skilled trades availability, which can push margins for contractors with Midwest exposure while raising costs and delays for less-preferred peers.

For GOOGL, this is incrementally positive because it strengthens the hyperscaler race narrative without materially changing near-term earnings. The investment is large enough to reinforce capacity discipline, but the real economic payoff comes if it helps secure load growth in a region with cheaper land and potentially better permitting than coastal alternatives. Over 12-24 months, that can improve AI infrastructure optionality and reduce the risk that compute expansion becomes a bottleneck in the company’s cloud monetization story.

AMZN faces a more nuanced setup: not direct competitive damage from this project, but a relative perception hit if it remains the company most associated with contentious local data-center expansion. That matters because political friction can slow timelines, increase mitigation costs, and create a higher reputational hurdle in future siting battles. The lawsuit and local backlash are the near-term catalyst; the risk is that this turns into a pattern of permitting delays across secondary markets rather than a one-off county issue.

The contrarian read is that the market may underappreciate how quickly these projects convert into non-tech beneficiaries while overfocusing on the headline beneficiary. If data-center proliferation keeps scaling, the scarce assets are power delivery, transformers, switchgear, and electricians—not the hyperscalers announcing capex. That creates a cleaner risk/reward in the picks-and-shovels trade than in chasing incremental upside in GOOGL after a already-sizeable capex commitment.

Key Decisions for Investors

• Long GOOGL vs. short AMZN as a 1-3 month relative-value pair: thesis is that GOOGL gets the cleaner political/operational read-through while AMZN carries more siting/friction overhang; target 3-5% spread capture, stop if AMZN resolves litigation cleanly.
• Long power-infrastructure beneficiaries for 6-12 months via ETN/EME/PWR: data-center load growth should tighten demand for electrical contractors and grid buildout names; expect better revenue visibility and multiple support versus software/hyperscalers.
• Buy LEAPS on grid equipment suppliers such as NVT or HUBB on weakness: the market typically underprices multi-year data-center demand inflections, and these names have cleaner leverage to capex intensity than the hyperscalers themselves.
• Avoid chasing GOOGL upside on this headline alone; use any post-news dip to reassess instead of adding aggressively. The event is supportive but not earnings-revising in the next 1-2 quarters, so upside is likely more duration than immediate multiple expansion.
• Watch AMZN into the June 1 legal milestone; if injunction risk rises, consider a short-dated put spread to express delay risk with defined premium outlay.