The Cedar Rapids Playbook

Last week's issue named a pattern. This week we're going to take it apart.

Issue #17 introduced what's emerging as the "third path" in the data center industry, the structured, transparent, enforceable agreements being negotiated between developers and host communities. We pointed to Cedar Rapids, DeKalb, San Jose, Lancaster, and El Paso as places where this model is already working.

That was the concept. This issue is the manual.

Because if you're a developer trying to reduce entitlement risk, a municipal official trying to negotiate from strength, a contractor wondering where the durable opportunities sit, or a community organizer trying to understand what a "good deal" actually looks like, you need more than a concept.

You need the contract terms. The dollar figures. The performance metrics. The penalties. The trade-offs. The lessons.

Cedar Rapids, Iowa has signed two of the most detailed data center development agreements in the country, one with Google for a $576 million facility, one with QTS for a project estimated at $1.75 billion. Both went through full city council approval. Both are public. Both contain specific terms that other communities and developers can model.

This is the breakdown.

Before we get into the agreements, the setup matters.

Cedar Rapids isn't a major data center market. It's a city of about 137,000 people in eastern Iowa. The mayor, Tiffany O'Donnell, is a Republican in a region that hasn't historically attracted hyperscale infrastructure. The economic development apparatus is built around manufacturing, agriculture processing, and insurance, not technology.

What Cedar Rapids has:

The city manager, Jeff Pomeranz, came to Cedar Rapids from West Des Moines, where he had directly overseen Microsoft's expansion. He arrived knowing what data center development could do for a mid-size city, and what mistakes he didn't want to repeat.

That context is critical. The Cedar Rapids playbook didn't emerge from theoretical best practices. It emerged from a city manager who had operated the West Des Moines/Microsoft model and wanted to negotiate the next version from a stronger position.

In March 2024, the Iowa Economic Development Authority Board approved the city of Cedar Rapids' plan to grant $56 million in local property tax exemptions over 20 years for a proposed Google data center.

This is the public structure of that agreement:

The investment:

The tax structure:

The employment requirement:

The community benefit:

The construction commitment:

The strategic positioning: This is roughly half the deal that QTS would sign in 2025. Smaller community contribution. Lower employment threshold. Less aggressive long-term structure. But the Google deal established the framework, Cedar Rapids would not approve data centers without community contribution components and meaningful employment requirements.

The estimated 20-year property tax revenue from the Google site alone, even with the 70% abatement: roughly $58 million in net city tax revenue, plus the $6 million in Community Betterment Fund contributions, plus 31+ permanent jobs at family-supporting wages, plus 1,200+ construction jobs over the build cycle.

Cedar Rapids took the deal. But it negotiated terms that would set the precedent for what came next.

The QTS agreement is where Cedar Rapids actually made history.

The Cedar Rapids City Council approved the original QTS development agreement on January 28, 2025. The deal was then amended and re-approved by unanimous council vote in December 2025, with the amendments capping the project at seven phases and adding "related property owners" to the agreement structure.

The numbers, as they stand today:

The investment:

The build structure:

The tax structure:

The employment requirement:

The community benefit:

The infrastructure cost-sharing:

The environmental commitment:

Combined with the Google deal, the two projects will occupy most of the 1,391-acre Big Cedar Industrial Center. The total combined investment will likely exceed $2.3 billion. The combined Community Betterment Fund contribution alone will be roughly $24 million over the agreements' lifetimes.

This is the part that other communities are watching most closely. Because if the fund is just a discretionary pile of money the city controls, it doesn't really change anything, local elected officials always control discretionary spending.

The fund's structure matters:

Governance:

Permitted uses (per published agreement terms):

Enforcement:

Critically: NO non-disclosure provisions.

The Cedar Rapids agreements are fully public documents. Council deliberations were held in open session. Press coverage was extensive. There was no shell company involvement at the time of approval, Google was identified as Google, QTS was identified as QTS. The Heaviside LLC and QTS Cedar Rapids LLC corporate entities are normal real estate structures, not concealment mechanisms.

This is the single most important departure from what we documented in Issue #17. The Wisconsin, Michigan, Minnesota, Arkansas, and Arizona deals were structured around concealment. The Cedar Rapids deals are structured around disclosure.

The trade-off Cedar Rapids accepted: less negotiating leverage during the courting phase (other cities offer NDAs that allow tech companies to evaluate sites in secret), more durable political support after the deal is signed.

The Community Betterment Fund payments started flowing in 2025 following the first phase milestones. Some of what's already been done:

The most recent Maxfield Research housing study commissioned by the city found that the construction workforce influx is now affecting Cedar Rapids' rental housing market. From that study: "If no new additional apartments are constructed to serve local long-term demand, there will definitely be a rental housing shortage during the short-term."

