AutoMaat
Knowledge base· Detection and control

How do you find missed upsell?

How to see in your own customer data which customers are ready to buy more, why nobody asks, and how to turn it into a list with an owner and an amount.

Ricardo Mastenbroek7 min read
Lees dit artikel in het Nederlands

You find missed upsell by comparing your existing customers with the customers who have already expanded, and looking for the same signals: growing usage, more employees or sites, recurring additional work, questions about a product they do not have yet. Customers who show that pattern but are still on their original package are your missed upsell. It only becomes usable once you attach an expected value and an owner to each customer.

Why upsell gets left on the table

Upsell is not a leak in the way a forgotten invoice is. Nothing goes wrong in a system. Nothing happens at all. That makes it hard to see.

In most B2B companies, expansion happens on the customer's initiative. They call, ask for an extra module, more capacity or an extra site, and sales prepares a quote. That feels like growth, but it is reactive. The customers who do not call, because they do not know it is possible or because they solve it internally, stay where they are.

On top of that come three structural causes:

  • Account managers are focused on new customers. Their targets and bonuses are about new revenue. A satisfied existing customer gets little attention.
  • The signals sit in systems sales does not see. Usage is in the product or the ticketing system, additional work in time tracking, the customer's growth in billing. The CRM shows only the original deal.
  • There is no list. Without a concrete list saying "these twenty customers are ready", nothing happens, however good the intentions.

The background and what it costs are covered in revenue leakage from missed upsells.

What signals should you look for?

Every company has its own signals, but these come up in B2B almost every time:

Signal Where to find it What it means
Usage growing towards the package limit Product data, licence management The customer is hitting their limit
Recurring additional work on the same topic Time tracking, billing There is structural demand that could become a standard product
Many support questions about a feature in a higher package Ticketing system The customer is looking for something you already sell
More users, sites or employees CRM, billing, public sources The customer has grown, their contract has not
Orders of individual products that are cheaper as a bundle Order history The customer pays per item for what they would want as a package
A similar customer who did expand Customer base You already have evidence that it works

The last signal is the strongest. If you know which customers expanded and what could be seen in them beforehand, you have a pattern to compare the rest against.

Step-by-step plan: from data to a list

  1. List the customers who expanded in the past two years. New module, higher package, extra site, larger framework agreement. Take it from billing, not from the CRM, because billing shows what actually went live. How to put the two side by side is covered in how to check CRM against billing.
  2. Look at what those customers showed in the six months beforehand. Growth in usage, additional work, specific support questions, a new contact person. You are looking for the two or three signals that keep recurring.
  3. Find customers who show the same signals now and have not yet expanded. That is your raw list.
  4. Estimate the value per customer. The price difference between the current package and the logical next one, times twelve months. Without an amount it will not become a priority.
  5. Filter out what is already in progress. Remove customers with an open quote or an ongoing conversation.
  6. Assign an owner and a date for each customer. Record it as a task in the CRM, not in a spreadsheet nobody opens again.
  7. Measure after three months. How many conversations took place, how many expansions were realised, and which signals turned out to be predictive. Adjust the list accordingly.

Worked example

Worked example: suppose you are a service provider with 180 customers on a basic subscription of EUR 600 a month. The next package costs EUR 1,100 a month. The analysis shows 25 customers who consistently buy more hours of additional work than the difference between the packages, and who also ask support questions about features in the higher package.

  • Difference per customer per year: 12 times EUR 500 is EUR 6,000.
  • For 25 customers: EUR 150,000 a year in possible expansion.

Some of those customers will say no, and the additional work they now pay for separately disappears when they move up. So calculate with the net difference. Even then, the amount is usually large enough to put someone on it permanently.

Upsell and under-invoicing overlap

Sometimes what looks like missed upsell is really a leak. A customer who already uses more than they pay for does not need an upsell. They need to be invoiced correctly. That is a different conversation: you are not selling anything new, you are charging for what is already being delivered. Keep the two separate on your list. The second belongs with customers who pay too little.

The reverse is also true. A customer who has been buying less for some time is not an upsell candidate but a retention risk. The signals sometimes look alike, for example many support questions. The difference is in the direction of what they buy. See how to spot customers who are quietly buying less.

Where execution goes wrong

The analysis is rarely the problem. The follow-up is. Three pitfalls:

  • The list goes to sales as a whole. Everyone thinks someone else will pick it up. One owner per customer, by name.
  • There is no evidence attached. "This customer is an upsell candidate" convinces nobody. "Over the past six months this customer bought an average of 14 hours a month of additional work on reporting, and reporting is in the higher package" does.
  • It is a one-off exercise. After one round the list disappears. Upsell signals arise continuously, so the list has to be updated continuously too.

That last point is where a platform makes a difference. The Opportunity Tracking module on the system page shows how RiOS puts growth signals next to leaks, each with an expected return in euros. It can also be done by hand, as long as someone does it again every quarter. Missed upsell is one of the areas in the broader approach to finding revenue leakage in a business.

Checklist

  • Do you know which customers expanded in the past two years, and what they showed at the time?
  • Can someone in your company produce, within an hour, a list of customers at the limit of their package?
  • Is additional work tracked per customer per month, so that structural additional work becomes visible?
  • Do account managers have a target for expanding existing customers, not only for new ones?
  • Is every upsell opportunity recorded as a task with an owner and a date in the CRM?

Frequently asked questions

What is the difference between upsell and cross-sell?

Upsell is more of the same or a higher package. Cross-sell is an additional, different product. For finding them it makes little difference: in both cases you look for customers who resemble customers who have already taken the step.

How many customers should be upsell candidates?

There is no reliable average. It depends on your product range, how fast your customers grow and how well you placed them at the start. A list of five to ten percent of your customers per quarter is a workable size for most teams.

Can I do this without product data?

Yes. Billing and time tracking already show a lot: additional work, individual orders, growth in volume. Product data makes it more precise, but it is not a prerequisite.

How do I avoid customers feeling pressured?

By starting from what they already do. A customer who pays for additional work every month benefits if you show them that another package is cheaper. A well-supported proposal feels like service, not selling.

Share this article
Knowledge base · Detection and control

More in this cluster

All 18 topics in this cluster

More from AutoMaat

Rather know what this costs you specifically?

The Revenue Audit puts a euro amount on where your revenue leaks.

Plan the Revenue Audit