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.

Get the Vampire Playbook