Key Takeaways
Carmen has the headcount request half written. The team has seven CSMs, a renewal forecast built in a spreadsheet, and a health score nobody trusts. The case for a customer success operations manager feels obvious to her. Her CFO asks one question before signing: how many companies our size actually have this role? She searches, and the answers don't agree. One report says 61%. Another says 20% or 41%, and a third says 51%. They all come from the same vendor.
The disagreement isn't sloppy research. It's a sign that the role is still being defined while it's being counted. For a leader about to hire one, that matters more than the percentage. It means the job description is hers to write, and the boundary she draws around it will decide whether the hire fixes the team's problems or just documents them.
What a customer success operations manager does
The two vendors that publish most on the role agree on its core. ChurnZero groups CS Ops work into data, process, people, systems and strategic initiatives. Its data work covers “renewal forecasting, account health, NPS, adoption”. Process work covers renewal playbooks and touchpoints. People work covers “goals, targets, performance, workforce/team planning”.
Gainsight describes the lead as “a master of programs, processes, and data.” Its sample job description is more specific about how the role is measured. The director builds CS programs “to impact critical metrics such as Net Revenue Retention (NRR), Customer Lifetime Value (CLV), Cost-to-Retain Customers (CRC), and Cost-to-Expand Customers (CEC).”
That last list is the useful part. Two of the four metrics are costs. A customer success operations manager isn't hired to make CSMs busier. The job is to make each retained or expanded dollar cheaper to keep. That's also the difference between CS Ops and the broader discipline covered in what customer operations is, which spans support and onboarding as well.
On timing, both vendors offer rules of thumb rather than benchmarks. ChurnZero says SaaS companies typically start investing in CS Ops “when they reach around $10 million in revenue.” Gainsight's 2021 guidance put the start at five or more CSMs, with expansion around 10 CSMs. Gainsight's 2023 data found the role “becoming more common in companies with more than 20 Customer Success Managers”.
Same survey, four answers on how common the role is
Here is every prevalence figure Gainsight has published for dedicated CS Ops, with the definition and sample behind each one.
| Report | Headline figure | What was counted | Sample |
|---|
| CS Index 2022 (press, March 2022) | 61% | 41% “newly formed” plus 20% “well-established” | 350+ companies, fieldwork late 2021 |
| CS Index 2023 North America | 20% in 2022, 41% in 2023 | “Dedicated CS Operations organization” | About 400 North American companies |
| CS Index 2024 | 51% | B2B tech companies with a “dedicated CS Ops team” | 250+ companies in North America and Europe |
Sources: Gainsight CS Index 2022, CS Index 2023 NA, CS Index 2024.
Read in sequence, the numbers look like wild swings. Read with their definitions, they tell a simpler story. In the 2022 release, 41% of companies described their CS Ops function as newly formed and 20% as well established. The 2023 report then compared its new figure with the stricter 2022 count. It said adoption had “more than doubled, from 20% in 2022 to 41% this year.” That's a change of definition, not a doubling.
The samples also change each year, from 350 companies to 400 in North America only to 250 across two regions. So the honest answer to Carmen's CFO is a range. Somewhere between two in five and three in five companies with a CS team report some dedicated CS Ops capacity, depending on what counts as dedicated. The role is common enough that nobody needs to defend its existence. It's not settled enough to copy a job description from someone else.
The budget rule runs from 3% to 10%, and one version is wrong
Budget guidance has the same problem. Three versions circulate, and they differ by an order of magnitude.
- A median of 3% of the CS budget. Gainsight's 2022 research says “the median investment in CS Ops reported by companies is 3% of the CS budget.” That's what companies were spending.
- 10% of the CS team's cost. Gainsight's 2021 guidance put “the overall mature level of resourcing for CS Ops at 10% of the cost of the CS team.” That's a recommendation for a mature team, not a median.
- “10% of revenue into CS Ops.” This version appeared in trade coverage of the 2022 index. Gainsight's own release says the companies with the highest NRR invested 10% of revenue in their CS and CSOps teams combined. Applying 10% of revenue to the ops function alone overstates it roughly tenfold.
For a seven-CSM team, the first two versions translate into very different requests. At 3%, CS Ops is a fraction of one person. At 10% of team cost, it's most of a full-time hire. Both are defensible, but only if the request says which one it's using and why. A budget line that cites “10% of revenue” won't survive a finance review, and it shouldn't.
Pay data is thinner still. We found no salary figure for this role with a published method. The figures that circulate are crowd-sourced job-site averages relayed by vendors, so benchmark pay against your own CS and RevOps bands instead.
Where the published scope stops, and where the work doesn't
Every vendor scope list above describes a job inside the CS team. The problems that justify the hire usually cross that line.
CS teams already run support tools
ChurnZero surveyed more than 1,000 CS leaders in 2024. “Nearly 64% of smaller companies surveyed ($5 million to $49 million) reported their CS teams adopting support software.” The report reads that as a lack of role definition between CS and support. For a CS Ops manager, it means the systems they're asked to run include a help desk they don't own, with data they can't change.
CSM workload is the real constraint
ChurnZero's 2024 survey of CSMs found that “just 40% of CSMs say their workload and schedule is realistic, and only 41% say they can complete their work without working evenings or weekends.” Much of that work is answering questions, chasing onboarding tasks and preparing reviews from several tools. A CS Ops manager can build a better dashboard of that workload. Removing it means changing where answers, tasks and requests live, and that reaches into support and knowledge.
AI plans run ahead of AI in the stack
The same 2024 study found 87% of respondents using or planning to use AI, but only 21% had adopted it in their CS tech stack. The usual blocker is the data under the AI. A CS Ops manager whose scope ends at the CS platform can't fix content that lives in the help center.
None of this means the role should absorb support operations. It means the boundary needs a decision, not a default. Our comparison of customer operations and customer success covers where that boundary tends to sit as companies grow.
How to scope a customer success operations manager before you hire
Scope the role by the records it will own. A job description written from a vendor template lists activities. A job description written from records tells the new hire where their authority starts and stops.
| Record | CS Ops owns | CS Ops shares | Decide explicitly |
|---|
| Account health and renewal forecast | Yes | | Which inputs come from support and product |
| CS playbooks and success plans | Yes | | Whether onboarding plans live here or in a project tool |
| CS platform and CRM fields | Yes | With RevOps | Who approves schema changes |
| Customer requests and help desk | | With support operations | Who owns routing when a CSM is involved |
| Help content and in-app guidance | | With knowledge or enablement | Who updates content when a playbook changes |
| Capacity and territory planning | Yes | With finance | Which cost measure the role reports |
The table is a template, not survey data. Fill it in with your own tools and teams. The rows marked “shares” are where most CS Ops hires stall, so name the partner and the decision before the start date.
- Pick the cost measures first. Adopt cost to retain and cost to expand from Gainsight's sample description. Agree how finance will calculate them.
- State the budget rule you're using. Median 3% of CS budget or 10% of team cost, with a sentence on why.
- Fill in the record table. Mark every shared record with a named partner and a decision owner.
- Set a 90-day deliverable per owned record. For example, a renewal forecast built from live fields instead of a spreadsheet.
- Plan the reporting line. Gainsight notes that most CS Ops leads report to CS leadership, the COO or the CRO. It also warns that “VPs of CS shouldn't split their job between executive leadership and operations.”
The founding-hire sequence after that, including when to add a second person, is covered in customer operations team structure.
Giving the role records it can actually own
The shared rows in the table are shared because the records sit in different tools. Onboarding plans live in a project tool, requests live in a help desk, and help content lives in a knowledge base. A CS Ops manager ends up building syncs between them instead of improving the programs they were hired to run.
MatrixFlows gives customer operations one foundation for those shared records. Onboarding projects, customer requests and knowledge articles are tables in Matrix with a shared taxonomy. Views chart any of them by account or segment, and Automations can route a request or create a follow-up task when a field changes. The operations manager changes forms, fields and rules without an engineering ticket. The CRM keeps the account and contract. The rows marked “shares” become records with one owner and several readers.
Carmen's CFO got a better answer than a percentage. She sent the record table with the budget rule written on it. The request was approved on the second read, because it said what the new hire would own.
Create a Free Workspace → and map the records your first CS Ops hire will own before you post the role.
.svg)
.svg)
.svg)
