Can You Limit How Much of Your Portfolio Depends on One Company?
September 14, 2026
Altsets
Research by Altsets Research
Treat repeated customers, suppliers, and other outside nodes as portfolio exposures that can be deliberately limited even when the company creating the concentration is not directly owned.
Data used:Altsets Supply Chain Intelligence: 90k+ entities, 400k+ relationships, 20+ years of history.
Key findings
- The supplied network shows a quantified 561M USD HPE-Microsoft relationship and a separate structural Nvidia-Microsoft edge, illustrating how one outside company can matter through multiple portfolio holdings with different evidence strength.
- A dependency ceiling can begin as a qualitative portfolio rule that limits repeated exposure without adding supplier revenue percentages, customer cost percentages, structural edges, and portfolio weights into one misleading number.
Yes. An investor can limit dependence on one outside company by identifying every holding connected to it, measuring each relationship with its proper directional metric, and capping the affected positions or aggregate dependency without forcing unlike percentages into one score.
That outside company may not even be owned. It can be a customer, supplier, foundry, infrastructure provider, or other economic node shared by several holdings. Once that overlap is visible, the investor can decide whether the combined exposure is intentional or larger than the portfolio was designed to carry.
The outside company can matter more than another ticker in the account
The supplied Altsets network shows a 561M USD relationship between HPE and Microsoft, while Nvidia also maps to Microsoft as a downstream customer in the supplied graph without a displayed economic metric on that edge.
A portfolio holding HPE and Nvidia therefore has two separate relationships pointing toward the same outside company. The evidence is not equally strong, so the two paths should not be treated as equal exposures. They still show why Microsoft can matter to the portfolio even if Microsoft itself has zero portfolio weight.
That is the kind of concentration ordinary position limits do not capture.
An exposure ceiling can be qualitative before it becomes quantitative
The investor does not need to calculate one perfect portfolio percentage for Microsoft dependence. A practical first rule can be simpler: do not let too many large positions rely on the same outside company unless that concentration is deliberate.
That can influence which new stock is added, how large the position becomes, or whether another holding tied to the same node is reduced.
The benefit comes from controlling repeated dependence, not from pretending every relationship can be translated into one common unit.
Different relationship metrics should not be blindly added
A supplier revenue percentage, customer cost percentage, relationship size, and structural relationship answer different questions. Adding them together would create false precision.
An exposure-aware portfolio should therefore preserve the type and direction of each relationship. A large quantified customer dependency can receive more attention than a structural-only edge, while a small financial relationship can still matter if public evidence shows that the supplier is operationally critical.
The limit should reflect evidence quality rather than force every edge into one score.
The rule becomes more useful before adding the next position
Imagine an investor already owns two companies connected to Microsoft and is considering a third. A conventional sector screen may show that the new company improves diversification.
The dependency view asks whether the new position would place still more capital behind the same external customer or infrastructure cycle. If the answer is yes, the investor can decide whether the expected return is strong enough to justify that additional concentration.
This turns dependency analysis into a portfolio-construction rule rather than a post-mortem.
Exposure limits can preserve a theme without letting one company dominate it
An investor may want strong exposure to AI, cloud infrastructure, electric vehicles, or semiconductors without wanting every position to depend on one customer.
That creates a useful design goal: keep the theme, but diversify the economic paths through which the theme reaches the portfolio.
The investor can look for holdings tied to different customers, suppliers, product cycles, and manufacturing nodes rather than abandoning the theme entirely.
The ceiling should change when catalysts approach
A level of repeated dependency that feels acceptable during normal conditions can become uncomfortable before a major earnings report, regulatory deadline, product launch, or sourcing decision.
The investor can temporarily tighten the effective exposure limit by reducing one position or simply refusing to add another connected stock before the catalyst.
After the event passes, the portfolio can be reassessed.
This makes exposure control dynamic rather than permanent.
The conclusion is control, not elimination
No portfolio can eliminate every shared dependency, and doing so would often remove attractive investments. The useful objective is knowing where repeated dependence exists and deciding how much of it the portfolio is willing to carry.
A dependency-aware portfolio can place limits on exposure to outside companies just as deliberately as it places limits on sectors or single-stock weights.
The external-company ranking guide explains how to identify non-owned companies that matter across several holdings. The position-sizing guide shows how dependency can influence the size of one position without becoming a mechanical formula.
For relationship definitions and evidence limits, read the Altsets methodology.