Customer concentration

Customer concentration measures how much revenue, margin or operational load depends on a small number of customers or buying groups. It is both a commercial fact and an operating condition.

In brief

A large customer can be a strength. It can stabilise demand, improve utilisation and fund growth. It can also create dependency.

The issue is not only percentage of revenue. A customer may represent 25% of revenue but 50% of planning attention, 60% of exceptions or most of the margin. Concentration must be read through finance and operations together.

Operational definition

Customer concentration can be measured by revenue share, margin share, receivables share, capacity share, exception volume and strategic dependency.

The relevant question is: what would happen to the company if this customer changed volume, terms, timing or requirements?

A concentrated customer base becomes fragile when the operating model adapts around one or few buyers without making the dependency explicit.

Why it matters for SMEs

SMEs often grow through a small number of important customers. This is normal. The danger appears when the company builds capacity, routines and priorities around them without a plan to manage dependency.

One customer’s forecast can shape production. One customer’s payment terms can shape the cash cycle. One customer’s custom requirements can increase cost of variety.

For buyers and investors, concentration affects resilience and valuation because the future depends on fewer relationships.

Observable signals

Look for one customer driving planning priorities.

Look for special rules that exist only for one account.

Look for payment timing tied to a few buyers.

Look for capacity reserved informally for one relationship.

Look for margin or rework concentrated in a small customer group.

Look for teams saying “we cannot say no to them”.

Common mistakes

The first mistake is measuring only revenue concentration.

The second is ignoring margin concentration.

The third is accepting operational exceptions without pricing or governance.

The fourth is treating dependency as loyalty rather than structural exposure.

Operational example

A company has one customer representing 38% of revenue. The relationship is profitable, but the customer also creates urgent changes, custom formats and late forecast shifts.

When the company reads concentration operationally, it sees that the customer consumes a disproportionate share of planning attention and WIP. The response is not to reject the customer. It is to define service rules, price exceptions and build a commercial plan that reduces dependency over time.

Diagnostic questions

What share of revenue comes from the top customers?

What share of margin comes from them?

What share of exceptions, WIP or planning changes do they create?

Which terms or promises are unique to them?

What would happen if volume changed quickly?

Which actions reduce dependency without damaging the relationship?

Practical implications

Measure concentration in more than one way: revenue, margin, receivables, capacity and exceptions.

Then decide which concentration is acceptable, which must be priced and which must be reduced.

Build rules for exceptional service so dependency does not quietly redesign the company.

MARTRO reading

In MARTRO’s reading, customer concentration is a bridge between finance, operations and governance. It affects cash cycle, capacity, cost of variety, leverage and fragility.

The structural question is not only “how much do they buy?” but “how much of the company has adapted around them?”

Frequently asked questions

Is customer concentration always bad? No. It can support growth. It becomes dangerous when unmanaged.

What should be measured besides revenue share? Margin, receivables, capacity use, exceptions and planning dependency.

Can a profitable customer still create fragility? Yes, if the company adapts too much around them without rules or alternatives.

How do we reduce concentration? Through commercial diversification, pricing of exceptions, service boundaries and capacity rules.

Why does it matter in due diligence? Because future performance depends more heavily on a small number of relationships.