Data-center developments increasingly arrive with headline investment figures large enough to reshape the economic conversation in a small city.
A proposed $200 million investment sounds transformative.
But what does that number tell a city manager, finance director, lender, council member, or taxpayer?
Surprisingly little about the municipality's eventual financial position.
It tells us something about the developer's anticipated capital expenditure. It does not establish the project's taxable value, recurring city revenue, infrastructure obligations, public-service costs, or long-term net benefit.
These are separate financial questions, and they should be modeled separately.
Start with the public balance sheet, not the developer's project budget.
A credible fiscal analysis needs to identify the actual revenue mechanisms.
Property taxes require estimates of taxable real and personal property, valuation timing, exemptions, depreciation, applicable levy limitations, and allocation among taxing districts.
Electrical utility-related revenue depends on the provider, actual power consumption, applicable tax provisions, and the legal treatment of the resulting receipts.
Other revenues may depend on negotiated agreements, development charges, permits, or other legally authorized mechanisms. Their enforceability and allocation matter as much as their nominal amount.
On the cost side, the city must examine potential infrastructure contributions, emergency services, water and wastewater capacity, road maintenance, administrative obligations, environmental monitoring, and financial exposure if assumptions fail.
The resulting question is straightforward:
What recurring, legally available net cash flow does the project create for each affected public entity?
A countywide tax benefit should not be reported as revenue to the host city's General Fund. Revenue dedicated to one purpose should not be treated as freely available for another.
And a utility upgrade funded entirely by a private developer should not be counted as a public subsidy simply because it is expensive. Equally, a developer-funded upgrade should not be credited as a broad public benefit unless others can demonstrably use or benefit from it.
Separate five types of economic value.
We find it useful to distinguish the project's direct financial contribution from its wider economic effects.
Construction activity generates temporary contracting demand, wages, purchases, and potentially local spending. Its duration, local participation, and leakage outside the region must be considered.
Permanent operations can produce employment, recurring purchases, property values, and ongoing tax activity. These should be modeled separately from construction.
Municipal fiscal effects capture the revenues and expenses attributable to the development, at the individual-fund level.
Infrastructure effects examine whether power, fiber, roads, and related systems become more capable or reliable for other users.
Future development opportunities involve the option for additional enterprises to locate or expand because infrastructure and operating conditions have improved.
The fifth category can be strategically significant, but it should not be treated as guaranteed revenue. A manufacturing facility that might become feasible because of a power upgrade is not an employer until someone funds, builds, and operates it.
Use scenario analysis instead of single-point forecasts.
KSIG's preferred approach is to model a base case and multiple sensitivities, not present one optimistic number as the answer.
For a proposed data center, sensitivity variables may include assessed value, depreciation, power utilization, revenue allocation, operating costs, utility demand charges, taxes and exemptions, the timing of construction, and major capital improvements.
We would also distinguish between costs borne by the city, costs borne by utilities, and costs borne by private parties.
An effective comparison examines the proposed site against feasible alternatives and the realistic no-project case.
That last comparison matters.
If the land could support another productive use, a data center's fiscal benefit cannot be evaluated in isolation. Its incremental contribution should be compared with the next credible alternative, not an assumption that the property would otherwise remain economically dormant forever.
Attribution is especially important when evaluating incentives.
Washington's 2026 Joint Legislative Audit and Review Committee examination of urban data-center tax preferences illustrates the challenge.
The review identified additional assessed value and property-tax payments associated with facilities benefiting from the preference. It also found that no new urban data centers were built using that preference and that the extent to which investments occurred because of the incentive could not be determined.
That distinction matters in any investment analysis.
Economic activity following an incentive is not necessarily economic activity caused by the incentive.
Incentives should be evaluated against incremental outcomes that would not otherwise have occurred.
Infrastructure value requires operational evidence.
A proposed data center might justify significant electrical or telecommunications investment.
But a CFO cannot simply capitalize a narrative about infrastructure benefits.
The analysis needs to establish ownership, availability, capacity, contractual rights, timing, maintenance obligations, operating cost allocation, and who actually receives the benefit.
If additional capacity could make future industrial development possible, that opportunity may deserve strategic value.
It should be reported separately from contracted revenue and existing cash flow.
This is the difference between identifying potential economic upside and recognizing it as a realized financial asset.
From fiscal impact to financial resilience
For municipalities facing financial pressure, new recurring revenues can improve fiscal capacity.
But fiscal capacity is not identical to the ability to service a particular obligation.
Debt repayment requires analysis of legal restrictions, fund balances, operating requirements, revenue reliability, and the contractual or court-supervised structure governing payments.
The same principle applies in business.
Cash flow is not simply what the income statement says was earned. It is what remains available, when it is needed, after necessary obligations have been met.
Our work at KSIG Advisors focuses on that discipline: turning financial information, operating realities, and capital requirements into decisions that stand up to scrutiny.
Major data-center investments deserve no less.
The strongest economic-development case is not the one with the largest announced capital budget.
It is the one with the most credible, durable, and independently verifiable net public benefit.
Research foundation
This financial-evaluation framework draws on independent research developed through WeHeartCleElumRoslyn (WHCER) and two complementary books.
Charles L. Marohn Jr.’s Strong Towns: A Bottom-Up Revolution to Rebuild American Prosperity sharpens the fiscal test: compare durable public value with the full lifecycle cost of the infrastructure and services required to support it.
Susan Crawford’s Fiber: The Coming Tech Revolution—and Why America Might Miss It sharpens the connectivity test: fiber creates broader economic capacity only when ownership, competition, last-mile service, and access allow others to benefit.
These books provide interpretive frameworks. They do not establish project-specific tax receipts, employment, infrastructure obligations, or local fiber buildout.
Related independent research: Cle Elum Data Center Analysis · Washington JLARC Data Center Tax Review
This article presents a financial-evaluation framework, not an audit, valuation, municipal forecast, or endorsement of a specific development.