This is a real cost to Cedar Rapids residents. Construction-driven housing pressure is a recognized externality of large industrial projects. The city is now using a portion of the early Community Betterment Fund discussions to consider housing investment, which would create a direct loop where data center money funds housing for the workers building the data centers.

This is precisely the kind of dynamic the CBA structure is supposed to enable. The fund exists specifically to address externalities. The City Council can allocate it where the impacts actually show up.

This isn't a love letter to Cedar Rapids. The deals have real problems that other communities should understand before copying the structure.

The job numbers are small. City Manager Pomeranz acknowledged this directly at the January 2025 council meeting, calling 15 jobs per phase "a relatively small number." The Google deal's 31 permanent positions and the QTS deal's 15-30 positions per phase are genuinely modest compared to the size of the public investment. A $58 million property tax abatement for Google produces fewer than 32 permanent jobs, roughly $1.8 million in tax revenue forgone per permanent job created. That's a high cost-per-job ratio by any measure.

The construction job benefit is temporary. The 5,000+ construction workers on the combined sites will leave when construction ends. The permanent operations workforce is small enough that the long-term local economic impact is mostly from property taxes and Community Betterment Fund contributions, not employment.

Energy demand is real and growing. Energy advocates have raised concerns about Alliant Energy's grid capacity and the implications for residential ratepayers. The data centers will draw significantly more power than typical commercial users. While Alliant has committed to using renewable sources, the marginal demand still affects grid economics for everyone connected to Alliant's system.

The 70% abatement is generous. Mayor O'Donnell defended the structure publicly: "If Cedar Rapids doesn't compete, we lose. We lose the jobs, we lose the investment, we lose the growth and let me be clear, I don't believe we can sit on the sidelines and watch others reap all of these benefits." That's a defensible position. It's also true that 70% is at the high end of what other cities have offered, and Iowa's data center incentive structure is genuinely competitive for developers.

Property tax reform looms. Council member Ashley Vanorny noted during the January 2025 approval that Iowa Legislature property tax reform discussions create uncertainty about future revenue projections. If the Iowa Legislature reduces commercial property tax bases over the next 20 years, the math on Cedar Rapids' net revenue from these projects could deteriorate.

The CBA structure is voluntary, not statutory. Cedar Rapids could have demanded more. Some critics argue it should have. The CBA model only works if cities have the political will to negotiate from strength, and not every city has Pomeranz's experience or O'Donnell's positioning.

These are real critiques. They don't invalidate the model. But they should temper any assumption that the Cedar Rapids playbook is automatically transferable to every community.

If you're a municipal official, economic development director, or city manager looking at the Cedar Rapids structure as a model, here's what actually transfers:

1. Insist on disclosure. No NDAs with shell companies before zoning approval. If a developer won't tell you who they actually are before they ask you to approve their project, walk away. Cedar Rapids did this and still attracted Google and QTS. The "NDAs are mandatory" claim is a negotiating tactic, not a market reality.

2. Tie incentives to performance. Cedar Rapids' tax abatements are conditional on employment thresholds. If Google fails to hit 31 jobs at the right wage rate, the abatement doesn't apply. This is the single most important structural feature. Unconditional tax breaks transfer all the risk to the city. Conditional abatements share it.

3. Build the community fund into the development agreement, not as a side promise. Cedar Rapids made the Community Betterment Fund contributions a contractual obligation, not a voluntary commitment. The dollar figures and payment schedules are in the agreement itself. That makes them enforceable in ways that handshake commitments aren't.

4. Cap the abatement period. 20 years is a long time. Cedar Rapids capped it. Some communities have offered indefinite or 30-year abatements. The longer the period, the more the city is essentially signing away future revenue without knowing what future conditions will be.

5. Phase the agreement. The QTS deal's seven-phase structure means each new building requires meeting milestones from the previous one. If QTS fails to hit benchmarks, the next phase doesn't get the same incentives. This creates ongoing leverage for the city.

6. Require water-free cooling where possible. This is the single biggest local environmental concession Cedar Rapids extracted. Water consumption is the most politically charged data center issue in most communities. Negotiating it into the agreement removes the issue from the political fight.

7. Get the contracts public and the council deliberations open. The political support Cedar Rapids enjoys for these projects exists precisely because the terms are visible. When residents complain about specific provisions, the city can point to them. When developers ask for changes, those have to happen in public.

8. Have an experienced city manager. This may sound obvious, but it's the under-discussed factor. Pomeranz had directly negotiated with Microsoft in West Des Moines. He knew what the developers would and wouldn't accept. Most cities approaching their first data center deal don't have that experience. They should hire it, or insist on extensive pre-negotiation consultation with cities that have.

If you're a developer studying Cedar Rapids:

1. Disclosure isn't fatal. Both Google and QTS were publicly identified throughout the entitlement process. They still got the deals. The NDA strategy may be expedient, but it isn't necessary. Cities are increasingly willing to walk away from secret deals, but they're not walking away from transparent ones.

