customer concentrationrevenue concentrationrenewal churnb2b saassaas metrics

One Customer at 10% of Revenue Triggers an SEC Disclosure Rule. Most Private SaaS Companies Have Never Run Their Own Number.

Public companies must disclose any customer over 10% of revenue. Here's why that threshold should worry you long before you're anywhere near an IPO.

XY
19 November 2026 · 9 min read

Ask most SaaS founders what percentage of revenue comes from their single largest customer and you'll get a guess, not a number. It's one of the few metrics that's simultaneously easy to calculate — take one customer's ARR, divide by total ARR — and almost never calculated, because nobody's forcing the question until a board deck, a term sheet, or an acquirer's diligence checklist demands it. By then it's too late to do anything about the answer except explain it.

Key stat
10%
The share of total revenue from one customer that legally requires disclosure under US accounting rules (ASC 280) once you're a public company
Source: FASB ASC 280 (Segment Reporting), SEC Regulation S-K Item 105

The number that becomes a legal disclosure once you go public

Under ASC 280, any company reporting under US GAAP has to disclose the existence of a customer that makes up 10% or more of total consolidated revenue. It doesn't require naming the customer, and it doesn't apply to private companies filing no public financials — but it's not an arbitrary accounting quirk either. The 10% line exists because regulators concluded that's roughly the point where losing one relationship stops being a normal business event and starts being the kind of fact a reasonable investor would want to know before buying the stock.

Duck Creek Technologies' FY2020 10-K is a clean, real example of what that disclosure looks like in practice: the filing states that one customer accounted for approximately 10% of total revenue that year, flagged explicitly as a risk factor. That's not a hypothetical threshold from a consulting deck — it's a real company telling real investors, in a legally binding document, exactly how exposed it was to one relationship ending.

Private SaaS companies don't file anything like this, which is exactly the problem. The accounting rule doesn't kick in until you're already public, by which point the concentration has usually been building for years. The risk is identical whether anyone's required to disclose it or not — what changes is whether you're the one who finds out first, or whether your acquirer, your board, or your biggest customer's own procurement review finds out first.

Why the same dollar loss hits differently depending on where it comes from

A SaaS company losing $600,000 in ARR looks identical on a revenue line whether that $600,000 came from one account or from two hundred small ones. It is not identical anywhere else that matters. Losing two hundred small accounts to the same cause tells you something — a pricing problem, a competitive loss, an onboarding failure — and that something is usually fixable before it spreads further. Losing one account that happened to be twenty percent of your revenue tells you almost nothing generalizable, and it takes your growth rate, your gross margin, and your next fundraising conversation down with it in a single quarter.

M&A advisory firm L40 runs the math on exactly this scenario. Take a company at $3M ARR with 30% EBITDA margins, where one client is worth $900,000 — 30% of revenue. If that single account churns, revenue doesn't just drop to $2.1M; EBITDA compresses to roughly $630,000, because the fixed costs that supported serving that account don't disappear with it. The business doesn't just get smaller. It gets structurally less profitable at the same time, in the same breath, from a single non-renewal decision made in someone else's procurement meeting.

ScenarioARR beforeARR after lossRevenue impact
200 small accounts, evenly distributed, lose 10 to churn$3,000,000$2,850,000-5%, isolated and explainable
One account at 30% of ARR churns$3,000,000$2,100,000-30%, EBITDA falls to ~$630K at a 30% margin

Source: worked example from L40 Partners, SaaS/tech M&A advisory, "Customer Concentration Risk."

Diligence teams price this in directly. A business with the same growth rate and the same gross margin as a peer, but with a meaningfully higher share of revenue sitting in one or two accounts, gets a lower multiple — not because the historical numbers look worse, but because the forward-looking variance is higher. You're not being penalized for what happened. You're being penalized for how much of what happens next depends on one phone call going the right way.

What "too concentrated" actually means, by stage

There's no regulator-issued threshold for private companies, but the guardrails used in practice by pricing and M&A advisors converge on a similar shape: tolerance for concentration shrinks as you get bigger, because the absolute dollars at stake in a single account keep growing even as the relative risk is supposed to be diversifying away.

Maximum recommended share of revenue from one customer, by stage
Under $5M ARR20%
$5M–$50M ARR15%
Over $50M ARR10%

Source: Monetizely, "How to Measure Customer Concentration Risk in SaaS."

The same source puts top-five concentration at under 50% pre-$5M ARR, tightening to under 40% in the $5M–$50M range and under 30% past $50M. Treat these as reference points, not pass/fail grades — a vertical SaaS product serving a genuinely small addressable market, say five hospital systems or a dozen regional insurers, is going to run hotter than these numbers by the nature of the market, and that's a different conversation about whether the business should exist at all, not whether a single quarter's concentration metric is acceptable. For most horizontal SaaS, though, drifting past these lines without noticing is the actual failure mode, not the number itself.

Where concentration actually detonates: renewal

