Why the Best Acquisitions Start as Contracts, Not Companies

The strange similarity between a pharmacy breakup and an HTML tag

What do a major healthcare acquisition and the simplest rule in HTML have in common? More than you might think. In one case, a company is reducing dependence on a giant partner by buying a specialty pharmacy business. In the other, a web page exists because tags tell the browser where something begins and ends. Both are really stories about boundaries.

That may sound abstract, but boundaries are where modern systems become legible. They determine what belongs inside, what must stay outside, and how much control one party has over another. In business, weak boundaries create dependency. In code, missing boundaries create chaos. In both cases, the first step toward power is not growth. It is definition.

The deeper question connecting these two ideas is this: how do complex systems become independent without becoming fragmented? The answer begins with knowing where one thing ends and another begins.

---

The hidden architecture of dependence

Large organizations often look like they compete on products, pricing, or scale. But underneath those visible battles is a more structural contest: who owns the interfaces? A pharmacy benefit manager relationship, for example, is not just a commercial contract. It is an operating architecture. It decides how prescriptions flow, who captures margin, who controls data, and who gets leverage over the patient relationship.

When a company reduces reliance on a dominant intermediary, it is not merely switching vendors. It is re drawing its internal map of power. That is why a seemingly narrow acquisition can matter so much. It is a way of changing the shape of the system so that value does not leak out through someone else’s infrastructure.

HTML makes the same point in miniature. A page is not just text. It is text wrapped in tags that say, essentially, “this begins here, this ends there.” Without those markers, the browser cannot interpret the page reliably. The tag is not decorative. It is the difference between structure and ambiguity.

This is the part many businesses miss. They think independence comes from size. Often, it comes from clearer markup of the business itself.

Power in a complex system usually belongs to the party that controls the boundaries, not merely the one that owns the most assets.

Consider a simple analogy. If a warehouse has no labeled sections, inventory becomes hard to locate, restocking slows down, and theft becomes easier. Add clear zones, and suddenly you have a system that can move faster with less confusion. Companies are not so different. A well defined boundary is not bureaucracy. It is operational memory.

---

Why dependence is often just a failure to define the system

We tend to talk about dependence as if it were purely economic. One company buys from another, so it depends on it. That is true, but incomplete. Dependence is also created when a company allows another entity to become the default interpreter of its business.

That is what makes intermediary dependence so sticky. If another party controls routing, records, eligibility, claims, or customer access, then the “core business” quietly becomes secondary to the platform beneath it. The company may still own the brand, but someone else owns the traffic. It may still serve the customer, but someone else owns the rules of engagement.

In that sense, the most important acquisitions are often boundary acquisitions. They are not just about revenue. They are about reclaiming the right to define the edges of the business.

HTML gives us a useful mental model here: a page without tags is like a business without clear interfaces. Everything becomes context dependent. The browser guesses. Teams improvise. Systems drift. When elements are properly tagged, however, the structure becomes portable. A browser can render it. A developer can edit it. A machine can parse it. Boundaries create interoperability.

That is a surprising lesson for corporate strategy. The best systems are not those that lock everything down. They are those that make each part understandable enough to connect with others on purpose.

A company trapped inside another company’s infrastructure often has neither true autonomy nor true interoperability. It is half integrated, half captive. The strategic goal is not isolation. It is to build a boundary that makes connection optional rather than coercive.

---

The real value of structure is optionality

There is a common myth that structure limits creativity. In practice, the opposite is often true. Structure makes creativity usable. An HTML page with no tags can contain words, but it cannot easily contain navigation, emphasis, forms, images, or logic. The tags are constraints, yet they are also what make the page capable of doing more.

Business boundaries work the same way. A company that defines what it owns, what it outsources, what it controls, and what it shares can move with greater confidence. It knows where the data lives. It knows who owns the customer relationship. It knows which layer of the stack can be swapped and which cannot.

This matters especially in industries where infrastructure is invisible until it fails. Healthcare is one of them. Patients rarely see the systems that determine whether a prescription is filled smoothly or delayed in a maze of claims, formularies, and networks. Yet those hidden structures shape experience more than any slogan or ad campaign.

So when a firm acquires a specialty pharmacy to reduce reliance on a dominant partner, the move can be read as a form of strategic tagging. It says, “this capability belongs here, not there.” That may sound bureaucratic, but it is actually liberating. Once a system knows what is inside its boundary, it can design around it instead of being designed by someone else.

A useful framework is to think in terms of three layers:

1. Ownership layer: Who holds the asset or capability?
2. Control layer: Who sets the rules and decides the flow?
3. Interpretation layer: Who understands the data and can act on it?

Many companies own the first layer and assume they are safe. The real leverage, however, often sits in the second and third. That is why dependency can persist even after a purchase, and why some acquisitions fail to change much. The asset changes hands, but the operating logic does not.

---

The breakup is not the story. Recomposition is.

It is tempting to frame corporate separations as failures. But that misses a crucial point: breakups are often attempts to restore coherence. A complex organization can become so entangled with a dominant partner that it loses its own shape. In that situation, the breakup is not destruction. It is an act of structural recovery.

Think of it like editing code. If everything is tangled in one file, the program may still run, but it becomes impossible to maintain. Breaking it into functions does not weaken it. It makes it survivable. The same is true for businesses. When every important process routes through a single external system, the company may appear efficient. But efficiency built on dependency is fragile.

This is why acquisitions aimed at reducing reliance are especially interesting. They are not merely about adding capabilities. They are about recomposing the company into a shape where it can negotiate from strength. The point is not to be separate for its own sake. The point is to make separation possible when needed.

That is a subtle but profound shift in strategic thinking. Most leaders ask, “How do we integrate this new asset?” A better question is, “What boundary does this asset let us draw that we could not draw before?”

Once you start asking that, strategy changes. A purchase is no longer just a line item on a balance sheet. It becomes a line in a diagram. It can redraw flows of data, money, risk, and power.

The deepest purpose of structure is not order. It is the ability to change without losing identity.

This is the hidden connection to HTML. A well tagged document can be transformed by different browsers, devices, and systems without becoming meaningless. The structure makes the content resilient. Businesses, too, need structures that preserve meaning as they scale, partner, acquire, and separate.

---

Key Takeaways

• Look for boundary moves, not just growth moves. The most important strategic actions often change who controls the interface, not just who owns the asset.
• Audit your dependencies at the control layer. Ask who sets the rules, who owns the data, and who interprets the flow. Ownership alone is not enough.
• Treat structure as leverage, not overhead. Clear internal boundaries make a company faster, more adaptable, and less hostage to outside systems.
• Use acquisitions to redraw the map. The best deals often create optionality, allowing a business to connect on its own terms instead of by default.
• Think like markup, not just management. Define where capabilities begin and end so that teams, systems, and partners can work with them cleanly.

---

A new way to think about control

We usually imagine control as domination: bigger budget, larger market share, more assets. But in complex systems, control is often more elegant than that. It is the ability to mark edges clearly enough that the whole system can breathe. A company does not become stronger simply by absorbing more. It becomes stronger when it can say what is inside it, what is outside it, and what it chooses to depend on.

That is why the comparison to HTML matters. The humble tag is a reminder that structure is not the enemy of expression. It is what makes expression readable. Likewise, a strategic acquisition is not only about buying revenue. It can be about creating a legible business, one that knows where its sentence begins and ends.

In the end, the most durable organizations may be the ones that understand a simple truth: before you can scale a system, you must be able to name its boundaries. The companies that master this will not just grow. They will become easier to change, harder to control, and much more difficult to break.