Custify

High touch coverage does not scale. Signal driven coverage does. On Mastering CS – Candid Leader Insights, Dylan Berno, Head of Customer Success at Coast, broke down the operational shift that is allowing his team to grow without doubling headcount every two months. The old model is straightforward — more customers means more CSMs. But that math breaks down fast in a business growing as quickly as Coast is. So the team made a deliberate shift: Stop covering accounts by default. Start moving when the signals tell you to. That changes everything about how capacity is used: → Time goes toward activation, not maintenance → Interventions are intentional, not reactive → The team can manage a broad range of customers with different use cases without burning out And activation is where Coast invests most heavily — because their customers are busy leaders whose fuel and business spend is rarely the top priority on any given day. Value has to be created. Urgency has to be built. Nobody is waiting for your outreach. The metrics driving all of it are simple but clarifying: Revenue per headcount. NDR. Customer outcomes. Not activity. Not coverage. Results. Because the modern CS program is not about how many touches you make. It is about making the right touch at the right moment — and having the system to know the difference.

What if your Friday success plan updates wrote themselves? 🤖   Cassandra D., Enterprise Customer Success Manager at Orca Security, built her own AI workflows to cut admin time and focus on what actually moves accounts forward.   Here’s what her AI handles every week:   📩 Drafts a follow-up email for every customer meeting, ready for her to review and send   📋 Updates success plans and key milestones every Friday based on customer conversations   🚨 Flags and prioritizes risks from calls, Slack, and her calendar as critical, high, medium, or low   🔍 Analyzes support tickets from her biggest accounts to spot misunderstood features, hidden requirements, and expansion opportunities   Her take: most CS admin follows the same format with different content, which makes it perfect for automation. The time saved goes into strategic work.   In this episode of Mastering CS: Candid Leader Insights, Cassandra also talks with Irina Cismas about milestone-based onboarding, closing Q4 early in EMEA, and building the first CS playbook for the French market at Procore.   🎧 Watch or listen to the full episode: https://lnkd.in/dkT-R_gX   #CustomerSuccess #AIinCS #CSM #CustomerSuccessManagement #MasteringCS

No two customers arrive at onboarding the same way. The process has to meet them where they are. On Mastering CS – Candid Leader Insights, Erik Törnblom, Customer Success Manager at PLAYipp, shared how his team handles one of the most common challenges in CS. PLAYipp has a standard three session onboarding that covers both the technical and communication sides of a product that does both. But the balance shifts depending on who is in the room. A technically strong customer needs more focus on content and communication. A customer with strong communication skills needs more time on the technical administration side. Same process. Different emphasis. Every time. And for larger or more complex implementations, onboarding can stretch into months. The structure adapts to the scale, not the other way around.

Most teams send customer feedback to Sales. The best teams send it to Marketing first. On Mastering CS – Candid Leader Insights, Dominik Nenicka explains how Customer Success shapes the entire GTM motion. CS sits closest to reality: New fraud patterns. New regulations. New customer problems. And that insight changes everything. Three rules for a working feedback loop: → Send insights CS → Marketing first, not Sales → Build messaging around problems you already solve → Continuously refine your ICP based on real signals Because when the loop breaks, misalignment compounds fast. And when it works, your entire GTM stays grounded in reality.

One enterprise customer on paper can be ten different companies in reality. And that changes everything about how CS works. On Mastering CS – Candid Leader Insights, Alex Frunza, Head of Customer Success, Enablement and Support at Otera, broke down why the old way of measuring CS capacity breaks down at the enterprise level. The traditional metrics made sense once: → ARR or budget managed per CSM → Number of accounts in a portfolio → Users spread across a defined customer base But in enterprise CS, the ground shifts constantly. One account can sit still for three months. Then five new legal entities under the same umbrella show interest overnight. Suddenly you need to ramp up across all of them — capturing use cases, mapping stakeholders, and building momentum as fast as possible. That is not a capacity problem you can solve with a headcount formula. It requires a completely different way of thinking about how CS resources are structured and deployed. Because in enterprise, you are rarely managing accounts. You are managing ecosystems — with different timelines, different stakeholders, and different definitions of value at every level. The CSMs who thrive here are not the ones who manage the most accounts. They are the ones who know how to move fast when the moment demands it.

