bargaining power
Why Big Companies Gain More Leverage Over Public Infrastructure
Large customers do not simply buy more.
They can change the relationship between buyer and system.
A household needs electricity.
A small business needs banking.
A local employer needs roads, utilities, permits, and public services.
For most participants, the relationship is straightforward:
The system establishes the terms.
You participate within them.
But scale can alter that arrangement.
Become large enough, economically important enough, or difficult enough to replace, and the relationship begins to reverse.
The system may start adapting to you.
This is why the big companies gain more leverage over shared systems.
Buying More Is Only the Beginning
We normally think of a large customer as a customer who purchases more of something.
That’s true.
But size can create a second advantage:
importance.
If one customer represents a meaningful amount of revenue, investment, employment, tax income, or future growth, losing that customer becomes more consequential.
That changes incentives.
The question is no longer merely:
What are the rules?
It becomes:
What would we need to change to keep this participant?
That is the beginning of leverage.
The Household and the Data Center
Electricity provides a useful example.
An ordinary household connects to the grid under established terms.
The household generally does not negotiate a custom rate structure, request a new substation, demand accelerated transmission construction, or invite multiple states to compete for its business.
Its individual consumption is too small to meaningfully alter the system.
A massive data center is different.
Its electricity demand can be large enough to affect infrastructure planning.
Its investment can be large enough to interest governments.
Its location may be flexible enough that multiple regions compete for it.
Suddenly, the customer is not merely using the system.
Its decisions matter to the system.
Scale Creates an Exit Option
One of the most important sources of bargaining power is the ability to leave.
If you have only one practical option, your negotiating position is weak.
If several parties want your participation, your position improves.
Large corporations can sometimes choose among:
- different cities,
- different states,
- different utility territories,
- different suppliers,
- different financing arrangements.
That creates competition on the other side of the transaction.
A locality may worry that another locality will offer a better deal.
A utility may worry that a major project will locate somewhere else.
A government may worry about losing jobs and investment.
The customer’s ability to say no becomes economically valuable.
Everyone Wants the Whale
This mechanism appears far beyond electricity.
Businesses often distinguish between ordinary customers and exceptionally valuable ones.
Banks have private-client divisions.
Suppliers offer volume pricing.
Software companies negotiate enterprise contracts.
Governments negotiate development agreements.
Commercial landlords customize large leases.
None of this is inherently improper.
It reflects a basic incentive:
the more valuable a participant is to the system, the more costly it becomes to lose that participant.
And the more costly you are to lose, the more negotiating leverage you tend to acquire.
The Shared-System Problem
Things become more interesting when the negotiation involves a shared system.
Suppose a supplier gives its largest customer a discount.
That is primarily a transaction between two private parties.
But suppose a large customer negotiates terms involving:
- electrical infrastructure,
- roads,
- water systems,
- tax treatment,
- public financing,
- land use,
- other shared resources.
Now the consequences can extend beyond the negotiating parties.
The deal may affect infrastructure used by people who were never at the negotiating table.
This is where bargaining power becomes a structural issue rather than merely a commercial one.
The Leverage Asymmetry
Consider the positions.
A large corporation may have lawyers, consultants, accountants, site-selection teams, economists, lobbyists, and years of experience negotiating complex agreements.
A small municipality may negotiate only a handful of projects of comparable scale in a generation.
Or the imbalance may run the other direction: a sophisticated regulator may have considerably more information than a new market entrant.
The point is not that one side always wins.
It is that bargaining power is rarely distributed evenly.
Structural literacy asks:
Who can credibly walk away?
Who needs the deal more?
Who has better information?
Who can survive a failed negotiation?
Those questions reveal leverage better than titles do.
Why Competition Can Increase Corporate Leverage
Competition is usually presented as something that disciplines companies.
Often it does.
But competition can occur in the opposite direction too.
Governments can compete for companies.
Utilities can compete for large industrial loads.
Cities can compete for headquarters.
Regions can compete for factories and data centers.
Once that happens, the company becomes the scarce prize.
The competitors begin bidding for its participation.
That can produce:
- tax incentives,
- infrastructure commitments,
- faster approvals,
- customized agreements,
- favorable financing.
Again, no villain is required.
Each jurisdiction may simply be trying to avoid losing the opportunity to another jurisdiction.
The collective result emerges from individually rational decisions.
The Advantage Can Compound
This creates a feedback loop.
Size creates leverage.
Leverage can produce better terms.
Better terms can improve economics.
Improved economics can support additional growth.
Additional growth creates more size.
Which creates more leverage.
This is one reason power tends to concentrate without requiring anyone to explicitly design concentration.
Advantages can generate conditions that produce additional advantages.
The Five-Layer Map
The familiar VG hierarchy helps locate the mechanism:
Deciders → Creators → Operators → Enforcers → Everyone Else
- Deciders determine which large participants are valuable enough to accommodate.
- Creators negotiate and design the contracts, incentives, rates, and infrastructure arrangements.
- Operators make those arrangements function.
- Enforcers administer the resulting rules.
- Everyone Else operates within the system that emerges.
Most people encounter standardized rules.
The most powerful participants are more likely to encounter negotiable ones.
That distinction is easy to miss.
Rules Aren’t Equally Rigid for Everyone
This does not necessarily mean rules are being broken.
Often the system explicitly permits negotiation.
Different rate classes can be legal.
Development incentives can be legal.
Customized contracts can be legal.
Infrastructure agreements can be legal.
The structural issue is subtler:
the same system can feel rigid from the bottom and flexible from the top.
To a small participant, the rules appear fixed.
To a sufficiently valuable participant, some of those rules become variables.
Both experiences can accurately describe the same system.
The Clarifying Insight
The biggest customers often gain leverage over shared systems because scale changes what the system has to lose.
A small participant usually needs the system more than the system needs that particular participant.
At sufficient scale, that relationship can change.
The participant brings revenue.
Jobs.
Investment.
Tax receipts.
Prestige.
Future growth.
And perhaps most importantly, the ability to take those things somewhere else.
That creates bargaining power.
The useful question therefore isn’t:
Why do powerful organizations get special treatment?
That framing immediately adds moral heat.
Ask instead:
What makes this participant expensive for the system to lose?
Once you can answer that, the leverage stops looking mysterious.
It becomes architecture.
Want the larger map?
The Vampire Playbook maps the recurring mechanics that move power, rewards, costs, and consequences through modern systems.
How Corporate Expansion Becomes Your Infrastructure Problem
A company expands.
That sounds like a company matter.
It buys land.
Builds facilities.
Hires workers.
Purchases equipment.
Increases production.
But sufficiently large corporate expansion rarely stops at the company’s property line.
More activity requires more infrastructure.
More electricity.
More water.
More roads.
More transmission.
More housing.
More public services.
Eventually, a private decision begins creating requirements for systems shared by everyone else.
That is how corporate expansion becomes your infrastructure problem.
Not automatically.
Not always unfairly.
But predictably enough that the mechanism is worth understanding.
The Expansion Has a Perimeter
Every private project has a boundary.
Inside that boundary, responsibility is relatively obvious.
If a company needs a new building, it generally pays for the building.
If it needs servers, machinery, desks, or forklifts, those are business expenses.
The interesting part begins outside the perimeter.
What happens when the new facility requires a larger electrical substation?
What happens when thousands of additional vehicle trips require road improvements?
What happens when local water capacity must expand?
What happens when thousands of new workers increase demand for housing, schools, transportation, emergency services, and other community systems?
The expansion may still be private.
Its requirements are no longer entirely private.
The Infrastructure Shadow
Think of every large project as casting an infrastructure shadow.
The visible project is the facility itself.
The shadow is everything around it that must change for the project to function.
A factory may need roads and freight capacity.
A large residential development may require schools, water, sewer, and transportation.
A data center may require generation, transmission, substations, and water.
A major commercial development may require intersections, public safety, utilities, and additional municipal services.
The larger the project, the larger its potential infrastructure shadow.
And that shadow has a cost.
The First Question Is Who Caused the Cost
This seems straightforward.
If a development creates the need for an infrastructure upgrade, make the developer pay.
Sometimes that is exactly what happens.
But shared infrastructure complicates the calculation.
Suppose a company creates the immediate need for a new road.
Other people will use the road too.
Suppose a data center triggers a transmission upgrade.
The stronger grid may later benefit other customers.
Suppose a new development requires a larger water system.
That additional capacity may eventually support future growth.
Now the accounting question changes.
Instead of simply asking:
Who caused this?
the system begins asking:
Who benefits from it?
That is reasonable.
It also creates room for costs to spread.
Shared Benefit Can Become Shared Cost
This is one of the quiet mechanics underneath infrastructure financing.
If an asset can plausibly benefit the wider community, some portion of its cost can potentially be treated as a shared investment.
Sometimes that is entirely appropriate.
A new bridge does not cease being useful because a private development helped create the need for it.
But notice what has happened.
A private expansion created a requirement.
The resulting infrastructure was classified partly as a shared benefit.
And the original private cost can now begin migrating outward.
Private requirement → shared infrastructure → shared financing.
That sequence is one of the ways corporate expansion becomes everyone else’s infrastructure problem.
Economic Development Adds Another Incentive
Now add competition.
Cities, states, regions, and countries want investment.
They want jobs.
They want tax revenue.
They want new industries.
They want to be chosen instead of somewhere else.
That means the relationship between a large company and a community is not merely regulatory.
It is also competitive.
A sufficiently desirable project can effectively say:
We can build here.
Or we can build somewhere else.
The larger the expected economic prize, the more incentive governments have to make the location attractive.
Infrastructure becomes one of the negotiating variables.
The Bargaining Position Is Unequal
An ordinary household cannot usually negotiate the infrastructure surrounding its arrival.
You cannot tell a city:
Improve the road, expand the electrical system, give me favorable tax treatment, and perhaps I’ll move here.
You can try.
The ribbon-cutting ceremony may be sparsely attended.
A multibillion-dollar project occupies a different position.
Scale creates leverage.
That leverage can influence:
- tax treatment,
- infrastructure commitments,
- utility agreements,
- development rules,
- public financing,
- permitting priorities.
This does not require corruption.
It requires competition.
When multiple jurisdictions want the same investment, each has an incentive to improve the offer.
The Benefit Is Concentrated Before the Cost Is Distributed
Corporate expansion often creates real economic value.
But the benefits and costs do not necessarily travel through the same channels.
Profits accrue to owners and investors.
Wages accrue to employees.
Contracts accrue to suppliers.
Tax revenue accrues to governments.
Meanwhile, infrastructure costs may appear elsewhere:
- utility rates,
- public debt,
- tax expenditures,
- transportation budgets,
- housing pressure,
- water-system expansion,
- municipal services.
This does not mean the project produces a net loss.
It means aggregate claims like “this project creates $X billion in economic value” can conceal the distribution.
Who receives which benefit?
Who absorbs which cost?
Those are different questions.
The Five-Layer Map
The familiar VG hierarchy makes the distribution easier to see:
Deciders → Creators → Operators → Enforcers → Everyone Else
- Deciders choose which forms of growth to pursue and what concessions are acceptable.
- Creators design development agreements, infrastructure plans, tax structures, utility rates, and financing mechanisms.
- Operators build and maintain the systems required to support the expansion.
- Enforcers administer permits, rules, rates, taxes, and requirements.
- Everyone Else lives inside the resulting economic environment.
Notice the asymmetry.
Everyone Else usually enters the process after the important allocation decisions have already been made.
They experience the architecture.
They rarely design it.
How the Cost Becomes Difficult to See
The infrastructure bill rarely arrives in one envelope.
That matters.
Costs can be distributed across:
- different agencies,
- different utilities,
- different taxes,
- different rate classes,
- different budgets,
- different years.
A billion-dollar corporate investment is easy to announce.
A few dollars added here, a public appropriation there, a road project somewhere else, and a tax concession spread over twenty years are much harder to perceive as one transaction.
The benefits remain narratively concentrated.
The costs become administratively fragmented.
That alone can distort how the deal is understood.
This Is Why “Who Paid?” Is Harder Than It Sounds
Ask who paid for a corporate headquarters and you may get a clear number.
Ask who paid for everything necessary for that headquarters to exist in that location and the answer becomes much harder.
Some infrastructure existed already.
Some was upgraded.
Some serves everyone.
Some received public financing.
Some was paid directly by the company.
Some costs may not appear for years.
This complexity is not necessarily evidence of deception.
It is a property of large shared systems.
But complexity also makes cost transfer harder to recognize.
The Better Way to Evaluate Growth
“Is corporate expansion good or bad?” is not a particularly useful question.
Large investments can produce enormous public benefits.
They can also transfer costs outward.
Both can occur simultaneously.
A more useful evaluation asks:
- What new infrastructure does the project require?
- Who pays for that infrastructure?
- Who owns the resulting assets?
- Who receives the economic benefits?
- Who carries the risk if projections fail?
- What costs are being shifted to people outside the original transaction?
Now you are examining the architecture rather than the announcement.
The Clarifying Insight
How corporate expansion becomes everyone else’s infrastructure problem is not mysterious.
Growth creates requirements.
Requirements encounter shared systems.
Shared systems create allocation decisions.
Allocation decisions are shaped by incentives and bargaining power.
And costs that begin with one project can eventually be distributed among people who never participated in the original decision.
That does not make corporate growth inherently exploitative.
It makes cost allocation worth examining.
So when the next enormous project is announced, look beyond the investment figure.
Look for its infrastructure shadow.
Then ask:
What has to be built around this?
Who is paying for it?
And who would pay if the projections turn out to be wrong?
That’s where the rest of the transaction is hiding.
Want the larger map?
The Vampire Playbook explains how modern systems distribute power, costs, risks, and consequences—and why they so often travel in different directions.