Revenue leakage from missed upsells
The difference between a customer who uses more than they pay for and one who is ready for more, where both go wrong and how to find them systematically.
Revenue leakage from missed upsells arises in two ways. The first: a customer already uses more than they pay for, such as extra users, extra locations or a higher volume than their bundle, and nobody invoices the difference. The second: a customer is clearly ready for a larger package or an additional service, and nobody asks the question. The first is money you have already earned. The second is revenue a competitor can pick up. You find both by putting usage, billing and CRM data side by side instead of looking at each system on its own.
What are the two kinds of missed upsell?
The word upsell is often used for anything a customer could buy more of. For revenue leakage it helps to draw a sharp line.
Overuse without an invoice. The customer has a licence for fifty users and seventy are active. The maintenance contract covers three sites, and the engineer now drives to five. The retainer budget is twenty hours a month, and thirty are booked every month without an invoice for the extra work. Here the service has already been delivered. It is not an opportunity, it is unbilled revenue, and it belongs in the same category as revenue leakage from wrong subscriptions.
Expansion nobody proposes. The customer has grown, uses your service more intensively than comparable customers and buys additional services elsewhere. Nothing has been invoiced incorrectly. But a customer who is ready for more and does not buy it from you will eventually buy it from someone else. That makes it a retention risk as well.
In both cases the money does not appear in any report as a loss. It is revenue that should have been there and that nobody misses, because nobody expected it. That is the core of revenue leakage: the difference between what you could have invoiced and what you did invoice, without any alarm going off.
Where does it go wrong?
Usage lives in a different system from billing. The number of active users is in the admin portal of your software platform. The number of licences invoiced is in Exact, Moneybird, Xero or NetSuite. Hours booked are in the time tracking system, the hours budget is in the contract. As long as nobody regularly compares the two, the gap grows unseen. It is the same mechanism as revenue leakage between CRM and billing: two systems that are each correct, but not together.
Nobody owns the existing customer. In many B2B companies, sales is organised around new customers. After signature the customer moves to operations or support. They see the overuse, but have no commercial mandate to act on it. The account manager is too busy with new deals. Expansion then only happens when the customer asks for it.
Tolerance becomes habit. "Those few extra users, call it goodwill." Once, that is a sensible choice. But if nobody records it, three years later it has become a structural 40 percent discount that nobody consciously granted.
The signal arrives too late. A customer opening more sites, starting a new department or acquiring a competitor is the moment for a conversation. If you only notice at the annual renewal, you are often too late: the customer has already met the additional need elsewhere.
How do you recognise overuse?
Overuse is the easiest to find, because it is measurable. For each customer you need two numbers: what was agreed and what is actually being consumed.
- Licences and users. Number of active accounts on the platform against the number of licences invoiced.
- Volumes. Transactions, storage, messages, shipments or other units against the bundle in the contract.
- Hours. Hours booked to a customer or project against the hours budget or fixed price.
- Locations and assets. Number of sites, installations, vehicles or machines under maintenance against what the contract lists.
- Services. Work that falls outside the scope of the contract but is carried out under it, such as extra reports, emergency call-outs or support outside office hours.
Worked example: suppose you supply software to 120 business customers at EUR 25 per user per month. A check shows that 30 customers have, on average, 6 more active users than are invoiced. That is 30 × 6 × EUR 25 × 12 = EUR 54,000 a year in service delivered but not invoiced. Nobody made a mistake. There is simply nobody comparing the two.
How do you recognise expansion opportunities?
Expansion opportunities are harder, because there is no contract to compare against. You compare the customer with other customers. The question is: which customers behave like customers who have already expanded, but have not yet done so themselves?
Signals that help:
- Usage close to the package limit. A customer using 90 percent of their bundle every month will soon need a larger package.
- Growth at the customer. New sites, job openings, an acquisition or a new product line. You will not find this in your own systems, but in the news, on LinkedIn or through contact with the customer.
- Support questions about features in a higher tier. A customer asking how to do something their package cannot do is telling you what they want to buy.
- One-off extra orders that become regular. Ordering the same extra service separately three times in six months is a signal for a permanent extension.
- Comparable customers buy more. If customers of the same size and sector buy two services on average and this customer buys one, that is a question you can ask.
How does this relate to churn?
Missed upsell and churn are two sides of the same problem: nobody looks at the existing customer until something happens. A customer who stops growing with you is sometimes growing elsewhere. A customer who buys additional services from a competitor already has that competitor through the door. The opposite signal, customers who quietly buy less, calls for the same discipline: regularly checking, customer by customer, how their buying pattern is developing.
Step by step: the first round
You can do this in a week, with the data you already have.
- Pick one product or service where usage is measurable. Licences, hours, volumes or locations.
- Export actual usage per customer over the past three months. From the platform, the time tracking system or the scheduling system.
- Export what was invoiced per customer over the same period. From your accounting or billing system.
- Match the two on customer number. Be aware that customer numbers often differ between systems. This is usually the most work.
- Flag every customer with consistently more usage than invoiced. Consistently means more than one month in a row, not a one-off peak.
- Check the contract for each flagged customer. Can you invoice overuse? At what rate? Was anything different ever agreed?
- Record a decision for each customer. Invoice, move to a larger package, or consciously tolerate it with a reason and an end date.
- List the customers close to their limit. Those are the expansion conversations for the coming quarter.
How do you handle it structurally?
A one-off round usually pays off straight away. But overuse arises again every month. To keep it closed, the comparison between usage and billing has to be recurring.
- Make it a monthly check with an owner. Not as a project, but as a fixed part of the month-end close.
- Put the rules in the contract. A clear clause on how overuse is invoiced turns the conversation with the customer into a formality rather than a negotiation.
- Give account management a list, not a dashboard. A dashboard with a hundred customers does not get read. A list of the ten customers with the largest gap in euros does get acted on.
- Connect the systems where you can. If usage flows automatically into the billing system, nobody needs to compare it. Where that is not possible, an automated comparison is the next best step.
Frequently asked questions
Is a missed upsell really revenue leakage?
Overuse without an invoice certainly is: the service was delivered and not paid for. An expansion nobody proposed is, strictly speaking, missed revenue rather than a leak. But for your results it makes little difference, and the cause is the same: nobody looks systematically at existing customers.
Should I always invoice overuse?
No. Sometimes it is sensible to tolerate it for a while, for example in the run-up to a renewal. The point is that it must be a conscious decision, with a name, a reason and an end date. Otherwise goodwill quietly becomes a permanent discount.
How often should I check usage against billing?
For recurring services, monthly, as part of the close. For project work, per milestone or per invoicing moment. The longer you wait, the harder the conversation with the customer becomes.
Who owns upsell with existing customers?
It must be assigned explicitly, to account management or customer success. In companies where sales only focuses on new customers and operations has no commercial role, the existing customer belongs to nobody. That is where this leak arises.
More in this cluster
- What is revenue leakage? The complete guideStart here
- Where does revenue leakage come from?
- How much revenue does a B2B company leak on average?
- How do you calculate revenue leakage?
- 25 examples of revenue leakage
- Revenue leakage between CRM and billing
- Revenue leakage between contract and invoice
- Revenue leakage from wrong prices