November 2022 CS Ops Newsletter

  • 9 November 2022
  • 9 replies

Userlevel 7
Badge +6
  • Gainsight Employee: ACE
  • 548 replies

Subscribe to this monthly newsletter here!



Hi there,

I’ve recently had a surge in questions about the ‘right’ investment in CS Ops. Welcome to budget season! I respect that it’s a tricky challenge. You’re not buying more of the same ol’ stuff. It’s more nuanced: you’re investing to unlock access to a more sophisticated version of your CS team.


(Also recently, I’ve had entirely too much fun with DALL-E, generating AI art.)


So, if you’re taking stock of your CS Ops spend, I have two north stars to offer:


(1) What’s everyone else investing?

Data from 2021 says:

  • A ratio of CSM:CS Ops of 12:1. This comes from a Gainsight survey of 60+ companies with at least one CS Ops role.
  • 61% of companies have CS Ops, which was triple the rate of the previous year. Average CS Ops spend = 3% of CS spend (middle two quartiles ranged from 1% to 7%). This comes from a Gainsight and RevOps Squared report, based on a survey of 350 companies.
  • For example, Gainsight’s CS Ops team is called “Ops & Scale”, and is over 20 people, including its SVP, who reports to the CCO. Our remit is large (see below), but our mission ties us together: Ops & Scale creates elegant solutions to ambiguous problems in customer and teammate experiences.


(2) How much do you get from the investment?

  • CS Ops is always oriented towards improving retention, expansion, account ratios, or new logos (via advocacy). Get Finance’s help to pick the one(s) that will have the biggest impact on your business. I explain in this blog how to be a storyteller to leadership, drawing the line from these dollar-based metrics to programs that CS Ops pros are experts at executing.
  • Reinforce your storytelling with metrics. I posted the best tactics I’ve heard to measure CS Ops impact. Please comment with your own ideas and questions.


Digital Customer Success

(a.k.a. easy-to-explain ROI for CS Ops)

I used to think that, if Digital CS had a subtitle, it would be, “Automating CSM tasks.” I’ve changed my tune. I now frame Digital CS as, “Answering customers’ questions so CSMs don’t have to.” Automation can serve up resources so that a customer wouldn’t even ask the CSM at all, but don’t ignore opt-in/on-demand Digital CS. For example, Gainsight customers have questions about CS Ops all the time. Our CSMs now have numerous resources to offer, including this newsletter. In the olden days, CSMs would have had to compose and present information customer-by-customer. 

My manager, Tyler McNally, has been dropping some awesome visuals about Digital CS at Gainsight in my post about Digital CS org structures: Comment 1 | Comment 2.

  • Next week! Digital EBRs meetup
    Join us November 15 at 11am Pacific to meet peers working in digital-led CS. Our topic will be "Digital Business Reviews". We’ll settle in briefly before moving to breakout rooms for discussion (and storytelling!). Each group will take notes to help us come back together to share the most impactful takeaways. (This is the same format as our last session, which was focused on digital-led onboarding -- see the next bullet.)

  • Digital onboarding: Watch our meetup
    Our last meetup focused on digital onboarding processes. Seven breakout rooms discussed the most important things to keep in the move from human- to digital-led, and success metrics.

    Watch & Read the Takeaways
  • Digital-and-human blend
    Carolyn di Buono of Propeller Aero (and Gainsight alumna) presented about their program that blends digital and human touchpoints: webinar | blog. (Learn more by reviewing the takeaways from an earlier meetup on the topic.)

    Read the Propeller Aero Blog
  • Digital CS at Alteryx
    The Alteryx team has also been on a tear sharing their digital CS story, and is even presenting about it at Pulse Europe this week. Get the overview: webinar | blog. Also, learn about their prescriptive success plans.

    Read the Alteryx Blog
  • Digital CS best practices
    We've just published the Big Book of Digital Customer Success, covering the cornerstones and best practices of a strong program. Bring it with you as you grab a cup of tea, a comfy chair, and a notebook, and get ready to think Big Thoughts about what you most need to build next.
Change Management in CS

If you missed (or are fondly missing) Pulse in San Francisco, I'm delighted to surprise you with one more session! Justin Bills wasn’t able to present live, so here’s your chance to get back in the mood.

Poor change management can be a Gainsight Admin’s kryptonite. Learn from Justin Bills as he shares his superhero origin story, which began when he took over Greenhouse’s Gainsight instance post-implementation. Learn the superpowers for change management that enabled Justin to drive team-wide adoption of Gainsight alongside record-breaking retention for the business. You’ll fly away understanding how to engage your stakeholders, leverage agile project management, create visibility into CS operations, demystify an existing Gainsight instance, and enable your team.

Join us November 30, 9am Pacific. The registration page is almost live! Block it on your calendar with a link to our community events page, where you'll be able to find the info.


