Customer concentration asks how much revenue depends on a small number of accounts. A common calculation divides revenue from the largest customer or group of customers by total revenue for the same period and basis. The metric can reveal dependency, but it does not prove that a large account is unhealthy: contract duration, margin, collection risk, switching cost, pipeline coverage, and relationship quality matter. This lesson builds a top-five view with transparent account hierarchy and scenario math rather than relying on a borrowed benchmark.

VISUAL LESSON

What you will learn

  1. 01Define revenue and customer-account scope.
  2. 02Calculate top-one and top-five concentration.
  3. 03Model scenarios and assign risk actions.
Five emphasized customer revenue columns feed a concentration gauge with loss and growth scenario paths
Concentration analysis combines portfolio share, account hierarchy, contract and margin context, and scenario planning—not one alarming percentage.

ILLUSTRATIVE WORKED EXAMPLE

Work an illustrative top-five concentration example

Total annual revenueIllustrative net revenue basis
$1.00M
Largest customer12% of total
$120K
Top five customers38% of total
$380K
All other customersDistributed across the rest
$620K
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Build the concentration table and scenario view

Scope01Define revenue and account hierarchy

Choose gross or net recognized revenue, period, currency treatment, parent-child rollup, exclusions, and source-system reconciliation.

Math02Rank and calculate shares

Sum revenue by resolved customer, divide the largest and top-five sums by total revenue, and retain absolute revenue and margin.

Scenarios03Model loss, growth, and diversification

Recalculate revenue, margin, and concentration after plausible account changes, then assign protection and pipeline actions with owners.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Resolved accounts → ranked revenue → concentration shares → action scenarios

ResolveRevenue and hierarchy
CalculateTop-one and top-five
RespondProtect and diversify

THE LEAD ATLAS METHOD

Lead Atlas Data can produce a custom business-contact list for diversification campaigns aimed at specific markets, locations, and business categories, helping the team widen the prospect base without confusing new-pipeline activity with existing-customer revenue.See how custom list research works ↗
01

Define the revenue basis and period

Choose booked, billed, collected, gross recognized, or net recognized revenue based on the decision, and use the same basis for every customer and the total. Set the period, business timezone, currencies and conversion date, refunds, credits, taxes, pass-through costs, intercompany activity, and source system.

Reconcile the scoped total with finance before ranking customers. A concentration percentage built from CRM opportunity values or mixed currencies can look precise while disagreeing with the revenue the business actually recognizes.

02

Resolve the customer hierarchy

Decide whether concentration is measured by legal entity, billing account, parent company, brand, franchise group, agency, or another economic relationship. Create a reversible mapping from source accounts and invoices to the reporting customer and flag uncertain relationships.

Do not hide dependency by splitting one parent into branches, or exaggerate it by merging unrelated franchisees. Preserve both parent and operating-location views when the risk and commercial ownership differ.

03

Calculate top-one and top-five shares

Aggregate revenue by resolved customer, sort from largest to smallest, and calculate the largest customer’s revenue divided by total revenue and the sum of the five largest divided by total revenue. Show absolute revenue, percentage, gross margin, receivables, contract end, and renewal context beside each account.

In the illustrative example, the largest customer contributes $120,000 of $1,000,000, or 12%, and the top five contribute $380,000, or 38%. Those values describe the example only; they are not a benchmark or automatic risk threshold.

04

Run loss, growth, and margin scenarios

Model the loss of the largest account, partial contraction, delayed payment, renewal, expansion, and the addition of diversified revenue. Recalculate total revenue, gross profit, top-five composition, capacity, cash needs, pipeline coverage, and the time required to replace the contribution.

If the $120,000 largest account disappeared in the example, revenue would fall to $880,000 and the remaining former top-five accounts would contribute $260,000, about 29.5% of the new total. The lower concentration percentage would not make the revenue loss good; scenarios must keep absolute impact visible.

05

Assign protection and diversification actions

For each major account, record relationship owner, stakeholders, value delivered, service risks, renewal timeline, receivables, margin, concentration exposure, and a realistic protection plan. Separately define target segments, offer, pipeline volume, acquisition cost, capacity, and timeline for diversification.

Deliverable: revenue-basis contract, finance reconciliation, account-hierarchy map, ranked customer table, top-one and top-five calculations, margin and receivables context, loss and growth scenarios, account-protection plans, diversification brief, pipeline coverage view, owners, review cadence, and documented thresholds chosen by the business.

THE TAKEAWAY

Use one revenue basis and account hierarchy, calculate top-one and top-five shares, test realistic loss and growth scenarios, add margin and contract context, and turn the analysis into named diversification and account-protection actions.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.