I've found two KPIs to be difficult to commit to: 1. Customer Health. If you have a robust algorithm to measure customer health (influenced by a number of inputs ), it can be hard commit to a certain outcome. To frame this another way, I've often observed customer health scores as being a bit of a black box where it's hard to tie the actions you take to specific outcomes when there could be a number of variables outside of your control that influence the ultimate score. I much prefer to commit to lead measures that are directly within the control of the team. KPIs related to customer engagement are a good example of things that are more directly within the team's control. 2. Upgrade rate. Many CSM teams are measured on Net Revenue Retention. As part of this, your CSMs may be responsible for identifying growth opportunities within the install base of customers. I find it's effective to measure the team on how many growth opportunities the team identifies but not the close rate or upgrade rate, especially if the Sales or Account Management team owns the closing motion. 

Technical Support response targets! We’ve all been there, and being the first Success Hire is super exciting. You get to wear many hats, get involved all the way through the customer lifecycle and be scrappy to get customers what they need. For us at the beginning, that meant taking on a lot of Technical Support tickets for our EMEA customers, especially in the morning before our then US-based tech support team was online. On the one hand, this gives you a lot of valuable product knowledge that can help you be an impactful CSM, but on the other hand, it can mask the business need to expand technical support teams and can hurt your focus in the long term. If you can, explain early the difference between CS and Tech support KPIs and ensure that anything you take on is temporary!

Rather than just asking a candidate about their background, I prefer to ask about real situational questions. Here are a few of my favorites: * Tell me about a time you had an unhappy customer. What was the issue and how did you resolve it? * Take me through a time when a customer provided a churn notice and you were able to save them. What was your process and how did you turn things around? * Walk me through one of your recent renewals. When did you start the renewal conversation and what did the entire process look like? Also, in my opinion, all candidates need to do some type of live presentation for the hiring manager/team before an offer is sent out. Keep in mind, presenting to customers is a major part of a CSM's job and is not a skill I recommend you judge based on an interview and/or resume. While a candidate can tell you all about their communication style and experience, I believe the only way to truly judge their presentation skills is to see it live. 

I find the best CSMs are: * Curious - they want to understand “why”. This translates well with customers as it means they have an innate desire to understand their business. It also means that they are likely to find the CSM role very rewarding. * Builders - especially in the early days. * Empathetic - Empathy has 2 components as a CSM: 1) it helps build a personal connection 2) it allows a CSM to more successfully advocate on a customer's behalf internally.

Our current path goes CSM - Sr. CSM - Principal CSM - Mgr, CSM - Dir, CSM - Sr Dir, CSM. I think there are options along the way as well to move into or come from pre-sales, sales, marketing, product, ops, or talent acquisition, depending on how your organization is set up.

The two areas I would recommend are 1) Sharpening your Sales skills and 2) Adopting some Product Manager mindsets. When working with customers and the further upmarket you go, the more enriched these conversations need to be and the immediate areas for many customers are to understand their contracts, how they can scale with your product, value alignment, and ROI. Supplementing this, customers want to know how your product will be evolving and how their feedback can influence the roadmap. Being able to cut right to the value of a product, requirements, outcomes, and how those align with the customer's values will set your customer and Product teams up for mutual success!

My journey was the other way around. I started at a company where CS was brand new, and then came to a company where CS was established. Looking back, here are some interesting findings. * Perceptions of what Customer Success is/isn't vary widely, even if the function already exists at the company. When CS doesn't exist yet, there's an explicit need to educate the executives, sales reps, product org, etc. on what the team will do and the results they will drive. At a company where CS is established, that need for ongoing education still exists-- it just takes a different flavor over time. * When there's no Customer Success (and even when there is), information on customers can be scattered all over the place. That's why we prioritized getting a CS tool early on, so if nothing else, we would have one place where customer documents, interactions, health, etc. were kept. It takes time to manage that change (put info here, not in your notepad) but it's worth it. * If Customer Success hasn't existed, the company may be getting its first taste of churn (what prompted them to create Customer Success anyway?). That first taste of churn is bitter, and chances are the data and workflows around risk mitigation and learning from churn aren't well built out. This is an area to invest early- capture the reason codes, build a churn forecasting process, and educate everyone on churn and risk. Moves you make today may take 6+ months to have an impact so make sure to set expectations.

This answer is entirely dependent on the what field/product the CSM works with, who their target persona is and what resources are available based on company maturity. For someone dealing in cybersecurity, working mostly with CISOs, technical skills are more important. For someone in general CRM, maybe not so much. My feeling is that process experts > product experts. I find the best CSMs have strong business acumen, can step into a customer relationship and understand where there is opportunity to either (1) inject their product into existing process to create efficiency or (2) suggest a new process built around their product that drives better outcomes. That is less about deep technical knowledge and more about an ability to understand what value means to your customers and how your product can deliver that. Assuming that you have resources available to you that allows you or the customer to solve a technical issue when they arise, your true value is driving results vs. troubleshooting.

The first step to knowing if a client is at risk of churning is to identify the potential warning signs: * Lack of Engagement * Client Turnover * Service/Support Issues * Economic Climate * Poor Performance * Low CSAT/NPS Scores Once you understand what to look for you can better assess risk within any given account and create an action plan to get things back on track. I've found the most impactful element to avoiding churn from the onset is to create strong executive relationships with clients. This allows for a feedback loop to prevent frustrations and address issues quickly.

* What does "Customer Success" mean to you? Customer Success as a field and profession is relatively new, and the term can mean different things to different people. A candidate's answer helps me assess their whether their experience is aligned to a proactive vs reactive approach, what kinds of customers they've worked with in the past, how they think about the customer experience, and more. * If you were constructing a CS team from scratch, what metrics would you use to gauge success? Both internally and customer-facing? While this is a highly debatable topic, the key is that metrics described cannot only be financial. Yes, at the end of the day (... or, quarter) we are all working towards financial outcomes. But Revenue Retention is a lagging indicator, and it's important to understand that leading indicators such as product usage, presence of risk factors, and engagement are critical for proactive customer success. * How do you know a customer is successful? The best candidates use this as an opportunity to talk about aligning the value a company's product and services drive to the customer's business goals. I'm looking for CSMs who focus on a customer's business-level outcomes at a strategic level, rather than those who focus on getting their customers to adopt our product or services.