There's a version of this conversation that happens in almost every CS organization at some point. A CSM brings up a product upgrade or an additional service on a customer call. The customer seems a little caught off guard. Maybe they push back. Maybe they just go quiet. The CSM walks away feeling like they crossed a line. And the internal narrative becomes: upselling damages the relationship. We need to be careful about this.
That narrative is wrong. And it's worth being precise about why, because the wrong lesson leads to a lot of avoidance that ultimately hurts customers more than it hurts the business.
Upselling doesn't hurt trust. The wrong thing, to the wrong person, at the wrong time hurts trust. Those are three separate variables, and conflating them leads CS teams to throw out the whole conversation instead of fixing what's actually broken.
The Three Variables
The wrong thing is a product or service that genuinely isn't a fit for where the customer is. You're suggesting something they don't need, can't use, or aren't ready for. The customer can tell. It feels like you're going through a checklist of things to sell rather than actually thinking about their situation. This is a knowledge problem. The CSM doesn't understand the product well enough, or the customer well enough, to know what actually makes sense.
The wrong person is bringing the expansion conversation to someone who doesn't have the authority, the context, or the relationship to receive it. You've been building a relationship with a practitioner and suddenly you're asking them to champion a $75K upgrade to their CFO. Or you're talking to the wrong stakeholder entirely, someone who will feel threatened by the expansion rather than excited about it. This is a champion problem. The CSM hasn't mapped the account well enough to know who the right person is.
The wrong time is the most common failure. The customer is in the middle of a difficult implementation. They just came off a frustrating support experience. They haven't realized the value of what they already have. Or they're not at the milestone yet where the next thing would make sense. You bring it up anyway, because the quarter is ending or the renewal is coming up or someone on the leadership team asked about expansion in this account. The customer feels the misalignment immediately. It doesn't feel like help. It feels like sales. This is a timing problem. The CSM is operating on the vendor's calendar instead of the customer's journey.
Fix any one of those three and the conversation gets better. Fix all three and it stops feeling like upselling entirely.
What Good Timing Actually Looks Like
Good timing isn't about waiting long enough that the customer trusts you. Trust is necessary but it's not sufficient. Good timing is about the customer being at a point in their journey where the next thing is genuinely the next thing. Where it solves a problem they're experiencing, or gets them to a place they're already trying to reach, or removes a friction that's becoming visible.
At that moment, the conversation doesn't feel commercial. It feels useful. The customer's reaction isn't "why are you trying to sell me something" but "oh, I was actually thinking about this." Or "I didn't know that existed, tell me more." Or "yes, we've been trying to figure out how to handle exactly this."
That reaction is available. It's not rare. It's what happens when the CSM knows the product path well enough to see what's coming and knows the customer well enough to recognize when they've arrived at the moment.
The CSM who has that picture can also plant seeds in advance. They can tell a customer, months before the conversation needs to happen, that when they reach a certain milestone there's something that's going to be worth talking about. They can give the customer time to think, to budget, to get internally aligned. And when the moment comes, the conversation isn't a surprise. It's expected. The customer is ready. The trust isn't damaged. It's deepened, because the CSM called the shot in advance and it landed exactly where they said it would.
The Avoidance Tax
Every time a CS team decides that expansion conversations are too risky, too commercial, too likely to damage the relationship, they pay an avoidance tax.
The tax has two parts. The first part is the obvious one: the revenue that doesn't get captured. The upgrade that doesn't happen. The module that doesn't get added. The support tier that stays lower than it should. That's real money that was available and went uncollected.
The second part is less obvious and more damaging: the customer who doesn't get what they need. Who stays at a level that's starting to create friction. Who goes looking for a solution elsewhere because nobody showed them that their current vendor could solve the problem. Who eventually churns not because the product failed but because the relationship failed to grow.
The avoidance tax compounds. And it gets paid by both sides.
Reframing the Conversation
The fix isn't to train CS teams to be more aggressive about expansion. That overcorrection creates exactly the transactional dynamic that erodes trust. The fix is to reframe what the expansion conversation actually is.
It's not a sales call. It's not a pitch. It's a CSM saying: I know where you are, I know where you're going, and I know what you're going to need when you get there. Here's what that looks like and here's when it's going to matter.
That's not selling. That's the most valuable thing a trusted advisor can do. It's connecting the customer's future to the resources available to help them reach it. It's doing the job completely, not just the safe parts of it.
Upselling doesn't hurt trust. Being genuinely useful builds it. And being genuinely useful sometimes means telling a customer about something they're not ready for yet, so that when they are ready, they know exactly where to turn.
That's not a commercial conversation. That's a relationship.
Lincoln Murphy formally named and popularized Customer Success starting in 2010 and has spent 15 years connecting it to expansion revenue and commercial outcomes. Read The Premise.