Revenue Is a Volume Signal, Not a Value Signal
Two customers can pay you the same amount in a given quarter and leave your business in completely different shape. One pays on schedule, uses the product as designed, and rarely calls support. The other negotiates a discount, asks for a custom integration, pays late, and generates a stream of small exceptions that your team quietly absorbs. On a revenue report, they look identical. Economically, they are not.
This isn’t a reason to distrust growth — it’s a reason to look past it. A business can be adding revenue every month while becoming less efficient to serve, because the mix of customers it’s adding skews toward the expensive kind. Growth multiplies whatever economics you already have, good or bad.
The Largest Customer Isn’t Always the Best One
It’s tempting to assume your biggest accounts are your best accounts — they bought the most, after all. A well-known case from a Swedish manufacturer complicates that assumption: once the company built a more detailed way of assigning selling, ordering, and administrative costs to individual customers, it discovered that two of its three largest customers by sales volume were among its least profitable. The most profitable 20% of its customers generated roughly 225% of total company profit, while the least profitable 10% wiped out about 125% of it.
That’s not an argument that big customers are bad or that every customized account is a loss — some large, high-touch relationships are genuinely worth the extra cost, for revenue, credibility, or strategic reasons. It’s an argument for finding out, instead of assuming, because size alone can hide the real picture. A large customer often has the leverage to negotiate deeper discounts, longer payment terms, and more customization — while also placing irregular orders or demanding more attention than a standard account.
Three Different Questions, Often Confused as One
Part of why this slips past founders is that revenue, gross margin, and customer profitability get treated as the same conversation when they’re really three separate ones.
| Metric | What it captures | What it misses | How it should guide decisions |
|---|---|---|---|
| Revenue | Total dollars a customer brings in | Discounts, payment delays, support load, exceptions | Shows momentum, not health — useful for growth tracking, not segment strategy |
| Gross margin | Cost of the product or service itself | Operational costs scattered across sales, support, credit, and admin | Tells you if the core offer is priced right, not if a specific customer relationship is profitable |
| Customer profitability | Revenue minus the full cost of serving that specific account | A clean, universal formula that fits every industry — it has to be built, not assumed | Should shape who you sell to next, not just how you treat existing accounts |
Gross margin is a product question. Customer profitability is a relationship question. Conflating them is how a team ends up celebrating a quarter of strong revenue while quietly building an organization that’s harder and harder to run profitably.
How a Small Request Turns Into a Structural Cost
The mechanism is rarely dramatic. It’s a sequence of small, reasonable-sounding asks that compound.
flowchart LR A[Customer requests discount, custom work, or flexible terms] --> B[Team says yes to close or retain the deal] B --> C[Request becomes standard practice for that account] C --> D[Support, billing, or engineering absorbs ongoing cost] D --> E[Margin erodes without appearing on revenue reports] E --> F[Team reconsiders pricing, segment focus, or standardization]
This is the trap early-stage companies fall into without noticing: the first few paying customers often shape the operating model for everyone who comes after. One account gets a custom report, another negotiates a unique billing cycle, a third needs a different workflow. Each accommodation feels small and justified at the time — the deal mattered, the customer validated the product, the revenue showed up when it was needed. The risk shows up later, when those early exceptions quietly became the template, and the company has added people and complexity to manage requirements that were never meant to scale.
A Checklist for Spotting Costly Behavior After the Sale
Before scaling sales motions or pricing around your early customers, it helps to document what each account actually requires, not just what it pays. A few questions worth tracking per customer or per segment:
- Exceptions: How often does this account need something outside your standard process?
- Support load: How many hours of staff time does it consume relative to its revenue?
- Payment behavior: Does it pay on time and according to terms, or does it generate collection activity?
- Customization: Does it require unique reporting, billing, or service workflows that other accounts don’t?
- Rework or returns: Does it generate disproportionate warranty claims, revisions, or returns?
None of these questions has a universal threshold — what counts as "too much" support time looks different for a SaaS company than for a lender or a manufacturer. The goal isn’t a single formula; it’s a habit of asking the question before the account’s quirks get baked into how the whole company operates.
Redesigning the Relationship, Not Abandoning It
Finding an expensive customer isn’t automatically a reason to end the relationship. The more useful question is whether the economics can be changed. Pricing, service tiers, payment terms, minimum order sizes, and the amount of customization allowed are all levers. A shipping company’s pricing can reflect that an oversized or irregular package isn’t economically interchangeable with a standard one; the same logic lets a software company reserve high-touch service for a premium tier, or a lender adjust terms as risk rises. The principle is simple: when a customer’s behavior changes your cost, your pricing or service structure should be allowed to respond to it.
Writing It Down So the Lesson Sticks
For a small team, the real value of this exercise isn’t a perfect profitability model — it’s a decision record. After reviewing even a handful of accounts, write down what you found: which behaviors (not which customers) tend to drive cost, which terms you’d change next time, and which segment you’d pursue more of if you had the choice. That record becomes the filter for the next sales conversation, the next pricing tier, the next "yes" to a custom request.
Customer profitability is a directional tool, not a verdict — a customer that looks expensive by the numbers may still be worth keeping for the credibility, learning, or cash flow it provides. And none of this replaces proper accounting, legal, or pricing advice tailored to your specific business. But the underlying habit is cheap and worth building early: track not just who buys, but what each pattern of buying costs you to serve — and let that insight, not just the revenue line, decide who you go after next.
