SaaS · Customer concentration and vendor lock-in as hidden financial risk
Bandwidth Inc., a communications platform company, has disclosed in its annual reports that a small number of large customers account for a meaningful share of its revenue. That kind of sentence sits quietly in a 10-KKThe average number of new users each existing user generates through referrals. Above 1.0, growth compounds on itself and becomes exponential.View full definition → risk factor, yet it is exactly the line a lender's credit committee or a private equity diligence team should circle in red. One canceled contract or one renegotiated enterprise deal, and a "growth story" can turn into a covenant breach overnight.
This lesson covers two connected risks in SaaS finance: customer concentration (revenue leaning on a small number of clients) and vendor lock-in (the company's own dependency on a single cloud provider). Both are structural and contractual, and both often stay invisible until stress hits.
Why concentration is a financial risk, and a commercial one
SaaS valuations are built on recurring revenue multiples. Investors pay 4x to 8x annual recurring revenueannual recurring revenueAnnual Recurring Revenue (ARR) is the normalized, predictable revenue a subscription business expects to earn from active contracts over a single year.View full definition → (ARR, the annualized value of active subscription contracts), an estimate based on 2025 market conditions, because that revenue is assumed to be durable and diversified.
Customer concentration breaks that assumption. If one client represents 15% to 20% of ARR, its renewal decision becomes a single point of failure that can move revenue growth by double digits.
Where this shows up in financial documents:
- Form 10-K "Risk Factors" section (US public companies, filed with the Securities and Exchange Commission, SEC)
- Credit agreements with concentration covenants tied to borrowing base calculations
- Private equity data rooms, in customer cohort and logo-retention analyses
A useful benchmark: enterprise SaaS companies whose top 10 customers exceed 30% of revenue are flagged more often in lender credit risk models. This is an estimate based on typical asset-based lending (ABL) practice, not a published rule.
Worked example: covenant math
Say a SaaS company's credit agreement requires net revenue retentionnet revenue retentionNet Revenue Retention measures the percentage of recurring revenue retained and grown from existing customers over a period, including upsell and expansion, net of downgrades and churn.View full definition → (NRR, the percentage of recurring revenue kept from existing customers year over year, including expansion and contraction, excluding new logos) to stay above 100%.
- Total ARR at the start of the year: $50 million
- Top client: $9 million (18% of ARR)
- The other $41 million grows 8% through expansion, to about $44.3 million
If the top client renews flat, ending ARR from existing customers is $9m + $44.3m = $53.3m, so NRR is about 106.6%. Comfortably compliant.
If the top client churns at renewal, ending ARR is $44.3m, so NRR is $44.3m / $50m, about 88.6%. Same product, same team, same growth in the rest of the book. One logo loss flips the covenant from compliant to breached, and the lender can reprice the debt or demand acceleration.
Vendor lock-in: the other side of the ledger
Concentration risk also covers who you depend on to deliver the product, alongside who pays you.
Most SaaS companies run on one hyperscaler: Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP). Synergy Research Group estimates put AWS at roughly 30% of global cloud infrastructure spend, Azure around 20% to 25%, and GCP around 12% to 13% (see Synergy's public commentary for current splits).
That dependency creates real financial exposure:
- Pricing power asymmetry. Migrating a production workload off AWS can cost months of engineering time plus egress fees (charges for moving data out of a cloud provider), which gives the hyperscaler leverage in renewal talks.
- Committed-use contracts. Many SaaS firms sign multi-year committed spend agreements (for example, the AWS Enterprise Discount Program) to get discounts. These behave like take-or-pay obligations and sometimes appear in the "commitments and contingencies" footnote.
- Margin compression. Hosting is a major cost of goods sold line for SaaS. If a provider raises prices or a discount tier expires, gross margingross marginGross margin is the share of revenue left after subtracting the direct cost of producing goods or services, expressed as a percentage of revenue.View full definition → can drop several points with no change to the product.
- Outage exposure. On 20 October 2025, a failure in AWS's us-east-1 region took down or degraded services at thousands of companies for most of a day. SaaS vendors on that region faced SLASLAA formal commitment defining the service level a provider guarantees to a customer, with measurable targets and consequences if they are missed.View full definition → credits and support costs, and some lost customer trust, for an incident they could not fix themselves.
Regulatory and disclosure framework
There is no SaaS-specific regulator, but several existing regimes touch this risk:
- SEC Regulation S-K, Item 105 requires US public companies to disclose material risk factors, which in practice includes customer concentration and dependency on third parties such as cloud providers.
- The EU Digital Operational Resilience Act (DORA), applicable since 17 January 2025, requires financial entities in the EU to manage ICT (information and communication technology) third-party risk, including concentration risk. The obligations flow down to SaaS vendors through contracts. In November 2025 the European Supervisory Authorities published their first list of critical ICT third-party providers under direct EU oversight, and it includes the major hyperscalers. See the EIOPA DORA overview.
- US bank regulators (OCC, Federal Reserve, FDIC) issued interagency guidance on third-party risk management in June 2023. It asks banks to consider concentration risk, including when one critical vendor (often a cloud provider) serves many regulated institutions at once.
This matters for SaaS finance teams because regulated customers such as banks and insurers now push audit rights, exit plans and incident reporting terms down to their SaaS vendors. Those terms change the vendor's cost to serve and its renewal risk.
Due diligence checklist: what to actually pull and read
When assessing a SaaS target or counterparty, request and review:
- Customer cohort table by ARR band: what share of revenue sits in the top 5, top 10 and top 20 accounts.
- Contract renewal calendar. Concentration risk is worse if large contracts cluster around the same renewal date.
- Termination-for-convenience clauses: can a large client walk with 30 days' notice, or is there a multi-year commitment with penalties?
- Cloud spend commitment schedule: total committed spend, discount tier thresholds, and penalties if usage falls short.
- Exit feasibility. Has the company ever costed a migration off its primary cloud provider, or at least a move to a second region? No analysis at all is a red flag.
- Covenant definitions in credit agreements. Check whether NRR, ARR and concentration triggers are defined precisely, since vague definitions create dispute risk in a downturn.
A free reference for how analysts frame these metrics is the Bessemer Venture Partners State of the Cloud report, published annually, which benchmarks retention and growth norms across public SaaS companies.
Knowledge check
1. Why does customer concentration undermine the logic behind SaaS revenue multiples (e.g., 4x-8x ARR)?
2. A private equity diligence team reviewing a SaaS target's customer cohort analysis discovers the top client represents 18% of ARR. What is the most appropriate financial interpretation?
3. Why is customer concentration described as a risk that is 'structural, contractual, and often invisible until stress hits' rather than simply a commercial issue?
4. Select ALL correct answers about where customer concentration risk typically becomes visible in financial documentation.
Select all the correct answers.
5. Select ALL correct answers about why customer concentration and vendor lock-in are grouped together as related financial risks in SaaS companies.
Select all the correct answers.
Reading the balance of power
Three actors pull in different directions:
- The SaaS company wants diversified revenue and cloud flexibility, but both cost money and slow product work.
- The enterprise customer wants deep integration and volume discounts, which naturally concentrates spend with fewer vendors.
- The hyperscaler wants committed, sticky workloads, and gets them through egress costs, proprietary services and discounts that reward exclusivity.
None of them is acting in bad faith. The risk is structural. Each actor's rational incentive points toward concentration, and concentration is what breaks financial resilience under stress: a lost client, a price increase, a regional outage.
🎬 [VIDEO: "AWS Outage Shows Danger of Cloud Computing Concentration" - youtube.com - a Bloomberg/CNBC-style news segment on how a single hyperscaler outage, such as the October 2025 us-east-1 incident, cascades into financial and operational risk for dependent companies; search the title on YouTube for the most current segment]
A quick technical lens: spotting concentration in ARR data
Finance teams can approximate concentration risk with a simple calculation, no engineering background needed:
top_10_client_ARR = [9, 4, 3, 2.5, 2, 1.8, 1.5, 1.2, 1, 0.9] # in $ millions
total_ARR = 50 # in $ millions
concentration_ratio = sum(top_10_client_ARR) / total_ARR
# = 26.9 / 50 = 0.538 -> 53.8%A ratio above roughly 40% to 50% (an informal estimate, with no legal threshold) is usually treated by lenders and acquirers as elevated risk. Expect tighter covenants, escrow holdbacks or purchase price adjustments in an M&A deal.
Key Takeaways
- One renewal can decide covenant compliance: in the example, losing an 18% client moves NRR from about 107% to about 89%.
- Vendor lock-in is the mirror-image risk. Committed spend, egress costs and outages like the October 2025 AWS incident hit margins and customer trust.
- Regulation now names this risk: SEC Item 105 disclosure in the US, the 2023 interagency guidance for banks, and DORA in the EU, which since November 2025 directly oversees designated critical cloud providers.
- Pull the customer cohort table, renewal calendar, cloud commitment schedule and termination clauses, not just the ARR growth chart.
- Treat a top 10 concentration ratio above roughly 40% to 50% as a flag for tighter deal terms, and confirm against current lender or buyer practice.