How to Hire and Measure Customer Success Across SMB and Enterprise | Pratibha Wadhwani

Customer success hiring looks deceptively simple. Post the role, screen for communication skills, and check for SaaS experience. Done. But anyone who has tried to build a CS team knows this is where the errors start. The skills required for SMB customer success and the skills required for enterprise customer success are not the same. The metrics that matter for each segment are not the same. The career paths that produce strong CSMs are not the same.

Pratibha Wadhwani knows this because she has lived in all three. She began as a sales coordinator, moved into account management, and now works as a Senior Customer Success Manager at Birdeye. In this episode #6 of Xobin Talks, host Amrit Acharya, our co-founder and COO of Xobin, sits down with Pratibha to unpack the specific differences in CS across segments, how to hire for each, what metrics to track, and how to run the function when your customers are in a different time zone.

Why Does a Sales and Account Management Background Produce Strong CSMs?

Customer success sits at the intersection of three disciplines: sales, account management and strategic consulting. A CSM who has only ever done support will struggle with upsell conversations. A CSM who has only ever done sales will struggle with the long-term relationship cadence. The CSM who has done both is almost always the most complete practitioner.

What Sales Teaches a Future CSM: Pratibha is direct about her own journey and why it prepared her well. As a salesperson, she learned to find opportunities, build pipelines and close toward a target. Three to four years of that work made her comfortable with commercial conversations. She learned to spot when a customer had a budget, intent and a business problem worth solving.

What Account Management Adds: As an account manager, she learned to sustain relationships over time. Account management is not about closing. It is about keeping. You learn to read different client personas. You learn that not every account can be managed with the same playbook. You learn that tailored solutions and consistent touchpoints are what separate accounts that grow from accounts that drift.

As a CSM, she uses both of these simultaneously. When a customer is underusing a product, the account management instinct kicks in. She maps the gap and creates a plan. When there is an upsell opportunity, the sales instinct kicks in. After that, she builds the conversation.

Is Client-Facing Work Right for You? The same pattern holds for people transitioning from marketing or QA. The first question to ask is not "Do I know enough about customer success?" It is "Do I like being client-facing?" Some people do not. Client-facing roles require a willingness to sit with uncertainty, manage escalations, represent a company under pressure and show up differently for 50 different personalities. If the honest answer to that question is no, the transition will be hard regardless of what course someone completes.

Pratibha's trajectory from sales coordinator to account manager to senior CSM across different industries and geographies gives her a practitioner's view that most CS training programs simply cannot replicate.

How Does the CSM Role Change Between SMB and Enterprise?

The role shares a name but not a skill set. Top-performing SaaS companies with strong customer success programs push NRR above 110-130% (Velaris, 2025). But how you get there looks completely different depending on who your customers are.

The SMB Customer Success Manager: SMB customers are typically less technically sophisticated. They need more onboarding. They need more training. They need more hand-holding through product adoption. Even after a dedicated onboarding team completes implementation, an SMB CSM should expect to revisit core features repeatedly. These customers forget. They have high staff turnover. They come and go from the platform. The relationship building is harder because they are often harder to reach. They do not always show up to monthly cadence calls. They miss QBR invites.

The SMB CSM who succeeds stays organized enough to manage 100 or more accounts without dropping any. Therefore, they work with precision and follow structured systems. Every day, they actively handle a defined set of accounts with clear focus. Meanwhile, every week, they maintain a sharp view of which accounts show risk signals. They do not rely on memory or instinct to guide decisions. Instead, they depend on data and processes to stay consistent. Once the number crosses 100 accounts, instinct no longer works.

The Enterprise Customer Success Manager: Enterprise customers are the inverse. They come in technically prepared. They have done the research. They know the product. In many cases, the VP of Marketing or Director of Operations on the other side of the table knows the platform better than a junior CSM. The Enterprise CSM who walks in without product depth gets exposed immediately.

What Enterprise CSMs must bring is presence and conviction. They need to take control of a QBR, not just present data. They need to push back constructively when a customer is using the product in a way that undercuts their own results. They need to build relationships at the VP and C-suite levels. The book of business is smaller, typically 30-50 accounts, but the relationship depth required per account is far greater.

How Should You Hire for SMB vs. Enterprise Customer Success Roles?

The interview process should look different for each. Companies with NRR above 120% grow 2.5x faster than low-NRR counterparts (Fullview, 2025). That growth is driven by CSMs who are correctly matched to their segment.

For SMB, Pratibha looks for someone meticulous by nature. Someone who is naturally organized. Someone who thinks in systems and is not overwhelmed by volume. Communication matters, but precision matters more. Can this person track 100 accounts, maintain cadences, flag renewal risks 90 days out and still run outreach for product adoption? That is the job.

For Enterprise, she looks for a consultant's mindset. Product knowledge is non-negotiable. The candidate must be able to talk about the product's ROI with specificity. They need to demonstrate business acumen. They need to handle tough questions from senior stakeholders without losing composure.

Her preferred evaluation method is practical. She gives candidates a demo or QBR simulation. Not a hypothetical. An actual scenario: Here is the product, here is a customer profile, and here is the data. Present the results as if you are in the room with the client. This single exercise reveals everything: how the candidate structures their thinking, how they communicate results, how they handle pressure, whether they have the presence to hold a senior audience's attention.

