The observation
One client now represents thirty-eight per cent of a company’s revenue. The relationship itself is good — responsive, collaborative, mutually valuable. The natural framing, when this kind of concentration is discussed at leadership level, is risk management: what happens if this client leaves, and what should be done to diversify the customer base so no single relationship carries this much weight.
That framing is correct as far as it goes, but it treats the concentration as a static fact about the revenue line rather than a dynamic fact about the organisation itself. Revenue concentration of this kind rarely arrives without changing how the business actually operates — and by the time the concentration is visible enough to discuss as a risk, the operational changes it has already caused are frequently substantial and largely undocumented as decisions, because none of them were made as a single decision at all.
What leaders usually conclude
The standard response to customer concentration is commercial: grow other accounts, win new logos, reduce the percentage by expanding the denominator rather than shrinking the numerator. This is sound strategic advice and, in isolation, addresses a real vulnerability. What it tends to miss is a second, quieter form of dependency that grows alongside the commercial one: operational adaptation.
A large, demanding client rarely stays passive within a supplier’s existing way of working. Over time, delivery gets adjusted to fit that client’s specific requirements. Scheduling shifts to accommodate their cadence. Reporting formats, escalation routes, even internal role definitions can bend, gradually and reasonably, toward what this one relationship needs — each adjustment justified individually, each one small enough not to register as a strategic choice. The organisation has not decided to restructure itself around one client. It has simply made a long sequence of locally sensible accommodations that, added together, amount to something close to that.
What the evidence suggests
Consider an organisation in exactly this position. Delivery, scheduling and structure have each been adapted, incrementally, to serve the largest client’s requirements. Nobody made a single decision to reorganise around this relationship — it happened through many individually reasonable choices, each made in the moment it was needed. The consequence, visible now, is that serving smaller clients has become progressively less efficient, not because those clients changed, but because the organisation’s operating model quietly shifted shape around the dominant one, leaving less slack and less standard process available for everyone else.
This is the deeper observation the concentration risk framing tends to obscure: the concentration is not only commercial, it has become structural. Reducing dependence on this client is no longer purely a sales-and-marketing exercise of winning new business. It now requires operational change — reworking scheduling, delivery and structure that were never designed with any other client primarily in mind — because the organisation the business currently has is, in a real sense, an organisation built to serve this one relationship well, with everything else fitted around the edges.
Edith Penrose’s foundational work on the growth of the firm is instructive here, even though her focus was managerial capacity rather than customer relationships specifically. Penrose argued that organisations grow along the paths their existing resources and capabilities make available to them, and that this path-dependency is largely invisible from the inside because each step looks like a sensible extension of what the organisation already does well. The same logic applies to concentration around a dominant relationship: each accommodation was a sensible extension of serving a good client better, and the cumulative direction of travel — toward an operating model shaped around one account — was never chosen as a destination, only arrived at as the sum of many reasonable steps.
This pattern also tends to vary by how the dominant relationship began. Where a large client was won deliberately, with the organisation actively pursuing and shaping capability around them from the outset, the resulting structural adaptation is at least partly a chosen trade-off, weighed — even if imperfectly — against its risks. Where a client simply grew into dominance over time, starting as one relationship among several and expanding faster than the rest of the business, the structural adaptation tends to be far less deliberate, because no single point existed at which anyone assessed whether the relationship’s growing share of revenue justified the growing share of the operating model being quietly rebuilt around it. The second path is more common than the first, and it is also the one leadership teams are more likely to discover after the fact rather than choose in advance.
A further complication is that the people best placed to notice the accommodation — those directly delivering the work — often experience each individual adjustment as simply good client service, not as evidence of a structural shift. Flagging the pattern usually requires someone with visibility across multiple functions, since delivery may see the scheduling changes, while operations sees the process changes, and neither necessarily sees the other’s adaptations as part of the same underlying trend.
There is a genuine tension leadership teams face once this becomes visible. Unwinding the accommodations that serve the dominant client risks damaging the relationship that currently anchors much of the business’s revenue and, often, its operational learning. Leaving them in place risks deepening a dependency that already extends well beyond the commercial exposure most risk registers are built to capture. Neither choice is clean, and the evidence does not point to a single correct answer — only to the fact that the decision is bigger, and more structural, than it initially appears when framed purely as customer concentration.
For how this pattern presents in other kinds of organisation, see other sectors.
Questions worth considering
- How many of the organisation’s current delivery, scheduling or structural norms exist specifically because of one client’s requirements, rather than as a deliberate general design?
- If the dominant relationship ended tomorrow, what would the organisation’s operating model actually look like — and would it still work well for everyone else?
- Was the current level of accommodation ever assessed as a cumulative whole, or only ever approved one reasonable step at a time?
This perspective is part of Growth.
Your team is facing similar challenges?
Subscribe to The Riddle Ledger
Perspectives are sent as they are published, with no promotional email, and you can unsubscribe at any time.