---
title: "Issue archive"
canonical: "https://anchor.is/groundbreak/issues"
publication: "Groundbreak"
publisher: "Groundbreak"
language: "en-US"
guide: "https://anchor.is/groundbreak/llms.txt"
issues: 7
---

# Groundbreak

> Groundbreak exists to close the intelligence gap that costs tier-3 American cities manufacturing deals they are structurally positioned to win. The reshoring wave is delivering hundreds of thousands of industrial jobs back to domestic soil, but the analysis helping cities compete for that investment has been written for tier-1 metros, site selection consultants, and corporate real estate teams. Groundbreak is built for the practitioners at the other end: economic development directors in mid-sized cities who have the land, the workforce, and the infrastructure, but not the market intelligence to know which industries are looking for exactly what they have. The publication is a subscription intelligence product. Success is not measured one reader at a time — it is measured in aggregate deal flow: a national readership of ED teams, each using the publication to build a sharper sector target list, collectively closing a disproportionate share of the manufacturing deals that tier-3 markets can win.

[Read on the website](<https://anchor.is/groundbreak/issues>)

## Issue archive

- [Issue 7](<https://anchor.is/groundbreak/issue/7/markdown>) — Published 2026-08-31: We started this issue by reconstructing a deal in Gadsden, Alabama: a $430 million automotive components campus, rising on ground that was a Superfund steel site when EPA began cleanup in 2007. Nearly two decades of environmental work before private capital arrived. That timeline forced a question we couldn't set aside. If proof expires and your team can only keep a few site uncertainties current, which ones do you retire first? Most of what follows is our framework for making that call.

- [Issue 6](<https://anchor.is/groundbreak/issue/6/markdown>) — Published 2026-08-24: Somewhere in every site selector conversation, the workforce question comes up. The usual tier-3 answer is "strong workforce, great community college, good work ethic." We built this issue around what happens next: that answer fails first-cut screening. The consultant needs occupation counts within a commute radius, wage data by SOC code, a training pipeline with scheduled seats and a completion date. That gap runs deeper than workforce. Cities are pledging GO bonds for spec buildings without a base rate for occupancy outcomes. Deal terms announced two years ago look different now that public records have caught up. The pattern is the same everywhere we looked: real commitments made against standards nobody has written down.

- [Issue 5](<https://anchor.is/groundbreak/issue/5/markdown>) — Published 2026-08-17: Great Falls, Montana won an $800 million aerospace campus. We expected to find a city that was shovel-ready. What we found was a city that could prove, stage by stage, how far along it actually was. Those aren't the same thing. A transformer plant in Weirton had the building, the workforce, the steel, and public support, and still collapsed because one critical element was missing. Knowing where you stand means knowing what's absent. This issue is built around that discipline: from how you finance a spec building to what you do with the deals you lost and stopped thinking about.

- [Issue 4](<https://anchor.is/groundbreak/issue/4/markdown>) — Published 2026-08-10: We built this issue around a test most cities haven't run: pick a specific project type, list what it actually requires, and find where your answers break. Great Falls just landed an $830M aerospace campus. The commission packet shows a city that hadn't solved everything. It had documented what was ready, flagged what wasn't, and authorized a structure around both. That's what kept surfacing across every piece we wrote. The question worth sitting with before you read any of them: when a selector calls Tuesday, can you show your work?

- [Issue 3](<https://anchor.is/groundbreak/issue/3/markdown>) — Published 2026-08-03: We spent this issue trying to verify things that should be verifiable. Form Energy's battery plant in Weirton is operating, shipping product, 400 people on site. We still can't trace $110 million of the $290 million state incentive package through public records. A third of the headline number, for a plant that already works. That gap should change how you read every competitor deal announcement that crosses your desk. It changed how we wrote the rest of this issue: decomposing incentive instruments, grading site answers by what's actually been proved, asking when a training center becomes a workforce pipeline. Start with the Weirton piece.

- [Issue 2](<https://anchor.is/groundbreak/issue/2/markdown>) — Published 2026-07-27: We kept hitting the same wall across this issue. Rome, Georgia just committed $3.5M to run water to an industrial park. The sewer waits for a named prospect. That tells Rome which manufacturers it can pitch to now and which it can't, and it's a sharper position than most cities hold, because most haven't asked the question underneath. The utility, the treatment plant, the community college, the landowner: each controls a piece of what a site selector needs, and none of them report to you. Getting their answers on paper before the RFI arrives is the whole game.

- [Issue 1](<https://anchor.is/groundbreak/issue/1/markdown>) — Published 2026-07-20: We spent this issue on a problem that sounds administrative and isn't. A site selector asks what your wastewater system can handle, and you probably know the answer. The trouble is you haven't been cleared to say it. Your utility hasn't agreed on what's public. Your treatment plant hasn't put a review timeline in writing. So you go vague. Sixty-one percent of site selectors use utility capacity as an elimination screen, and a vague answer reads the same as no answer. Everything in here is about closing that gap before the question arrives.

## More

- [Publication guide](<https://anchor.is/groundbreak/llms.txt>)
- [Issue archive](<https://anchor.is/groundbreak/issues/markdown>)