Assessment tools also play a role. Especially for SMB roles, where volume is high and mis-hires are expensive at scale. A skills assessment before the interview stage helps filter candidates who look good on paper but lack the analytical or communication depth the role requires, and structured AI interviews keep the early screening consistent across a large applicant pool.

What KPIs and Metrics Should a CS Team Be Tracking?

The six metrics that matter most are NPS, CSAT, churn rate, NRR, customer health score and time to value. NRR is the one metric that best represents overall CS health because it combines retention, expansion and contraction in a single number (Gurusup, 2026). But Pratibha is clear that daily operations require a broader view.

Daily: Payment and Activity Monitoring. On a daily basis, she tracks whether there is a past-due on any account. A client with an outstanding payment is at quiet risk. They may not say anything. But the moment billing creates friction, renewal risk increases.

Weekly: Account Health Review. On a weekly basis, she reviews account health: which accounts have not logged in, which accounts have support tickets that are aging, which accounts missed their last call. Each of these signals a potential problem worth addressing before it becomes a formal renewal conversation.

Quarterly: NRR and Renewal Pipeline. On a quarterly basis, the key metric is NRR. Pratibha is given a target of 90% NRR and above in her book. That means downgrades and churns must be offset by expansions. To hit that number, product adoption is the most important lever. If a client subscribed to 10 features and is only using six, that is a downgrade risk. The CSM's job is to run the ROI story on the unused four features before renewal arrives.

Renewals are managed through a 90-day pipeline. Not 30 days. Not 60 days. Instead, ninety days ensure better control. When you spot a renewal risk at 30 days, you have almost no time to fix the core issue. However, identifying it at 90 days gives you enough space to act. You can schedule a QBR, run a SWOT analysis on the account, and close the product adoption gap. As a result, you enter the renewal phase with a stronger, more convincing story.

The SWOT Method for At-Risk Accounts: Pratibha uses a SWOT analysis approach for at-risk accounts, and this stands out as one of the most practical methods shared in this episode. When accounts start showing warning signs, her team selects five accounts per sprint and evaluates each using strengths, weaknesses, opportunities, and threats. Then, they convert the identified weaknesses and threats into clear call-to-action steps. For example, if they notice low adoption of a specific feature, they respond by organizing a live training session. Similarly, if a client mentions a competing product as a threat, they address it by sharing a case study along with an ROI comparison. As a result, this method transforms account reviews from a passive activity into a focused and structured intervention.

What Are the Specific Challenges of Cross-Geography Customer Success?

Geography changes the rules of engagement, not the goal. The goal is still retention, product adoption and expansion. But what it takes to build a relationship is shaped by cultural norms that CSMs must learn to read.

Pratibha manages accounts in international markets from India. This means working across time zones, conducting all relationships digitally and adapting her communication style based on who she is speaking to.

The most important behavioral difference she has observed is in how clients signal discomfort. Indian clients, in her experience, tend to avoid a direct "no." They may go quiet. They may reschedule calls. They may become vague about renewal timelines. A CSM who reads silence as agreement will miss early churn signals entirely.

International clients, particularly in the US and Europe, tend to be more direct. If they are not interested in a renewal or expansion, they will say so. This clarity is actually easier to work with for a CSM who is trying to manage a pipeline, even when the signal is negative.

What both markets share is a response to transparency and product confidence. Clients who feel that their CSM genuinely understands the product, knows their business context and is being honest about capabilities and limitations are more likely to stay, regardless of geography. Empathy is not culturally specific. Preparation is not culturally specific. Showing up to a QBR knowing your data is not culturally specific. These are the things that build trust across every geography.

How Do You Navigate the Case Study Approval Process?

The instinct to get a case study signed off quickly is usually what kills the process. Pratibha has seen this pattern repeatedly. A CSM gets excited about a strong customer result. They rush the request. Legal gets involved. Marketing reframes the story. The client's team loses interest. The case study dies.

Her approach is different. She gives a customer six to eight months to see real results before requesting advocacy. Not a success story. Actual data. Meaningful outcomes. By the time she makes the case study ask, the client already has a story they want to tell. They are proud of the result. The request lands in a different emotional context.

Volume also matters. A CS team that manages 300+ customers over two to three years should build a library of 50-60 case studies. This step is not optional. Instead, it forms core infrastructure. When a prospect asks for proof, a case study from their exact industry answers their exact question. As a result, it becomes the fastest way to close a deal. However, when you lack one, you end up improvising.

Meanwhile, if marketing or legal slows the formal process, Pratibha relies on analytics. She presents ROI data directly during client conversations. On top of that, she uses the platform's dashboard to highlight what the client has achieved. Also, she turns the quarterly business review into a strong proof point. Therefore, the case study becomes a formal record of a story the client already knows is real.

What Tools Does a CSM Actually Need?

One good CRM used consistently outperforms three tools used badly. Pratibha's core tool is Salesforce. Not because it is the most complex platform available, but because her entire team uses it consistently. That consistency is what makes it valuable.

Every client conversation is logged. Every CSM next step is recorded after each call. Every renewal date is tracked. Every risk flag is visible to the manager when they review an account. When a CSM is out sick, the account does not go dark because everything about it lives in one place.

She also uses Salesforce to manage the activity rhythm of her team. Good CSM behavior, proactive outreach, case study sharing, and ROI conversations are not visible unless they are logged. By reviewing activity history regularly, she can see which CSMs are composing and not just replying.

The tool is not magic. A CSM who does not log will have an empty Salesforce record that tells their manager nothing. The discipline to document is the skill that amplifies the tool's value.