ProblemsToo Dependent on One Customer › Manufacturing

Too Dependent on One Customer
in Manufacturing

Concentration is only a problem in proportion to how easily the customer could leave, which is a question about switching costs rather than about percentages. This page works through it for manufacturers specifically — including an unedited excerpt from a real analysis of a manufacturer.

The short answer

Concentration is only a problem in proportion to how easily the customer could leave, which is a question about switching costs rather than about percentages. Manufacturers carry a specific bind here — the $45M automation case depends on the very customer that causes the margin problem. Until that is priced, contribution per machine hour will keep moving for reasons nobody can attribute, and the debate about revenue concentration will stay a matter of opinion.

A customer at 40% of revenue is dangerous or fine depending entirely on the structure underneath. If they can replace you within a quarter, that is an existential exposure. If replacing you means re-engineering their operation, it is a strong position that happens to look concentrated.

The trap is that concentration usually comes with worse economics — the large customer negotiates harder, demands more service and pays later — so the risk and the margin damage arrive together. Diluting concentration by growing elsewhere is slow; the faster lever is usually repricing the dependency to reflect the risk being carried.

It is also worth separating revenue concentration from contribution concentration. They can point in opposite directions, and the second is the one that would actually hurt.

How to tell this is actually your problem

These three together are the signature. One on its own usually points somewhere else.

✓ One customer exceeds a quarter of revenue
✓ That customer has materially better terms than everyone else
✓ Losing them would require immediate cost action rather than a plan

The move that usually makes it worse. Chasing volume elsewhere to dilute the percentage, which adds cost while leaving the dependency intact.

Who this is for — and who it is not

It is for you if you run or finance a manufacturer and one customer exceeds a quarter of revenue. It is the situation where the numbers are available but nobody has put them in an order that produces a decision.

It is not for you if Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.

Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.

What this looks like when the analysis is actually run

Below is an excerpt from a real run of this analysis on a manufacturer. It is a sample profile rather than a customer, and it is unedited engine output — this is the format you get, on your own numbers.

The subject is Kessler Industrial Components, a sample company profile used for testing rather than a customer — $310M revenue, three plants.

Excerpt from a real Percision run · Customer Value Architecture · sample company profile

The move. Automate Cedar Falls to lock in Customer A manifold volumes at 19% lower cost before Mexican alternates scale.

The leak it closes. Scrap rate reduced from 3.8% to 2.1%; 78-minute changeover reduced toward world-class 25 minutes

The assumption it rests on. Customer A does not activate dual-sourcing before automation payback (3.8 years) — the engine put the probability at 0.65.

What the run committed to
Investment required$45M total
Expected return24% IRR on $45M investment over 7-year Customer A programme life
Revenue, year 1$340M (no incremental revenue; cost protection only)
Revenue, year 2$351M (3% price-down offset by automation savings)
Revenue, year 3$362M (Customer A volume stability plus new Mexican OEM programmes)
Exit criteriaIf Customer A dual-source volume migration exceeds 25% by Month 18, cease further automation spend and redirect remaining capex to Querétaro expansion and aftermarket channel build-out.

This is one move out of a full analysis. Read a complete report — every page, no email required.

What the engine does with this question

This question routes to Proprietary EFF Methodology, one of 29 engagements the platform runs. For manufacturers it works through contribution per machine hour, capacity utilisation, customer concentration and scrap, then produces the sequence rather than a list of options — which move first, what it funds, and the observation that would say the sequence is wrong.

You watch the analysis get built before paying anything. Read a complete report here if you would rather see the depth first.

Questions people ask about this

What level of customer concentration is dangerous?

There is no threshold that means much on its own. What matters is how quickly they could replace you and what happens to your fixed costs if they do. Both are answerable.

Should I turn away business from a large customer?

Rarely on concentration grounds alone, and often on margin grounds. If the largest account is also the worst-priced, the concentration problem and the margin problem have the same fix.

How do I reduce dependency without losing the account?

Increase what it would cost them to leave, and reprice the exposure. Growing a second segment is the right long answer and does not help within the notice period you actually have.

Is this different in manufacturing than in other industries?

Materially, yes. The $45M automation case depends on the very customer that causes the margin problem — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are contribution per machine hour, capacity utilisation, customer concentration, and an answer built on industry-general benchmarks will usually point at the wrong one first.

What data do I need before this analysis is worth running for a manufacturer?

Less than most people expect. Your last twelve months of revenue and cost split the way you already split it, plus whatever you hold on contribution per machine hour and capacity utilisation. The analysis is explicit about what it is assuming where your data stops, which is more useful than waiting for numbers you may never have.

When is Percision the wrong tool?

Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.

Does Percision replace a lawyer, tax advisor, auditor, or AI implementation team?

Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.

Is this what is happening in your business?

Describe the situation in your own words and we will tell you which analysis answers it — before you sign up for anything.

Describe my situation →

Prefer to skip ahead? Go straight to the free diagnostic.