Become Indispensable, Not a Bottleneck

In M&A, do not build dependence through control. Build it through irreplaceable contribution. People should rely on you because they want to, not because they have to.

Learn to keep people dependent on you. To maintain your independence you must always be needed and wanted.
Robert Greene, The 48 Laws of Power

Built on Robert Greene’s The 48 Laws of Power. The M&A interpretation and case analysis are my own.

24 min read

The Law

Every deal team has someone everyone calls first. When negotiations stall. When an integration issue escalates. When the board needs clarity. When the client is anxious. When the model no longer explains the real problem.

It is not always the most senior person, and not always the smartest person. It is the person others trust to make complexity manageable. In M&A, influence rarely comes from title alone. It comes from becoming the person whose presence consistently improves the outcome.

Robert Greene’s eleventh law says to keep people dependent on you. Read literally, that can become advice to hoard knowledge, protect territory and make yourself impossible to bypass. In M&A, that reading is dangerous. The person who creates dependence through control may gain short-term relevance, but they also become a bottleneck. Eventually the team works around them, resents them or stops trusting them.

The professional version is healthier and more powerful. Become indispensable through contribution, not control. Make yourself needed by making the deal better, the team stronger and the work easier to execute.

People do not depend on the best professionals because they have to. They depend on them because they want to.

Law 10 was about what spreads through an integration. Law 11 is about what people rely on when the work becomes difficult. The strongest professionals do not create dependence by weakening others. They create it by becoming a source of clarity, reliability, connection and judgment.

The M&A Translation

The M&A translation of Law 11 is this: become indispensable, not a bottleneck.

There are two kinds of dependence in dealmaking. The first is brittle dependence. It is created by hoarding information, owning access, blocking decisions, refusing to document work or making every answer pass through one person. It looks powerful for a while because everyone must come to you. But it is fragile. The moment the organisation can replace the bottleneck, it will.

The second is durable dependence. It is created by unique contribution. You solve problems others struggle with. You connect people who need each other. You simplify complexity. You transfer knowledge. You make clients, teams and leaders more effective. People rely on you not because you trapped them, but because working with you makes the outcome better.

That is the mature form of indispensability. It does not make others weaker. It raises the performance of everyone around you.

The best kind of indispensability is not control over others. It is value others do not want to lose.

Where This Shows Up in a Deal

Law 11 appears wherever a person, team, asset or platform becomes central to how others work.

It appears in advisory teams, when one professional becomes the person who can translate chaos into a board-ready answer. It appears in corporate development, when a deal lead becomes trusted because they can coordinate legal, tax, diligence, valuation and integration without losing the thread. It appears in integration, when a workstream lead removes friction and makes other teams faster.

It appears in software and infrastructure deals, where the target is valuable because customers already depend on it every day. It appears in ecosystem acquisitions, where the buyer is not only buying revenue, but a position inside the customer’s workflow. It appears in crisis transactions, where institutions turn to the player that can act under pressure.

In every version, the same question matters. Is the dependence based on value, or based on lock-in? One creates loyalty. The other creates resentment.

The Deal Power Map

For Law 11, the power map is an indispensability map. The question is not only who is needed. It is why they are needed, whether the dependence strengthens the system and whether it can survive without becoming a single point of failure.

Five Questions to Map Indispensability Risk

Before celebrating dependence, map whether it is healthy, durable and value creating.

  1. 1
    Who is everyone depending on?

    Identify the person, team, platform, advisor, system or asset that others repeatedly rely on when work becomes difficult.

  2. 2
    Why are they needed?

    Separate value-based dependence from control-based dependence. Are they needed because they solve hard problems, or because they have trapped knowledge and access?

  3. 3
    What happens if they disappear?

    If the team stops functioning, there may be a single point of failure. Healthy indispensability should improve the system, not make it collapse in one person’s absence.

  4. 4
    Are they developing others?

    Durable contributors transfer knowledge, build successors and make the organisation stronger. Bottlenecks protect their own irreplaceability.

  5. 5
    Does the dependence create trust or resentment?

    Value-based dependence creates loyalty. Lock-in, gatekeeping and forced reliance create frustration that eventually searches for an exit.

