economic development
When Does Private Infrastructure Become a Public Obligation?
A business needs electricity.
A factory needs roads.
A data center needs transmission capacity.
A development needs water.
A corporation needs workers who can afford to live nearby.
At small scale, these requirements look like ordinary costs of doing business.
At sufficient scale, something changes.
The private requirement begins colliding with systems that communities already share.
Then a difficult question appears:
When does private infrastructure become a public obligation?
There is no universal line.
But understanding how that line moves reveals a great deal about power, incentives, and modern economic development.
Private Need and Public Need Are Not the Same Thing
Start with a simple distinction.
A company can need something without the public needing to provide it.
If a restaurant needs a larger refrigerator, that is normally the restaurant’s problem.
If a factory needs specialized machinery, the factory buys it.
If a data center needs servers, the company pays for servers.
These are private inputs supporting private activity.
But suppose the factory requires a highway interchange.
Or the data center requires major electrical-grid expansion.
Or a large development requires new water and sewer capacity.
Now the required asset sits partly outside the private enterprise.
It becomes connected to a shared system.
And shared systems operate under different rules.
The Boundary Is Where the Negotiation Begins
The interesting question is not whether businesses should use public infrastructure.
Of course they should.
Businesses depend on roads, ports, electricity, water, communications, courts, education, emergency services, and countless other shared systems.
So do individuals.
Shared infrastructure is one of the foundations that makes complex economic activity possible.
The structural question appears when an individual project requires the shared system to change substantially on its behalf.
Who should pay for that change?
The company?
Existing users?
Future users?
Taxpayers?
Some combination?
That boundary is not discovered.
It is negotiated.
Scale Changes the Question
Scale matters because small requirements can usually be absorbed by existing capacity.
One new household rarely requires a power plant.
One small store rarely requires a highway expansion.
One office rarely requires a new water system.
But sufficiently large projects can alter the infrastructure requirements of an entire region.
At that point, the project becomes economically entangled with the surrounding system.
The private actor can say:
We cannot build unless this capacity exists.
The community can respond:
We want the investment, so perhaps creating that capacity is worthwhile.
And a private necessity has begun its transformation into a public-development question.
The Transformation Happens Through Benefits
The strongest argument for public participation is usually not:
This corporation needs help.
It is:
The community will benefit if the project happens.
Jobs may be created.
Tax revenue may increase.
New industries may form around the project.
Infrastructure built for the project may serve other users.
The region may become more economically competitive.
These can all be legitimate benefits.
But notice the mechanical shift.
The original question was:
What does this company need?
The new question becomes:
What should the community invest to obtain the benefits this company may create?
The need has not changed.
Its framing has.
Economic Development Changes Who Is Buying Whom
This creates a strange reversal.
Normally, companies compete for customers.
But desirable investments can make communities compete for companies.
A large employer can choose among locations.
A factory can be built in another state.
A data center can potentially locate in another utility territory.
A corporate headquarters can move to another city.
Now the company possesses something jurisdictions want.
Investment.
Employment.
Tax revenue.
Growth.
The company becomes both buyer and product.
It is buying a location.
But communities are also competing to buy its presence.
That competition affects where the private/public boundary is drawn.
How a Private Requirement Becomes a Public Obligation
The transition often follows a recognizable sequence:
1. A private project requires additional capacity.
The company identifies infrastructure it needs to operate.
2. The project is associated with wider economic benefits.
Jobs, investment, taxes, or future development enter the calculation.
3. The required infrastructure is reframed as a shared asset.
The road will serve everyone.
The stronger grid may support future growth.
The expanded water system may benefit later development.
4. Shared benefit creates an argument for shared financing.
Government, utilities, taxpayers, ratepayers, or future users can now reasonably be included in the discussion.
5. The private requirement becomes part of public planning.
What began as something a company needed becomes something the wider system is expected to help provide.
None of these steps is inherently illegitimate.
But together they show how the boundary moves.
The Important Word Is “Obligation”
There is a difference between a public investment and a public obligation.
A community may freely decide that building infrastructure is worthwhile.
That is an investment decision.
The more interesting condition appears when development becomes difficult to imagine without public participation.
The argument starts sounding like:
If we don’t provide this, the project will go somewhere else.
If we don’t expand the infrastructure, growth will stop.
If we don’t compete, another region will win.
The public contribution now feels less optional.
Competition has transformed an opportunity into pressure.
This Is Where Leverage Matters
Not every private need has equal power to become a public priority.
A small business may desperately need better infrastructure and receive little attention.
A multibillion-dollar development may generate meetings at the highest levels of government.
Why?
Scale.
The larger the expected economic effect, the more consequential the project becomes to decision-makers.
That gives large projects greater ability to place their private requirements onto the public agenda.
This does not require anyone to secretly favor large corporations.
The incentives already point in that direction.
Large projects promise large visible outcomes.
Large visible outcomes attract institutional attention.
Institutional attention increases negotiating leverage.
The Public Can Still Get an Excellent Deal
None of this means public participation is foolish.
Imagine a community spends $100 million on infrastructure that produces billions in additional economic activity over several decades.
That could be an excellent investment.
Public infrastructure has always helped create private prosperity.
The mistake is not public investment.
The mistake is treating the public benefit as self-evident merely because the private investment is large.
The transaction still needs examination.
What is being contributed?
What is being received?
Who receives it?
Over what period?
And who carries the downside if expectations are wrong?
Socialized Cost, Privatized Profit Is Too Simple
You will sometimes hear arrangements like these summarized as:
Privatize the profits. Socialize the costs.
Sometimes that description may fit.
But as a general explanation, it is too blunt.
A shared infrastructure investment may genuinely create shared value.
Companies may pay substantial portions of the costs they create.
Public investments may generate returns far beyond their original expense.
The more useful VG question is not:
Is somebody stealing from us?
It is:
Are the costs, benefits, and risks distributed in proportion to the value each participant receives?
That question survives ideology.
The Five-Layer Map
The VG hierarchy shows where the transformation occurs:
Deciders → Creators → Operators → Enforcers → Everyone Else
- Deciders determine whether attracting the investment is worth public participation.
- Creators design the infrastructure agreements, incentives, financing, rates, and cost allocation.
- Operators build and maintain the resulting systems.
- Enforcers administer the rules and obligations.
- Everyone Else inherits the resulting infrastructure, economic activity, costs, benefits, and risks.
By the time Everyone Else encounters the outcome, the original question may have disappeared.
The infrastructure simply exists.
The rates simply exist.
The taxes simply exist.
The development simply exists.
The negotiation that created them is now history.
The Clarifying Insight
When does private infrastructure become a public obligation?
Usually when a private requirement becomes sufficiently connected to a desired public outcome.
The company needs capacity.
The community wants growth.
The infrastructure connects the two.
From there, incentives determine who is willing to contribute what.
The arrangement may be excellent.
It may be terrible.
It may be somewhere in between.
The important thing is not to confuse the private requirement with the public interest.
They overlap.
They are not identical.
So when a private project requires public participation, ask:
What does the company need?
What does the public receive?
Who pays?
Who carries the risk?
And who had enough leverage to define the deal?
Those questions reveal where private necessity ends and public obligation begins.
Want the larger map?
The Vampire Playbook maps how power, incentives, costs, risks, and rewards move through modern systems—and how private interests can become embedded in shared architecture.
The Hidden Subsidy Inside “Economic Development”
Economic development sounds like something a community receives.
A company arrives.
Investment increases.
Jobs appear.
Tax revenue grows.
The local economy expands.
Sometimes that is exactly what happens.
But there is another side of the transaction that receives considerably less attention:
What did the community provide to make the development happen?
Tax incentives are the obvious answer.
They are not the only one.
Roads can be expanded.
Utilities can be upgraded.
Land can be prepared.
Financing can be supported.
Public agencies can devote resources to permitting, planning, and development.
Shared infrastructure can be enlarged around the needs of a private project.
None of this automatically makes economic development a bad deal.
But it does mean the headline investment number rarely tells you the entire price.
Economic Development Is an Exchange
Communities often talk about development as if companies simply choose a location and bring economic activity with them.
Large projects are frequently more negotiated than that.
The company wants something.
The community wants something.
The company may want:
- access to infrastructure,
- favorable operating costs,
- predictable regulation,
- tax advantages,
- available land,
- a suitable workforce.
The community may want:
- jobs,
- investment,
- tax revenue,
- population growth,
- new industries,
- political prestige.
Economic development is therefore not simply a gift arriving from outside.
It is an exchange.
Once you see it that way, a better question appears:
What is each side actually contributing?
The Visible Subsidy Is Easy to See
Some subsidies are explicit.
A government may offer tax credits.
Property taxes may be reduced for a period of time.
Grants may be provided.
Land may be sold on favorable terms.
Public financing mechanisms may support construction.
These arrangements can be debated because they are at least reasonably visible.
You can estimate the value of the incentive and compare it with the expected benefit.
The more interesting subsidies are harder to isolate.
The Hidden Subsidy Can Be Infrastructure
Suppose a large industrial project needs a road improvement before it can operate efficiently.
Who pays for the road?
Suppose a data center needs substantial new electrical infrastructure.
Who pays for the upgrades?
Suppose a major development requires additional water or sewer capacity.
Who finances the expansion?
If the company pays the full incremental cost, the answer is relatively straightforward.
But if some portion is absorbed by a utility, government, existing customers, or future taxpayers, something else has happened.
Part of the cost of making the private project viable has moved outside the company.
That is a subsidy in functional terms, even when nobody writes a check labeled “subsidy.”
Subsidies Do Not Have to Be Cash
This is where the language can obscure the architecture.
People tend to imagine a subsidy as government handing money to a company.
But economic support can take many forms.
A project can benefit from:
- reduced taxes,
- public infrastructure,
- below-market financing,
- publicly funded site preparation,
- utility investments,
- special development arrangements,
- risk absorbed by another institution.
The economic effect can be similar.
A cost the company might otherwise have carried is reduced, delayed, shared, or transferred.
The support becomes harder to see because it is distributed across different systems.
Why Communities Offer It
No conspiracy is necessary.
The incentives are obvious.
Imagine two states competing for a multibillion-dollar factory.
Both believe the project will create jobs and economic activity.
State A offers ordinary terms.
State B offers infrastructure improvements and tax incentives.
State A now faces a choice.
It can improve its offer.
Or it can risk losing the project.
Once jurisdictions compete for mobile capital, concessions become predictable.
Each government may be acting rationally from its own position.
Collectively, however, the competition can transfer some of the economic benefit from the host community back toward the company being recruited.
The company does not need to force anyone.
Competition does the work.
The Auction Nobody Calls an Auction
Large economic-development projects can therefore resemble an auction operating in reverse.
Instead of companies bidding for access to a community, communities may effectively bid for access to the company.
The prize is investment.
The bids can include:
- tax concessions,
- infrastructure,
- land,
- financing,
- regulatory accommodations,
- other economic incentives.
The more desirable the project, the stronger this dynamic can become.
This explains something that otherwise looks contradictory:
The participant with the most money can sometimes receive the most assistance.
Not because the system believes the richest participant needs help.
Because the richest participant may control something multiple jurisdictions want.
That creates leverage.
The Headline Number Can Hide the Exchange
Suppose a company announces a $5 billion investment.
That number will probably appear in the headline.
But imagine the project also receives:
- tax concessions,
- new infrastructure,
- utility upgrades,
- public financing support.
The meaningful economic question is no longer simply:
How much is the company investing?
It becomes:
What is the net exchange between the company and the community?
How much value comes in?
How much public value goes out?
Who receives the benefits?
Who absorbs the costs?
How long do the benefits last?
What happens if the promised activity does not materialize?
Those questions are less exciting than an investment announcement.
They are considerably more informative.
Not Every Subsidy Is a Bad Deal
This distinction matters.
A subsidy can produce more public value than it costs.
A road built partly for a factory may benefit an entire region for decades.
Electrical infrastructure built for a large customer may eventually support additional development.
A tax incentive may help attract an industry that creates substantial long-term economic activity.
The word subsidy should therefore not function as a verdict.
It describes part of the transaction.
The question is whether the exchange makes sense.
That requires measuring both sides.
Risk Is Part of the Subsidy Too
There is another form of support that is even easier to overlook:
risk transfer.
Suppose infrastructure is built around projections of future corporate activity.
If the projections are correct, everyone may benefit.
But what happens if they are wrong?
If the company can reduce operations, relocate, automate more heavily than expected, or abandon a project while the community remains responsible for infrastructure debt, risk has been distributed asymmetrically.
The company captured the option to change course.
Someone else inherited part of the downside.
That risk has economic value even if it never appears in an incentive package.
The Five-Layer Map
The VG hierarchy makes the arrangement easier to examine:
Deciders → Creators → Operators → Enforcers → Everyone Else
- Deciders determine which investments are worth pursuing.
- Creators design incentive packages, tax structures, development agreements, and infrastructure commitments.
- Operators build and maintain the systems supporting the development.
- Enforcers administer the resulting agreements and requirements.
- Everyone Else experiences the eventual jobs, growth, taxes, rates, debt, infrastructure, and risks.
The promotional story usually emphasizes what enters the system.
Structural literacy also examines what leaves it.
The Clarifying Insight
The hidden subsidy inside economic development is not necessarily a secret payment.
It is often the collection of costs, resources, infrastructure, concessions, and risks that sit outside the headline investment figure.
Some may be justified.
Some may produce excellent returns.
Some may not.
The point is not to decide before looking.
The point is to look.
When you hear:
“This company is investing $5 billion in our community,”
add one question:
What is the community investing in the company?
Now you can see both sides of the transaction.
Want the larger map?
The Vampire Playbook maps how incentives, leverage, costs, risks, and rewards move through modern systems—and why the visible transaction is often only part of the story.