<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Joe Hoffman on Medium]]></title>
        <description><![CDATA[Stories by Joe Hoffman on Medium]]></description>
        <link>https://medium.com/@josephahoffman?source=rss-3f01b885d212------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_qI-aJUGp43NkSR5.jpeg</url>
            <title>Stories by Joe Hoffman on Medium</title>
            <link>https://medium.com/@josephahoffman?source=rss-3f01b885d212------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:52:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@josephahoffman/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Bill Comes Due on Data Center Tax Breaks]]></title>
            <link>https://josephahoffman.medium.com/the-bill-comes-due-on-data-center-tax-breaks-3b52912fa2ce?source=rss-3f01b885d212------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b52912fa2ce</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[data-center]]></category>
            <category><![CDATA[policy]]></category>
            <category><![CDATA[taxes]]></category>
            <dc:creator><![CDATA[Joe Hoffman]]></dc:creator>
            <pubDate>Sat, 18 Apr 2026 14:39:10 GMT</pubDate>
            <atom:updated>2026-04-18T14:39:10.295Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ogqwf8-JsYYrSppOR5Vjw.jpeg" /><figcaption>Image generated in Google AI Studio</figcaption></figure><p><strong>AI Disclosure:</strong> This essay is AI assisted.</p><p>In Independence, Missouri, residents filed a lawsuit seeking a referendum against their own city. The complaint names the $6 billion twenty-year tax break that the city council approved for a $150 billion AI data center project. The plaintiffs are neighbors suing their commissioners over a deal made in their name. However, the judge ruled city-approved tax breaks are not eligible for the public referendum process.</p><p>That is what the end of a bad deal looks like at the local level.</p><p>Independence is not an isolated case. In March 2026, the Virginia Senate voted to end an annual $1.6 billion tax break for data centers. The vote paralyzed the state budget and pushed Virginia toward a special session. One senator noted the opposition evolved from NIMBY to BANANA (Build Absolutely Nothing Anywhere Near Anything).</p><p>Georgia’s Senate voted to claw back its own breaks. The full legislature then reversed course and left them intact, punting the fight to another session. Oregon adopted a moratorium on new deals. Washington came close to eliminating its exemption. In Brazoria County, Texas, commissioners rejected a $3 billion AI project’s tax break outright, one of the first major local rejections in the country.</p><p>These cases form a pattern of barely scrutinized tax deals coming due all at once. The reckoning is not polite. In Virginia, the exemption fight quickly became a fight about who had been paying for the buildout. Electric ratepayers had watched their bills rise. Localities had surrendered the property tax base. Legislators realized the exemption was eating a revenue line they had assumed was bottomless.</p><p>The pattern is familiar once you see it. Deals were sold on projections that nobody stress-tested. In Ohio, data center tax breaks contributed to energy demand and inflated residential electric bills to pay the infrastructure costs. West Virginia structured its agreements so poorly that the state, by one analysis, “could get nothing in taxes” from the data centers operating there. Nevada residents received “few details” about exemptions for their data centers. Lack of transparency makes accountability impossible after the fact. Did anyone do the math for Georgia when it granted billions in sales tax breaks?</p><p>Likewise, long-term job numbers may not survive scrutiny. A single Ohio exemption worth $4.5 million covered ten full-time positions. A $2.4 billion South Carolina project was projected to generate twenty permanent jobs. Construction can employ hundreds, while operating does not. Data centers are designed for efficiency, employing little operating staff. It also makes the case for large per-project tax breaks so difficult to defend.</p><p>The lobbying pressure behind these deals is global. India is offering zero taxes through 2047 to attract AI infrastructure. Singapore launched a new package of AI tax measures in 2026. Developers threaten American legislators with this warning: approve the tax breaks or else investments go elsewhere. It is the last argument used before a bad deal, but what is it worth if there is little added value for the community, and utility customers shoulder the burden?</p><p>How do many communities avoid the short end of a sharp stick?</p><p>Part of the answer lies in the deals that work. Minnesota requires data center companies to meet climate and water preservation standards as a condition of qualifying for tax breaks. The subsidy depends on community protection and not just investment size. Henrico County, Virginia, uses its $60 million data center tax revenue to fund affordable housing, gaining community benefits from an industry it already welcomes. These outcomes require writing the conditions into agreements.</p><p>The good deal, bad deal differences are boring and specific. A sunset clause sets a hard expiration on the break, forcing a review rather than letting the subsidy evolve into a permanent policy. A clawback provision requires the company to return the benefit if it fails to hit investment or hiring targets. Utility cost protections keep the company from offloading its own transmission upgrades onto the grid. The absence of a confidentiality clause means the officials can discuss terms with their constituents. These are ordinary contract terms and make the difference between an incentive and a transfer of public value to a private interest.</p><p>Earlier this year, the South Dakota legislature was asked to approve a fifty-year sales tax exemption for data centers. The proposal failed, but the fact that anyone put it forward seriously shows how far the ask had drifted. A tax break that outlives the careers of every official who votes on it is not an incentive but a permanent transfer. They might as well ask for a perpetuity.</p><p>Organizations like Good Jobs First and the Institute on Taxation and Economic Policy track these agreements nationally, pulling the terms with public records requests. The questions any official should be able to answer before signing are short. What is the sunset date? What are the permanent job benchmarks, and what happens if the project misses them? Who pays for the transmission upgrades? Can you discuss the terms publicly, or did you sign something that seals your lips?</p><p>In Independence, the residents have started asking those questions in court. Communities that didn’t ask them before signing are finding out what a bad deal costs on the back end. The bill always comes due, but the question is who pays it.</p><p><strong>AI Use:</strong> This essay uses notes tagged and organized in an Obsidian vault that were created from public sources and local news accounts. Selected notes were surfaced with Obsidian Bases, and AI assistance was used to develop an outline and candidate pieces. Final editing is my own, and and touched up using Grammarly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b52912fa2ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>