Cases from the Deal Floor

These cases separate two kinds of indispensability: the durable kind built on value created, and the brittle kind built on lock-in, control or single-point dependence.

Case 1Done right

JPMorgan–Bear Stearns2008

The dependence

In the financial crisis, regulators depended heavily on JPMorgan.

During the 2008 financial crisis, the system needed a buyer for Bear Stearns under extreme time pressure. The situation required balance-sheet strength, execution capability, regulatory trust and the ability to move over a weekend while markets were under stress.

The call went to JPMorgan. That was not accidental. The firm had built the credibility and capability to act in a moment when many others could not. Regulators and markets needed an institution that could absorb complexity under pressure.

This is Law 11 at institutional scale. Dependence was not engineered through lock-in. It was earned through capacity, credibility and trust. JPMorgan became needed because it could do something difficult when the system required it.

Institutions that consistently deliver become the first call in moments of uncertainty.

$10 / share
Final price after initial lower offer
First call
Regulators turned to JPMorgan
Capability
Balance sheet plus credibility
Key lesson

Institutions that consistently deliver become the first call during moments of uncertainty.

Case 2Done right

Google–Android2005

The dependence

Google did not try to build everything internally.

Google’s acquisition of Android was small in financial terms compared with its later strategic importance. Rather than build the entire mobile operating system future internally from scratch, Google bought a capability and allowed it to develop into something central to the ecosystem.

Android became a foundation for Google’s mobile strategy. It helped ensure that Google services had a place in the smartphone era and gave the company strategic relevance in a market that could otherwise have been controlled by others.

This is healthy dependence because it is mutual. Android became central to Google, but Google’s scale, distribution and resources also made Android more powerful. The acquired capability did not become valuable by being trapped. It became valuable by being enabled.

Strategic value, allowed to develop, creates dependence that benefits both sides.

~$50M
Reported acquisition price
Core
Central to Google mobile strategy
Enabled
Android leadership and capability were scaled
Key lesson

Strategic value creates mutual dependence.

Case 3Done right

Salesforce–Slack2021

The dependence

Salesforce recognised that modern work increasingly depends on collaboration platforms.

Slack was not merely a feature. For many organisations, it had become part of the daily operating rhythm. Teams used it to coordinate, communicate, share documents, escalate issues and maintain visibility across workstreams.

That kind of embedded usage creates durable value. A product that solves a daily problem becomes difficult to remove because it is woven into how people work. Salesforce saw the opportunity to connect that collaboration layer with its broader customer and enterprise ecosystem.

The important point is that Slack’s dependence was not created mainly through force. It was created through repeated usefulness. Users came back because the product made coordination easier.

The strongest assets solve problems others repeatedly face.

$27.7B
Acquisition of Slack
Infrastructure
A workflow layer, not only a product
Recurring
Solved a daily coordination problem
Key lesson

The greatest assets solve problems others repeatedly face.

Case 4Cautionary tale

Oracle–PeopleSoft2005

The dependence

Oracle pursued customer relationships and an installed base.

Oracle’s hostile pursuit of PeopleSoft revealed a hard truth about enterprise software. Installed bases matter because switching costs create leverage. When organisations build processes, data, training and governance around a system, they do not leave quickly.

That stickiness was a large part of the prize. PeopleSoft customers represented not only revenue, but dependence. They had workflows, processes and systems tied to the product.

But the case also shows the tension inside Law 11. Dependence built through value creates loyalty. Dependence built through lock-in creates resentment. Customers may stay because switching is hard, but staying is not the same as wanting to stay.

A company can be needed and disliked at the same time. That is powerful, but brittle.

$10.3B
Hostile acquisition value
Switching costs
Created real leverage
Lock-in
Can breed resentment over time
Key lesson