Use Your Data

I’m reading a book from 10 years ago, which offers a passionate call-to-arms to capture data about your customers. Part of me thought, “Ha! I couldn't stop collecting data. Can’t wait for the section about CD-ROMs.” But another part of me raised an eyebrow at the first part: “How much are you actually using the data you’ve got, Seth?” The grunt-work of analysis pushes me away. I’ve spent enough time in my life doing VLOOKUPs by email address. (I particularly resent the pang of fear, after an hour of work, that VLOOKUP might be case-sensitive. Spoilers: It isn’t. But I just had to look it up. Again.) Let’s keep reminding ourselves of how much power lives in our data.

As today's reminder, Valuize CCO Emily Ryan continues her series of CS Ops conversations by talking about customer data blind spots. She’ll talk with Joel Passen, co-Founder at Sturdy, about how data can improve Net Retention when you make it visible, and when you use it to shape the customer experience.

Watch Emily & Joel


CS Ops Career Development

Come meet folks any time:

Maximize this Newsletter

You made it all the way to the end! 

Let me reward you with Romain Belvas hitting a bit too close to home:


Customer Success Systems Architect




Seth Wylie | Director of CS Ops & Admin Community
He/Him/His | Based in Boston, MA
Gainsight Certified Administrator

9 replies

Userlevel 7
Badge +11

Unpopular opinion: rather than a CSM:CS Ops Ratio, we should be talking about a CX IC:CS Ops Ratio. Limiting ourselves to CSM users only limits the way CS Leadership and Ops/Systems leadership soaks in these studies in order to make business and resource planning decisions. At least 1/3 of our GS users are not CSMs - but require just as much support. 

Userlevel 7
Badge +6

Deeply in support of the sentiment behind this: CS Ops serves people beyond CSMs. That said:

  • Those people are broader than even CX individual contributors
  • If/when CS Ops includes Digital CS, then the CSM:CS Ops ratio is even more meaningless
  • The ratio does approximate the size of an organization. More CSMs means that you’re more likely to have more customer segments and verticals, more sophisticated programs, etc.

All of that being said, the main reason I shared the ratio is because it’s the data that existed. 😆 However, I’m glad you brought this up, @gunjanm , since I didn’t really think about whether or not to include it at all, or to give it an asterisk.

Should we remove all these complications by thinking about CS Ops spend as % of ARR? 🤔

Userlevel 7
Badge +11

@seth I think an even better approach may be a weighted avg based on # of customers with dedicated account teams (and some component of size of those account teams) vs tech touch customers. Complicates the formula quite a bit but hey, everyone knows there is no silver bullet here anyway!

Userlevel 7
Badge +6

I dunno -- if named CSMs have a separate calculation for Ops spend, then a company that has successfully moved tons of its accounts to digital-only will look the same as a company that hasn’t attempted to move any. Doesn’t it all come down to ‘how much of a customer base are you giving the CS they need?’

Userlevel 5
Badge +3

Great discussion - it’s hard to add to!

I do think it can be challenging to demonstrate ROI if the equation is: many groups benefit in different ways and the costs are centralized in CS Ops. 


That’s why I think focusing on the primary/largest value can make it easier to talk about.  If we add one CS ops person, we can increase ratios by x%.  Is that worth it?


Ultimately - IMO - cost of CS / cost to serve customers is probably a better metric.  But I think ops:CSM ratio is still helpful in certain cases.


@seth, thanks for the informative newsletter. Interested in your take on how the renewal motion (e.g., automated renewals or customer self-service renewals) ties into or relates Digital Customer Success. Is it part of the same department and digitally-led motions?




Userlevel 7
Badge +6

Great call-out, @DougCaviness ! I do feel like it’s only a digital CS team that’s going to understand the nuances of:

  • Which customers should get an automated renewal message?
  • At what time?
  • Via what channel(s)?
  • Sent to exactly which contacts?
  • What exactly should it say?

That said, I feel like it needs to be deeply collaborative with the sales team, because:

  • There should probably be an easy escalation motion if the customer doesn’t want to renew
  • There ideally would be an opportunity to talk about expansion
  • Sales / Sales Ops should handle the deal-desk side of things

So, Digital CS would own the communication, but Sales would design the renewal process.

@lane_h might have some more thoughts here

Userlevel 6
Badge +5

@DougCaviness Great question! Our Scale team worked with our Revenue Ops team to build a process for a “Low Touch” Renewal. I wrote the emails that would go to customers. Then we hired an individual transitioning into Tech to help execute them. We target 1, 30 min meeting or less with the customers in the low touch renewal process. For customers who signal desires for expansions we pass them back to the account management team.

Our process is a series of emails at 180, 120, 90, 60 and 45 days prior to renewal. The audience for the emails are key personas and decision makers.

Thanks @lane_h and @seth!