Should customer success own renewals?

Metrics, customers and the organization · Answered by Golden Section from more than 400 B2B software companies observed

The Golden Section answer

Yes. In vertical software the person who drove adoption is best placed to secure the renewal, because a renewal is mostly the proof that onboarding and adoption worked. Give customer success the renewal as an owned outcome, measured and paid on gross revenue retention across the book, rather than leaving it to someone who meets the customer for the first time at contract end. Golden Section's view is that customer success should also carry the expansion quota, paid only on the increase and only after the customer pays. Hand customers from sales at signature with a written profile of what was promised, and move them from onboarding to the account owner when they reach a defined adoption metric, not on a date. Start by naming one owner for each stage.

The decision rule

One owner per stage of the customer lifecycle. Customer success owns adoption, the renewal and the expansion quota; it is paid on gross revenue retention across the book, not per renewal signed, and on expansion only for the increase and only after the customer pays.

Usually ready when

  • A written handoff profile from sales for every new customer
  • An adoption metric that ends onboarding
  • Renewal dates and terms held in a contract register

Probably too early when

  • Customer success also runs support and every implementation with no separation
  • Nobody can name who owns the renewal on the ten largest accounts

The numbers

MetricValueWhat it meansSource
Gross revenue retention to underwrite95%+starting ARR retained after churn and contraction, excluding expansionbelow 80% is disqualifying in our framework; the private median fell to 84% in 2025Golden Section, publishedInvesting in Software addendum
Customer support and success spend9% of ARR (median)support and customer success cost as a share of ARR2026 survey of more than 1,000 private B2B SaaS companies; 10% in the $3M–$5M ARR bandExternal benchmarkSaaS Capital, 2026 Spending Benchmarks for Private B2B SaaS Companies
Commission on expansionon the increase only, after paymentcommission paid on the delta of an upsell, never the whole contract, and only once cash is receivednever pay commission twice on the same revenueGolden Section playbookSales Compensation Plan play
Customer success pay on renewalsgross revenue retention across the book, not per renewal signedthe basis for customer success variable pay on renewalsrewards keeping the whole book healthy rather than saving individual signatures with discountsGolden Section operating viewGolden Section operating view

Why

A renewal is decided long before the renewal date. Our account management play describes it as the low-drama stage that follows onboarding and adoption: if the customer reached the promised outcome and knows it, the renewal is close to administrative. If not, no renewal conversation rescues it. That is why the owner of adoption should own the renewal; the alternative splits accountability for the most important number in the business between someone who did the work and someone who collects the signature.

The handoffs are where it breaks. Sales promises an outcome, and the onboarding play has the rep complete a customer profile at signature so the promise survives the handover; onboarding then ends at an adoption metric rather than a calendar date, and only then does the account pass to the long-term owner. A customer handed over on a date is often handed over mid-implementation, which is how churn is born.

Expansion belongs with the same owner. It happens only when someone sells it, and our view is that customer success should carry that quota, paid under the rules in the sales compensation play. Pay customer success on gross retention across the book, not on renewal volume, which rewards discounting at renewal and blurs the line between keeping a customer and buying them back.

Illustrative scenario

The numbers are fictional. A $6M company has account executives own renewals for their own customers, and customer success handles onboarding and support. Gross retention has slipped to 86%, and the churned accounts share a pattern: the AE had moved on to new deals, and the first renewal conversation happened 30 days before term end. The company moves renewals to customer success, sets the onboarding handoff at a defined adoption metric, and puts every renewal date in the contract register with a 120-day review. Customer success also takes an expansion quota, paid on the increase after cash is collected, and its variable pay moves to gross retention across the book rather than renewals signed. Time to the adoption metric becomes its leading indicator.

When this does not hold

In very small companies the founder or one account executive may hold every stage, and the rule becomes one written owner per stage even if it is the same person. Products with large, negotiated expansions into new divisions may need an account executive to lead the commercial conversation, with customer success owning the health of the account.

What to do on Monday

  1. Write down who owns onboarding, adoption, renewal and expansion for every customer segment
  2. Define the adoption metric that ends onboarding and triggers the handoff
  3. Build the sales-to-onboarding handoff profile and require it at signature
  4. Load every renewal date into the contract register with a review well before term end
  5. Set the expansion quota for customer success and the rules for paying on the increase
  6. Move customer success pay from renewals signed to gross revenue retention across the book

Mistakes founders make here

From the Golden Section mistakes list, each paired with the play that prevents it.

Mistake 130: Expecting a customer to expand without selling

If customer success does not carry the expansion quota, customers will renew at best and never grow.

Mistake 35: Hasty commission structure

Commission structures are hard to unwind, and a hasty one for customer success can reward discounting at renewal.

Mistake 108: Fuzzy organizational chart

Renewals that sit between sales and customer success have two owners, which in practice means none.

Plays we would run

In the order we would run them. Each is on its own page, most with a free Excel template.

Onboarding Process

Defines the sales handoff and the adoption metric that ends onboarding.

Account Management Process

Sets the four stages, onboarding, adoption, renewal and offboarding, and their owner.

Adoption Process

Gives the account owner the cadence and process that make renewal routine.

Contract Register

Keeps every renewal date and term visible so none is discovered late.

Sales Compensation Plan

Sets the rules for paying on expansion without paying twice.

Customer plays The customer lifecycle from handoff to renewal, with the processes each stage needs.

Questions this page answers

Should customer success have a quota?

Yes, for expansion. Golden Section's view is that customer success carries the expansion quota, because the person who knows whether the customer is getting value is best placed to grow the account. Pay commission only on the increase and only after the customer pays. Measure and pay the core work, adoption and renewal, on gross retention across the book.

When should sales hand customers to customer success?

At signature, with a written profile of what the customer was promised and why they bought. Onboarding then runs to a defined adoption metric, and the account passes to its long-term owner when that metric is met, not on a fixed date. Sales should stay reachable through onboarding for questions about what was sold.

Should customer success be paid on renewals?

Not per renewal signed. Pay customer success on gross revenue retention across the whole book. Paying per renewal invites discounting to save the signature, which shows up later as contraction and weaker pricing power.

Reviewed by Dougal Cameron, CEO & Co-Founder on 2026-10-22. Golden Section observations are labeled separately from external benchmarks and illustrative arithmetic.