These are support resources. The primary route should still move into launch-market scorecards, Time-to-Power Packs, and Speed-to-Power Watchlist.
Launch-market route
These support tools should push users into the launch-market scorecards and then into the Time-to-Power-Pack or Watchlist route. They are useful, but they are not the hero story of the business.
Priority market
Texas is the strongest launch anchor for speed-to-power screening, with the clearest near-term route into Time-to-Power-Pack-first commercial intent.
Use county and metro scorecards to separate attractive ERCOT narratives from real interconnection, curtailment, and water constraints.
Priority counties
Priority metros
Start with the Texas Time-to-Power Pack, then move into watchlist monitoring.
Priority market
Georgia-Atlanta is a real launch anchor alongside Texas because Atlanta demand gravity is commercially meaningful and the county / metro trust layer is now strong enough to support Time-to-Power-Pack-first intent.
Do not collapse Georgia-Atlanta into one clean story. Fulton, Coweta, Cherokee, and the Atlanta metro still need to be compared directly before assuming the region is equally ready or equally fast.
Priority metros
Treat Georgia-Atlanta as a launch-ready anchor, but earn the Time-to-Power Pack through county and metro comparison before moving into transaction-support diligence.
Priority market
The Carolinas are a real public market, but they work best as an honest beta route where county and metro comparison builds trust before the Time-to-Power Pack carries commercial weight.
Do not present the Carolinas as a fully uniform launch anchor. Metro and object quality can still vary, so public copy should keep confidence limits and beta honesty visible.
Use Carolinas county and metro pages to build trust first, then move into the Time-to-Power Pack or watchlist only after the route is convincing enough for deeper diligence.
Controlled coverage
Ohio-PJM is strategically important because PJM / power / queue relevance makes it commercially meaningful, but the public story should stay explicit about where authority is mixed and where confidence is still earned page by page.
Do not present Ohio-PJM as more authoritative than the current evidence warrants. Keep mixed-authority power caveats visible and avoid implying that public relevance equals uniform execution certainty.
Routes to Product A
Assess grid capacity, interconnection timelines, and power feasibility for AI deployments.
Routes to Product A
Evaluate water stress and cooling constraints for target metros.
Routes to Product A
Score latency, fiber, and IXP readiness for inference-heavy deployments.
Routes to Product B
Compare cloud vs buy vs lease economics and move into benchmark pricing.
Routes to Product B
Model residual value and underwriting assumptions before procurement commitments.
Routes to Product A
Estimate energization probability by ISO and queue friction.
Routes to Product A
Advanced finance workflow support for internal diligence and exports.
Routes to Product A
Model behind-the-meter pathways and route decisions back to readiness monitoring.
Explore More
Site-level investment attractiveness scoring
Open Speed-to-Power WatchlistCalculate GPU depreciation and residual values
Open Speed-to-Power Watchlist