How to Compensate Sales on Renewals and Expansion

Most compensation design attention goes to new business, which is where the smallest share of revenue usually comes from in a mature SaaS company. The renewal and expansion base is larger and the plans covering it are frequently an afterthought: a flat rate on everything, no risk segmentation, and credit rules that produce an argument every quarter. Fixing that starts with separating the two motions.

Why do renewals and expansion need separate treatment?

Because they are different amounts of work producing different kinds of revenue. A renewal preserves revenue the company already earned. An expansion creates new revenue that did not exist before. Paying the same commission rate on both tells the team that keeping is worth as much as growing, and the team will do the easier one.

The revenue waterfall makes the distinction clean. Beginning ARR moves through churned customer ARR, churned product ARR, and product decrease on the contraction side, then through new customer ARR, new product ARR, and increased product ARR on the expansion side, landing at ending ARR. Gross and net revenue retention both fall out of that same reconciliation. Compensation should map to the lines in the waterfall rather than to a blended number sitting on top of them.

How should the rates differ?

Lower on the renewal base, closer to new business on expansion. The structure below is a design template to model against your own attainment history rather than a benchmark to adopt. Rate design should follow the difficulty of the work. A cross-sell into a new department is a full sales cycle with a new buying committee and belongs at a new business rate.

Who should own the renewal number?

Whoever holds the relationship and the authority to negotiate commercial terms. Splitting those two creates the failure everyone recognizes: a customer success manager who knows the account cannot move on price, and an account executive who can move on price does not know the account.

Assign one accountable owner per account and write the credit rules for the cases where two roles touch the deal. Name the split percentage in the plan document rather than resolving it case by case, because case-by-case resolution means whoever escalates loudest wins.

How do you pay on retention without rewarding luck?

Pay on the components, not the portfolio ratio. Retained renewal dollars, expansion dollars added, and contraction avoided are all measurable at the account level and all reflect work someone did. A portfolio-level retention percentage does not separate the rep who saved three at-risk accounts from the rep who inherited a book that was never going to leave.

Segment the book by risk before the period starts. Score each account, set a renewal target that reflects the score, and publish the scoring inputs. Support behavior is one of the more useful inputs, and it does not run the direction most teams assume. An account with no support cases at all is at risk, because silence usually means nobody is using the product. An account with seven or more cases in a year is also at risk. The healthy pattern sits around three to five cases, usually lower severity, which describes a customer who is engaged and getting help.

Should customer success managers carry a quota?

Only when they hold commercial authority. A CSM who can negotiate price and sign an expansion order is doing sales work and should carry a number with meaningful variable pay. A CSM who can only surface an opportunity for a rep to close is doing a different job, and paying them heavy variable on an outcome they hand off creates frustration rather than motivation.

For the second case, use a lighter variable component measured on the outcomes the role actually controls: retention in the assigned book, expansion opportunities sourced and accepted, and reference participation. That structure keeps the role focused on the customer instead of turning every conversation into a sales call.

How do you forecast the cost of these plans?

Model the renewal base and the expansion motion separately, because they behave differently. The renewal base is largely knowable from contract dates and account health, which makes the cost predictable within a quarter. Expansion behaves more like new business and carries the same timing uncertainty.

That difference matters for accuracy. Forecast accuracy on new and expansion revenue tends to land around 90 percent when teams put serious manual effort into it, and that effort does not survive changing conditions. ORM targets 95 percent on the same revenue types without manual adjustment, holding from day 1 through day 90 of the quarter and updating as the quarter progresses. Renewal revenue is a separate forecast with its own drivers, and blending the two hides the risk in both. Keep them split in the plan and split in your forecast.

What is the most common mistake in renewal comp?

Paying a flat rate across the entire book with no risk segmentation. It overpays for renewals that would have happened without intervention and underpays for saves that required real work. Over a year, that pattern pushes the strongest renewal reps toward the easy accounts and leaves the at-risk ones unattended until the quarter they churn.

The second mistake is measuring the team on a blended retention number and nothing else. A blended number moves for reasons the team did not cause, including a single large customer's budget cycle. Pay on account-level outcomes, report the blended number to the board, and keep the two uses separate. Track the trend the same way you track forecast accuracy, as a monthly reconciliation rather than a quarterly surprise.