Too Dependent on One Customer
in B2B SaaS

The short answer

Concentration is only a problem in proportion to how easily the customer could churn, which is a question about switching costs visible in net revenue retention rather than about percentages of ARR. What makes this harder for B2B SaaS companies is structural: growth has fallen from 42% to 32% while 60% of revenue sits in the segment with the worst economics. Any credible answer therefore has to hold net revenue retention and CAC payback in the same view, which is exactly where most internal analysis stops because the two live in different systems.

A customer that accounts for a large share of ARR is dangerous or fine depending entirely on the structure underneath. If they can replace you within a quarter, that is an existential exposure visible in a sudden drop in net revenue retention. If replacing you means re-engineering their stack and losing land and expand momentum, it is a strong position that happens to look concentrated.

The trap is that concentration usually comes with worse economics: the large customer negotiates a lower ACV, demands more service that lengthens CAC payback, and pays on extended terms that compress gross margin, 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 when measured by segment gross margin and CAC payback.

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 ARR in the breakdown the CEO reviews each month.
✓ That customer shows materially worse ACV and CAC payback than the rest of the base.
✓ Losing them would require immediate cuts to engineering or support rather than a plan to reallocate capacity.

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

Who this is for — and who it is not

It is for you if you run or finance a B2B SaaS company 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 B2B SaaS company. 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 TechNova Solutions, a sample company profile used for testing rather than a customer — $45M ARR, 280 engineers.

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 B2B SaaS companies it works through net revenue retention, CAC payback, ACV by segment and gross margin, 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 b2b saas than in other industries?

Materially, yes. Growth has fallen from 42% to 32% while 60% of revenue sits in the segment with the worst economics — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are net revenue retention, CAC payback, ACV by segment, 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 B2B SaaS company?

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 net revenue retention and CAC payback. 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.