2. Community Betterment Fund contributions are cheap insurance. $24 million across the combined deals sounds like a lot. Spread over 20 years and divided by the total project investment ($2.3 billion+), it's roughly 1% of the project value. That's cheaper than a single zoning lawsuit, let alone a project killed by community opposition.

3. Conditional abatements aren't a deal-killer. Both Google and QTS accepted performance-tied tax structures. The market will accept these terms. The market is already accepting these terms.

4. Water-free cooling is the easiest political win. If your project uses water-free cooling, say so. Loudly. Frequently. Build it into the public communications from day one. It removes the single most common source of community opposition.

5. Local construction job emphasis matters. Cedar Rapids' construction workforce is substantial and visible. That's a political asset. Developers who hire locally, or at least visibly support local construction, earn community goodwill that pays dividends.

6. Phased deals build relationships. The QTS amendment process in December 2025, where the city and developer renegotiated to clarify corporate structure, demonstrates that an ongoing working relationship enables future flexibility. Deals structured as single transactions don't have that built-in mechanism for evolution.

Issue #17 named the brokerage layer between developers and communities as the most under-served professional services market in this industry. Cedar Rapids demonstrates what that work actually looks like.

The professional roles that made the Cedar Rapids deals possible:

That ecosystem doesn't fully exist in most American cities. Building it, or being it, is one of the most concrete opportunities in this entire industry.

If you can help a municipality negotiate the next Cedar Rapids deal, you have a service offering most cities don't currently know they need but will pay for once they understand what's at stake. The fees on this kind of work are not small. A typical hyperscale CBA negotiation can generate $200,000-$1 million in advisory fees alone for the right team. Add ongoing compliance monitoring across the 20-year contract life, and you're looking at a recurring revenue stream measured in millions per project.

This is the brokering business, made tangible.

Virginia. Today, May 22, is Governor Spanberger's deadline to act on remaining bills. The data center tax exemption fight remains unresolved at this hour. House Speaker Don Scott said yesterday a budget deal could be reached by June. Senate President Pro Tempore Louise Lucas continues to refuse a budget that includes the $1.9 billion annual data center tax exemption. The legislature must finalize a budget by June 30 to avoid a state government shutdown.

The data center industry's potential compromise: tying the exemption to clean energy requirements. Spanberger has also floated a "consumption tax" on data centers' heavy energy use as an alternative to ending the exemption outright. Neither approach has secured agreement.

In a moment that captured the political dynamics: while Spanberger was in Roanoke on April 27 signing bipartisan workforce bills at her hundred-day mark, a group of Botetourt County residents drove over to confront her directly about the data center sales tax exemption. The opposition is now organized enough to travel for these confrontations.

Maine. No override of the Mills veto. Legislature is reportedly drafting modified legislation for the next session.

Ohio. Statewide ballot signature gathering continues. Advocates report continued strong volunteer recruitment but face the July 1 deadline tight.

Wisconsin. The Senate NDA-disclosure bill remains stalled. A compromise version that would require 60-day disclosure of operator identity post-signature continues to be discussed.

Federal. Landsman's H.R. 8033 (No Harm Data Center Act) remains in committee.

This Week / Imminent:

Coming Up:

The third path is no longer hypothetical. It's documented. It's enforceable. It's working in at least one mid-size American city, and the underlying agreements are public records that any other community can read, copy, and improve.

The Cedar Rapids playbook doesn't solve every data center problem. The jobs are still modest relative to the public investment. The energy demand is still significant. The construction-phase impacts on housing and infrastructure are real. But the structure changes who carries the risk, who controls the outcomes, and who benefits from the upside.

For developers: Cedar Rapids proves you can build successful hyperscale projects without NDAs, shell companies, and adversarial community relations. The market will accept transparent, structured agreements. The market is, increasingly, demanding them.

For communities: Cedar Rapids proves you can negotiate from strength even if you're not a Tier 1 data center market. The developers will sign performance-tied incentives, contribute to community funds, and accept water-free cooling commitments. You have more leverage than the incumbents have led you to believe.

For brokers, attorneys, consultants, and engineers: this is your market. Most cities don't currently have the expertise to negotiate a Cedar Rapids-style deal. The ones that do are quietly establishing themselves as the professional infrastructure that resolves the entire industry's political crisis.

The Wisconsin NDA disclosure debates. The Michigan transparency fights. The Ohio ballot measure. The Maine moratorium. The Virginia budget standoff. All of it traces back to the same underlying problem: most data center deals haven't been structured the way Cedar Rapids structured them.

If they had been, this wouldn't be a fight. It would be a partnership.

Cedar Rapids is the proof of concept. The rest of the country is still catching up.

The DC Pipeline tracks data center construction, policy, and market intelligence across North America. New issues every week.

Have a tip? Hit reply.

Know someone who should be reading this? Forward it. They can subscribe at thedcpipeline.com.