Concentration risk isn't abstract until renewal, and it rarely detonates for product reasons. We've written about champion turnover as one of the strongest single-signal predictors of non-renewal in SaaS — an unmanaged champion change carries roughly a 51% chance of churn within 12 months, climbing higher for an executive sponsor. Run that signal against a diversified base and it costs you one account out of two hundred. Run it against your single largest customer and it's the same signal threatening the same 20–30% of your business all at once, from one person changing jobs.

Contract structure compounds it further. We've covered how co-terming collapses every product an account buys onto one shared renewal date — convenient for procurement, but it converts several independent checkpoints into a single binary event. A whale account is exactly the wrong place to let that happen by default. If your largest customer is already a disproportionate share of revenue, deliberately staggering their modules' renewal dates where you can — rather than letting procurement's preference for administrative simplicity merge everything onto one date — keeps a bad signal on one product from dragging your single biggest account into a full renewal crisis at once.

What to actually track and do about it

None of this argues for turning away large deals — a $900,000 account is still a $900,000 account, and most SaaS companies would take the concentration risk gladly in exchange for the revenue. The fix isn't refusal. It's treating concentration as a tracked metric with its own playbook, the same way you'd track any other churn risk factor.

  1. Calculate your actual number this quarter. Top customer's share of ARR, and top-five share. If you've never run it, assume it's higher than you'd guess — concentration accumulates quietly while everyone's focused on logo count and growth rate.
  2. Multi-thread concentrated accounts the way sales multi-threads a deal. One relationship carrying 20% of your revenue is the single-threading problem described in our champion turnover piece, just scaled up. Get a second and third stakeholder genuinely engaged, not just cc'd.
  3. Resist co-terming a whale account's add-ons onto one date by default. The administrative convenience that's a reasonable trade-off for a $20,000 account is a structural risk you're choosing to accept for a $900,000 one.
  4. Grow the denominator, not just defend the numerator. The fastest sustainable way to cut a concentration percentage is adding diversified revenue elsewhere, not capping or walking away from the big account. A whale that grows 20% a year while your base grows 40% a year is a shrinking concentration problem even though the account itself is expanding.

Run your own numbers through our churn calculator using your largest account's ACV against your total ARR, and compare what a 51% unmanaged champion-turnover probability costs on that one account versus the same probability spread across two hundred smaller ones. The gap is usually the clearest argument for giving concentration risk its own line in a board deck, well before anyone outside the company asks you to run the number for them.

The self-serve side of this problem is the same shape at smaller scale: a handful of high-ACV power accounts often carry a disproportionate share of a product-led business's revenue too, and a cancellation flow that treats every subscriber identically has no way to recognize when the account trying to leave is the one you can least afford to lose quietly. CancelFlow can route a different, better-resourced save path to your highest-value accounts specifically, which matters a great deal more once you know exactly how much of your revenue a handful of them actually represent.

Frequently asked questions

What is customer concentration risk in SaaS?+

Customer concentration risk is the exposure a company carries when a disproportionate share of its revenue comes from a small number of accounts. It's usually measured two ways: the largest single customer's share of total revenue, and the combined share held by the top five (or top ten) customers. A SaaS company at $3M ARR with one account worth $600,000 has 20% concentration in its single largest customer — meaning one non-renewal can erase a fifth of the business in a single event, regardless of how healthy every other account looks.

What percentage of revenue from one customer is considered risky?+

There's no single legal threshold, but the numbers used in practice cluster tightly. SaaS monetization consultancy Monetizely publishes stage-based guardrails: under $5M ARR, keep any one customer under 20% and your top five under 50%; at $5M–$50M ARR, tighten that to under 15% and under 40%; above $50M ARR, under 10% and under 30%. M&A advisory firm L40 notes that some acquirers flag 10% of revenue from just one or two accounts as high concentration risk on its own, before even looking at the rest of the book.

Why do public companies have to disclose customer concentration?+

US accounting standard ASC 280 requires a company to disclose the existence (though not necessarily the name) of any customer that accounts for 10% or more of total consolidated revenue, as part of segment reporting. SEC Regulation S-K similarly expects a company to describe in its risk factors when the loss of a major customer could have a material effect on the business. Duck Creek Technologies' FY2020 10-K is a real example: it disclosed that one customer accounted for approximately 10% of total revenue that year, naming the exposure explicitly as a risk factor for investors.

How do you reduce customer concentration risk without turning away big deals?+

You don't turn away the deal — you change what happens after you sign it. Multi-thread the account the way sales already multi-threads during the close, so no single departure can take the relationship with it. Resist co-terming every add-on this customer buys onto one renewal date, since that converts several independent checkpoints into one binary event. And keep growing the rest of the base fast enough that the whale's share of total revenue shrinks over time even as the account itself keeps expanding in dollar terms.

Try CancelFlow

Stop losing subscribers today

One script tag. One function call. A live cancellation flow in under 10 minutes.

Start free trial →
← All postsHome