The 80/20/30 Rule

Most CX leaders know the 80/20 rule. Eighty percent of your revenue comes from twenty percent of your customers. It’s the Pareto Principle, named after the Italian economist who observed it in land distribution and which has turned out to apply, with remarkable consistency, to almost every business context you care to examine. Support contact rates. Bug impact. Revenue concentration. You can point it at almost anything and find the ratio roughly holds.

What fewer people know is the amendment. The part that makes the original rule actionable rather than just descriptive. It’s called the 80/20/30 rule, and it changes the question you should be asking about your customer base from “who is making us money?” to “who is costing us money — and what are we going to do about it?”

What the 80/20/30 rule actually says.

The rule works like this. Eighty percent of your revenue comes from the top twenty percent of your customers. That part you probably already knew. But the rule adds a second, less comfortable observation: eighty percent of your costs come from the bottom thirty percent of your customers.

Those two things together describe a situation that most support leaders are living inside without having named it explicitly. Your highest-value customers are not, typically, your highest-contact customers. The accounts generating the most revenue tend to have capable users, good onboarding, and direct access to account management when something goes wrong. They contact support less, escalate less, and when they do engage with your team, the issues tend to be well-articulated and resolvable.

Your bottom thirty percent — the low-revenue, high-contact accounts — are a different story. They generate a disproportionate share of your ticket volume, require more agent time per resolution, escalate more frequently, and are less satisfied on average despite (or sometimes because of) the amount of attention they receive. They consume the resources that, freed up, would let you serve your best customers better.

This isn’t a new observation. Harvard Business Review has written about customer profitability analysis for decades — the finding that a segment of most companies’ customer bases is genuinely unprofitable when the full cost-to-serve is calculated is well established. What’s less well established is what support leaders should actually do about it.

Why support leaders rarely see this clearly.

There are two reasons this dynamic is usually invisible at the support leadership level, and both are worth naming because they’re structural rather than personal.

The first is that support metrics are almost never correlated with revenue data. Your support dashboard tells you ticket volume, handle time, CSAT, and SLA compliance. It almost never tells you what those tickets cost to resolve, or what revenue the customer generating them represents. You can measure FCR without ever asking whether the customer you’re measuring it for is worth the investment. The data systems that hold support metrics and the data systems that hold customer revenue data are almost always separate, and joining them requires someone to decide it’s worth doing.

The second is that support leaders are evaluated on customer satisfaction broadly — not on the efficiency of that satisfaction relative to the revenue each customer represents. A support leader who achieves 92% CSAT across their entire customer base looks good. A support leader who achieves 92% CSAT but has concentrated 60% of their team’s time on accounts representing 8% of revenue has a problem that the CSAT number doesn’t surface.

This is the conversation I wrote about in the Support Is Not a Cost Center post: the most credible support leaders are the ones who understand their cost-to-serve and can speak to it in the language finance uses. The 80/20/30 rule is a framework for that conversation — it gives you a way to describe the efficiency problem and propose a structural solution.

Running the analysis: what you actually need.

To apply the 80/20/30 rule in your own operation, you need to be able to answer two questions for each customer account: how much revenue do they represent, and how much support resource have they consumed over a defined period?

Revenue is typically available from your CRM or finance system. Support consumption is in your ticketing system — volume of cases opened, handle time per case if you track it, number of escalations, and time to resolution. The join between those two data sets is what most support operations don’t have automatically, but it’s usually achievable through a data export and a spreadsheet analysis.

Once you have both data points at the account level, sort by revenue descending and look at the distribution. You’re looking for: the top twenty percent of accounts by revenue — what percentage of your support volume do they generate? And the bottom thirty percent by revenue — what percentage of your support volume do they represent? If the distribution looks anything like the 80/20/30 model, your support team is spending a disproportionate amount of its time on your lowest-value accounts.

This is also where a properly designed VoC programme intersects with the 80/20/30 analysis. CSAT and NPS data by customer tier often reveals something counterintuitive: your bottom thirty percent frequently has lower satisfaction scores despite consuming more support resource, because volume alone doesn’t create satisfaction — the right kind of intervention does. Understanding what that bottom tier actually needs, rather than just measuring how much they contact you, is the starting point for a more strategic response.

What to do with each tier.

Once you have the analysis, you have three tiers to manage — and each requires a different strategy.

Your top twenty percent. These accounts deserve disproportionate attention, but not necessarily more reactive support contact — which they may not be generating much of anyway. What they deserve is proactive engagement: regular check-ins from customer success, faster escalation paths when they do contact support, and a dedicated account team that knows their environment well enough to anticipate problems before they become incidents. Your SLA framework should reflect this — premium tiers with faster response commitments aren’t just a commercial offering, they’re an operational acknowledgment that these customers have earned differentiated treatment.

Your middle fifty percent. This is your growth segment — accounts with meaningful revenue potential that haven’t fully realised it yet, and whose support experience is often generic rather than tailored. The goal here is to understand what’s preventing them from becoming top-tier accounts. Are they underusing the product because they haven’t been trained on the features that would deliver value? Are they contacting support for things a better knowledge base would resolve? Is there a product gap that, if addressed, would expand their footprint?

The support data on this segment is particularly valuable because it often reveals product gaps and onboarding failures that the product and customer success teams haven’t identified. Feeding those insights back upstream — to product, to implementation, to the teams that own the customer journey before the customer reaches support — is one of the highest-value things a support organisation can do. It converts reactive contact into proactive improvement.

Your bottom thirty percent. This is the uncomfortable tier, and it requires honesty about what you’re actually trying to achieve. The bottom thirty percent by revenue is consuming a disproportionate share of your support resource. The question is why — and the answer determines what you do about it.

Some of these accounts are low-revenue because they’re small businesses or early-stage companies with high support needs relative to their current spend. If they have growth potential and are on an expansion trajectory, high support consumption now may be justified by the lifetime value curve. Distinguish between accounts that are low-revenue-now and accounts that are low-revenue-forever before you make strategic decisions about them.

For accounts that are genuinely high-cost with no realistic path to higher revenue, the options are structural. A tiered service model where support entitlements are defined by contract tier — faster response, dedicated resources, or extended hours available at a premium — converts the cost-to-serve problem into a pricing conversation. Improved self-service, specifically targeted at the issue types driving high contact rates in this segment, reduces the volume without reducing the customer’s ability to resolve their problems. And in some cases, the honest answer is that certain accounts are not commercially viable at the support level they require, and the business decision about how to handle them sits above the support leader’s remit but should be surfaced with data.

The broader point.

The 80/20/30 rule is not an argument for abandoning low-revenue customers. It’s an argument for understanding the full economics of your customer base and making deliberate decisions about how to allocate your team’s finite capacity.

Every support leader is making allocation decisions constantly — which tickets to prioritise, how to staff for peak periods, where to invest in self-service versus agent handling. Most of those decisions are made without reference to the revenue distribution of the accounts those tickets represent. The 80/20/30 rule is a prompt to make that data visible and let it inform the decisions more explicitly.When you can tell your CFO that you know which customer segment accounts for 80% of your support costs, that you’ve mapped it against revenue, and that your tiered service strategy is designed specifically to address that imbalance — that is the conversation that earns support a seat at the table rather than a line item on a cost reduction initiative. The analysis takes an afternoon. The credibility it builds takes much longer to earn any other way.