How to Frame an Upsell as the Next Problem to Solve, not the Next Product to Buy.
You are about to recommend an additional product or tier and you want the customer to see it as obviously relevant, not as a sales move
Customers do not buy products - they buy outcomes. When an AM leads with a feature or a price, the customer's first instinct is to evaluate cost and push back. When the AM leads with a problem the customer already recognises and then connects a solution to it, the conversation stays in the customer's frame of reference. The product becomes the answer to a question they were already asking.
Where it goes wrong
Leading with the product - 'we just launched X, you should add it' - signals that the AM is working from a product roadmap, not from the customer's situation. It makes every future recommendation feel like a pitch rather than advice.
What you'll be able to do
You can structure an expansion conversation so the customer names the problem before you name the solution, making the recommendation feel like a natural next step.
How to do it
Use the first half of any expansion conversation to
Use the first half of any expansion conversation to review current value and ask gap questions - 'what is still manual or painful in this workflow?' and 'what are you trying to achieve this quarter that you have not fully cracked yet?' Your goal is to get the customer to describe the problem in their own words before you say anything about a product.
Once they have named a gap, play it back
Once they have named a gap, play it back and confirm it matters: 'So the bottleneck right now is X, and if that were fixed it would affect Y - is that right?' Get explicit agreement before you move to a recommendation.
When you do introduce the upsell or cross-sell, connect
When you do introduce the upsell or cross-sell, connect it directly to what they just said: 'Given what you described, there is one thing we can add that directly tackles that.' Then link the capability to the specific outcome or metric they care about, not to a feature list.
See the difference
'We have a new analytics add-on that a lot of customers are finding really valuable. It gives you dashboards, automated reports, and trend tracking. I can send over the pricing if you want to take a look.'
'You mentioned your team spends a couple of hours each week pulling numbers together for the leadership report. If that time came back, what would they do with it? ... Given that, the piece I would suggest looking at is the reporting module - it automates exactly that export and formats it the way you described. Customers with a similar setup have cut that process to about ten minutes. Want to see how it would work for your data?'
You can structure an expansion conversation so the customer names the problem before you name the solution, making the recommendation feel like a natural next s
How you'll know it's working
You have got it when the customer responds to your recommendation with something like 'yes, that is exactly what we need' rather than 'interesting, what does it cost?'
Questions people ask
How do you frame an upsell as the next problem to solve, not the next product to buy?
Customers do not buy products - they buy outcomes. When an AM leads with a feature or a price, the customer's first instinct is to evaluate cost and push back. You can structure an expansion conversation so the customer names the problem before you name the solution, making the recommendation feel like a natural next step.
What is the most common mistake to avoid?
Leading with the product - 'we just launched X, you should add it' - signals that the AM is working from a product roadmap, not from the customer's situation. It makes every future recommendation feel like a pitch rather than advice.
Hire with Assessment.
£7-10k flat fee. The methodology, delivered.
See Hire with Assessment