Dependency created through customer value is powerful. Dependency created through lock-in eventually breeds resentment.

Case 5Cautionary tale

Visa–Plaid2020

The dependence

Plaid had become critical infrastructure connecting fintech ecosystems.

Plaid sat at the centre of how many fintech applications connected to bank accounts. That centrality made it strategically valuable. The more developers, apps and financial institutions relied on the connectivity layer, the more important Plaid became.

That is the attractive side of indispensability. Critical infrastructure draws acquirers because it sits inside the workflow of an entire ecosystem. But indispensability also attracts scrutiny. If too many market participants rely on one layer, regulators begin asking what control over that layer would mean for competition.

Visa’s attempted acquisition of Plaid faced antitrust scrutiny and was abandoned. The lesson is that becoming essential increases strategic value, but it also increases responsibility and attention.

The more central you become, the more the market cares who controls you.

$5.3B
Attempted acquisition value
Critical
Fintech connectivity infrastructure
Abandoned
Deal ended after antitrust scrutiny
Key lesson

Becoming essential attracts both opportunity and attention.

Case 6Done right

Intuit–Mailchimp2021

The dependence

Mailchimp helped small businesses reach customers; Intuit helped them manage finances.

Intuit and Mailchimp each solved recurring problems for small businesses. Intuit helped with financial management. Mailchimp helped with customer communication and marketing. Together, they represented adjacent needs inside the same customer base.

This is a healthier ecosystem logic. Instead of trapping customers in one system, the combined company could deepen value by solving more of the problems customers already faced. Dependence grows because usefulness expands.

The strongest ecosystems do not rely only on switching costs. They become harder to replace because they help customers do more of what matters to them.

That is a powerful M&A lesson. Durable dependence is created by expanding the customer’s capability, not merely by reducing their ability to leave.

$12B
Acquisition of Mailchimp
Adjacent
Finances plus customer communication
Ecosystem
Multiple needs, one broader relationship
Key lesson

The strongest ecosystems solve multiple adjacent problems.

Case 7The everyday pattern

The Associate Who Made Life Easier

The situation

Two associates with similar technical skills, and one quiet difference in how they work.

Two associates join the same transaction. Both are technically capable. Both can build the model, update the deck, answer diligence questions and support the workstream. On paper, they are similar.

One protects their lane. They say, that is not my responsibility. They know things but do not document them well. They become hard to work around because important details sit inside their head. They are needed, but the dependence creates friction.

The other associate makes life easier. They simplify the messy file. They connect legal with finance before the issue escalates. They write down the assumption so others do not have to ask again. They help the manager see what matters. They make sure nothing falls through the cracks.

Soon partners request the second associate, clients trust them and new opportunities appear. Not because they hoarded knowledge, but because they reduced friction for everyone around them.

Key lesson

The professionals who become indispensable are often the ones who make everyone else’s job easier.

The Pattern Behind the Cases

Across these cases, indispensability separates into two forms.

The durable form is built on value. JPMorgan became the first call because it could act under pressure. Android became central because it enabled Google’s mobile future. Slack became valuable because it solved a daily coordination problem. Mailchimp deepened Intuit’s small-business ecosystem by addressing an adjacent need. The associate became requested because they made everyone else more effective.

The brittle form is built on control. Oracle and PeopleSoft show how switching costs create leverage, but also resentment. Visa and Plaid show how essential infrastructure attracts not only buyers, but regulators. Dependence creates power, but that power has to be handled carefully.

The pattern is simple. If people depend on you because you make them stronger, your influence compounds. If they depend on you because you made it difficult to function without you, your influence becomes fragile.

Indispensability built on value creates loyalty. Indispensability built on control creates escape plans.

Four Diagnostic Questions

Before trying to make yourself needed, ask four questions about the kind of dependence you are creating.

The Four Questions That Protect Healthy Indispensability

