The logic feels airtight. Customer success managers own the customer relationship. Renewals are the commercial outcome of that relationship. Therefore, pay CSMs on renewals. It's clean, it's measurable, it connects the team's work to business outcomes.
The problem is what it does to the work itself.
I first noticed this pattern in a client's CS team, a function that looked healthy on paper but had quietly developed a behavioural quirk. CSMs were taking longer than they should have to escalate at-risk accounts. The at-risk designation went into the CRM, got surfaced in the health score, and triggered a formal review process. But formal review processes create paper trails, and paper trails visible at renewal time can affect variable comp. The incentive was subtle, but it was there: surfacing an at-risk account cost something.
Nobody had designed that outcome. It emerged from a compensation structure that made sense on paper.
What renewal incentives actually incentivise
When you pay CSMs on renewal outcomes, you're attaching their earnings to something they influence significantly but don't control entirely. The renewal depends on product quality, competitive alternatives, the customer's own budget cycles, whether the champion who bought the product is still in the seat. The CSM can affect maybe sixty percent of that equation in a good month.
This isn't a problem unique to CS. Plenty of sales roles involve commission on outcomes that are partially outside the rep's control. The issue is what CS is supposed to be doing while it waits for the renewal to arrive.
Customer success work (real CS work) happens months before the renewal. It's the adoption conversations in month two. The check-in that catches a change in the customer's priorities before it becomes a risk. The business review that makes the value concrete. If CSMs are optimising for the renewal outcome, they're prone to a specific distortion: over-investing at renewal time and under-investing in the quarters before it. The renewal conversation is high-stakes and visible. The month-two adoption conversation is neither.
Three failure modes
Sandbagging risk signals. As I saw above, when health score ratings and at-risk designations are visible in comp tracking, CSMs have an incentive not to surface problems until they have a clear path to resolution. The risk gets managed privately, or not at all. Leadership gets a false picture of portfolio health.
The save mindset replacing the success mindset. A CSM optimising for renewals is, functionally, a save function. They're looking for accounts that are close to not renewing and intervening. That's valuable, but it's not the same as proactively driving adoption and value realisation across the full portfolio. The accounts that are quietly fine get less attention, because they're not at risk. The structure rewards firefighting.
Commercial tension with the customer. When CSMs know their comp is attached to the renewal, it changes how they show up in renewal conversations. Customers can feel the shift: the helpful partner who runs QBRs becomes someone with a visible stake in the commercial outcome. That's particularly acute when there's a legitimate reason not to renew, and the CSM is working against it.
What works better
None of this is an argument against incentivising CS commercially. Expansion motions, for instance, work well with CSM compensation tied to upsell or cross-sell, because the CSM is actively generating and identifying commercial opportunity rather than protecting an existing one.
For renewal retention specifically, a few structures work better than individual renewal commission:
Team-based renewal pool. The whole CS team participates in a shared renewal bonus. This preserves the commercial link without creating individual incentives to sandbag or over-manage individual accounts at renewal time.
Leading indicator metrics, not lagging outcomes. Pay on the work that produces renewals: adoption metrics at sixty days, QBR completion rate, health score movement in the defined at-risk segment, executive stakeholder coverage. These are behaviours the CSM actually controls, and they're earlier in the chain.
Clear role separation. Some companies keep CS compensation entirely off renewal outcomes and put commercial accountability (including renewal close) in a commercial team that CS partners with. The CSM stays focused on customer success; the commercial team handles the contract. It creates coordination complexity but removes the conflict of interest.
CS Ops and compensation design
This is a CS Ops problem as much as an HR or commercial one. The metrics that appear in the comp plan need to match the metrics in the health score model. If health score uses adoption data and relationship depth as leading indicators, but comp is on renewal lagging outcomes, you've designed a team that tracks two different versions of success, and they'll optimise for the one that pays.
CS Ops owns the data infrastructure those metrics are built on. That makes it the function best placed to advise on whether the proposed comp metrics are actually measurable, whether they're driving the right behaviour, and whether the leading indicators in the incentive plan match the model the team is using to manage the portfolio.
The comp conversation isn't separate from the CS Ops conversation. It's downstream of it.
Questions worth sitting with
- What behaviours does your current CSM comp structure actually incentivise, if you trace the logic through carefully?
- Is there any reason a CSM in your team would delay surfacing an at-risk account? If the answer is yes, what's creating that incentive?
- Do the metrics in your CSM comp plan match the metrics you're asking the team to track in the CRM?
The short version. Individual renewal commission for CSMs is intuitive but frequently creates perverse incentives: sandbagging risk signals, over-investing at renewal time, and muddying the partner relationship. Better structures include team-based renewal pools, leading indicator metrics, and clear role separation between success and commercial functions. CS Ops needs to be in the comp design conversation, because the metrics have to be consistent across health scoring, performance management, and compensation.
Working on this in your business?
We help UK SMEs and scale-ups turn this kind of thinking into action.
Read next
The first CS hire: what you actually need versus what you think you need
Making the CS Case to the CFO: What Finance Leaders Actually Need to Hear
Why CSMs Burn Out, and What the CS Ops Infrastructure Has to Do With It
Scaled CS: what it actually means and when you need it
Expansion revenue is a Customer Success responsibility. Here's why most teams aren't ready for it.