🎙️ New episode of Mastering CS: Candid Leader Insights is live! This week, Irina Cismas sat down with Christina Cato, Customer Success Director at Kontakt.io, a real-time location platform for hospitals. Christina spent years inside the hospital system as an analyst and quality program manager before moving to the vendor side, and that experience shapes everything about how she thinks about adoption, ROI, and what customers actually need. In this episode, Christina talks about: → Why adoption in healthcare is not a login but a workflow, and what it takes to get clinical staff to reach for the tool every single day → Why the CFO writes the check but the clinical staff are the loudest voice in the room when renewal comes around → How to start the ROI conversation before the contract is even signed and what to measure against at every QBR One thing that stuck with us: you can sit and read charts all day, but it's different when you sit next to the person closest to the work and understand what's really going on. Start by listening. 🎧 Listen here: https://lnkd.in/eA2-c9ee #CustomerSuccess #MasteringCS #HealthcareIT #SaaS #CSLeadership #Podcast

A private equity acquisition. A boss leaving. A new team you did not hire. A department to build from scratch. On Mastering CS – Candid Leader Insights, Lee-El Lewinsohn Primo, Senior Manager Service Solutions at Akamai Technologies, shared the mindset that has carried her through every curveball. Change is not the exception in a CS career. It is the constant. Startups pivot. Companies get acquired. Books of business get reshuffled. Things happen in your personal life that nobody planned for. The question Lee-El comes back to every time is the same. How do I make the best of this? What can I learn? What can I contribute? How can we achieve more from here? And she adds one more that most people are afraid to ask out loud. What is in it for me? Because a growth mindset is not just about the company. It is about knowing what you are building for yourself too.

🎙️ New episode of Mastering CS: Candid Leader Insights is live! This week, Irina Cismas sat down with Kristin Maguire, Senior Customer Success Manager at Rocketlane, a platform for running customer onboarding and implementation projects. Kristin spent most of her career on the implementation side before moving into strategic CS, and she had one of the most grounded takes on AI in CS we've heard. In this episode, Kristin talks about: → Why AI is not an add-on to customer success and what happens when teams treat it like one → How she handles the build versus buy conversation at renewal using the Lego analogy → How RocketLane's MCP connection with Claude changed how she onboards herself to a new product → Why scraping conversations for churn risk signals is the AI use case that actually scales a CSM's attention → Why measuring AI token consumption is an incomplete and potentially misleading adoption metric 🎧 Listen here: https://lnkd.in/dB8rJ7iS #CustomerSuccess #MasteringCS #AIinCS #SaaS #CSLeadership #Podcast

A low health score does not always mean what it looks like. On Mastering CS – Candid Leader Insights, Oksana Aloshyna, Strategic Customer Success Manager at ShortPoint, shared how she actually uses health scores in practice. The number is the starting point. Not the conclusion. A champion on extended leave. A team in the middle of an internal restructure. A product temporarily deprioritized because of a company wide initiative. None of that shows up in the health score. But all of it changes what the right response actually is. The context that fills the gap comes from people. Support teams, sales colleagues, anyone who has had a recent touchpoint with the account. Health scores tell you where you are. Relationships tell you what it means.

Most Customer Success playbooks assume customers behave in a straight line. Onboard them. Get them to adopt. Watch for risk. Renew them. Expand them. Real customers are much less cooperative. A customer can have great product usage and a disengaged champion. They can have low overall usage while one department is rapidly expanding. They can finish onboarding but never adopt the feature that creates the most value. They can look healthy 90 days before renewal and start slipping 30 days later. Yet many CS processes still work like this: Wait for the CSM to notice. Wait for the next account review. Wait for the next scheduled call. Then decide what to do. For a CSM managing 20 accounts, maybe that works. For a team managing hundreds or thousands, it starts to break. We see this problem a lot when talking to CS teams. Customer information sits across the CRM, product analytics, support tools, email and spreadsheets. The signals exist. The problem is turning them into action at the right moment. That’s the job of customer journey orchestration. You map the customer journey and then connect important signals to what should happen next. → Onboarding stalls → create the right follow-up → Usage suddenly drops → alert the CSM → A customer reaches an adoption milestone → move them forward → A low-touch customer becomes inactive → start an automated engagement → Usage suggests expansion potential → put it in front of the CSM → Renewal approaches with warning signals → escalate the account Some actions happen automatically. Others need a person. That distinction is important. The goal isn't to automate Customer Success. It's to stop asking CSMs to manually watch every account for every possible signal. A good orchestration setup should tell them: This changed. This matters. Here is what happens next. And when the situation needs context, judgment or an actual conversation, the CSM takes over. That is a much better use of a CSM’s time than checking five systems before every customer call to figure out what changed. We wrote a practical guide to Customer Journey Orchestration, from mapping the journey to setting triggers and deciding what to automate: https://lnkd.in/da9ZA62K #CustomerSuccess #CustomerJourney #CSM #CJO