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. 

You have to look at what the business cares about and then work backwards to how Customer Success fits into those overall targets. For example, if the business has a retention problem, it's probably important to have a Gross Revenue Retention KPI. If, however, the business is more interested in price increases and cross-sell and upsell, then tie CSMs to Net Revenue Retention. At AlertMedia, there was a business-wide push to build out our Advocacy program so we incentivized CSMs to source advocates and add them to our pool. This dramatically increased the number of advocates we have to pull from going forward.

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!

There are two questions I always like to ask during an initial interview with a candidate: 1. Tell me about a problem you have worked on and how you solved it? - In full transparency, I actually borrowed this question from an article I read about Elon Musk's interview questions. I found the reasoning behind this question to be extremely interesting. First, you gain insight into the types of challenges the candidate has come across and their thought process for overcoming those challenges. Second, Musk says that this question shows him if the candidate truly worked on resolving this problem. Someone who was integral in the solution of a problem will know all the details and be able to explain in length what they were thinking was during the process. I have found a lot of success in asking this question. 2. I ask candidates to share with me a time they had to articulate value of their product/solution to a customer. As I mentioned in another question, showcasing your company's value is one of the most important responsibilities of a CSM. If a candidate does not have experience with this, how can I expect them to articulate value to our customers?

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!

For me personally, the decision was easy. I moved from technical support to Customer Success. They combine in what we deliver called Customer Experience—transitioning a customer from pre-sales to post-sales and then a steady state followed by expansion. It is called the customer journey or roadmap. Influencing a ‘Promoter’ and a reference customer is a powerful and exciting feeling. This roadmap is driving thru an effective success program. It is essential to ensure that the customer journey ties directly to the growth of the customer. ‘What is in it for me’ and ‘Why should I do it.’ Historically there were package software products where we shipped diskettes and CDs to the customer. Today there is instant gratification via SaaS and Cloud delivery methodologies. Selling both have changed in many ways, and yet not so much. Changed from potentially selling shelf-ware to more value-based selling. However, the sales comp structure is different. Sales are often compensated based on new logs and new revenue. They stay engaged (sometimes)if there is a continued source of revenue, aka Beachhead or a potential large reference client. In some ways, sales and customer acquisition become a quarterly agenda and tactical focus. Customer Success, on the other hand, fills in this very important air gap. Success builds a long-term relationship with the customer. They map a customer’s journey from onboarding to go-live to additional use cases/verticals and adoption. Remember, Success in no way - Support. Support is ticket based reactive. Success is a program-based future roadmap for the customer. Success focuses on long-term relationships and building intrinsic value. Building and growing through nurturing a customer throughout their lifetime. In many ways, Success plays the most crucial role in the company because they retain customers and create value. The more value they create, the more sticker they are. The bottom line is that Wall Street is happy! Nutshell, a fundamental company structure, can only be built with these three pillars, Sales/Success/Support.

My philosophy is that I want everyone on my team to be eligible for a raise, so it’s my job to help them understand what they need to do so that I can make the case to the business. Just as they are the advocate for our customers, I am the advocate for them. It’s not just about the quantitative - there are many qualitative things I consider when recommending a pay rise. Some of the most common pieces of advice I give to my team are: 1. Make sure you are a master of your business. Exceed your metrics or have a clear explanation of where and why you fell short. It isn’t essential that CSMs are always over 100% on everything, but you should have a clear plan that addresses why you are behind. 2. Are you having an impact outside of your specific book of business? Are you helping others when you can? Are you seeking out and taking on additional projects and opportunities when they come up? 3. Are you upholding the values of the team and organization? Are you having a net-positive effect on the morale and engagement of your peers around you?

This is a tough one! In this situation, I would do my best to flex my diplomatic skills. Draft up communication that includes both Execs (with some other relevant stakeholders if possible) and do your best to lay out the pros and cons of both options, doing your best to appear as neutral as possible and then push these execs to make a decision one way or the other. If you feel very strongly that one option is the correct one, and you have facts to back this up, do not walk away from an opportunity to appear decisive and in control. I would much prefer to be fast and wrong (and then course correct) than taking too long to make a decision, or even worse never making one at all!

Business Model. For me the company should be a SaaS based company. I.e. selling cloud-based software for a subscription fee. If the company is hybrid i.e. has some older products that are still perpetual / on prem but mostly moving to SaaS then that is for the most part acceptable. Is the company's philosophy and strategy of Customer Success aligned with my own. I would also assess the maturity level of the Customer Success Organization and where it reports into. Ideally Customer Success reports to the Chief Customer Officer who in turn reports to the CEO Business Performance and Potential. Is it a high growth company? Is the NRR in lines with industry expectations? Does the company have low churn? Are they the market leader in their field (Gartner Magic Quadrant, Forrester Wave). Is it Customer Led Growth? Are they #1 or #2 is their chosen market(s). Is the company profitable? Are they hiring & retaining staff (in particular in customer success). I also weigh up the pros and cons of the company being publicly traded versus privately owned. The role: Is the role both a challenging one and one where I can add value. Is there opportunity for growth and development? Will I be enabled for success? Is it clear what success looks like for the role. Company Values: Are the company values aligned with my own? Can I add to the company culture? How is the company perceived an an employer (feedback from connection, reviews on indeed and glassdoor) Management & Leadership: Is the hiring manager (& next level manager) someone that I can connect with and have strong rapport. Can we work effectively together? Can I potentially work well with my Team One (Peers)? I examine the leadership and look at their past track records. Are they successful in building and growing companies?