What each function owns
CS ops runs the post-sale motion. RevOps owns the definitions that the post-sale motion gets scored on. CS ops builds the onboarding workflow, maintains the customer success platform, automates renewal and QBR tasks, and keeps the health score running. RevOps decides how retention is calculated, how a downgrade is recorded against ARR, and how the renewal number reconciles into the company forecast.The division holds because retention math is a company definition. If CS ops publishes its own version of net revenue retention, the board deck and the CS dashboard stop agreeing, and the CS number is the one that loses.
The renewal forecast is the seam
Renewals get forecast separately from new business and often by different people. That is where accountability goes missing. Sales claims the expansion, CS claims the renewal, and nobody owns the contraction. Name one owner for the renewal forecast method and hold it to the same forecast accuracy standard applied to new business.
ORM's retention model is a monthly waterfall. Beginning ARR, churned customer ARR, churned product ARR, product decrease ARR, new customer ARR, new product ARR, increased product ARR, ending ARR, where beginning ARR is the prior month's ending ARR. Gross and net retention sit on the same chart. Contraction becomes a visible line item instead of hiding inside a net figure that looks fine.
Health scores need a system owner
A health score is a model, and models decay. Somebody has to own the inputs, verify the score still separates accounts that renewed from accounts that churned, and remove signals that stopped predicting anything. CS ops maintains it. RevOps validates it against outcomes.
Support volume is the input most teams read backwards. ORM's finding is that accounts with no support cases are at risk, accounts with seven or more cases in a year are at risk, and accounts with three to five tier two or tier three tickets are less likely to churn, because those customers are engaged and getting help.
When to split the roles
One operations team can carry both while there is a single product and a single renewal motion. Split when the post-sale side gets its own platform, its own quota-carrying renewal team, or usage-based pricing that requires consumption reporting the sales stack cannot produce.
Keep the definitions central after the split. Two operations teams with independent retention math produce two retention numbers, and the executive team spends renewal season reconciling instead of saving accounts.
Frequently Asked Questions
Should CS ops report to RevOps?
Either line works as long as retention definitions stay central. CS ops reporting into customer success keeps proximity to the motion. CS ops reporting into RevOps keeps the numbers consistent. What fails is CS ops running its own retention math with no reconciliation to the company number.
Who forecasts renewals, customer success or sales?
Whoever carries the renewal quota submits the number, and RevOps owns the method behind it. Renewals need the same stage discipline as new business, including a defined commit standard and a record of when a renewal date moves.
What does the first CS ops hire actually own?
Usually three things in order: getting renewal dates and contract terms accurate in a system rather than in spreadsheets, building the onboarding and QBR workflow, and standing up a health score. Renewal data accuracy comes first because everything downstream reads it.
How do you keep a health score honest?
Score it against outcomes on a schedule. Check whether accounts the model called healthy renewed at a higher rate than accounts it called at risk. Retire inputs that stopped separating the two groups. A health score nobody validates becomes a usage report with a color on it.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like customer success operations vs revops into prescriptive action for your team.
Schedule a Demo