These questions separate contribution from control.

  1. 1
    1. Am I indispensable because I add unique value, or because I am a bottleneck?

    The first form creates trust. The second creates frustration. If people need you only because you have trapped information, your position is weaker than it looks.

  2. 2
    2. Whose job did I make easier this week?

    Healthy indispensability is measured by the performance improvement you create around you, not only by the work you personally complete.

  3. 3
    3. If I went on leave tomorrow, would the team function?

    If the answer is no, ask whether you have created resilience or dependence. A strong contributor leaves systems stronger, not more fragile.

  4. 4
    4. Am I developing a successor, or protecting my own irreplaceability?

    Developing others does not reduce your value. It proves you can create leverage beyond your own capacity.

The Four Sources of Indispensability

Real indispensability is built, not hoarded. It comes from four sources that together create a kind of professional gravity.

  1. 1
    Expertise

    Can you solve difficult problems that others cannot, or cannot solve as well?

  2. 2
    Reliability

    Do people trust you to deliver consistently, without being chased?

  3. 3
    Connectivity

    Can you bring the right people together at the right moment?

  4. 4
    Stewardship

    Do others believe you act in the collective interest rather than only your own?

How to Apply This at Your Level

Role Lens: Senior, Mid-Level and Junior

Senior

If you are a CEO, founder, partner, managing director, board member or investor, build an organisation people choose to rely upon, and avoid creating single points of failure, including yourself. Develop successors. A leader who cannot be replaced has often failed to build something that lasts beyond them.

At every level, Law 11 asks for the same shift: from protecting your own relevance to increasing the capability of the system around you.

The Trap

The trap of Law 11 is mistaking control for indispensability.

Some professionals protect their relevance by making work depend on them. They keep the key file messy. They hold the client relationship too tightly. They avoid documenting assumptions. They answer questions privately instead of building repeatable knowledge. They become the only person who knows how something works.

For a while, this can look like power. Everyone has to ask them. Nothing moves without them. Their absence creates problems. But this is not durable influence. It is system fragility disguised as importance.

The best professionals do the opposite. They document. They teach. They develop successors. They make complexity easier for others to handle. They share knowledge generously. Paradoxically, this makes them more valued, not less, because everyone sees that the team performs better when they are involved.

The mature version of Law 11 is not to make others dependent by weakening them. It is to become so useful that stronger people still want you in the room.

A bottleneck is needed because the system is weak. A force multiplier is wanted because the system becomes stronger.

The Paradox at the End of Law 11

The paradox of Law 11 is that the people who try hardest to make others dependent on them often become replaceable, while the people who make others stronger become harder to replace.

The bottleneck feels secure because everyone must come through them. But the organisation experiences that dependence as friction. Over time, leaders look for ways to remove the constraint. They hire around it, automate around it, document around it or promote someone else who can scale the work without hoarding it.

The force multiplier feels less possessive. They share knowledge. They develop people. They make work repeatable. They connect others. They reduce dependence on themselves at the task level, but increase demand for themselves at the leadership level.

Every transaction reveals who truly creates value. Not the person who guards information, and not the person who protects territory, but the person who makes uncertainty manageable, complexity understandable and collaboration possible. Their phone rings first in a crisis. Their opinion carries weight in difficult decisions. Their absence is felt immediately, not because the team collapses, but because the team performs better when they are there.

The professionals who share knowledge most generously often become the hardest to replace.
Law 11 of 48

Become Indispensable, Not a Bottleneck

In M&A, do not build dependence through control. Build it through irreplaceable contribution. People should rely on you because they want to, not because they have to.

Because influence in M&A is rarely built by making others weaker. It is built by making others stronger.

Dealmaker’s Reflection

Before your next meeting on a live deal, ask yourself:

  • 1.Am I indispensable because I add unique value, or because I have made myself a bottleneck?
  • 2.Whose job did I make easier this week?
  • 3.If I went on leave tomorrow, would the team function, or have I hoarded what only I know?
  • 4.Am I developing a successor, or quietly protecting my own irreplaceability?