Customer Concentration Risk: What If Your Largest Account Leaves?

An ARR concentration view compares recurring contract values at a point in time. A recognized-revenue view compares revenue over a period. Either can be useful, but they answer different questions. Do not divide one account’s annual contract value by the company’s monthly revenue.

Stripe describes customer concentration as dependence on a small customer group. This guide uses an original ARR example. Exclude one-time fees if your denominator excludes them, and use a consistent currency conversion policy across the register.

Example: a SaaS company has EUR 1,000,000 of ARR across 100 customers. Its largest customer represents EUR 180,000. The next four represent EUR 90,000, EUR 70,000, EUR 60,000 and EUR 50,000. The other 95 customers contribute EUR 550,000.

If the largest customer leaves and all others stay unchanged, ARR falls to EUR 820,000. Customer-count retention could still be 99% for this starting group, while retained starting ARR is 82%. That difference is not a calculation error. The larger account carries more revenue weight.

This scenario assumes a whole-account loss, no expansion, no contraction elsewhere and no new sales. It is an exposure calculation, not a prediction. Do not assign an 18% probability of churn simply because the account represents 18% of ARR. The share describes impact, not likelihood.

Several Company records may belong to one purchasing group. Two subsidiaries can have different contacts while depending on the same budget owner. Conversely, matching domains do not prove that accounts should be merged. Keep the legal and commercial relationships clear.

Create a separate group view when several agreements depend on one renewal decision. Explain the grouping rule and keep the original customer detail. This can reveal exposure that a simple top-five list misses without changing how finance recognizes the individual accounts.

An account representing 18% of ARR deserves an understood owner and renewal process. Check the agreements, decision dates, customer goals and current evidence. Separate verified concerns from assumptions. A large account with a distant renewal and a smaller one facing an immediate decision need different next steps.

A proposed review sheet can include customer ID, ARR, share of total, group relationship, next agreement date, decision owner, evidence checked date and next action. These are worksheet suggestions, not built-in fields or a scoring model. Use the renewal forecast guide to connect upcoming agreements to a due-period view.

Account coverage may mean bringing in a second relationship owner, verifying a procurement timeline or resolving an open delivery issue. Business planning may mean testing how the team would respond to a large loss. Acquiring more customers can reduce dependence over time, but it does not answer an open decision at the largest account today.

Review concentration when revenue, ownership or contract structure changes. Keep a historical snapshot so that genuine diversification can be separated from an account being renamed or split into records. The goal is a decision you can explain, rather than a color on a dashboard.

Use CLE Index to explore what retention assumptions mean for the current revenue base over time. Use a customer register for named-account shares and loss scenarios. Do not treat a portfolio benchmark as evidence that a particular customer will leave.

Renewal Radar can identify supported Company-level renewal follow-up needs in HubSpot. Its revenue-at-risk number is also different from a concentration share. Label each measure so a reader knows whether it describes dependence, current attention or an assumed future path.