Dependent — The Structurally Contingent

The Dependent is the fifth structural role in L17X Power Mapping. It describes a company whose strategic position is materially contingent on factors outside its own control — specifically, on the decisions, platforms, infrastructure, or resources of another entity. Dependency is not about size, profitability, or growth rate. It is a structural description of where control over the company's competitive position actually sits.

Three Types of Dependency

Platform Dependents are companies whose distribution, discovery, or core functionality depends on a platform they do not control. When the platform changes its algorithm, its pricing terms, or its content policies, the Dependent's business is directly affected — often without recourse. The platform's strategic decisions are not made with the Dependent's interests as a primary consideration. The defining test: remove the platform. Does the business survive in a recognizable form? If the answer is "not easily," the dependency is structural.

Regulatory Dependents are companies whose core business model exists because of a specific regulatory framework — and would not exist, or would exist in a fundamentally different form, if that framework changed. This dependency is not always visible from the outside; it requires understanding the regulatory basis of the business model rather than just the revenue model.

Customer Dependents are companies where one or a small number of customers account for a disproportionate share of revenue — typically above 20-30% with a single customer — and where the loss of that customer would be structurally significant rather than merely financially painful. When the customer's strategic decisions materially constrain the Dependent's own strategy, the dependency is structural.

The Defining Test

Remove the platform, the regulatory framework, or the key customer. Does the business survive in a structurally recognizable form?

This test reveals the underlying structural reality. A company that passes this test — whose core value proposition, customer relationships, and competitive advantages are not contingent on a specific external entity — is structurally self-sufficient. One that fails the test carries structural dependency as a fundamental characteristic of its risk profile.

Why Large Companies Can Be Dependents

Size does not eliminate structural dependency. A company with billions of dollars of revenue can still be a Dependent if that revenue rests on a platform, regulatory environment, or customer concentration that it does not control. In some sectors, the largest companies by revenue are structurally among the most dependent — because their scale is built on top of another entity's structural foundation.

This is one of the analytical insights that Power Mapping provides that pure financial analysis misses. Revenue size, margin profile, and growth rates can all look attractive while the structural position is fundamentally contingent on external control. The Dependent classification flags this reality explicitly.

Dependency as a Risk Profile, Not a Verdict

Dependent is not a negative judgement. Many Dependents are excellent businesses with strong financials and attractive returns. The classification describes a structural reality, not a recommendation. A Dependent with a 6% dividend yield, strong cash flows, and an apparently stable dependency relationship may be a compelling holding. But the analytical framework for understanding it — and the risks specific to it — is fundamentally different from a Status-Quo-Player with similar metrics.

The dependency is the ceiling. As long as the dependent relationship is stable and the external entity's strategy is aligned, the Dependent can generate strong returns. When the relationship shifts — when the platform changes terms, when the regulator acts, when the key customer finds an alternative — the structural ceiling can become a structural floor, rapidly.